Your message dated Thu, 30 Apr 2009 11:52:26 -0500
with message-id <[email protected]>
and subject line Re: Bug#526333: kernel-package: A default script for --initrd
in /etc/kernel/postinst.d would be nice
has caused the Debian Bug report #526333,
regarding kernel-package: A default script for --initrd in
/etc/kernel/postinst.d would be nice
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
526333: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=526333
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: kernel-package
Version: 12.009
Severity: wishlist
I suggest to put the script "initramfs-tools", ( which resides under
/usr/share/doc/kernel-package/examples/ ) per default in /etc/kernel/... .
(Maybe other scripts too)
I think cp'ing that script to /etc/kernel is what most users would do anyway,
after wondering why "make-kpkg --initrd" isn't working any more like expected,
reading the docs (or at first bugreports ;) ), and then doing some guesswork
which example script they would need to copy and which not.
I think the actual state is OK, since it's stated in the NEWS-file what's new
an what has to be done, but i think it would be better to have a working
default, because that would make things easier for a lot of people. One would
not loose anything (everyone could still delete/replace/edit the defaults in
/etc/kernel/), but one would regain the behaviour that it works out of the
box for standard cases.
--- End Message ---
--- Begin Message ---
On Thu, Apr 30 2009, [email protected] wrote:
> I suggest to put the script "initramfs-tools", ( which resides under
> /usr/share/doc/kernel-package/examples/ ) per default in /etc/kernel/... .
> (Maybe other scripts too)
This is not so simple. If every single kernel image package puts
in that script i that location, they will all have to conflict. So,
only one kernel image possible on the machine -- which is unacceptable.
Now each image can create a random file name -- but that
clutters up the directory, and a user wanting to change the behaviour
will have to make changes for every kernel image -- which is a
nightmare.
> I think cp'ing that script to /etc/kernel is what most users would do
> anyway, after wondering why "make-kpkg --initrd" isn't working any
> more like expected, reading the docs (or at first bugreports ;) ), and
> then doing some guesswork which example script they would need to copy
> and which not.
I think users might want to use yaird too. Hmm. I'll add yaird
scripts in there for the next release, so people have a choice.
> I think the actual state is OK, since it's stated in the NEWS-file
> what's new an what has to be done, but i think it would be better to
> have a working default, because that would make things easier for a
> lot of people. One would not loose anything (everyone could still
> delete/replace/edit the defaults in /etc/kernel/), but one would
> regain the behaviour that it works out of the box for standard cases.
The standard case, for people using make-kpkg, would be to not
use initrds. Why slow down the bootup? All you need is a ext3 /boot,
and compile in ext3, and boom. Fast boots with no initrd needed.
manoj
who no longer uses modules or initrd
--
I've had a perfectly wonderful evening. But this wasn't it. Groucho
Marx
Manoj Srivastava <[email protected]> <http://www.golden-gryphon.com/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
--- End Message ---
