[ On Wednesday, July 26, Gerhard Sittig wrote: ]
>
> Which turns out to be a little hard sometimes (been there with
> the 4.0 CD set this week) when the fixit media doesn't have slice
> entries in /dev and you don't have access to the (yet to be
> mounted!) filesystem with the appropriate /dev entries. Funnily
> ad0s1 happily gets mounted when it regularly should be ad0s1a,
> later I found that the minor numbers are the same for them. But
> the fixit prompts never would let me access slices other than *a.
> And it took quite some time to find the minors' numbering (I
> finally found it when reading disklabel(5) for completely other
> reasons). Once this is known you can mknod(8) whatever you need
> at the fixit prompt.
That brings up a topic that I'd started in this group about 2 weeks ago when I
had a similar "difficult" experience using the "fixit" procedure after booting
from CD. I ended up getting the CD's MAKEDEV to work after I un-hard-coded
/sbin/mknod ... much more difficult than it should be me thinks.
I intend on working on the problem and contributing a chapter to the
handbook on "using the fixit disk" but didn't want to push things as we were
going through the release cycle. I want Jordan to get some needed sleep before
I spam him and the rest of the list with what-if questions regarding the fixit
floppy, etc. (for instance, MAKEDEV has a special "fixit" ``target'' with
comments saying "gotta reduce devices to save precious inodes" ... so the
natural inclination of making "sh MAKEDEV all|fixit" create the slice entries
seems like that won't work).
More in a few days after 4.1-R excitement dies down a bit.
-Jr
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| John Reynolds WCCG, CCE, Higher Levels of Abstraction |
| Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 602-868-6512 |
| [EMAIL PROTECTED] http://www-aec.ch.intel.com/~jreynold/ |
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
