And also see http://lilo.alioth.debian.org/olddoc/html/tech_21-5.html
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Hendrik Boom wrote:
>> I don't understand this. My understanding of lilo is that is just finds
>> the blocks where the kernel is, and usually the kernel file is not placed
>> in any superblock or signature; shouldn't the file system driver ensure
>> that ?
>
> It has to find the partition with
On Wed, Aug 17, 2016 at 02:09:02PM +0200, k...@aspodata.se wrote:
> Henrik Boom:
> > On Tue, Aug 16, 2016 at 10:05:12PM +0200, k...@aspodata.se wrote:
> ...
> > > Next scenario is if you have the bootloader on a different media, say
> > > e.g. a floppy. Then, will lilo load the kernel from disk 2 w
Henrik Boom:
> On Tue, Aug 16, 2016 at 10:05:12PM +0200, k...@aspodata.se wrote:
...
> > Next scenario is if you have the bootloader on a different media, say
> > e.g. a floppy. Then, will lilo load the kernel from disk 2 when disk 1
> > fails (assuming mirrored /boot) ? Do grub handle that ?
>
>
k...@aspodata.se wrote:
> Next scenario is if you have the bootloader on a different media, say
> e.g. a floppy. Then, will lilo load the kernel from disk 2 when disk 1
> fails (assuming mirrored /boot) ? Do grub handle that ?
With Grub you can specify the disk/partition by system device name (eg
On 16/08/16 21:54, Rainer Weikusat wrote:
Apart from that, current LILO versions already do seem to support this
and even if they didn't, adding a "Try 0x81. In case it doesn't exist,
try 0x80" option to the code wouldn't be terribly complicated. Just
requires "another learning curve" ...
I ha
On Tue, Aug 16, 2016 at 10:05:12PM +0200, k...@aspodata.se wrote:
> Rick Moen:
> > Quoting k...@aspodata.se (k...@aspodata.se):
> > > It does not care about MBR vs. GPT as long it can find the blocks where
> > > the kernel and possible initrd/initramfs is.
> > > I use Lilo on two GPT formatted dis
Rick Moen:
> Quoting k...@aspodata.se (k...@aspodata.se):
> > It does not care about MBR vs. GPT as long it can find the blocks where
> > the kernel and possible initrd/initramfs is.
> > I use Lilo on two GPT formatted disks where the partitions are mirrored
> > and have no problems with it, remov
Quoting k...@aspodata.se (k...@aspodata.se):
> It does not care about MBR vs. GPT as long it can find the blocks where
> the kernel and possible initrd/initramfs is.
>
> I use Lilo on two GPT formatted disks where the partitions are mirrored
> and have no problems with it, remove any disk, still
Brad Campbell writes:
> On 16/08/16 00:09, Rick Moen wrote:
>> Quoting Adam Borowski (kilob...@angband.pl):
>>
>
>>
>>> Or, the first disk gets assigned a different position.
>>
>> Which happens when exactly? Because you're screwing around with
>> swapping in and out different HBAs? Well, if you
Edward Bartolo:
...
> LILO is out of question.
...
> Besides that, it cannot recognize GPT formatted disks.
It does not care about MBR vs. GPT as long it can find the blocks where
the kernel and possible initrd/initramfs is.
I use Lilo on two GPT formatted disks where the partitions are mirrore
Brad Campbell wrote:
<<
I even migrated from Grub 0.9x to Grub2 and I've had nothing but
unicorns and rainbows there too. Again, another learning curve, but
nothing a couple of hours didn't sort out. I seem to be the only
person alive that actually gets along with Grub, but that's ok because
it wor
Quoting Brad Campbell (lists2...@fnarfbargle.com):
> Details are sketchy now as I made this change in 2005 after 9 good
> years with LILO. I did try very hard to make it work, and it may
> have been an issue with the BIOS ultimately. I actually had a hard
> copy of that particular howto next to my
On 16/08/16 11:50, Rick Moen wrote:
Quoting Brad Campbell (lists2...@fnarfbargle.com):
Actually, this exact reason is why I moved from Lilo to Grub a few
moons ago.
It happens *when* one of the primary OS drives dies in your server
and you get a reboot before you have a chance to fix the array
Quoting Brad Campbell (lists2...@fnarfbargle.com):
> Actually, this exact reason is why I moved from Lilo to Grub a few
> moons ago.
>
> It happens *when* one of the primary OS drives dies in your server
> and you get a reboot before you have a chance to fix the array.
>
> Example (because this
On 16/08/16 00:09, Rick Moen wrote:
Quoting Adam Borowski (kilob...@angband.pl):
Or, the first disk gets assigned a different position.
Which happens when exactly? Because you're screwing around with
swapping in and out different HBAs? Well, if you're doing that, see
Actually, this e
Quoting Adam Borowski (kilob...@angband.pl):
> LILO is anything but 'finished'. It's not 'stable', either
Cry me a river.
> -- even on simple filesystems where it works, it dies horribly the
> moment any of blocks the kernel was written on gets moved.
Important rule: If you don't understand h
On Mon, 15 Aug 2016 04:32:45 -0700
Rick Moen wrote:
> And, honestly, this matter needs to be seen in proper perspective.
> Sometimes a piece of software is relatively simple and well enough
> debugged that it makes just as much sense to call it 'finished and
> stable' as it does 'unmaintained'.
On Mon, Aug 15, 2016 at 04:32:45AM -0700, Rick Moen wrote:
> > > The author has updated their site to say:
> > >
> > > "NOTE: I will finish development of LILO at December 2015 because of
> > > some limitations (e.g. with BTFS, GPT, RAID). If someone want to
> > > develop this nice software furt
Quoting Hendrik Boom (hend...@topoi.pooq.com):
> On Tue, Jan 19, 2016 at 02:44:59PM -, dev1fanboy wrote:
> > https://lilo.alioth.debian.org/
> >
> > The author has updated their site to say:
> >
> > "NOTE: I will finish development of LILO at December 2015 because of some
> > limitations (e
On Tue, Jan 19, 2016 at 02:44:59PM -, dev1fanboy wrote:
> https://lilo.alioth.debian.org/
>
> The author has updated their site to say:
>
> "NOTE: I will finish development of LILO at December 2015 because of some
> limitations (e.g. with BTFS, GPT, RAID). If someone want to develop this nic
Le 20/01/2016 17:18, k...@aspodata.se a écrit :
Le 20/01/2016 13:14, Simon Hobson a écrit :
...
> >AIUI, if you use md and raid1, with metadata version 0.9, for
> >/boot - then each member of the raid set contains a complete
> >image of /boot which is safe to use read-only. So the bootloader
>
Didier Kryn:
> Le 20/01/2016 13:14, Simon Hobson a écrit :
...
> > AIUI, if you use md and raid1, with metadata version 0.9, for
> > /boot - then each member of the raid set contains a complete
> > image of /boot which is safe to use read-only. So the bootloader
> > doesn't need to understand md, a
Le 20/01/2016 15:29, dev1fanboy a écrit :
It seems enough to me that extlinux is available if it is as easy to work with
as it looks, grub will be around for a while so people have that.
Yeah. I understand it's similar to syslinux. I used syslinux to
boot from usb keys. I don't see any re
It seems enough to me that extlinux is available if it is as easy to work with
as it looks, grub will be around for a while so people have that.
I also note there is elilo for EFI, not sure how usable that is on traditional
setups though.
On Wednesday, January 20, 2016 12:14 PM, Simon Hobson
Le 20/01/2016 13:14, Simon Hobson a écrit :
Didier Kryn wrote:
I don't think Grub2 is all about pretty colours though. The veteran admin likes
to have a bootloader which is easy to configure, but the random admin, likes to
have a working multi-boot bootloader at the end of the installation.
Didier Kryn wrote:
> I don't think Grub2 is all about pretty colours though. The veteran admin
> likes to have a bootloader which is easy to configure, but the random admin,
> likes to have a working multi-boot bootloader at the end of the installation.
Indeed, and when ${random_admin} has a m
Le 19/01/2016 17:02, Steve Litt a écrit :
Grub is the systemd of bootloaders. It's all about pretty colors, nice
images, and hiding the fact that processes are being instantiated.
Someone said that the developpers of grub-0.9 (now Grub legacy) had
maintenance problems. Often, in this case, th
Steve Litt:
> On Wed, 20 Jan 2016 00:04:25 +0100
> richard lucassen wrote:
...
> > Unless you use a small ext2 boot partition for your kernels. And for
Lilo is the reader of the boot partition and lily does not understand
any fs. Isn't it sufficient with any fs which preferably puts the kernel
in
On Tue, Jan 19, 2016 at 03:25:13PM +, Nuno Magalhães wrote:
> On Tue, Jan 19, 2016 at 2:44 PM, dev1fanboy
> wrote:
> > So I assume lilo has stopped development altogether from the last release,
> > and we can look forward to only having the more complex grub2.
I'm still using lolp on Debian
Hi everyone. It's been a long time since I posted here, but don't worry, I
haven't gone over to the Dark Side (ie Systemd). I've just been quietly
waiting for Devuan-beta, and in the meantime have tried to keep out of the
way of the Devuan developers rather than waste their time with my ignorant
pr
On Wed, 20 Jan 2016 00:04:25 +0100
richard lucassen wrote:
> On Tue, 19 Jan 2016 14:44:59 -
> "dev1fanboy" wrote:
> > So I assume lilo has stopped development altogether from the last
> > release, and we can look forward to only having the more complex
> > grub2.
>
> Unless you use a sm
On Tue, 19 Jan 2016 07:26:57 -1000
Joel Roth wrote:
> Steve Litt wrote:
> > On Tue, 19 Jan 2016 17:20:10 +0100
> > Adam Borowski wrote:
> >
> > > On Tue, Jan 19, 2016 at 11:02:17AM -0500, Steve Litt wrote:
> > > > Grub is the systemd of bootloaders. It's all about pretty
> > > > colors, nic
On Tue, 19 Jan 2016 14:44:59 -
"dev1fanboy" wrote:
> https://lilo.alioth.debian.org/
>
> The author has updated their site to say:
>
> "NOTE: I will finish development of LILO at December 2015 because of
> some limitations (e.g. with BTFS, GPT, RAID). If someone want to
> develop this nice
I use lilo on assorted tired old bits of kit.
The fact it can't cope with GPT and what have you isn't a problem.
I will be using lilo on old kit until they fall over.
Grub1 was getting a bit tired. I can understand why they felt grub2 was
needed.
I was running debian unstable during the changeove
the plethora of numbered config files is a consequence of debian policy
(config files have to be owned by exactly one package, and that's the only
package which can automatically touch them) rather, than any design of
grub2 itself. Split configs is the way that Debian works around this policy
while
Hi All,
On this machine I am using right now on which I developed netman, I
have grub2 installed. Since I never agreed with how grub2 should be
managed, I opted to use a manual method to update grub.cfg. This
machine has about 9 Debian/Devuan installations installed to separate
partitions on a GPT
Steve Litt wrote:
> On Tue, 19 Jan 2016 17:20:10 +0100
> Adam Borowski wrote:
>
> > On Tue, Jan 19, 2016 at 11:02:17AM -0500, Steve Litt wrote:
> > > Grub is the systemd of bootloaders. It's all about pretty colors,
> > > nice images, and hiding the fact that processes are being
> > > instantiate
On Tue, 19 Jan 2016 17:20:10 +0100
Adam Borowski wrote:
> On Tue, Jan 19, 2016 at 11:02:17AM -0500, Steve Litt wrote:
> > Grub is the systemd of bootloaders. It's all about pretty colors,
> > nice images, and hiding the fact that processes are being
> > instantiated.
>
> Grub is complex, but t
On Tue, Jan 19, 2016 at 11:02:17AM -0500, Steve Litt wrote:
> Grub is the systemd of bootloaders. It's all about pretty colors, nice
> images, and hiding the fact that processes are being instantiated.
Grub is complex, but that's caused by what it tries to do (read the kernel
image from real files
Steve Litt writes:
> On Tue, 19 Jan 2016 15:48:40 -
> "dev1fanboy" wrote:
>
>> Hopefully something will happen with it, personally I'd use grub but
>> it does some fancy stuff I'm not a fan of.
>
> Grub is the systemd of bootloaders. It's all about pretty colors, nice
> images, and hiding the
Hopefully something will happen with it, personally I'd use grub but it does
some fancy stuff I'm not a fan of.
On Tuesday, January 19, 2016 3:25 PM, Nuno Magalhães
wrote:
> On Tue, Jan 19, 2016 at 2:44 PM, dev1fanboy
> wrote:
>> So I assume lilo has stopped development altogether from the las
On Tue, 19 Jan 2016 15:48:40 -
"dev1fanboy" wrote:
> Hopefully something will happen with it, personally I'd use grub but
> it does some fancy stuff I'm not a fan of.
Grub is the systemd of bootloaders. It's all about pretty colors, nice
images, and hiding the fact that processes are being i
On Tue, 19 Jan 2016 14:44:59 -
"dev1fanboy" wrote:
> https://lilo.alioth.debian.org/
>
> The author has updated their site to say:
>
> "NOTE: I will finish development of LILO at December 2015 because of
> some limitations (e.g. with BTFS, GPT, RAID). If someone want to
> develop this nice
On Tue, Jan 19, 2016 at 2:44 PM, dev1fanboy wrote:
> So I assume lilo has stopped development altogether from the last release,
> and we can look forward to only having the more complex grub2.
Slackware uses lilo by default, maybe someone there will tend to it.
Or the IoT crowd.
https://lilo.alioth.debian.org/
The author has updated their site to say:
"NOTE: I will finish development of LILO at December 2015 because of some
limitations (e.g. with BTFS, GPT, RAID). If someone want to develop this nice
software further, please let me know ..."
So I assume lilo has stopp
46 matches
Mail list logo
