public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Frank Peters <frank.peters@comcast.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: Alsa Problem With Kernel 2.6.37
Date: Sat, 8 Jan 2011 18:11:27 -0500	[thread overview]
Message-ID: <20110108181127.014f30f0.frank.peters@comcast.net> (raw)
In-Reply-To: <AANLkTimkLSxJK7GcxmHw2hQY5kv6T4ancKFLc8uD=Fim@mail.gmail.com>

On Sat, 8 Jan 2011 22:20:28 +0100
Martin Herrman <martin@herrman.nl> wrote:

> works perfect here.

Thanks for the report -- even though, to me, it's bad news.

> 
> Curious: why aren't you using udev?
> 

I've been using Linux since 1998 and I like most the opportunity
for control that Linux allows.  To suit my minimalist needs, I have
customized my system to a great extent.  For example, I have completely
eliminated the complex and cumbersome initialization scripts that
are found in /etc/init.d, /etc/conf.d, and other locations.  In their
place I wrote my own very simple initialization script that automatically
boots into console (no login).  From there I can go to X (my usual action)
or just use the console for configuration, troubleshooting, or other tasks.

(I probably should not admit this.  If any Gentoo maintainers hear about
it they would flatly refuse to help if any problems arise.  But I think
that I understand the system well enough to take this approach safely.)

I have also eliminated udev as part of this simplification.  I know what's
on my machine and what has to be done to enable it.  I would rather not
have actions performed "automagically" for me whenever I plug in a USB
printer of storage device.  Part of the reason is philosophical and part
is just a desire to understand the OS better.

Linux allows many possibilities for customization and, IMO, that is half
the fun of using it.  Most distributions, including Gentoo, adhere to the
standard methods.  But if one has the inclination for exploration then
there is much that can be done to go well beyond the standard methods.

Frank Peters



  reply	other threads:[~2011-01-09  0:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-08 16:28 [gentoo-amd64] Alsa Problem With Kernel 2.6.37 Frank Peters
2011-01-08 17:20 ` [gentoo-amd64] " Nikos Chantziaras
2011-01-08 18:22   ` Res: " Axial Astaroth
2011-01-08 18:10 ` Duncan
2011-01-08 19:41   ` Frank Peters
2011-01-08 21:20     ` Martin Herrman
2011-01-08 23:11       ` Frank Peters [this message]
2011-01-09  6:06         ` Duncan
2011-01-09 12:03         ` Rich Freeman
2011-01-09  1:08 ` [gentoo-amd64] Alsa Problem With Kernel 2.6.37[Solved] Frank Peters
2011-01-22 12:00   ` Zhu Sha Zang
2011-01-22 15:24     ` Frank Peters
2011-01-22 18:13       ` Zhu Sha Zang

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=20110108181127.014f30f0.frank.peters@comcast.net \
    --to=frank.peters@comcast.net \
    --cc=gentoo-amd64@lists.gentoo.org \
    /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