Re: [DNG] LILO Framebuffer and X screen resolution

On Thu, May 28, 2020 at 08:37:01AM -0700, Ian Zimmerman wrote: > On 2020-05-23 14:36, Marc Shapiro via Dng wrote: > > > I have been using Debian for the last 20+ years. I don't like systemd > > and that has kept me on Stretch, where I can still use SysV as init. I > > have tried several times to

Re: [DNG] LILO Framebuffer and X screen resolution

On 2020-05-23 14:36, Marc Shapiro via Dng wrote: > I have been using Debian for the last 20+ years. I don't like systemd > and that has kept me on Stretch, where I can still use SysV as init. I > have tried several times to upgrade to Buster without SysV, but have > had no luck. So here I am at

Re: [DNG] LILO Framebuffer and X screen resolution (SOLVED)

On 5/23/20 2:36 PM, Marc Shapiro wrote: I have been using Debian for the last 20+ years.  I don't like systemd and that has kept me on Stretch, where I can still use SysV as init.  I have tried several times to upgrade to Buster without SysV, but have had no luck.  So here I am at Devuan. I

[DNG] LILO Framebuffer and X screen resolution

I have been using Debian for the last 20+ years.  I don't like systemd and that has kept me on Stretch, where I can still use SysV as init.  I have tried several times to upgrade to Buster without SysV, but have had no luck.  So here I am at Devuan. I installed Ascii on a separate set of

Re: [DNG] lilo development has ended

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

Re: [DNG] lilo development has ended

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

Re: [DNG] lilo development has ended

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

Re: [DNG] lilo development has ended

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 ? > >

Re: [DNG] lilo development has ended

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

Re: [DNG] lilo development has ended

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

Re: [DNG] lilo development has ended

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

Re: [DNG] lilo development has ended

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,

Re: [DNG] lilo development has ended

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,

Re: [DNG] lilo development has ended

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

Re: [DNG] lilo development has ended

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

Re: [DNG] lilo development has ended

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

Re: [DNG] lilo development has ended

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

Re: [DNG] lilo development has ended

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

Re: [DNG] lilo development has ended

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

Re: [DNG] lilo development has ended

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

Re: [DNG] lilo development has ended

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

Re: [DNG] lilo development has ended

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

Re: [DNG] lilo development has ended

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

Re: [DNG] lilo development has ended

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

Re: [DNG] lilo development has ended

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

Re: [DNG] lilo

On Sun, Jul 10, 2016 at 12:16:38PM +0200, k...@aspodata.se wrote: > Joel Roth: > > I'm revisiting this thread, after reading more about the > > automatic kernel and bootloader upgrading policies in Debian and > > Ubuntu. > > > > Personally, I'm astonished that a casual upgrade will > > end up

Re: [DNG] lilo

Joel Roth: > I'm revisiting this thread, after reading more about the > automatic kernel and bootloader upgrading policies in Debian and > Ubuntu. > > Personally, I'm astonished that a casual upgrade will > end up trying to update a working bootloader. ... This used to fend off the automatic

Re: [DNG] lilo

Am Sat, 09 Jul 2016 21:14:42 + schrieb Joel Roth : > To me it's an important part of linux infrastructure. > (Has anyone investigated if syslinux/extlinux can offer the same > functionality?) Me too, i prefer lilo (so used to from years with slackware ;) ) - and i don't

Re: [DNG] lilo

I'm revisiting this thread, after reading more about the automatic kernel and bootloader upgrading policies in Debian and Ubuntu. Personally, I'm astonished that a casual upgrade will end up trying to update a working bootloader. This is another instance where I feel that less code, and less

Re: [DNG] lilo

Rainer Weikusat writes: [...] > I'll certainly fix any CVE-level issue I consider to be relevant for my > use cases While we're at that: There's a bunch of (very likely harmless) buffer overflows in the bsect_common function (bsect.c), namely this here: if ((root =

Re: [DNG] lilo

Jaromil writes: > On Mon, 30 May 2016, Rainer Weikusat wrote: > >> I have no plans to use anything but lilo unless that's a technical >> requirement. It boots. That's all I want from it. > > having dealt with it recently, what is your opinion on the current > state of Lilo code?

Re: [DNG] lilo

