Re: New ad*s* devices not automatically appearing in devfs

[Darren Pilgrim]

[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