|Mike Smith||Mar 9, 1998 12:52 am|
|Bruce Evans||Mar 9, 1998 2:19 am|
|Gary Schrock||Mar 9, 1998 11:16 am|
|Bruce M. Walter||Mar 9, 1998 1:58 pm|
|Mike Smith||Mar 9, 1998 2:10 pm|
|Bruce Evans||Mar 9, 1998 6:01 pm|
|Mike Smith||Mar 9, 1998 6:55 pm|
|Bruce Evans||Mar 9, 1998 7:42 pm|
|Joao Carlos Mendes Luis||Mar 9, 1998 8:37 pm|
|Bruce Evans||Mar 9, 1998 9:17 pm|
|Luoqi Chen||Mar 10, 1998 12:27 am|
|Bruce Evans||Mar 10, 1998 2:00 am|
|Mike Smith||Mar 11, 1998 3:24 am|
|Gary Schrock||Mar 11, 1998 9:47 am|
|David E. O'Brien||Mar 13, 1998 6:50 pm|
|Bruce Evans||Mar 13, 1998 8:36 pm|
|David E. Tweten||Mar 13, 1998 9:16 pm|
|Mike Smith||Mar 13, 1998 10:40 pm|
|David E. O'Brien||Mar 13, 1998 10:55 pm|
|Mike Smith||Mar 13, 1998 11:10 pm|
|Bruce Evans||Mar 13, 1998 11:15 pm|
|Dmitrij Tejblum||Mar 14, 1998 8:23 am|
|Dmitrij Tejblum||Mar 14, 1998 8:24 am|
|Dmitrij Tejblum||Mar 14, 1998 8:25 am|
|Dmitrij Tejblum||Mar 14, 1998 9:59 am|
|Bruce Evans||Mar 14, 1998 7:08 pm|
|Dmitrij Tejblum||Mar 15, 1998 2:00 am|
|Subject:||Re: *HEADS UP* Correction to previous postings.|
|From:||Mike Smith (mi...@smith.net.au)|
|Date:||Mar 9, 1998 2:10:03 pm|
Please note that in the recent postings regarding the changes to the fashion in which the root filesystem is located and mounted there has been a fundamental factual error on my part.
This error *will* cause users with dedicated disks serious problems, unless they adopt the same procedure require by non-dedicated disk users.
The error in this case was the assumption that partitions on a dedicated disk were handled as though they were truly equivalent to the compatability slice entries.
A correct assumption.
This doesn't appear to be borne out in any consistent fashion.
This is not correct; rather they appear as though they were in the first slice on the disk.
Not with normal slice naming. The first slice (s1) doesn't exist on dangerously dedicated disks. Rev.1.88 of autoconf.c just breaks support for dangerously dedicated disks. Rev.1.87 was correct in this areas, except it spells COMPATIBILITY_SLICE as 0.
That's odd then; libdisk calls them 'xdNs1', and you appear to be able to mount them like that.
More significantly, the bootstrap passes the invalid slice number 1 in; using this is guaranteed to result in failure, as there aren't any devices with a '1' in the slice field.
I believed that I had, actually, tested on a dedicated-disk system, however it appears otherwise. 8(
disks are not as easy to create as they used to be. Mine have an all-zero DOS partition table. The update procedure for dangerously-dedicated disks is to back out rev.1.88 of autoconf.c.
I thought that I had established this correctly twice now, based on code study and our earlier discussions. Can I please confirm, so that this isn't screwed for good?
- If the slice number from the bootstrap is in the range BASE_SLICE to MAX_SLICES, it is OK to insert this as-is into the root device minor number.
- If the slice number is < BASE_SLICE, the correct minor for the root device will have a 0 in the slice field.
ie. I should be using COMPATABILITY_SLICE not BASE_SLICE in the test in setroot()?
To Unsubscribe: send mail to majo...@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message