head	2.8;
access;
symbols
	fourth_edition:2.8;
locks
	grog:2.8; strict;
comment	@# @;


2.8
date	2003.01.19.07.56.38;	author grog;	state Exp;
branches;
next	2.7;

2.7
date	2003.01.18.02.11.52;	author grog;	state Exp;
branches;
next	2.6;

2.6
date	2002.12.12.06.00.21;	author grog;	state Exp;
branches;
next	2.5;

2.5
date	2002.10.21.09.09.06;	author grog;	state Exp;
branches;
next	2.4;

2.4
date	2002.09.14.07.07.06;	author grog;	state Exp;
branches;
next	2.3;

2.3
date	2002.06.19.01.35.51;	author grog;	state Exp;
branches;
next	2.2;

2.2
date	2002.06.12.22.52.28;	author grog;	state Exp;
branches;
next	2.1;

2.1
date	97.12.07.08.34.53;	author grog;	state Exp;
branches;
next	1.5;

1.5
date	97.11.01.09.58.57;	author grog;	state Exp;
branches;
next	1.4;

1.4
date	97.11.01.08.20.53;	author grog;	state Exp;
branches;
next	1.3;

1.3
date	97.10.28.06.54.31;	author grog;	state Exp;
branches;
next	1.2;

1.2
date	97.08.31.04.43.18;	author grog;	state Exp;
branches;
next	1.1;

1.1
date	96.01.10.16.54.11;	author grog;	state Exp;
branches;
next	;


desc
@Open problems
@


2.8
log
@Checkpoint 19 January.
@
text
@How to set up HP inkjets

Check diskless section in starting.mm again.

- Get table numbers with chapter
- building: introduction to first table
  	    space out the device entry descriptions

- X: how to swap keys

- overview of the releases

Man pages:

! - title width
! - Fx macro
! - csh ^ and friends

Check that chapter refs are still correct

Section on moving file systems.

Check the contents of the CD-ROMs.

On Wednesday, 12 June 2002 at  2:02:09 -0700, Annelise Anderson wrote:
> How then does the system know where the root partition is,

Normally it'll look in the a compatibility partition of the drive from
which you booted, but you can override it in /boot/loader.conf.  I
don't know if this is needed here, but I'll put it in my "to think
about" list.

> and what needs to be done in addition to the dump | restore?  (I
> have actually done this, having two almost identical systems in one
> machine on separate drives, each bootable, maintained in fairly
> close alignment with rsync, so I could boot either one (and fix the
> other if necessary)...Certainly /etc/fstab could not just be "copied
> over," but there was also some other stuff I dealt with.

There shouldn't be much else.

> In this regard it's also fairly common for people to want to take a
> disk from one computer and stick it in another, and they often have
> trouble with the disk getting read, being seen as the wrong disk,
> etc.  Especially with the IDE drives, where the CDROM is located
> seems to affect the BIOS/FreeBSD understand of whether a disk is ad1
> or ad2 or whatever. (Other chapters may deal with some of these
> difficulties.)

I don't understand the problem.  You mean the device naming?  I did
mention that in a SCSI context earlier on in this chapter, but in fact
IDE is simpler, since the numbers don't change.  I talk about the
device names in a different chapter.

--------------------------------------------------

> That's probably not going to do it for you. Put the following in
> /boot/loader.conf.local (create if needed) and reboot:
>
> hw.ata.ata_dma="1"
> hw.ata.atapi_dma="1"

FBSDU:  Page 617

Go through review drafts of before October.

Check IP addresses and domains (no LEMIS).
@


2.7
log
@Checkpoint 18 January.
@
text
@d1 2
@


2.6
log
@Checkin 22 December
@
text
@d1 2
@


2.5
log
@Checkpoint 27 October 2002
@
text
@d61 3
@


2.4
log
@Checkpoint 13 October 2002
@
text
@d57 4
a60 1
> hw.ata.atapi_dma="1"@


2.3
log
@Checkpoint 10 September.
@
text
@d19 2
@


2.2
log
@Odds and ends.
@
text
@d49 7
@


2.1
log
@Base second edition
@
text
@d16 33
@


1.5
log
@Checkin 3 November 1997
@
text
@@


1.4
log
@*** empty log message ***
@
text
@d15 1
a15 1
Check that chapter refs are still correct@


1.3
log
@28 Oct
@
text
@d14 2
@


1.2
log
@Things to do
@
text
@d8 6
@


1.1
log
@Initial revision
@
text
@d6 2
@
