Derek Ragona wrote:
If you read the early adopters doc at:
http://www.freebsd.org/releases/5.1R/early-adopter.html
You will se it clearly says:
"MAKEDEV is no longer available, nor is it required. FreeBSD 5.X uses a
device filesystem, which automatically creates device nodes on demand. For
mor
ystem,
besides which FreeBSD 4.8 or 4.9 are not for sale at CompUSA as a consolation.
I did ask to know what documentation there is for the new behavior, but I have
not heard any replies. If there isn't any documentation, that's an answer too.
-ecsd
Poul-Henning Kamp writes:
In message &l
Harti Brandt wrote:
On Wed, 8 Oct 2003, ecsd wrote:
e>I had already been able to go so far as to "disklabel -w -r ad3 auto".
e>After doing this on a 4.X system I would then "disklabel -e /dev/ad3s1c"
e>but /dev/ad3s1c does not exist, so I am stuck.
e>Maybe there is
ork to do:
*** Working on device /dev/ad3 ***
[...]
Information from DOS bootblock is:
1: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 63, size 39102273 (19092 Meg), flag 80 (active)
beg: cyl 0/ head 1/ sector 1;
end: cyl 1023/ head 15/ sector 63
2:
3:
4:
Harti Brandt wr
Here are the contents of my /dev. As you can see, there are no entries
for the
partitions of ad3. My 5.0 system has no "bsdlabel" command. Can anyone
tell me how I can coax the ad3s1* entries into existence?
./ ad2s1c dspW0.1 pci
stdin@ ttypg
..
Poul-Henning Kamp writes:
In message <[EMAIL PROTECTED]>, ecsd writes:
with MAKEDEV gone, the mystery is how to use devfs.
In /dev I have ad3, but I cannot "disklabel -e /dev/ad3s1d",
nor can I "disklabel -e /dev/ad3", and I can't determine
what minor device number
with MAKEDEV gone, the mystery is how to use devfs.
In /dev I have ad3, but I cannot "disklabel -e /dev/ad3s1d",
nor can I "disklabel -e /dev/ad3", and I can't determine
what minor device numbers to assign for mknod to create
the partition entries.
So how does one use devfs to do what MAKEDEV used
