Hi all
Lilo + software raid 1 +xfs + lvm curent disfunction and next release sugesstion
First a suggestion for the next release (9.2):
When creating a software raid 1 with xfs file system lilo doesn't know
how to write a boot loader to /dev/md0 device. It says that it will
destroy the file system
Hi all
First a suggestion for the next release (9.2):
When creating a software raid 1 with xfs file system lilo doesn't know
how to write a boot loader to /dev/md0 device. It saues that it will
destroy the file system if it does that which is true but instead it
should add raid-extra-boot= mbr-o
I am not sure this is what you want, I urpmi kernel, select one and I was
surprise to not have messages from mkinitrd, I retype lilo and got:
[EMAIL PROTECTED] olivier]# lilo
Added linux *
Added failsafe
Added windows
Added floppy
Added 2422-7
[EMAIL PROTECTED] olivier]# rpm -qa | grep kernel
ker
Lilo makes some mistakes when removing a kernel. Take a look at the
following. This is my /boot/ directory before I started:
[EMAIL PROTECTED] boot]# ls -l
total 9339
lrwxrwxrwx1 root root 32 Sep 7 23:16 System.map ->
System.map-2.4.22-6mdkenterprise
-rw-r--r--1 root r
So What info is required in order to troubleshoot this problem?
Or is it a bug?
Nasa
On Fri, 2003-08-15 at 20:40, Nathan A. Smith wrote:
> Hi,
>
> I am getting the following error when I try to run lilo:
>
> Warning: '/proc/partitions' does not match '/dev' directory structure.
> Name cha
Hi,
I am getting the following error when I try to run lilo:
Warning: '/proc/partitions' does not match '/dev' directory structure.
Name change: '/dev/ide/host0/bus0/target0/lun0/disc' ->
'/dev/ide/host0/bus0/target0/lun0/disc'
Fatal: open /dev/ide/host0/bus0/target0/lun0/disc: No such file o
On Mon, Aug 11, 2003 at 04:42:17PM +0200, Svetoslav Slavtchev wrote:
> shouldn't urpme/ rpm -e remove the entries on uninstall ?
It does unless it's been broken recently.
--
Ben Reser <[EMAIL PROTECTED]>
http://ben.reser.org
"What upsets me is not that you lied to me, but that from now on I ca
"bjørn" <[EMAIL PROTECTED]> writes:
> well,, I have 2 problems with lilo now,
> 1. It cant have more than 11 images (I use it with this mandrake theme)
>
> 2. If you uninstall the defolt kernel (the one that 9.1 come with).
> That kernel is linked to "22 Jul 23 07:07 initrd.img ->
> initrd-2.4.21
well,, I have 2 problems with lilo now,
1. It cant have more than 11 images (I use it with this mandrake theme)
2. If you uninstall the defolt kernel (the one that 9.1 come with). That kernel is
linked to "22 Jul 23 07:07 initrd.img -> initrd-2.4.21-5mdk.img", so when I now try to
type "lilo" I
Quoting Pixel <[EMAIL PROTECTED]>:
> "bjørn" <[EMAIL PROTECTED]> writes:
>
> > well,, I have 2 problems with lilo now,
> > 1. It cant have more than 11 images (I use it with this mandrake theme)
text-mode lilo is limited to 24 if i remember correctly,
and yes i did run several times in :
"ERROR
Tibor Pittich <[EMAIL PROTECTED]> writes:
> On 30. sep 2002 11:52, Guillaume Rousse wrote:
>
> > Le Lundi 30 Septembre 2002 11:30, Tibor Pittich a écrit :
>
> > > i can't find lilo binary when i booted from 1st cd in rescue mode. grub
> > > is included (wow, gpart too :) ), but lilo don't. it
Le Lundi 30 Septembre 2002 12:44, Tibor Pittich a écrit :
> On 30. sep 2002 11:52, Guillaume Rousse wrote:
> > Le Lundi 30 Septembre 2002 11:30, Tibor Pittich a écrit :
> > > i can't find lilo binary when i booted from 1st cd in rescue mode. grub
> > > is included (wow, gpart too :) ), but lilo d
Guillaume Rousse wrote:
> Le Lundi 30 Septembre 2002 11:30, Tibor Pittich a écrit :
>
>>hello
>>
>>i can't find lilo binary when i booted from 1st cd in rescue mode. grub
>>is included (wow, gpart too :) ), but lilo don't. it is accident or on
>>purpose ?
>
> Why should it be included ? Mount yo
On 30. sep 2002 11:52, Guillaume Rousse wrote:
> Le Lundi 30 Septembre 2002 11:30, Tibor Pittich a écrit :
> > i can't find lilo binary when i booted from 1st cd in rescue mode. grub
> > is included (wow, gpart too :) ), but lilo don't. it is accident or on
> > purpose ?
> Why should it be inc
Le Lundi 30 Septembre 2002 11:30, Tibor Pittich a écrit :
> hello
>
> i can't find lilo binary when i booted from 1st cd in rescue mode. grub
> is included (wow, gpart too :) ), but lilo don't. it is accident or on
> purpose ?
Why should it be included ? Mount your / partition from disk, it should
hello
i can't find lilo binary when i booted from 1st cd in rescue mode. grub
is included (wow, gpart too :) ), but lilo don't. it is accident or on
purpose ?
--
Linux 2.4.19-16mdk
Mandrake Linux release 9.0 (Cooker) for i586
11:26am up 6 days, 6:46, 4 users, load average: 0.04, 0.03, 0.00
On Tue Sep 24 23:32 +0200, Pieter Kubben wrote:
> bob and paul, thanks... I felt an idiot, but now it works fine... now
> 'just' the mouse problem
*Insert flame from GRUB user*... :o)
--
Levi Ramsey
[EMAIL PROTECTED] [EMAIL PROTECTED]
Love lies in pools of questions.
Currently p
x27; the mouse problem
>
> best regards,Pieter
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]] On Behalf Of Litwack, Paul
> Sent: dinsdag 24 september 2002 21:24
> To: '[EMAIL PROTECTED]'
> Subject: RE: [Cooker] LILO:
ECTED]'
Subject: RE: [Cooker] LILO: change OS order & default in RC3 [pieter78]
I don't mean to be cute, but did you remember to execute the lilo
program after changing the config file?
-Original Message-
From: Pieter Kubben [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, S
I don't mean to be cute, but did you remember to execute the lilo program
after changing the config file?
-Original Message-
From: Pieter Kubben [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September 24, 2002 11:16 AM
To: Mandrake Linux Cooker List
Subject: [Cooker] LILO: change OS
Did you run 'lilo' after the change?
bob
On Tuesday 24 September 2002 11:15 am, Pieter Kubben wrote:
> Hello,
>
> I am not sure if this is a bug (it might be one called my name ;-) ) but
> I cannot change Lilo's OS order and default OS. I su'd as a root and
> used
>
> > emacs /etc/lilo.conf
>
>
Hello,
I am not sure if this is a bug (it might be one called my name ;-) ) but
I cannot change Lilo's OS order and default OS. I su'd as a root and
used
> emacs /etc/lilo.conf
I changed the text behind default in "windows" instead of "linux" (if I
don't I might get beaten up by the other famil
David Walser <[EMAIL PROTECTED]> writes:
> > oh, i drop support for non-lba32 at install, and
> > this will not bother
> > us again
>
> But you don't need lba32 if you make a /boot partition
> < 1024 cylinders (like at the beginning of the drive)
> :o(
you don't need it, but it doesn't break on
But you don't need lba32 if you make a /boot partition
< 1024 cylinders (like at the beginning of the drive)
:o(
If it was possible to detect that and not use lba32
then that'd be cool, dunno how hard it'd be.
--- Pixel <[EMAIL PROTECTED]> wrote:
> oh, i drop support for non-lba32 at install, an
Aurélien Bompard <[EMAIL PROTECTED]> writes:
> Hi all
>
> I've changed my boot options with drakconf, and it added the "geometric"
> option in lilo.conf, thus preventing lilo to install, since I have a debian
> partition after the 1024th cylinder.
> In the man page, lilo seems to use lba32 by
Hi all
I've changed my boot options with drakconf, and it added the "geometric"
option in lilo.conf, thus preventing lilo to install, since I have a debian
partition after the 1024th cylinder.
In the man page, lilo seems to use lba32 by default, so the solution would be
not to add the "geometr
"Brian J. Murrell" <[EMAIL PROTECTED]> writes:
> Warning: Kernel & BIOS return differing head/sector geometries for
> device 0x80
> Kernel: 38792 cylinders, 16 heads, 63 sectors
> BIOS: 1023 cylinders, 255 heads, 63 sectors
> Added linux *
> Added single,nodevfs
> Added single
> Added f
[EMAIL PROTECTED] wrote on Sat, Jul 06, 2002 at 01:00:10AM -0400 :
> Look up the "optional" flag under man lilo.conf_but_ personally I'd
Sweet, I didn't even notice that it was added with the optional flag.
Thanks.
Blue skies... Todd
--
Todd Lyons -- MandrakeSoft, Inc. http:
Jul 2002 21:45:10 -0700
> From: Todd Lyons <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: [Cooker] lilo new feature?
>
> I just saw something for the first time:
>
> [root@fiji ~]# lilo
> Added linux
> Add
I just saw something for the first time:
[root@fiji ~]# lilo
Added linux
Added linux-nonfb
Added failsafe
Added floppy
Added 2418-18
Added 2418-19
Added 2418-20
Added 2418-21 *
[root@fiji ~]# rpm -e kernel-2.4.18.18mdk
[root@fiji ~]# lilo
Added linux
Added linux-nonfb
Added fails
<[EMAIL PROTECTED]> writes:
> i run drakboot at console text mode to config lilo.
> and i found that if lilo.conf contain the line with "vga="
> then drakboot will seg fault when i press "down".
> if lilo.conf has no "vga=" line, console drakboot seems work well.
bug accepted. will get f
Hi:
i run drakboot at console text mode to config lilo.
and i found that if lilo.conf contain the line with "vga="
then drakboot will seg fault when i press "down".
if lilo.conf has no "vga=" line, console drakboot seems work well.
Best Regards,
tbsky
During an install (or upgrade) on a Compaq DL380 w/
raid 5, lilo is created with the following:
boot=/dev/ida/c0d0
However when installing a new kernel and lilo is
invoked I get the following error:
[root@dl380 sczjd]# lilo
Fatal: open /dev/ida/c0d0: Is a directory
the contents of /dev/ida/c0d0
I have a hard drive module that I can plug in and out
of my laptop. I tried to create a lilo statement for
it using drakboot and it ran fine as long as it is
installed. However, while having a cdrw in that bay
and rerunning lilo, lilo fails because there is no
/dev/hdc1. Is there a way to make lil
÷ ÷ÓË, 10.03.2002, × 11:26, SI Reasoning ÎÁÐÉÓÁÌ:
> I have the following lilo error:
> [root@dl380 sczjd]# lilo
> Fatal: open /dev/ida/c0d0: Is a directory
>
Did installer put it in?
> [root@dl380 ida]# cd c0d0
> [root@dl380 c0d0]# d
> disc part1 part2 part5 part6 part7 part8 part9
>
>
I have the following lilo error:
[root@dl380 sczjd]# lilo
Fatal: open /dev/ida/c0d0: Is a directory
/etc/lilo.conf contains
boot=/dev/ida/c0d0
[root@dl380 etc]# cd /dev/ida
[root@dl380 ida]# d
c0d0/ c0d0p1@ c0d0p2@ c0d0p5@ c0d0p6@ c0d0p7@
c0d0p8@ c0d0p9@
[root@dl380 ida]# cd c0d0
[root@dl
> "guillaume" == Guillaume Cottenceau <[EMAIL PROTECTED]> writes:
guillaume> Pixel <[EMAIL PROTECTED]> writes:
>> Borsenkow Andrej <[EMAIL PROTECTED]> writes:
>>
>> > Warning: Int 0x13 function 8 and function 0x48 return different
>> > head/sector geometries for BIOS drive 0x80
>> >
>> > ev
On Tue, Feb 19, 2002 at 09:02:37AM +0300, Borsenkow Andrej wrote:
>
> >
> > When lilo locates more kernels in /boot
> > and generates appropiate entries in /etc/lilo.conf
>
> lilo does not locate or generate anything.
Well, then somebody does for lilo, maybe DrakX.
Keld
>
> When lilo locates more kernels in /boot
> and generates appropiate entries in /etc/lilo.conf
lilo does not locate or generate anything.
-andrej
When lilo locates more kernels in /boot
and generates appropiate entries in /etc/lilo.conf
it generates lines with initrd that are the standard
initrd instead of looking of an initrd with the
same version as the kernel in question. I would just
recommend that it looked for that version first
(wo
Keld Jørn Simonsen <[EMAIL PROTECTED]> writes:
> When lilo locates more kernels in /boot
> and generates appropiate entries in /etc/lilo.conf
> it generates lines with initrd that are the standard
> initrd instead of looking of an initrd with the
> same version as the kernel in question. I woul
Pixel <[EMAIL PROTECTED]> writes:
> Borsenkow Andrej <[EMAIL PROTECTED]> writes:
>
> > Warning: Int 0x13 function 8 and function 0x48 return different
> > head/sector geometries for BIOS drive 0x80
> >
> > everything seems to work (I can boot :-) Anything to worry about?
>
> i don't think so.
Op do 31-01-2002, om 12:10 schreef Neuromancer:
>
> Yep. I wonder why they decided on that?
>
> -Russ
Windows uses also 16 colors(don't know the size at the to of my head).
This makes it almost certain to work
On Thu, Jan 31, 2002 at 11:06:36AM +0100, François Pons wrote:
> Look at /boot/lilo, where does it points ? Do you have modified it by hand ?
> (possible values are currently lilo-text, lilo-graphic, lilo-menu, lilo-bmp).
Argh, oups, shame on me: you were right: I don't know how it happens,
lilo
>
> But really, don't you think 640x480 (or even 800x600) in 256 colors is
not
> better ?
>
As Mandrake managed to prove it depends :-)
Neuromancer <[EMAIL PROTECTED]> writes:
> Thus spake François Pons about Life, the Universe, and Everything:
> | Look at /boot/lilo, where does it points ? Do you have modified it by hand ?
> | (possible values are currently lilo-text, lilo-graphic, lilo-menu, lilo-bmp).
>
> Out of curiosity, wh
Gregoire Favre <[EMAIL PROTECTED]> writes:
> > if that is the case, re-install lilo cleanly (eg: rpm -i lilo-22*.rpm --force)
> > and it should work.
>
> No: rpm -i lilo-22.1-4mdk.i586.rpm --force
> lilo
> Fatal: First boot sector is version 21.7. Expecting version 22.1.
> rpm -e lilo and then r
Borsenkow Andrej <[EMAIL PROTECTED]> writes:
> Warning: Int 0x13 function 8 and function 0x48 return different
> head/sector geometries for BIOS drive 0x80
>
> everything seems to work (I can boot :-) Anything to worry about?
i don't think so. AFAIK when using LBA32 you don't have to worry abou
Since update to new lilo I get this:
Warning: Int 0x13 function 8 and function 0x48 return different
head/sector geometries for BIOS drive 0x80
everything seems to work (I can boot :-) Anything to worry about?
-andrej
On Wed, Jan 30, 2002 at 01:23:39AM +0100, Pixel wrote:
> > Fatal: First boot sector is version 21.7. Expecting version 22.1.
>
> i'd say you have a seperate /boot where there is an old /boot/boot.b, whereas
> /sbin/lilo is more up to date
Yep:
rpm -V lilo gives:
.M.. g /boot/lilo
Exit 1
>
Gregoire Favre <[EMAIL PROTECTED]> writes:
> and lilo
> 29.01 22:02
> Fatal: First boot sector is version 21.7. Expecting version 22.1.
i'd say you have a seperate /boot where there is an old /boot/boot.b, whereas
/sbin/lilo is more up to date
try "rpm -V lilo" to verify that things are weird.
Hello,
I have done an HD change, and copied all files on the old HD to the new
one, run lilo, removed the old HD, and now, I don't manage running lilo
anymore... Even lilo -u
29.01 22:18
Fatal: Boot sector of /dev/sda doesn't have a LILO signature
and lilo
29.01 22:02
Fatal: First boot sector is
Am Mon, 2002-01-28 um 17.30 schrieb Guillaume Cottenceau:
> suka_at <[EMAIL PROTECTED]> writes:
>
> > Will the new Lilo-Bootscreen stay like it is now? Because the image is
> > really dead ugly now (even the old one was better), and the font looks
>
> Agreed.
>
> > very dirty, the shadow makes
suka_at <[EMAIL PROTECTED]> writes:
> Will the new Lilo-Bootscreen stay like it is now? Because the image is
> really dead ugly now (even the old one was better), and the font looks
Agreed.
> very dirty, the shadow makes it nearly unreadable.
>
> I hope this changes, as the rest of the artwork
"J.P. Pasnak" <[EMAIL PROTECTED]> writes:
> On January 28, 2002 05:30 am Guillaume Rousse said:
>
> >Ainsi parlait J.P. Pasnak :
> >> !,
> >>
> >> rpm -Uvh lilo-22.1-3mdk.i586.rpm
> >> Preparing...###
> >> [100%] 1:lilo
>
On January 28, 2002 05:30 am Guillaume Rousse said:
>Ainsi parlait J.P. Pasnak :
>> !,
>>
>> rpm -Uvh lilo-22.1-3mdk.i586.rpm
>> Preparing...###
>> [100%] 1:lilo
>> ### [100%] Warning
Ainsi parlait J.P. Pasnak :
> !,
>
> rpm -Uvh lilo-22.1-3mdk.i586.rpm
> Preparing...###
> [100%] 1:lilo ###
> [100%] Warning: 'menu-scheme' not supported by boot loader
>
> Before I re
!,
rpm -Uvh lilo-22.1-3mdk.i586.rpm
Preparing...### [100%]
1:lilo ### [100%]
Warning: 'menu-scheme' not supported by boot loader
Before I reboot, what's up with that?
--
Live f
Will the new Lilo-Bootscreen stay like it is now? Because the image is
really dead ugly now (even the old one was better), and the font looks
very dirty, the shadow makes it nearly unreadable.
I hope this changes, as the rest of the artwork (icons and the Mandrake
Control Center) really improved
andre <[EMAIL PROTECTED]> writes:
> The new lilo shows only 7 entries for me and that is used to few for me.
> Could we go back to the previous version. It looked also better
The latest lilo in cooker contains 9 entries visible and now allow simple
scrolling (lilo-22.1-3mdk).
François.
Updating to the latest lilo:
lilo
##
Warning: 'menu-scheme' not supported by boot loader
-andrej
>
> andre <[EMAIL PROTECTED]> writes:
>
> > So if i copy the message file from 8.0 it will be displayed as it was in
> > 8.0
>
> Yes, but re-run lilo for changes to be valid.
>
> François.
>
And is there also somewhere information on how to make a message file?
andre <[EMAIL PROTECTED]> writes:
> So if i copy the message file from 8.0 it will be displayed as it was in
> 8.0
Yes, but re-run lilo for changes to be valid.
François.
Op di 22-01-2002, om 17:58 schreef François Pons:
> andre <[EMAIL PROTECTED]> writes:
>
> > The new lilo shows only 7 entries for me and that is used to few for me.
> > Could we go back to the previous version. It looked also better
>
> Everything is in the message file itself, if you drop it (o
andre <[EMAIL PROTECTED]> writes:
> The new lilo shows only 7 entries for me and that is used to few for me.
> Could we go back to the previous version. It looked also better
Everything is in the message file itself, if you drop it (or change it with
another version) it will be correct.
It will
The new lilo shows only 7 entries for me and that is used to few for me.
Could we go back to the previous version. It looked also better
Guillaume Cottenceau <[EMAIL PROTECTED]> writes:
[...]
> > When installing Mandrake on a mixed system, SCSI and IDE drives, and the
> > system is set to boot off the SCSI drives, LILO writes the boot device as
> > /dev/hdc. It should be /dev/sda.
>
> There is no way from DrakX to know if the BI
"Pete" <[EMAIL PROTECTED]> writes:
[...]
> Yes it does ask, but still seems to pick an ide drive. I had a similar
> problem.
> Scenario:
> Mixed ide/scsi system booting from /dev/sda running cooker. Used urpmi
> --auto-select to update cooker. This installed a new kernel and updated
> lilo.conf
sure it was something I
missed, then OK that's fine. If not, I'm just trying to help make a
wonderful distro better:)
Steve
-Original Message-
From: Guillaume Cottenceau [mailto:[EMAIL PROTECTED]]
Sent: Monday, November 26, 2001 9:53 AM
To: [EMAIL PROTECTED]
Subject: Re:
"Thomas, Stephen W-CONT" <[EMAIL PROTECTED]> writes:
> I had this problem last night when installing 8.1 It may be fixed in cooker,
> but just in case
>
> When installing Mandrake on a mixed system, SCSI and IDE drives, and the
> system is set to boot off the SCSI drives, LILO writes the boo
Borsenkow Andrej wrote:
>>I had this problem last night when installing 8.1 It may be fixed in
>>cooker,
>>but just in case
>>
>>When installing Mandrake on a mixed system, SCSI and IDE drives, and
>>
>the
>
>>system is set to boot off the SCSI drives, LILO writes the boot device
>>
>as
>
>>/
>
> I had this problem last night when installing 8.1 It may be fixed in
> cooker,
> but just in case
>
> When installing Mandrake on a mixed system, SCSI and IDE drives, and
the
> system is set to boot off the SCSI drives, LILO writes the boot device
as
> /dev/hdc. It should be /dev/sda.
>
I had this problem last night when installing 8.1 It may be fixed in cooker,
but just in case
When installing Mandrake on a mixed system, SCSI and IDE drives, and the
system is set to boot off the SCSI drives, LILO writes the boot device as
/dev/hdc. It should be /dev/sda.
The bios is set to
Just installed kernel-2.4.12-3mdk on the other computer and everything
works fine. lilo -v
completed and installed the new bootloader for the lilo.conf.
Now, on the other computer everything is done and need to run 'lilo -v'
on it to finish. It has the same version of lilo, but complains.
Have t
I had a problem installing beta2 cds. After the reboot after installation
(chose lilo text) it printed a nice pattern of ' 40' repeated endlessly.
The setup may be unusual. I had win2k taking up all of a 2GB
partition on /dev/hda and installed Mandrake in a partition
on the 13GB /dev/hdb. I then
Daouda LO <[EMAIL PROTECTED]> writes:
> Guillaume Rousse <[EMAIL PROTECTED]> writes:
>
> > Ainsi parlait Guillaume Rousse :
> > > While trying to re-install cooker:
> > > Fatal: can't put the boot sector on logical partition 0x305
> > > I use reiserFS on every partition, but it worked well befor
Guillaume Rousse <[EMAIL PROTECTED]> writes:
> Ainsi parlait Guillaume Rousse :
> > While trying to re-install cooker:
> > Fatal: can't put the boot sector on logical partition 0x305
> > I use reiserFS on every partition, but it worked well before...
>
> Solved : it was just missing
> boot=/dev
> Anyway, it seems to be a bug in new DrakX (build just one or two days ago).
Well, Pixel did warn us :P!
Ainsi parlait Guillaume Rousse :
> While trying to re-install cooker:
> Fatal: can't put the boot sector on logical partition 0x305
> I use reiserFS on every partition, but it worked well before...
Solved : it was just missing
boot=/dev/hda in /etc/lilo.conf
Anyway, it seems to be a bug in new D
While trying to re-install cooker:
Fatal: can't put the boot sector on logical partition 0x305
I use reiserFS on every partition, but it worked well before...
--
Guillaume Rousse <[EMAIL PROTECTED]>
GPG key http://bohm.snv.jussieu.fr/~rousse/gpgkey.html
> there is a bug in installer (both in Mdk8 and cooker) - I have selected
> "Graphical menu" but still got just text menu. I have lilo-0.21.7-11mdk -
> is it the latest?
the lilo files names had changed, we need to update drakx according to
this.
will be done asap.
yves
--
Yves Duret
[EMAIL PR
On Sat, 5 May 2001, SI Reasoning wrote:
> Since the last lilo upgrade I have not been able to
> get it to work with either text or graphical menu. I
> have manually linked it to the directory of choice and
> also tried to get it to work through the interace in
> drakconf. I can get grub to work f
Since the last lilo upgrade I have not been able to
get it to work with either text or graphical menu. I
have manually linked it to the directory of choice and
also tried to get it to work through the interace in
drakconf. I can get grub to work from there but not
lilo. The only lilo I get now is
On 27 Apr 2001, François Pons wrote:
> Sebastian Dransfeld <[EMAIL PROTECTED]> writes:
>
> > Could you do
> >
> > 'mv /boot/message /boot/message-text'
> >
> > And then symlink the right message (message-graphic or message-text) to
> > message?
>
> We will do something like symlinking a directory
Sebastian Dransfeld <[EMAIL PROTECTED]> writes:
> Could you do
>
> 'mv /boot/message /boot/message-text'
>
> And then symlink the right message (message-graphic or message-text) to
> message?
We will do something like symlinking a directory where the right stage2 and its
message file are store
Could you do
'mv /boot/message /boot/message-text'
And then symlink the right message (message-graphic or message-text) to
message?
seb
Armisis Aieoln <[EMAIL PROTECTED]> writes:
> Fatal: open /boot/initrd.img: No such file or directory
humm you did a bad kernel update here ?
--
MandrakeSoft Inc http://www.chmouel.org
--Chmouel
Fatal: open /boot/initrd.img: No such file or directory
Dave
"Tim" <[EMAIL PROTECTED]> writes:
> Tried to install last night and I'm not sure if I caught the mirror in the
> middle of an update or what, but when the install got to the "Install Boot
> Loader" option I got an error message to the tune of "NOT AN ARRAY VALUE."
> Unfortunately, this means that
Tried to install last night and I'm not sure if I
caught the mirror in the middle of an update or what, but when the install got
to the "Install Boot Loader" option I got an error message to the tune of "NOT
AN ARRAY VALUE." Unfortunately, this means that I have no way to boot the system
wit
Hi all!
How can I install LILO in a floppy after the installation is finished?
> Jonas Mbongui
>
> -Message d'origine-
> De: [EMAIL PROTECTED]@SUNGARD À la place de "M. van den Berg"
> <[EMAIL PROTECTED]>
> Date: lundi 12 février 2001 12:38
> À:[EMAIL PROTECTED]
> Objet:
> Um, some of us don't like full-screen boot logos on another os because we
> like to see the start-up stuff.
>
> Matthew
Read the message. Besides if you have ever used Aurora it does cover over
the messages. What I said was twofold: #1 Make sure Aurora stays visible
(if in init 5) until kdm st
When you click on an icon it pops up the text - maybe reserve a couple
centimeters on the bottom of the screen to display these all the time,
rather than have to click on moving icons? Just a thought.
V.
OS wrote:
>
> I think all that space below the penguin could be put to more use. For
> exa
I think all that space below the penguin could be put to more use. For
example telling us the progress of e2fsck. When disk check is forced the boot
screen goes alarmingly blank, especially for a 'newbie'. Before Aurora went
Mandrake changes were put in to do just this, but they have now disapp
Um, some of us don't like full-screen boot logos on another os because we
like to see the start-up stuff.
Matthew
- Original Message -
From: David Walluck <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, February 09, 2001 11:49 AM
Subject: Re: [Cooker] Lilo B
On Fri, 9 Feb 2001, Frederic Crozat wrote:
>
> Be patient, young Skywalker, be patient :))
>
Even with Aurora I can still see all the kernel messages on tty1 before
kdm starts. Can't we start kdm in the background and wait for it to be up,
and then switch over from Aurora in a way that looks se
Hi,
Dans l'article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] a écrit :
> The boot of Cooker with will aurora is very beautiful, but why not add
> in more one image on LILO,
> with MKLILOMSG MKLILOMSG uses an image PCX (256 color palette)
Be patient, young Skywalker, be patient :))
--
Frédéric C
Hi,
The boot of Cooker with will aurora is very beautiful, but why not add in
more one image on LILO,
with MKLILOMSG MKLILOMSG uses an image PCX (256 color palette)
Vincent GUARDIOLA
TSC Micro / Lan Server Support & IBM Linux Help Center France
I would prefer postinstall script limitis itself to warn user he has to
run lilo, not running it itself. If lilo.conf is not in a valid state,
result could be rather dangereous.
--
Guillaume Rousse
Murphy's law : If anything can go wrong, it will.
O'Tool's commentary : Murphy was an optimist.
---
Guillaume Rousse <[EMAIL PROTECTED]> writes:
> Pixel a écrit :
>
> > ben c'est ce qu'est fait!
> ^^^
> french speaking forbidden here ! Pan sur le bec ! :-)
sorry, i thought it was chmouel-sent only :-/
>
> > %post
> > if [ -f /etc/lilo.conf ]; then
> > if [ -x /usr/
1 - 100 of 150 matches
Mail list logo
