Re: New ad*s* devices not automatically appearing in devfs
[EMAIL PROTECTED] wrote: In message <[EMAIL PROTECTED]>, Darren Pilgrim writes: [EMAIL PROTECTED] wrote: In message <[EMAIL PROTECTED]>, Darren Pilgrim writes: When I add a new slice or partition to a disk, the device files don't automatically appear in /dev. If I reboot, it shows up, but having to reboot twice just to add a filesystem to a running disk is absurd. How do I make /dev automatically add these devices upon creation? Failing that, how do I force the system to notice the new device(s) and add them to /dev? Which exact commands do you use to create them ? I used sysinstall, Configure->Fdisk to (in order) delete s3, create a 5120m s2, then Write the changes to disk. After exiting sysinstall: But the changes do appear after you reboot ? Yes, after rebooting a /dev/ad4s2 is present. I can then issue `disklabel -w ad4s2 auto` to intialize the slice with an appropriate empty label. I can use `disklabel -e ad4s2` or sysinstall to create the partitions. Sysinstall will complain about the lack of partition devices but write the label out anyway. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New ad*s* devices not automatically appearing in devfs
In message <[EMAIL PROTECTED]>, Darren Pilgrim writes: >[EMAIL PROTECTED] wrote: >> In message <[EMAIL PROTECTED]>, Darren Pilgrim writes: >> >>>When I add a new slice or partition to a disk, the device files don't >>>automatically appear in /dev. If I reboot, it shows up, but having to >>>reboot twice just to add a filesystem to a running disk is absurd. How >>>do I make /dev automatically add these devices upon creation? Failing >>>that, how do I force the system to notice the new device(s) and add them >>>to /dev? >> >> >> Which exact commands do you use to create them ? > >I used sysinstall, Configure->Fdisk to (in order) delete s3, create a >5120m s2, then Write the changes to disk. After exiting sysinstall: But the changes do appear after you reboot ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New ad*s* devices not automatically appearing in devfs
[EMAIL PROTECTED] wrote: In message <[EMAIL PROTECTED]>, Darren Pilgrim writes: When I add a new slice or partition to a disk, the device files don't automatically appear in /dev. If I reboot, it shows up, but having to reboot twice just to add a filesystem to a running disk is absurd. How do I make /dev automatically add these devices upon creation? Failing that, how do I force the system to notice the new device(s) and add them to /dev? Which exact commands do you use to create them ? I used sysinstall, Configure->Fdisk to (in order) delete s3, create a 5120m s2, then Write the changes to disk. After exiting sysinstall: # fdisk ad4 *** Working on device /dev/ad4 *** parameters extracted from in-core disklabel are: cylinders=39714 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=39714 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 10485153 (5119 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 15/ sector 63 The data for partition 2 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 10485216, size 10485216 (5119 Meg), flag 80 (active) beg: cyl 1023/ head 255/ sector 63; end: cyl 1023/ head 15/ sector 63 The data for partition 3 is: The data for partition 4 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 30967776, size 9063936 (4425 Meg), flag 80 (active) beg: cyl 1023/ head 255/ sector 63; end: cyl 1023/ head 15/ sector 63 # disklabel ad2s2 disklabel: /dev/ad2s2: No such file or directory # disklabel -r ad2s2 disklabel: /dev/ad2s2: No such file or directory # disklabel -w ad4s2 auto disklabel: /dev/ad4s2: No such file or directory Going back into sysinstall, the fdisk screen shows the old slice table, and the label screen shows s1, s3, and s4, but no s2. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New ad*s* devices not automatically appearing in devfs
In message <[EMAIL PROTECTED]>, Darren Pilgrim writes: >When I add a new slice or partition to a disk, the device files don't >automatically appear in /dev. If I reboot, it shows up, but having to >reboot twice just to add a filesystem to a running disk is absurd. How >do I make /dev automatically add these devices upon creation? Failing >that, how do I force the system to notice the new device(s) and add them >to /dev? Which exact commands do you use to create them ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
New ad*s* devices not automatically appearing in devfs
When I add a new slice or partition to a disk, the device files don't automatically appear in /dev. If I reboot, it shows up, but having to reboot twice just to add a filesystem to a running disk is absurd. How do I make /dev automatically add these devices upon creation? Failing that, how do I force the system to notice the new device(s) and add them to /dev? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
