On Thu, 28 Jul 2005, dpk wrote:
> truss indicates that fdisk may be getting the error from somewhere else:
>
> stat("/dev/da0",0xbfbfeb30) = 0 (0x0)
> open("/dev/da0",0x2,00) ERR#1 'Operation not
> permitted'
> open("/dev/da0",0x0,027757765630) = 6 (0x6)
> open("/dev/da0s1",0x2,01001210100) ERR#1 'Operation not
> permitted'
> open("/dev/da0s2",0x2,01001210100) ERR#2 'No such file or
> directory'
> open("/dev/da0s3",0x2,01001210100) ERR#2 'No such file or
> directory'
> open("/dev/da0s4",0x2,01001210100) ERR#2 'No such file or
> directory'
>
> Because it is using devfs, I'm not able to create these missing slices in
> /dev. Most unfortunately, it appears it uses devfs in single user mode as
> well, so I can't test the theory.
Under a chrooted shell, I created the s1-4 /dev entries. fdisk -u now
reports 'Device not configured', which supports the theory that fdisk is
just using whatever error it last sees and gives up.
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
