Emmanuel Blindauer <[EMAIL PROTECTED]> writes:

> > > I could not use my dvd drive until I turned dma use on, so in a
> > > way it is necessary to boot my system.
> >
> > no since:
> > - dma drive access is not generally needed to boot a system
> > - having dma off usually does not prevent to access a dvd drive

> Watching dvd *need* to have dma turned on a many system, because low
> performance without it.

it's not *needed* for proper system bootstrapping, thus we must not
force everey user to have it installed

to watch dvds, you may prefer having an x server and a good video
card, but you don't need them, you can go with libaa for rendering.

recommendation != absolute requires

> but, as mandrake disable dma on cdrom and dvd(comments said it
> causes problem?), when users want to reactivate it with hdparm, they
> won't find it.

if hdparm is not installed, then we don't do anything regarding cdrom

> Activating dma at boot is good but it doesn't work every time.
> after several mdk install, I've found that on some system, disk
> performances are bad, because dma wasn't activated by kernel (why?),
> so having hdparm -d1 in /etc/rc.sysinit doing the stuff needed is
> good -> we need hdparm.

no, it just show that *some* people need it but not everybody.
thus, hdparm should not go in basesystem.

if we follow such logic, then let force people have ipv6 tools[1],
dhcp server[1], bind server[1], kernel-smp[1], openoffice[1], ...

we can force servers to have mplayer installed, after all some users
need it to watch dvds, ...

such logic is bloated.


[1] after all, some people need it


Reply via email to