Hendrik Boom writes: > On Sun, May 29, 2016 at 08:37:08PM +0100, dev1fanboy wrote: >> >> Also worth pointing out that lilo is without an upstream maintainer >> as of recently. > > I'm happily using lilo to boot my server. JFTR: I've recently (last week) added a

Re: [DNG] lilo

On Sun, May 29, 2016 at 11:25:09PM +0200, Patrick Erdmann wrote: > On 29.05.2016 22:42, Hendrik Boom wrote: > > On Sun, May 29, 2016 at 08:37:08PM +0100, dev1fanboy wrote: > >> > >> Also worth pointing out that lilo is without an upstream maintainer > >> as of recently. > > > > I'm happily using

Re: [DNG] lilo development has ended

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: [DNG] lilo development has ended

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 >

Re: [DNG] lilo development has ended

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,

Re: [DNG] lilo development has ended

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

Re: [DNG] lilo development has ended

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

Re: [DNG] lilo development has ended

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

Re: [DNG] lilo development has ended

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

Re: [DNG] lilo development has ended

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

Re: [DNG] lilo development has ended

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

Re: [DNG] lilo development has ended

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

Re: [DNG] lilo development has ended

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

Re: [DNG] lilo development has ended

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.

Re: [DNG] lilo development has ended

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

[DNG] lilo development has ended

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

Re: [DNG] lilo development has ended

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.

Re: [DNG] lilo development has ended

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

[DNG] lilo development has ended

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

Re: [DNG] lilo development has ended

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

Re: [DNG] lilo development has ended

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

Re: [DNG] lilo development has ended

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

Re: [DNG] lilo development has ended

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

Re: [DNG] lilo development has ended

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. > >

Re: [DNG] lilo development has ended

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

Re: [Dng] LILO

2015-02-08 22:13 GMT+01:00 T.J. Duchene t.j.duch...@gmail.com: On Sunday, February 08, 2015 12:00:01 PM dng-requ...@lists.dyne.org wrote: From: Daniel Cegiełka daniel.cegie...@gmail.com To: bill.m.m...@gmail.com CC: Dng@lists.dyne.org Date: Today 04:01:42 AM NOTE: I plan to finish

Re: [Dng] LILO

I'm not really a fan of any bootloaders but grub2 has always worked which is more than i can say for other bootloaders. -- Gravis On Sun, Feb 8, 2015 at 4:50 PM, Daniel Cegiełka daniel.cegie...@gmail.com wrote: 2015-02-08 22:13 GMT+01:00 T.J. Duchene t.j.duch...@gmail.com: On Sunday, February

Re: [Dng] LILO

From my perspective, Grub2 is the systemd or bootloaders. grub2 is well tested, does only one thing, has no interdependencies and is easily removed/replaced. so tell me, how is it the systemd of boatloaders? --Gravis On Sun, Feb 8, 2015 at 5:30 PM, Steve Litt sl...@troubleshooters.com wrote:

Re: [Dng] LILO

I use linux even without partition... with Grub 2 :) In this thread you can note that the Grub 2 does not have too many fans. In my opinion, the best choice is extlinux... but we discuss the same topic in two threads. Apologies. I get the list in digest format, and clearly missed that.

Re: [Dng] LILO

On Sun, 08 Feb 2015, Gravis wrote: sure configuring it may be a mess but it works I haven't looked deeply into it, but I also feel annoyed by the overcomplication of grub2 compared to its predecessor. now am I wrong to think that most of the cruft on its configuration is added by the current

Re: [Dng] LILO

On Mon, 9 Feb 2015 01:45:43 + Jaromil jaro...@dyne.org wrote: now am I wrong to think that most of the cruft on its configuration is added by the current way Debian handles it? I'm on Gentoo. I am supposed to have grub 2 installed. But, I can send information on how things are set up

Re: [Dng] LILO

On Sun, 8 Feb 2015 17:47:42 -0500 Gravis rin...@adaptivetime.com wrote: From my perspective, Grub2 is the systemd or bootloaders. grub2 is well tested, does only one thing, has no interdependencies and is easily removed/replaced. so tell me, how is it the systemd of boatloaders?

Re: [Dng] LILO

On February 8, 2015 at 8:06 PM Gravis rin...@adaptivetime.com wrote: You spend twenty minutes reviewing docs on which of the many files to put your modifications in and the commands to use, you do it just that way, and it doesn't work. if it's not working then either documentation is