xfs
[Top] [All Lists]

Re: /dev/sound

To: Alan Eldridge <alane@xxxxxxxxxxxx>
Subject: Re: /dev/sound
From: "Nathan J. Mehl" <memory@xxxxxxxxx>
Date: Mon, 25 Jun 2001 01:51:17 -0400
Cc: Dusan <dusan@xxxxxxxxx>, linux-xfs@xxxxxxxxxxx
In-reply-to: <20010625003153.A4433@xxxxxxxxxxxxxxxxxxxxx>; from alane@xxxxxxxxxxxx on Mon, Jun 25, 2001 at 12:31:53AM -0400
References: <Pine.LNX.4.21.0106242053080.7937-100000@xxxxxxxxxxxxxx> <20010625003153.A4433@xxxxxxxxxxxxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
User-agent: Mutt/1.2.5i
In the immortal words of Alan Eldridge (alane@xxxxxxxxxxxx):
> WARNING. HEAV:Y SARCASM AHEAD. It's late, and these are things that bit me
> and generally annoyed the crap out of me when I ws getting 7.1 up and
> running. These things are *not* the fault of the SGI dudes! It's the kernel
> interface from hell... yes, it's (shield your kid's eyes, folks, you don't
> want them to see this) DEVFS.

Eh.  Devfs itself is fine.  Coming from a solaris background, it's
nice to see one of the free unices catch up and join the mid-90s.  Of
course, it would be even nicer if devfs' namespace in some way
corresponded to the bios' view of the system bus (a la OpenBoot), but
we can't really hold Richard Gooch responsible for lousy design
decisions made by IBM ~15 years ago...

It's the transition issues that are currently biting everyone right
now.  Devfsd is a step in the right direction, but it could be a lot
better, both in implementation and documentation.  (Well, and
"/dev-state" is an atrocity...)

I suspect that a lot of the pain will Go Away once (well, if) one of
the "big three" distributions (redhat/suse/debian) take the leap and
enable it for their next release.  What devfs/devfsd need more than
anything else now is a solid run through an organized QA cycle.  In
that respect I'm grateful to SGI for sneaking it into the XFS 1.0
release -- the archives of this list will provide good starting
material for whoever wants to make their distribution work with it.
(Hint hint, redhat lurkers. :)

> vvv and add these (only use cdrom1 if you got it)
> 
> # ...and /dev/cdrom
> # In case no cdrom modules loaded, point link over to /dev/cdroms/cdrom?
> LOOKUP          cdrom           EXECUTE /bin/ln -sf cdroms/cdrom0 cdrom
> LOOKUP          cdrom1          EXECUTE /bin/ln -sf cdroms/cdrom1 cdrom1
> # Similarly, if the module loaded, create the /dev/cdrom link
> REGISTER        cdroms/cdrom0   EXECUTE /bin/ln -sf cdroms/cdrom0 cdrom
> REGISTER        cdroms/cdrom1   EXECUTE /bin/ln -sf cdroms/cdrom1 cdrom1

Addendum: if one of your cdrom devices is a CD-R[W] that you're
managing under the ide-scsi module in order to use with xcdroast,
you'll probably want to add the following as well:

LOOKUP          scd0            EXECUTE /bin/ln -sf cdroms/cdrom0 scd0

-n

------------------------------------------------------------<memory@xxxxxxxxx>
no plans / I'll go where the machine goes / the past is a placebo / dissolving
in a drain / I'll sleep beside the railroad tracks / with no more rent
or income tax / I got no fixed address now / I'm waiting for a train.
                                             (--Firewater, "So Long Superman")
<http://blank.org/memory/>----------------------------------------------------

<Prev in Thread] Current Thread [Next in Thread>