On Fri, 31 Dec 1999, Wilko Bulte wrote:
> As for ample warning: I've seen MAKEDEVs display a list of the devices
> they are creating. I think the Tru64 version does this. I myself think this
> is a good behaviour (and hope people won't start yelling 'bloat' for once)
I like this idea a *lot*.
-
On Fri, Dec 31, 1999 at 01:45:31AM -0500, a little birdie told me
that Brian Fundakowski Feldman remarked
> The way certain devices, like cd with its monotonically increasing counter
> where devices are probed in order and assigned device based on precedence
> and not hardwiring/controller connect
On Fri, Dec 31, 1999 at 03:15:02PM -0500, Chuck Robey wrote:
> On Fri, 31 Dec 1999, Wilko Bulte wrote:
>
> > > > Why are "certain" devices wildly different than all other ones? I've
> > > > never encountered that kind of syntax before, and I can't see that it's
> > > > documented anywhere at all
Everything that sysinstall does WRT devs is abstracted by libdisk.
> On Fri, Dec 31, 1999 at 03:15:02PM -0500, Chuck Robey wrote:
> > On Fri, 31 Dec 1999, Wilko Bulte wrote:
> >
> > > > > Why are "certain" devices wildly different than all other ones? I've
> > > > > never encountered that kind
On Fri, 31 Dec 1999, Jeroen C. van Gelderen wrote:
> What about having
> ./MAKEDEV cd0 cd1 cd4 -da2 da6-da9
> create cd0, cd1, cd4, da1, da2, da6, da7, da8, da9 ? This would be
It's not the unix way. What's wrong with using standard utilities?
sh MAKEDEV cd0 cd1 cd4 $(jot -w da 2) $(jot -w
"Jeroen C. van Gelderen" wrote:
> Bruce Evans wrote:
> >
> > On Fri, 31 Dec 1999, Chuck Robey wrote:
> >
> > > Why are "certain" devices wildly different than all other ones? I've
> >
> > Because the CAM update broke (SCSI) cd devices in rev.1.171 of MAKEDEV.
> > mcd and scd were in the same c
Bruce Evans wrote:
>
> On Fri, 31 Dec 1999, Chuck Robey wrote:
>
> > Why are "certain" devices wildly different than all other ones? I've
>
> Because the CAM update broke (SCSI) cd devices in rev.1.171 of MAKEDEV.
> mcd and scd were in the same case statement so they were broken too. The
> br
On Fri, 31 Dec 1999, Wilko Bulte wrote:
> > > Why are "certain" devices wildly different than all other ones? I've
> > > never encountered that kind of syntax before, and I can't see that it's
> > > documented anywhere at all. Certainly, MAKEDEV itself (in it's
> > > comments) treats cd* just l
On Fri, Dec 31, 1999 at 09:25:42AM -0500, Brian Fundakowski Feldman wrote:
> On Fri, 31 Dec 1999, Chuck Robey wrote:
>
> > On Fri, 31 Dec 1999, Brian Fundakowski Feldman wrote:
> >
> > > The way certain devices, like cd with its monotonically increasing counter
> > > where devices are probed in
On Fri, 31 Dec 1999, Chuck Robey wrote:
> Why are "certain" devices wildly different than all other ones? I've
Because the CAM update broke (SCSI) cd devices in rev.1.171 of MAKEDEV.
mcd and scd were in the same case statement so they were broken too. The
breakage has spread to acd and ccd (al
On Fri, 31 Dec 1999, Chuck Robey wrote:
> On Fri, 31 Dec 1999, Brian Fundakowski Feldman wrote:
>
> > The way certain devices, like cd with its monotonically increasing counter
> > where devices are probed in order and assigned device based on precedence
> > and not hardwiring/controller connect
On Fri, 31 Dec 1999, Chuck Robey wrote:
> On Fri, 31 Dec 1999, Brian Fundakowski Feldman wrote:
>
> > The way certain devices, like cd with its monotonically increasing counter
> > where devices are probed in order and assigned device based on precedence
> > and not hardwiring/controller connect
From: Chuck Robey <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, December 31, 1999 6:29 AM
Subject: multiple cd devices
> Anyhow, getting the kernel to recognize cd1 was no problem, but getting
> /dev/MAKEDEV to do that was a hairy PITA. I couldn't locate, in
On Fri, 31 Dec 1999, Brian Fundakowski Feldman wrote:
> The way certain devices, like cd with its monotonically increasing counter
> where devices are probed in order and assigned device based on precedence
> and not hardwiring/controller connection, work is consistent between
> the kernel and MA
The way certain devices, like cd with its monotonically increasing counter
where devices are probed in order and assigned device based on precedence
and not hardwiring/controller connection, work is consistent between
the kernel and MAKEDEV. If you have 2 cd devices, you have cd0 and cd1,
so MAKE
I've been doing a lot of neatening up here, and one of the tasks was to
get both of the cdrom drives I have (one per machine) moved over so that
they are on the same machine. This was so I can use the one that's a
writer in conjuntion with a reader, and do duplication.
Anyhow, getting the kernel
16 matches
Mail list logo
