From: Oleg Verych <olecom@flower.upol.cz>
To: linux-kernel@vger.kernel.org
Cc: 7eggert@gmx.de, Dirk <noisyb@gmx.net>, linux-kernel@vger.kernel.org
Subject: Re: PATCH/FIX for drivers/cdrom/cdrom.c
Date: Sat, 19 Aug 2006 19:52:25 +0200 [thread overview]
Message-ID: <44E74FD9.7000507@flower.upol.cz> (raw)
In-Reply-To: <20060817143633.GF13641@csclub.uwaterloo.ca>
Lennart Sorensen wrote:
>
> Hmm, so how does one tell hal to go to hell and leave the cdrom device
> alone at all times (other than totally disabling hal).
AFAIK many drivers allow multiple opening of device files. If programs do not
honor any kind of locking (advisory, O_EXCL) use mandatory locking (DOS 2.0
compatibility, no problems ;)
> Who the heck wants all that stupid auto crap anyhow. :)
>
Yea. But see RH managers on its videos, happy about usb sticks being plugged
and worked, he-he:
<http://www.redhat.com/v/magazine/mov/005_BehindScenes_RHEL4.mov>.
I've just installed debian-gnu and got all that
cpufrequtils, powermgmt, acpiutils installed on amd64 laptop
while i just need:
,-
|modprobe powernow-k8
|modprobe cpufreq_ondemand
|echo ondemand >scailing_governor
`-
Anyway long, almost 10 years, way to win95 and win98 is never ending ;D
--
-o--=O`C /. .\ (???) (+) /o o\
#oo'L O o | o.
<___=E M ^-- | (you're barking up the wrong tree) =--'
next prev parent reply other threads:[~2006-08-19 16:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6Kxns-7AV-13@gated-at.bofh.it>
[not found] ` <6Kytd-1g2-31@gated-at.bofh.it>
[not found] ` <6KyCQ-1w7-25@gated-at.bofh.it>
2006-08-17 12:27 ` PATCH/FIX for drivers/cdrom/cdrom.c Bodo Eggert
2006-08-17 12:35 ` Arjan van de Ven
2006-08-18 12:31 ` Bodo Eggert
2006-08-18 12:53 ` Arjan van de Ven
2006-08-18 16:45 ` Alan Cox
2006-08-17 13:39 ` Alan Cox
2006-08-17 13:23 ` Lennart Sorensen
2006-08-17 13:41 ` Jeff Garzik
2006-08-17 13:54 ` Lennart Sorensen
2006-08-17 14:38 ` Helge Hafting
2006-08-18 12:39 ` Bodo Eggert
2006-08-17 13:48 ` Alan Cox
2006-08-17 14:36 ` Lennart Sorensen
2006-08-17 14:38 ` Arjan van de Ven
2006-08-17 15:09 ` Alan Cox
2006-08-19 17:52 ` Oleg Verych [this message]
2006-08-21 17:31 ` Lennart Sorensen
2006-08-16 17:26 Dirk
2006-08-16 17:40 ` Jan Engelhardt
2006-08-16 18:37 ` Dirk
2006-08-16 18:37 ` Lennart Sorensen
2006-08-16 18:44 ` Arjan van de Ven
2006-08-16 19:30 ` Dirk
2006-08-16 19:08 ` Alan Cox
2006-08-16 22:25 ` Andrew Morton
2006-08-17 7:50 ` Jan Engelhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44E74FD9.7000507@flower.upol.cz \
--to=olecom@flower.upol.cz \
--cc=7eggert@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=noisyb@gmx.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox