, I don't. dpt_i2o is working just fine for me.
All's well that ends well!
Regards,
--
.''`. Stephen Powell
: :' :
`. `'`
`-
On Mon, May 23, 2016, at 22:16, Ben Hutchings wrote:
> On Mon, 2016-05-23 at 21:06 -0400, Stephen Powell wrote:
>>
>> The following message is received at boot time when booting the stock Debian
>> kernel
>> version 4.5.3-2 on the s390x architecture:
>>
>&g
-
tainting kernel
The kernel does boot; but the kernel gets tainted, which disables lock
debugging.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
;
> Ben.
>
Interesting. I wasn't aware of that. Thank you for calling my attention
to it. Under the circumstances, wishlist is fine.
Regards,
--
.''`. Stephen Powell
: :' :
`. `'`
`-
other error checking corner cases.
Respectfully submitted,
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--- a/functions 2016-01-21 18:33:59.0 -0500
+++ b/functions 2016-03-24 08:09:11.0 -0400
@@ -128,14 +128,28 @@
# lilo compatibility
parse
Forwarding to the Debian bug log
- Forwarded Message -
From: Luis Henriques
To: linux-ker...@vger.kernel.org, sta...@vger.kernel.org,
kernel-t...@lists.ubuntu.com
Cc: Sebastian Ott , Martin Schwidefsky
, Stephen Powell , Luis Henriques
Sent: Fri, 04 Sep 2015 09:08:33 -0400 (EDT
Forwarding the below message to the relevant Debian Bug Log
- Forwarded Message -
From: Luis Henriques
To: Sebastian Ott
Cc: Martin Schwidefsky , Stephen Powell
, Luis Henriques ,
kernel-t...@lists.ubuntu.com
Sent: Thu, 03 Sep 2015 06:38:07 -0400 (EDT)
Subject: [3.16.y-ckt stable
On Thu, 27 Aug 2015 18:06:49 -0400 (EDT), Ben Hutchings wrote:
>
> On Wed, 2015-08-26 at 21:33 -0400, Stephen Powell wrote:
>>
>> The Linux kernel in jessie fails to build from source for
>> the combination ARCH=s390, CONFIG_SMP=n, and CONFIG_DYNAMIC_DEBUG=y.
>> Co
=a313bdc5310dd807655d3ca3eb2219cd65dfe45a
--
.''`. Stephen Powell
: :' :
`. `'`
`-
id=0b991f5cdcd6201e5401f83ca3a672343c3bfc49
I have personally tested the fixes, and they work for me on my z890.
Respectfully submitted,
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with
Control: tags -1 patch
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/119
them seem to have
a colon in them. I suggest the following code to replace the above:
case "${modalias}" in
""|*:*)
:
;;
*)
force_load "${modalias}"
;;
esa
case you're interested.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.o
; then
in the parse_numeric function. Problem solved. And yes, I realize that using
disk labels or uuids is the recommended way to specify the root file system
these
days. But that's another story, as I mentioned earlier.
Respectfully yours,
--
.''`. Stephen Powell
f. With the patch, it should be able to handle any valid
kernel composite device number.
Respectfully submitted,
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscri
ant to, with
any boot loader.
Let me know what you think.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
the next higher multiple of 8. Is this correct?
I have no idea. What I do know is that the current algorithm doesn't work for
me, but the above does. For now. Will it continue to work in the future?
I don't know.
--
.''`. Stephen Powell
: :' :
`. `'
have tested, and it fixes the problem. Here's a link to the
official upstream git commit at kernel.org:
https://git.kernel.org/cgit/linux/kernel/git/s390/linux.git/commit/?h=features&id=e512d56c799517f33b301d81e9a5e0ebf30c2d1e
--
.''`. Stephen Powell
: :&#x
n
> that has happened.
The patch is now official.
Here is a link to the official git commit at kernel.org:
https://git.kernel.org/cgit/linux/kernel/git/s390/linux.git/commit/?h=features&id=26d766c60f4ea08cd14f0f3435a6db3d6cc2ae96
--
.''`. Stephen Powell
: :' :
`. `&#
submitted to kernel.org soon, if it hasn't been already.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
nder
"Kernel Hacking".) Then I issued
make KDEB_PKGVERSION=3.14.4-1 KBUILD_PKG_ROOTCMD=fakeroot \
INSTALL_MOD_STRIP=1 KBUILD_DEBARCH=s390x deb-pkg
as a non-root user. It built a kernel image package just the way I wanted it.
--
.''`. Stephen Powell
: :' :
file is renamed to the expected naming convention (*_s390x.deb).
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.
#CP VINPUT VMSG 1
as opposed to letting a timeout occur and letting the default kernel
boot via a timeout. I don't know why that matters, but that has been
my experience.
I will be more than happy to assist in debugging this.
--
.''`. Stephen Powell
: :'
On Sat, 01 Feb 2014 14:54:32 -0500 (EST), Stephen Powell wrote:
>
> I may have found the problem. This problem may be related to Debian bug
> number 736892.
As it turned out, Debian bug number 736892 was an unrelated problem.
My real problem was faulty memory (RAM). Ben, I know
n all systems with
non-ECC memory
from now on. Thanks for the tip!
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas
On Fri, 07 Feb 2014 05:49:55 -0500 (EST), Ben Hutchings wrote:
> Stephen Powell wrote:
>> [38587.355263] BUG: unable to handle kernel paging request at
>> 081c
>
> Looks like a bit flip to me (0 turned to 0x800 and then treated
> as a real pointer). D
716703 ]---
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/2027073877.834564.1391741777992.javamail.r...@md01.wow.synacor.com
vives long enough for
me to login as root and issue these two commands before it crashes.
But once I get that far, I haven't had any problems since. I now
think 736892 really is a bug, and that it is the cause of the kernel
crashes I have been experiencing.
--
.''`. Stephe
to be the common denominator. I don't
even know where to start. I may as well turn my computer off until
I can find a stable kernel. If there's anything I can do to help,
please let me know.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUB
On Sun, 24 Nov 2013 23:25:41 -0500 (EST), Ben Hutchings wrote:
>
> On Sun, 2013-11-24 at 20:29 -0500, Stephen Powell wrote:
>>
>> The real-time preemption patches for kernel 3.11 do not appear to be present
>> in linux-source-3.11. What happened to them?
>
> The
The real-time preemption patches for kernel 3.11 do not appear to be present
in linux-source-3.11. What happened to them?
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of &q
ill. If you want
to enhance the code to correctly handle the full 16-hex-digit composite
device number, go ahead. As you say, it's trivial. And that would
once again make you the author of the final patch, which is fine.
--
.''`. Stephen Powell
: :' :
`. `'`
tools assumes also. If those assumptions
ever become a problem, lilo will probably specify the root file system
in a different way rather than continuing to use a hexadecimal number.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to de
re using the "root" kernel boot
parameter in a non-standard way, in which case you are on your own.
There is a legitimate bug in the parse_numeric function which has
been discovered as the result of your bug report, and it appears to
me that this proposed patch fixes that problem. But adding su
hat you have not encountered. Have you tried the patch? (You will of
course need to rebuild the initial RAM file system after applying the
patch.)
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debia
wowway.com/~zlinuxman/parse_numeric.patch
I have used a link to it, rather than include the patch inline, since
my e-mail client has the nasty habit of expanding tabs, inserting unwanted
line breaks, etc.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIB
an the complete string is numeric
or is
the null string.) But these are not regular expressions, these are shell
patterns.
As a shell pattern, [0-9]* means "a single numeric digit at the beginning of the
string followed by zero or more arbitrary characters". Your patch solves t
risk. But if you do try it, please report
your results.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.or
ccur if the user
specifies a block special file name or a symbolic link to a block special
file name.
For more information, see my LILO web page:
http://users.wowway.com/~zlinuxman/lilo.htm
I hope this helps.
--
.''`. Stephen Powell
: :' :
`. `'`
tabs,
inserting unwanted line breaks, etc. Therefore, to preserve the patch
unaltered, I provided a link instead.
I have tested the patch on my system, and it works fine. The patch is
applied to /usr/share/initramfs-tools/hook-functions.
--
.''`. Step
,sg
usbcore 108302 3 ehci_hcd,uhci_hcd
usb_common 12338 1 usbcore
Obviously not all of these need to be in the initial RAM file system.
When using MODULES=most, everything works fine.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
-
n,
I may stop recommending it.
Any further communication regarding this issue should be posted to debian-user,
since the kernel team does not support kernel-package.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/1733626537.566900.1330134799559.javamail.r...@md01.wow.synacor.com
author or the Debian
package maintainer for kernel-package (i.e. Manoj). It seems to
work for me and for my purposes, but I do not warrant the patch
to be free from defects. Take this with as many grains of salt
as you think it's worth.
P.S. kernel-package is also incompatible with make 3.8
On Wed, 20 Jul 2011 09:25:37 -0400 (EDT), Ben Hutchings wrote:
> On Wed, 2011-07-20 at 07:39 -0400 (EDT), Stephen Powell wrote:
>> On Wed, 20 Jul 2011 04:52:59 -0400 (EDT), Ben Hutchings wrote:
>>>
>>> Hook scripts will just perpetuate the use of the undocument
, but it's just one of a long
> list of tasks.
I didn't start this thread as criticism. As a matter of fact, I am
amazed at the prolific productivity of the kernel team. I don't know
how you find time to do all that you do. But I didn't want to wait
until the last minute to
alternatives that I haven't thought of. What are your
thoughts?
P.S. For this initial post I have CC-ed debian-boot and debian-devel, as
there may be interested parties on that list that are not subscribed
to debian-kernel, but it is my intention that the discussion take place
on debian-ke
l fix:
http://users.wowway.com/~zlinuxman/kernel/interlace.diff
I used kernel 2.6.38 as my code base.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe".
far all my changes have been to generic KMS code and are not
nouveau-specific.
I'd rather wait to publish my fixes until I have everything working
correctly. The trouble is I haven't had much time to work on it lately.
--
.''`. Stephen Powell
: :' :
`. `'
On Sun, 24 Apr 2011 19:52:47 -0400 (EDT), Greg KH wrote:
> On Sat, Apr 23, 2011 at 09:10:19AM -0400, Stephen Powell wrote:
>> On Fri, 22 Apr 2011 23:09:50 -0400 (EDT), Jonathan Nieder wrote:
>>>
>>> If you run "git log dd30ac3 --grep='dasd: correct device t
; Date: Thu Feb 17 13:13:55 2011 +0100
>
> [S390] dasd: correct device table
>
> The 3880 storage control unit supports a 3380 device
> type, but not a 3390 device type.
>
> Reported-by: Stephen Powell
> Signed-off-by: Stefan Haberland
> Signed
I ask sta...@kernel.org to port the whole commit?
(It may have dependencies on previous commits and get complicated rather
quickly.) Or do I ask them to cherry pick that one-line change in
drivers/s390/block/dasd_eckd.c? I could use some advice here.
--
.''`. Stephen Powell
On Tue, 19 Apr 2011 02:34:01 -0400 (EDT), Heiko Carstens wrote:
> Stephen Powell wrote:
>> I installed linux-image-2.6.38-2-s390x version 2.6.38-3 on my up-to-date
>> Wheezy
>> system today. It runs in a virtual machine under z/VM 5.4.0 running in an
>> LPAR
>>
hours now,
which is definitely a good sign. Without this patch, I've not been able
to keep a 2.6.38 s390x kernel up for more than a few hours. Unfortunately,
since I can't reproduce the problem on demand, I cannot say with 100%
certainty that the problem is fixed, but it looks good and
On Thu, 14 Apr 2011 21:48:56 -0400 (EDT), Stephen Powell wrote:
>
> The problem appears to be fixed in the latest vanilla upstream kernel
> source, which at the time of this writing is 2.6.39-rc3.
> ...
Oops! I spoke too soon. I checked the server before I went to bed
last night
handled. I will run the upstream
vanilla kernel source until a Debian package containing the fix is
available. Thanks, Jonathan.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of &q
nion bug
number 620126 in package sysconfig-hardware for the same bug in another
package.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Conta
CPGIR450W CP entered; disabled wait PSW 00020001 8000 0001DE26
I have backed out to a 2.6.32 kernel until the problem is resolved. The 2.6.38
kernel is obviously unusable for me.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email
bug report can be found at
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607416
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Cont
On Sat, 18 Dec 2010 19:59:00 -0500 (EST), Stephen Powell wrote:
>
> This is a bug report for drivers/s390/block/dasd_eckd.c in the
> Linux kernel source code. The device table indicates that a
> combination of a 3880 storage control unit and a 3390 DASD device
> type is valid. Th
with no apparent ill effects.
However, you might want to look things over to see if anything
needs to be changed in the code logic as well.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.o
ually made it into a future stable point release.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.or
lation.
The kernel command line sees
... root=UUID=055d446a-977d-4aa6-877d-62c716f5e85a ...
which gets you around the problem for now.
Respectfully submitted,
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@
hat says
... root=806 ...
(the leading zero is suppressed). Chances are, the user is not directly
specifying the root device as a hexadecimal number anywhere. The boot
loader makes this substitution. lilo has done this forever, and zipl
was patterned after lilo.
--
.''
team! Thanks! I can go back to running
stock kernel images again instead of custom builds with custom patches.
And thanks to upstream too! Peter, Moritz, Ben, thank you all.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ
this link
http://packages.debian.org/search?keywords=lilo&searchon=names&suite=unstable§ion=all
and saw that the current version was still 1:22.8-8.1. Either the package
hasn't been uploaded yet or the web page is not in sync with the repository.
--
.''`. Stephen Powel
;#!/bin/bash" and change your
symlink /bin/sh to point back to dash, or whatever it used to be
pointing to. But maybe this is not why you are having installation
problems.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kern
as I know, no decision has yet been made. (See bug number 587886.)
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debia
package hook scripts without changing the package hook scripts when
the package hook scripts are buggy or incomplete. (But of course I
open a bug report against the package too.)
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kerne
te scripts do. I got that logic originally from
a template script in kernel-package
> It seems from my system at least grub2 will need fixing.
I wasn't aware that grub2 used -- or needed -- any hook scripts.
grub1, yes; but not grub2.
--
.''`. Stephen Powell
: :'
open until
an official Debian kernel with this fix included has been uploaded
to the Debian archive.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? C
or FBA DASD. My concern is that it will break for CKD DASD. Are you
sure that this is correct? Did you test the fix for CKD DASD as well
as FBA DASD?
Respectfully submitted.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kern
Peter. I'm really busy right now, but I'll try to test this
sometime in the next few weeks.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe".
rcumvention, you may be able
to work around this problem by listing the extra modules you need in
/etc/initramfs-tools/modules. I was able to circumvent a similar problem by
doing this. (See bug report 588452.)
--
.''`. Stephen Powell
: :' :
`. `'`
`-
. Exit status
is zero, even if the file does not exist. The "exit 0" is unnecessary.
Good catch, Mika!
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "uns
rnel/drivers/s390/block/dasd_eckd_mod.ko
In other words, it list only the module itself plus hard dependencies.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsu
cannot be brought online. Therefore, the permanent
root file system cannot be mounted.
I am able to circumvent the problem by explicitly listing dasd_diag_mod
in /etc/initramfs-tools/modules, but this should not be necessary.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
On Tue, 06 Jul 2010 09:38:53 -0400 (EDT), Ben Hutchings wrote:
> On Tue, 2010-07-06 at 09:18 -0400, Stephen Powell wrote:
>> ...
>> Perhaps more importantly, why do these architectures use the vmlinux
>> naming convention
>
> Hysterical raisins.
I take that to mea
ok
script is only interested in an update (to match the current behavior of
update-initramfs).
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/609145822.187199.1278422298504.javamail.r...@md01.wow.synacor.com
On Fri, 02 Jul 2010 02:20:45 -0400 (EDT), maximilian attems wrote:
> On Wed, 30 Jun 2010, Stephen Powell wrote:
>>
>> As promised, here are my proposed changes to the initramfs-tools hook
>> scripts.
>
> thank you very much. applied your 3 changes to branch maks/hooks
On Fri, 02 Jul 2010 02:20:45 -0400 (EDT), maximilian attems wrote:
> On Wed, 30 Jun 2010, Stephen Powell wrote:
>> Max,
>>
>> As promised, here are my proposed changes to the initramfs-tools hook
>> scripts.
>> ...
>
> thank you very much. applied your 3
On Wed, 30 Jun 2010 09:29:42 -0400 (EDT), Stephen Powell wrote:
>
> Since symlinks are not associated with any package in particular,
> and since they seem to have been designed for the convenience of
> historic boot loaders such as lilo and zipl, perhaps the best way
> to handle
On Wed, 30 Jun 2010 10:54:53 -0400 (EDT), Jonas Smedegaard wrote:
> On Wed, Jun 30, 2010 at 10:31:32AM -0400, Stephen Powell wrote:
>> dpkg does not prevent multiple boot loaders from being installed
>> concurrently; but this environment is not supported by the various
>> syst
On Wed, 30 Jun 2010 10:00:10 -0400 (EDT), Jonas Smedegaard wrote:
> On Wed, Jun 30, 2010 at 09:29:42AM -0400, Stephen Powell wrote:
>> ...
>> Since symlinks are not associated with any package in particular,
>> and since they seem to have been designed for the convenienc
On Tue, 29 Jun 2010 16:35:40 -0400 (EDT), maximilian attems wrote:
> On Tue, Jun 29, 2010 at 04:24:48PM -0400, Stephen Powell wrote:
>>
>> Sorry I didn't think of this the first time, but there are up to
>> four steps to preparing a kernel for booting:
>>
>>
creates an initial RAM file system for kernel image packages
created by make-kpkg, even if the user doesn't want one.
There is a way to check to see if one is needed. I can
submit a revised version of the script if you like. Would
you like me to do so?
--
.''`. Stephen Powell
hey
so desire. I have now subscribed to debian-kernel myself;
so there is no need to CC me.
> On Mon, 2010-06-28 at 11:16 -0400, Stephen Powell wrote:
>> On Sun, 27 Jun 2010 22:02:35 -0400 (EDT), Ben Hutchings wrote:
>>> [...]
>>> The environment variable DEB_MAINT_PARA
ernel image.
> On Mon, Jun 28, 2010 at 11:16:58AM -0400, Stephen Powell wrote:
>> Currently, hook scripts invoked by a stock kernel maintainer script
>> or a maintainer script from a kernel image package created by make-kpkg
>> pass these exact same arguments.
>
> no.
>Fr
if
you're going to drop support for it in Squeeze, then yes,
a warning message is necessary. Both the kernel maintainer scripts
*and* "update-initramfs -u" *must* issue a warning message if they
find "do_bootloader = yes" specified in /etc/kernel
oked from a kernel hook script.
>
> We're still left with the question of how to transition from the current
> mess.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a sub
On Sat, 26 Jun 2010 20:45:58 -0400 (EDT), Ben Hutchings wrote:
> On Sat, 2010-06-26 at 20:35 -0400, Stephen Powell wrote:
>>
>> Sounds reasonable to me. This is for Squeeze+1, right?
>
> No, we need something like this for squeeze.
On Fri, 18 Jun 2010 17:51:11 +0200, Ma
t; distinguish creation, update and deletion. However, I suspect that
> these scripts will need to invoke the same command in all cases.
Sounds reasonable to me. This is for Squeeze+1, right?
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To
ebian web site.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/765636083.229248.1277306459777.javamail.r...@md01.wow.synacor.com
On Fri, 18 Jun 2010 22:55:38 -0400 (EDT), Ben Hutchings wrote:
>
> Stephen Powell recently reminded the kernel team that LILO is not
> automatically updated on installation of a new kernel version in lenny.
> In fact there is a general problem that there are several different ways
>
n using a custom kernel.
If you have any further questions about this lilo problem, please post
to this bug log (585856).
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsu
On Fri, 18 Jun 2010 11:51:11 -0400 (EDT), maximilian attems wrote:
> On Fri, Jun 18, 2010 at 10:55:35AM -0400, Stephen Powell wrote:
>> As for "update-initramfs -u", it *will* invoke lilo if lilo is installed
>> and "do_bootloader = yes" is specified in /etc
On Fri, 18 Jun 2010 04:25:38 -0400 (EDT), Joachim Wiedorn wrote:
> Ben Hutchings wrote on 2010-06-18 02:02:
>> On Thu, 2010-06-17 at 20:37 -0400, Stephen Powell wrote:
>>> And how would one go about setting this "loader" variable?
>>> The "loader"
rical' bootloader
> setting should be restored in an update to lenny.
Great! What about Squeeze? It still supports creating the initial RAM
file system and updating symlinks via variables in /etc/kernel-img.conf.
Doesn't it make sense to allow the historical boot loader code to work
On Thu, 17 Jun 2010 18:11:04 -0400 (EDT), Ben Hutchings wrote:
> On Thu, Jun 17, 2010 at 12:33:58PM -0400, Stephen Powell wrote:
>> [...]
>> I can maybe accept your proposal for Squeeze. But for Lenny, I believe
>> that the maintainer scripts should be changed back they
On Tue, 15 Jun 2010 23:25:45 -0400 (EDT), Ben Hutchings wrote:
> On Tue, 2010-06-08 at 09:43 -0400, Stephen Powell wrote:
>>
>>do_bootloader = yes
>>
>> in /etc/kernel-img.conf means "run the historic boot loader for this
>> platform".
>> Fo
On Tue, 08 Jun 2010 07:39:58 -0400 (EDT), Vincent Danjean wrote:
> On 07/06/2010 17:37, Stephen Powell wrote:
>> But for a kernel install or reconfigure, it is the responsibility of the
>> kernel maintainer scripts to invoke the bootloader. See also, for example,
>> linu
1 - 100 of 146 matches
Mail list logo
