Hi all, the LILO package for Debian has been using bootscreens for each
distribution. Currently there is a bootscreen for woody, sarge and sid
but there is not one for etch. I'd thank any Debian user that will be
willing to create a DFSG-compliant image to merge it with the LILO
package for Etc
ing a shell script that checks
> if the machine is pingable, but I'm finding that often the service has
> died but the machine is still reachable with ping.
>
> Thanks in advance,
> Mike
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "
The real problem is that your lilo.conf file makes reference
to an /initrd.img file which may not exist. The warning can
be skipped and means that your kernel was compiled with DEVFS_FS
support and you are not using it.
--
Andrés Roldán <[EMAIL PROTECTED]>
GPG Key-ID: 0xB29396E
gt; # NORMAL select normal 80x25 text mode.
> # EXTENDED select 80x50 text mode. The word EXTENDED can be
> # abbreviated to EXT.
> # ASK stop and ask for user input (at boot time).
> # use the corresponding text mode. A list of available modes
> # can be obtained
------
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a
> subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>
--
Andrés Roldán <[EMAIL PROTECTED]>
GPG Key-ID: 0xB29396EB
http://people.fluidsignal.com/~aroldan
pgp0.pgp
Description: PGP signature
Patrick Wiseman <[EMAIL PROTECTED]> writes:
> On Mon, 29 Dec 2003 at 3:05pm, Andrés Roldán wrote:
>
> :Add the line:
> :
> :disk=/dev/sda inaccessible
> :
> :to the lilo.conf file.
>
> Thanks! That fixed it. But why does lilo care about /dev/sda in the
> fi
tting the MBR on /dev/sda, which is not my situation.
>
> Hoping someone can help,
>
> Patrick
>
> --
> Patrick Wiseman [EMAIL PROTECTED]
> Linux user #17943 *Google First, Ask Later*
>
>
> --
> To UNSUBSCRIBE, email to [
s message, please put
> `do_initrd = Yes'
> in /etc/kernel-img.conf.
> Do you want to stop now? [Y/n]
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>
--
Andrés Roldán <[EMAIL PROTECTED]>
GPG Key-ID: 0xB29396EB
http://people.fluidsignal.com/~aroldan
pgp0.pgp
Description: PGP signature
Check the 'boot-as' parameter on lilo.conf(5).
duck <[EMAIL PROTECTED]> writes:
> On Wed, 10 Dec 2003 20:00:25 +0100, LeVA wrote:
>
>> I have these lines in my /etc/lilo.conf:
>>
>> other=/dev/hdg1
>> label="Win"
>>
>> When I run 'lilo', it says:
>>
>> ...
>> Added Win
>> ...
>>
>> This
I've made a patch to LILO to support labels with spaces. However, you must enclose
the name between quotes. This patch will be released on the next (1:22.5.8-6)
upload.
Cheers.
Joel Konkle-Parker <[EMAIL PROTECTED]> writes:
> For some reason, LILO in unstable doesn't seem to like multi-word Lab
Tom <[EMAIL PROTECTED]> writes:
> On Sat, Nov 08, 2003 at 01:38:56PM -0500, BruceG wrote:
> [cut]
>> > Willem-Jan Meijer wrote:
>> > > but when I wanted to boot I saw the letters LI, and after that the
>> system hangs.
>>
>> I had the same problem after my upgrade. If you made a boot floppy durin
Robert Story <[EMAIL PROTECTED]> writes:
> Dear All,
>
> I'm trying to use efax to receive faxes. I've read the man page and it seems
> reasonably clear enough.
>
> However, I'm only able to get efax to work if I'm root. As an individual user, this
> is what I get when I try to put the fax modem
When lilo finds the field bitmap= on lilo.conf, it assumes "install=bmp".
The syntaxis "install=/boot/*.b" is now deprecated as LILO has put together
all those *.b files into its binary. You can even remove that install= line
or, for avoiding problems, just put install=bmp and all will work fine.
Alvin Oga <[EMAIL PROTECTED]> writes:
> On Tue, 4 Nov 2003, David Z Maze wrote:
>
>> "W. Borgert" <[EMAIL PROTECTED]> writes:
>>
>> > I have a machine where I want to cleanly install Debian, but the
>> > MBR has remains of grub. I searched the net, but all hits I got
>> > involved a DOS diskette
See the boot-as= option on lilo.conf(5)
Moreover, I'd like to hear what happened with your lilo.conf file after
the dist-upgrade.
Thanks.
techlists <[EMAIL PROTECTED]> writes:
> Ok, I use to have a setup where Linux was on my primary HD, and windows
> was on a 2nd slave HD. I had once found so
Wrong file :)
This is the patch.
Daniel Barclay <[EMAIL PROTECTED]> writes:
> Is it possible to disable the boot logo from LILO (e.g., via a kernel
> boot parameter)?
>
> With vga=ask in lilo.conf, when I boot and select a video mode, it seems
> LILO changes the video mode but the kernel immedia
"Daniel B." <[EMAIL PROTECTED]> writes:
> Roberto Sanchez wrote:
>>
>> Daniel Barclay wrote:
>> > Is it possible to disable the boot logo from LILO (e.g., via a kernel
>> > boot parameter)?
>> >
>> > With vga=ask in lilo.conf, when I boot and select a video mode, it seems
>> > LILO changes the vi
Just for the sake of being clear, LILO does not change anything in the
kernel, it just passes parameters to the kernel and then, when the
kernel has been completely loaded, LILO has nothing to do hereafter.
Daniel Barclay <[EMAIL PROTECTED]> writes:
> Is it possible to disable the boot logo from
Alexander Onic <[EMAIL PROTECTED]> writes:
> Hi,
>
> I have problems with lilo 22.5.7-1 on Debian Woody.
> Woody is running and booting from my onboard ide-controller (/dev/hda)
> with kernel 2.4.18-bf2.4.
LILO 22.5.7-1 on Woody?
>
> My Asus A7V133 also has an onboard Promise-Controller running
LILO makes a cache of the disks and partitions using /proc/partitions.
The default Debian kernel has been compiled with DEVFS_FS support and
therefore, if you see your /proc/partitions, you will notice that this
filehas a "devfs scheme". Thereby, /dev/ide/host0/bus0/target0/lun0/disc
does not ex
Have the disks different volume ID?
Check this by issuing:
# lilo -T vol-ID
If not, you must set different volume ID to each disk.
Read README.raid1.gz (from lilo-doc package) and README.volumeID.gz
(from lilo package) for more information. Doing the following will
set different volume ID to your
Adam Heath <[EMAIL PROTECTED]> writes:
> On Wed, 17 Sep 2003, Andrés Roldán wrote:
>
>> PS: valgrind-snapshot conflicts with valgrind for obvious reasons.
>
> Er, why? I see no reason for it to. Just rename the binaries in the package.
Both packages have the same sh
Adam Heath <[EMAIL PROTECTED]> writes:
> On Wed, 17 Sep 2003, Andrés Roldán wrote:
>
>> I'm glad to announce that valgrind-snapshot has been packaged.
>> I've made a script that makes the package daily.
>>
>> It is currently not on the official Debian
I'm glad to announce that valgrind-snapshot has been packaged.
I've made a script that makes the package daily.
It is currently not on the official Debian archives so, please,
do NOT report bugs to valgrind if you found a bug in valgrind-snapshot.
Instead, send me an email with the description of
Robert Tilley <[EMAIL PROTECTED]> writes:
> What is the meaning of the following LILO response?
>
> debian-rti:/# lilo
> Warning: '/proc/partitions' does not match '/dev' directory structure.
> Name change: '/dev/ide/host0/bus0/target0/lun0/disc' -> '/dev/hda'
> The kernel was compiled wit
Dan Jacobson <[EMAIL PROTECTED]> writes:
> LILO version 22.5.7.2 says
> Warning: '/proc/partitions' does not match '/dev' directory structure.
> The kernel was compiled with DEVFS_FS, but 'devfs=mount' was omitted
> as a kernel command-line boot parameter; hence, the '/dev' direc
Change boot=/dev/sda1 for boot=/dev/sda and rerun /sbin/lilo
"Victory" <[EMAIL PROTECTED]> writes:
> I use Noton Ghost 2003 to create disk to CD images then
> restored from CD Image to another disk, After done I the reboot
> to new disk and after MBR it support to start LILO 22.2 but it
> show a
[EMAIL PROTECTED] writes:
> I have to ask a dumb question. When booting is lilo.conf read?
> Or is lilo.conf only used for writing the MBR plus the additional boot
> sectors? I assume it's not read while booting.
>
> I'm trying to understand the "disk", "boot", and "root" options in
> lilo.conf
A new valgrind version is available. It is a snapshot from the cvs head
but the upstream says at his homepage that this is the most stable version
and can be considered for being packaged. It may have some bugs and
therefore I will wait to upload it officialy to Debian. However, you can
get a pre-r
Andrés Roldán <[EMAIL PROTECTED]> writes:
> You can try zeroing the MBR (not including the partition table) and rerun
> grub-install. Try the following:
>
> dd if=/dev/hda of=mbr.bak bs=512 count=1
>
> this will make a backup of your mbr including the partition table.
You can try zeroing the MBR (not including the partition table) and rerun
grub-install. Try the following:
dd if=/dev/hda of=mbr.bak bs=512 count=1
this will make a backup of your mbr including the partition table. Then run:
dd if=/dev/zero of=/dev/hda bs=443 count=1
After the 443 byte it is th
Nori Heikkinen <[EMAIL PROTECTED]> writes:
> In my ongoing quest to put Debian on this Dell Inspiron 8000, I
> recompiled the kernel and disabled framebuffer support (so the screen
> doesn't go all wacky). I hadn't seen some of the options presented me
> by the install menu when i did dpkg -i ker
Hi
This may be caused because files such as /boot/boot.b /boot/boot-menu.b are
deprecated in newer versions of LILO and may conflict with previous LILO
installations.
Please refer to LILO documentation at /usr/share/doc/lilo/README.common.problems
The most important thing to note is the followi
33 matches
Mail list logo
