> I agree (patches accepted), although it is hard to figure out just
> exactly what is needed to "run one's system".
>
> Maybe a "remake" entry in MAKEDEV which remakes all current entries
> if possible.
cd /dev/; sh MAKEDEV *
perhaps? It is going to be one hell of a ride on your disk,
In message <[EMAIL PROTECTED]> Frank Mayhar writes:
: Personally, I think this is a needed enhancement for MAKEDEV. IMHO, it
: violates the POLA that a "MAKEDEV all" doesn't make _all_ the necessary
: devices to run one's system.
That's one of the reasons that there is a strong desire to have
de
On Tue, Nov 30, 1999 at 12:27:53PM -0500, Thomas Stromberg wrote:
> I thought all I needed to do was "./MAKEDEV all" in /dev after a
> mergemaster (I also tried MAKEDEV drive) However, I guess this is not
> the case. Evidentally if I makedev a drive or all, it does not MAKEDEV
> the slices. I coul
Thomas Stromberg wrote:
> I thought all I needed to do was "./MAKEDEV all" in /dev after a
> mergemaster (I also tried MAKEDEV drive) However, I guess this is not
> the case. Evidentally if I makedev a drive or all, it does not MAKEDEV
> the slices. I could of sworn it was supposed to.. alas! Lear
In message <[EMAIL PROTECTED]>, Frank Mayhar writes:
>Thomas Stromberg wrote:
>> I thought all I needed to do was "./MAKEDEV all" in /dev after a
>> mergemaster (I also tried MAKEDEV drive) However, I guess this is not
>> the case. Evidentally if I makedev a drive or all, it does not MAKEDEV
>> th
"Andrey A. Chernov" wrote:
>
> On Tue, Nov 30, 1999 at 10:49:57AM -0500, Thomas Stromberg wrote:
> > [root@karma] dumpon> dumpon /dev/wd0s1b
> > dumpon: /dev/wd0s1b: must specify a block device
> > [root@karma] dumpon> dumpon /dev/rwd0s1b
> > [root@karma] dumpon>
> >
> > Bug or Feature?
>
> This
