Re: Goals for 1.3?
marekm@i17linuxb.ists.pwr.wroc.pl (Marek Michalkiewicz) wrote on 21.12.96 in <[🔎] m0vbHDM-0007urC@i17linuxb.ists.pwr.wroc.pl>:
> Christian Schwarz:
> > - Boot disks should contain drivers for more systems/cards (???)
>
> ... but drivers that don't probe reliably shouldn't do it by default,
> unless explicitly enabled at the boot prompt. cm206 locks up solid,
> NE2000 cards are mis-identified as sonycd535 CD-ROMs, etc.
NE2000s are a (famous) general problem. Last week, I had a problem with a
Compaq Setup hosing the machine on autoprobe - no OS involved (well,
Compaq Setup uses DOS on a Setup partition - but the "OS" doesn't do the
probing).
I guess in this case, the right solution is to search for NE2000 _first_ -
and/or to document the problem clearly and tell people how to work around
it.
> > * No bug reports older than 12 months at release time
>
> Some bugs need to be fixed upstream - I don't think we should close
> them just to satisfy the above requirement... (and then re-open them
> right after the release :-)
Isn't that what the "forwarded" bug state is for?
> > * Move config information from install scripts to "cfgtool" (???)
>
> Hmm, I feel a little nervous about putting thigs like
>
> SULOGIN=`cfgtool --get boot.sulogin`
>
> at the very beginning of /etc/init.d/boot. Why not just:
Why?
> created using MAKEDEV only if necessary. Also, maybe we should
> tell the device list maintainers about that great concept:
> directories... (example: /dev/vcs63 -> /dev/vcs/63)
Whenever this comes up, some people see problems with this approach.
Usually it's some programs that know where to find devices (by parsing
/dev, that is). I expect ttyname() is an example of this; so are programs
handling ptys. There are probably more.
MfG Kai
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com
Reply to: