| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
#607411.
|
|
|
|
closes: #521286.
|
|
#520690.
|
|
While parsing the command line options, we check to see if the number of
options is sane. On most architectures, this is either three or four
options; except of course, powerpc has to be all different, and passes in
a fifth argument, because it is "special". We now ignore the fifth
argument, and do not flag is as an error, which it would be for any arch
apart from powerpc
Signed-Off-By: Manoj Srivastava <srivasta@debian.org>
|
|
The check to see if we need to handle symbolic links in boot in
installkernel, meant to check whether the current link points to a
different file than the one being installed, works fine provided that we
are indeed not reinstalling the same kernel version. Otherwise, the
inequality test will fail and we'll fall back to the else clause of the
if statement, leading to plain file creation again.
Nested the if statements.
Signed-Off-By: Manoj Srivastava <srivasta@debian.org>
|
|
Calling mkboot is far from existing practice in modern Debian
installations, and in almost all cases calling it would be the wrong
thing to do. This patch updates the documentation, and also cleans up
the installkernel script by removing the obsolete, commented out call
to mkboot.
Signed-Off-By: Manoj Srivastava <srivasta@debian.org>
|
|
Debian installations, which now default to grub, and not LILO, and
also tend to run initial RAM fs creators, and other post processing
steps, before hooking in their boot manager update scripts.
mkboot has not been the default way to setup a newly installed kernel
in about a decade or so.
installkernel also unconditionally created symbolic links in
$DESTDIR (nominally /boot). The symlinks created were:
$DESTDIR/{config,System.map,vmlinu[xz]}
These symlinks are not useful if you use grub, or use official kernel
images. Creating these links make it less useful when used to create
kernel image packages. (running mkboot is even worse when building a
kernel image package).
Ideally, the symbolic links should be updated if they exist, but
should not be created when they do not, which is what this patch does.
Next, the modern Debian installation has kernel images run scripts
which have been dropped into /etc/kernel/{pre,post}{inst,rm}.d/
directories, or put into /etc/kernel-img.conf -- and installkernel
does not do anything like this. When installkernel is called (by
running make install in a kernel source directory), the modules might
not yet have been installed, so running the scripts would be wrong
(intramfs, for instance, depends on the modules being around)
Signed-off-by: Manoj Srivastava <srivasta@debian.org>
|
|
|
|
(automatically generated log message)
git-archimport-id: schizo@debian.org--etch/debianutils--etch--0--base-0
|
