Jonas Smedegaard a écrit :
> If you dislike the confusion of the many choices (and us package
maintainers disagreeing of what's best), then use the same as gets installed by
default using a recent
debian-installer. On IBM-compatible x86 systems that means the bootloader "grub", the ramdisk-ge
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Jun 04, 2008 at 02:22:47PM +0200, [EMAIL PROTECTED] wrote:
> Jonas Smedegaard a écrit :
>>
>> Those tools are different approaches indeed. How do you find them
>> contradictory? Please elaborate - I sincerely want to understand
>> better.
>
Jonas Smedegaard a écrit :
Those tools are different approaches indeed. How do you find them
contradictory? Please elaborate - I sincerely want to understand
better.
Sorry for being confusing. Saying contradictory I wasn't talking about the tools themselves, but about the comments #43,
#48
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Jun 04, 2008 at 10:05:01AM +0200, [EMAIL PROTECTED] wrote:
> I've found a work around :now I never reboot any distant machine,
> There are so many bugs indicating boot problems for so much different
> reasons (394608,334831,327335,422217,4622
I've found a work around :now I never reboot any distant machine,
I never follow the stressing instructions provided :
You are attempting to install a kernel version that is the same as the version
you are currently running (version
> 2.6.18-4-686).
The modules list is quite likely to have be
On Mon, Apr 07, 2008 at 10:08:47AM +0200, [EMAIL PROTECTED] wrote:
> Hello,
>
> As there is a new upgrade on package linux-image-2.6
> I'm wondering if I can apply this upgrade without risk of hanging one more
> time my production server ?
you never provided any error message, so your bug repor
Hello,
As there is a new upgrade on package linux-image-2.6
I'm wondering if I can apply this upgrade without risk of hanging one more
time my production server ?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Feb 19, 2008 at 03:43:40PM +0100, maximilian attems wrote:
>On Tue, 19 Feb 2008, Jonas Smedegaard wrote:
>
>> On Tue, Feb 19, 2008 at 11:49:21AM +0100, maximilian attems wrote:
>> >yaird breaks on every upgrade and has several troubles.
>>
>>
On Tue, 19 Feb 2008, Jonas Smedegaard wrote:
> On Tue, Feb 19, 2008 at 11:49:21AM +0100, maximilian attems wrote:
> >yaird breaks on every upgrade and has several troubles.
>
> Wrong.
proven by experience and bug reports.
> But feel free to play russian roulette with Max. He maintains
> initr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Feb 19, 2008 at 11:49:21AM +0100, maximilian attems wrote:
>On Tue, Feb 19, 2008 at 11:03:33AM +0100, Jonas Smedegaard wrote:
>> On Tue, Feb 19, 2008 at 09:08:53AM +0100, [EMAIL PROTECTED] wrote:
>> > Is there a way to test or check the boot pr
On Tue, Feb 19, 2008 at 11:03:33AM +0100, Jonas Smedegaard wrote:
> On Tue, Feb 19, 2008 at 09:08:53AM +0100, [EMAIL PROTECTED] wrote:
> > Hello
> > Is there a way to test or check the boot process without actually booting ?
> > Because rebooting a remotely hosted server without any garanty that it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Feb 19, 2008 at 09:08:53AM +0100, [EMAIL PROTECTED] wrote:
> Hello
> Is there a way to test or check the boot process without actually booting ?
> Because rebooting a remotely hosted server without any garanty that it
> will be able to start,
Hello
Is there a way to test or check the boot process without actually booting ?
Because rebooting a remotely hosted server without any garanty that it will be able to start, is a bit like russian
roulet... one time it reboots one time it doesn't and if it doesn't nothing else can be done except
Hello,
I think I've found a clue about this bug :
the man page of kernel-img.conf says :
do_symlinks
By default, the kernel image post installation script shall create or
update the /vmlinuz and /vmlinuz.old symbolic links. This is true if
a /vmlinuz link already exists, however, in absence of /
Hello,
this morning, I had exactly the same problem while installing
linux-image-2.6.22-3-686 (2.6.22-6.lenny1 Debian-Security:None/testing)
The box didn't reboot.
The last time it happened, this is how our distant hostmaster managed to
correcte the problem :
>The technician had to boot the se
can you reproduce the bug with linux-image-2.6.18-5-686 ?
also this sounds more like an lilo failure?
--
maks
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Here's the whole session from login to reboot, hoping this will help
sorry, but messages are in french
---
[EMAIL PROTECTED]:~$ ns1
Password:
channel 1: open failed: administratively prohibited: open failed
Last login: T
Package: linux-image-2.6.18-4-686
Version: linux-image-2.6.18-4-686 2.6.18.dfsg.1-12etch2
Severity: critical
Justification: breaks the whole system
This morning, as usual I did :
apt-get update
apt-get upgrade
today, there was a security update on linux-image-2.6.18-4-686
I followed the given ins
18 matches
Mail list logo
