On Sat Jul 26 23:43 +0400, Andrey Borzenkov wrote:
> if you also make it run lilo/grub when updating existing kernel - even better.
> Currently when I recompile kernel and reinstall it I have to run lilo
> manually ("lilo entry already exists"). Not a big deal for normal users
> probably.
AFAIK
>> IMHO, this can only be considered in if /sbin/installkernel (or whatever
>> replaces it) ensures that on the first kernel update, an entry for the
>> original kernel is retained. Otherwise, automatic kernel update plus
>> unintentional reboot (ie power failure) = unhappy user/administrator (
On Sat, 26 Jul 2003, Buchan Milne wrote:
> IMHO, this can only be considered in if /sbin/installkernel (or whatever
> replaces it) ensures that on the first kernel update, an entry for the
> original kernel is retained. Otherwise, automatic kernel update plus
> unintentional reboot (ie power fa
Le sam 26/07/2003 à 17:45, [EMAIL PROTECTED] a écrit :
> For 9.1 I noticed that many people are still running 0.13mdk, not because
> they do not want to update but because they do not know that there is an
> update (it didn't show up in mdkupdate). Is there any good reason to keep
> this behavio
On Sat, 26 Jul 2003 [EMAIL PROTECTED] wrote:
> For 9.1 I noticed that many people are still running 0.13mdk, not because
> they do not want to update but because they do not know that there is an
> update (it didn't show up in mdkupdate). Is there any good reason to keep
> this behaviour for 9.
For 9.1 I noticed that many people are still running 0.13mdk, not because
they do not want to update but because they do not know that there is an
update (it didn't show up in mdkupdate). Is there any good reason to keep
this behaviour for 9.2? A kernel update requires a reboot I know, and not
Are the current cooker kernels Win4Lin-enabled or will Win4Lin-enabled
kernels be available only with the boxed sets with commercial apps?
Thanks,
Hoyt
Peter Ruskin <[EMAIL PROTECTED]> writes:
[...]
> >
> > Normally you just have to change your fstab, isn't it ?
>
> Did that already.
>
> >
> > > As I still can't get into cooker, I rebuilt my kernels in 7.2 with
> > > CONFIG_BLK_DEV_OFFBOARD set, ran lilo and rebooted.
> > >
> > > Result: kernel
On Monday 02 April 2001 22:04, Matthias Badaire wrote:
> Peter Ruskin <[EMAIL PROTECTED]> writes:
> > On Saturday 31 March 2001 17:30, Chmouel Boudjnah wrote:
> > > Peter Ruskin <[EMAIL PROTECTED]> writes:
> > > > On Saturday 31 March 2001 16:06, Chmouel Boudjnah wrote:
> > > > > Peter Ruskin <[EM
Peter Ruskin <[EMAIL PROTECTED]> writes:
> On Saturday 31 March 2001 17:30, Chmouel Boudjnah wrote:
> > Peter Ruskin <[EMAIL PROTECTED]> writes:
> > > On Saturday 31 March 2001 16:06, Chmouel Boudjnah wrote:
> > > > Peter Ruskin <[EMAIL PROTECTED]> writes:
> > > > > 1) kernel-2.4.2-i586.config (
On Saturday 31 March 2001 17:30, Chmouel Boudjnah wrote:
> Peter Ruskin <[EMAIL PROTECTED]> writes:
> > On Saturday 31 March 2001 16:06, Chmouel Boudjnah wrote:
> > > Peter Ruskin <[EMAIL PROTECTED]> writes:
> > > > 1) kernel-2.4.2-i586.config (2.4.2-18mdk) :
> > > > CONFIG_BLK_DEV_OFFBOARD=y 2)
Peter Ruskin <[EMAIL PROTECTED]> writes:
> On Saturday 31 March 2001 16:06, Chmouel Boudjnah wrote:
> > Peter Ruskin <[EMAIL PROTECTED]> writes:
> > > 1) kernel-2.4.2-i586.config (2.4.2-18mdk) :
> > > CONFIG_BLK_DEV_OFFBOARD=y 2) kernel-2.2.18-i586-up.config : #
> > > CONFIG_BLK_DEV_OFFBOARD
On Saturday 31 March 2001 16:06, Chmouel Boudjnah wrote:
> Peter Ruskin <[EMAIL PROTECTED]> writes:
> > 1) kernel-2.4.2-i586.config (2.4.2-18mdk) :
> > CONFIG_BLK_DEV_OFFBOARD=y 2) kernel-2.2.18-i586-up.config : #
> > CONFIG_BLK_DEV_OFFBOARD is not set
>
> i have forwarded to our kernel22 main
Peter Ruskin <[EMAIL PROTECTED]> writes:
> 1) kernel-2.4.2-i586.config (2.4.2-18mdk) : CONFIG_BLK_DEV_OFFBOARD=y
> 2) kernel-2.2.18-i586-up.config : # CONFIG_BLK_DEV_OFFBOARD is not set
i have forwarded to our kernel22 maintainners.
--
MandrakeSoft Inc http://www.chmoue
1) kernel-2.4.2-i586.config (2.4.2-18mdk) : CONFIG_BLK_DEV_OFFBOARD=y
2) kernel-2.2.18-i586-up.config : # CONFIG_BLK_DEV_OFFBOARD is not set
They should both be the same.
The result of 1) is that what were /dev/hd{e,f,g,h} are now /dev/hd{a,b,c,d}.
So I have to create device files and hack
Jean Meloche <[EMAIL PROTECTED]> writes:
> Hi... I notice that the recent kernel packages for cooker
> do not include new initrd images. They still link to the
> old kernel's initrd images. Is that an omission? Are we
> supposed to do the mkinitrd ourselves?
Last kernel call the installkernel wh
Hi... I notice that the recent kernel packages for cooker
do not include new initrd images. They still link to the
old kernel's initrd images. Is that an omission? Are we
supposed to do the mkinitrd ourselves?
Thanks.
--
Jean Meloche
[EMAIL PROTECTED]
e-gold # 133947
On Thu, Jun 29, 2000 at 11:40:00AM +0100, Alex Boag-Munroe wrote:
> Hello
>
> Can anyone tell me where stuff gets put once Cooker has finished with it? I
> am trying to find kernel 2.2.16, but can find a Mandrake RPM anywhere!
> Help!!
>
> begin 600 winmail.dat
> M>)\^(@,*`0:0"``$```!``$``
Hello
Can anyone tell me where stuff gets put once Cooker has finished with it? I
am trying to find kernel 2.2.16, but can find a Mandrake RPM anywhere!
Help!!
begin 600 winmail.dat
M>)\^(@,*`0:0"``$```!``$``0>0!@`(Y`0```#H``$(@`<`
M&$E032Y-:6-R;W-O9G0@36%I;"Y.;W1E`#$(`06``P`.``
19 matches
Mail list logo