too much bloat

[Andrey Vul]

On Jan 12, 2008 8:40 PM, Corey Burger <corey.burger at gmail.com> wrote:
> On Jan 12, 2008 5:34 PM, Andrey Vul <andrey.vul at gmail.com> wrote:
> > On Jan 12, 2008 7:32 PM, Corey Burger <corey.burger at gmail.com> wrote:
> > >
> > > On Jan 12, 2008 4:25 PM, Andrey Vul <andrey.vul at gmail.com> wrote:
> > > > The base install has a lot of bloat, such as UUID's in fstab and
> > > > unneeded crap in alsa rules and /etc/modules.d/ and is too automated
> > > > for my liking.
> > > > Which is more poweruser-friendly, debian, fedora, or other?
> > > > I pretty much want a binary distro that gives you almost as much
> > > > choice as gentoo *and supports jfs*, yet just works? My candidates so
> > > > far are debian-unstable and fedora-(7 or 8, whichever has jfs support)
> > > > (haven't tested either yet)?
> > >
> > > Umm, bloat?
> > >
> > > No, UUIDs are required to make certain you are actually mounting the
> > > right partion. Any modern 2.6.2x is going to require them. Alsa is
> > > automated to make your life easy.
> > /dev/hd* Just Works in gentoo.
>
> It might, but UUIDs mean that it will always work. Here is the spec
> that made the change:
> https://wiki.ubuntu.com/LibAtaForAtaDisks
What about LABELs rather than UUIDs? Alll of my devices and partitions
have unique names, such as 'ubuntu', 'boot', 'gentoo', 'swap',
'windows', 'ADATA_2GB', etc.

>
> >
> > For alsa, why not query the sound card type within a script to get the
> > sound card type (like lspci parsing) and use it to create the driver
> > load portion of a custom alsa file without boilerplate driver loading?
>
> If there is a bug in how soundcard loading is done and you think you
> know a better way, go talk to the alsa people. I rather suspect that
> the current soundcard stuff is done because scripts like that fail
> more often than they work.
Unfortunately, by hand works better than script :(


-- 
Andrey Vul