Apart from my own fat fingers, the pxe install of 15.5 is going well. currently less than 200 of 900 packages left. context - pxe+ssh install, from local mirror, root+home filesystem is jfs. Okay, all done before I finished typing. Slightly exotic - I'm trying to boot with lilo, and I can't even run lilo. "No such file or directory". (booted installer, chroot into new system with bind mounts): discompi8:/ # lilo -V bash: /sbin/lilo: No such file or directory discompi8:/ # l /sbin/lilo -rwxr-xr-x 1 root root 186896 May 16 2020 /sbin/lilo* discompi8:/ # strace lilo -V execve("/sbin/lilo", ["lilo", "-V"], 0x7ffc8e28c2e8 /* 40 vars */) = -1 ENOENT (No such file or directory) strace: exec: No such file or directory +++ exited with 1 +++ Granted, I have probahly not installed anything on real iron with lilo in two-three years or more, I must be missing something. -- Per Jessen, Zürich (12.8°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On 21.02.2023 20:23, Per Jessen wrote:
Apart from my own fat fingers, the pxe install of 15.5 is going well. currently less than 200 of 900 packages left.
context - pxe+ssh install, from local mirror, root+home filesystem is jfs.
Okay, all done before I finished typing.
Slightly exotic - I'm trying to boot with lilo, and I can't even run lilo. "No such file or directory".
Where it comes from? # Project # Package DISCONTINUED:openSUSE:10.3 lilo DISCONTINUED:openSUSE:11.1 lilo DISCONTINUED:openSUSE:11.2 lilo DISCONTINUED:openSUSE:11.3 lilo DISCONTINUED:openSUSE:11.3:Update lilo SUSE:SLE-12:GA lilo openSUSE:11.4 lilo openSUSE:12.1 lilo openSUSE:12.2 lilo openSUSE:12.3 lilo openSUSE:13.1 lilo openSUSE:13.1:Update lilo openSUSE:13.2 lilo openSUSE:42:Rings:1-MinimalX lilo openSUSE:Leap:15.0 lilo openSUSE:Leap:15.0:Rings:1-MinimalX lilo openSUSE:Leap:15.1 lilo openSUSE:Leap:15.1:Rings:1-MinimalX lilo openSUSE:Leap:42.1 lilo openSUSE:Leap:42.1:Rings:1-MinimalX lilo openSUSE:Leap:42.2 lilo openSUSE:Leap:42.3 lilo openSUSE:Maintenance:12.2_ArchPorts lilo
(booted installer, chroot into new system with bind mounts):
discompi8:/ # lilo -V bash: /sbin/lilo: No such file or directory discompi8:/ # l /sbin/lilo -rwxr-xr-x 1 root root 186896 May 16 2020 /sbin/lilo* discompi8:/ # strace lilo -V execve("/sbin/lilo", ["lilo", "-V"], 0x7ffc8e28c2e8 /* 40 vars */) = -1 ENOENT (No such file or directory) strace: exec: No such file or directory +++ exited with 1 +++
Granted, I have probahly not installed anything on real iron with lilo in two-three years or more, I must be missing something.
Andrei Borzenkov wrote:
On 21.02.2023 20:23, Per Jessen wrote:
Apart from my own fat fingers, the pxe install of 15.5 is going well. currently less than 200 of 900 packages left.
context - pxe+ssh install, from local mirror, root+home filesystem is jfs.
Okay, all done before I finished typing.
Slightly exotic - I'm trying to boot with lilo, and I can't even run lilo. "No such file or directory".
Where it comes from?
Built myself, but has worked on 15.3 with no problems. This one I just copied from a 15.3 system. -- Per Jessen, Zürich (5.4°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
Per Jessen wrote:
Andrei Borzenkov wrote:
On 21.02.2023 20:23, Per Jessen wrote:
Slightly exotic - I'm trying to boot with lilo, and I can't even run lilo. "No such file or directory".
Where it comes from?
Built myself, but has worked on 15.3 with no problems. This one I just copied from a 15.3 system.
Correction, that lilo is from Leap 15.2. per@office38:~> rpm -qf /sbin/lilo lilo-24.2-lp152.3.8.x86_64 -- Per Jessen, Zürich (9.2°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On 2023-02-22 09:44, Per Jessen wrote:
Per Jessen wrote:
Andrei Borzenkov wrote:
On 21.02.2023 20:23, Per Jessen wrote:
Slightly exotic - I'm trying to boot with lilo, and I can't even run lilo. "No such file or directory".
Where it comes from?
Built myself, but has worked on 15.3 with no problems. This one I just copied from a 15.3 system.
Correction, that lilo is from Leap 15.2.
per@office38:~> rpm -qf /sbin/lilo lilo-24.2-lp152.3.8.x86_64
So the program exists, and claims the lilo file doesn't exist? I don't understand. I just drank a cup of coffee, I must be missing something. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Carlos E. R. wrote:
On 2023-02-22 09:44, Per Jessen wrote:
per@office38:~> rpm -qf /sbin/lilo lilo-24.2-lp152.3.8.x86_64
So the program exists, and claims the lilo file doesn't exist? I don't understand. I just drank a cup of coffee, I must be missing something.
No, you have understood perfectly well :-) - that is the situation. /sbin/lilo exists, but when bash tries to run it with execve(), suddenly it seems to "not exist". I'm guessing some permissions/apparmor thing, but .... I have just now booted the installer from 15.2 (just in case), but same problem. -- Per Jessen, Zürich (9.5°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On 2023-02-22 10:05, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-02-22 09:44, Per Jessen wrote:
per@office38:~> rpm -qf /sbin/lilo lilo-24.2-lp152.3.8.x86_64
So the program exists, and claims the lilo file doesn't exist? I don't understand. I just drank a cup of coffee, I must be missing something.
No, you have understood perfectly well :-) - that is the situation.
/sbin/lilo exists, but when bash tries to run it with execve(), suddenly it seems to "not exist". I'm guessing some permissions/apparmor thing, but ....
Run "aa-logprof". It will tell you immediately.
I have just now booted the installer from 15.2 (just in case), but same problem.
-- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Carlos E. R. wrote:
On 2023-02-22 10:05, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-02-22 09:44, Per Jessen wrote:
per@office38:~> rpm -qf /sbin/lilo lilo-24.2-lp152.3.8.x86_64
So the program exists, and claims the lilo file doesn't exist? I don't understand. I just drank a cup of coffee, I must be missing something.
No, you have understood perfectly well :-) - that is the situation.
/sbin/lilo exists, but when bash tries to run it with execve(), suddenly it seems to "not exist". I'm guessing some permissions/apparmor thing, but ....
Run "aa-logprof". It will tell you immediately.
BTDT :-) discompi8:/ # aa-logprof ERROR: It seems AppArmor was not started. Please enable AppArmor and try again. -- Per Jessen, Zürich (11.4°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On Wed, Feb 22, 2023 at 11:44 AM Per Jessen <per@jessen.ch> wrote:
Per Jessen wrote:
Andrei Borzenkov wrote:
On 21.02.2023 20:23, Per Jessen wrote:
Slightly exotic - I'm trying to boot with lilo, and I can't even run lilo. "No such file or directory".
Where it comes from?
Built myself, but has worked on 15.3 with no problems. This one I just copied from a 15.3 system.
Correction, that lilo is from Leap 15.2.
per@office38:~> rpm -qf /sbin/lilo lilo-24.2-lp152.3.8.x86_64
There is no lilo in Leap 15.2 "official" repositories. So the question remains - where does it come from.
Andrei Borzenkov wrote:
On Wed, Feb 22, 2023 at 11:44 AM Per Jessen <per@jessen.ch> wrote:
per@office38:~> rpm -qf /sbin/lilo lilo-24.2-lp152.3.8.x86_64
There is no lilo in Leap 15.2 "official" repositories. So the question remains - where does it come from.
See what I just replied to Felix, "rpm -qi" output. However, the thing is - it works fine in 15.1, 15.2 and 15.3. The error I'm getting with 15.5 is weird. If there was something wrong with lilo "itself", I wouldn't be asking here, but this "No such file or directory" ??? -- Per Jessen, Zürich (10.9°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
Per Jessen wrote:
Andrei Borzenkov wrote:
On Wed, Feb 22, 2023 at 11:44 AM Per Jessen <per@jessen.ch> wrote:
per@office38:~> rpm -qf /sbin/lilo lilo-24.2-lp152.3.8.x86_64
There is no lilo in Leap 15.2 "official" repositories. So the question remains - where does it come from.
See what I just replied to Felix, "rpm -qi" output. However, the thing is - it works fine in 15.1, 15.2 and 15.3. The error I'm getting with 15.5 is weird.
Oh, btw, lilo also works fine on my two TW systems. -- Per Jessen, Zürich (11.3°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
Per Jessen composed on 2023-02-21 18:23 (UTC+0100):
Slightly exotic - I'm trying to boot with lilo, and I can't even run lilo. "No such file or directory". ... Granted, I have probahly not installed anything on real iron with lilo in two-three years or more, I must be missing something.
# inxi -S System: Host: big41 Kernel: 4.12.14-lp151.28.67-default arch: x86_64 bits: 64 Console: pty pts/0 Distro: openSUSE Leap 15.1 # zypse lilo | elilo | package | 3.16-lp151.3.1 | x86_64 | OSS | lilo | package | 24.2-lp151.2.3 | x86_64 | OSS # # inxi -S System: Host: gb970 Kernel: 5.3.18-lp152.106-default arch: x86_64 bits: 64 Console: pty pts/0 Distro: openSUSE Leap 15.2 # zypse lilo | elilo | package | 3.16-lp152.4.5 | x86_64 | OSS # -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
Felix Miata wrote:
Per Jessen composed on 2023-02-21 18:23 (UTC+0100):
Slightly exotic - I'm trying to boot with lilo, and I can't even run lilo. "No such file or directory". ... Granted, I have probahly not installed anything on real iron with lilo in two-three years or more, I must be missing something.
# inxi -S System: Host: big41 Kernel: 4.12.14-lp151.28.67-default arch: x86_64 bits: 64 Console: pty pts/0 Distro: openSUSE Leap 15.1 # zypse lilo | elilo | package | 3.16-lp151.3.1 | x86_64 | OSS | lilo | package | 24.2-lp151.2.3 | x86_64 | OSS
Ah good point Felix - my lilo is from leap 15.2, not home built as I wrote to Andrei. -- Per Jessen, Zürich (8.2°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
Per Jessen composed on 2023-02-22 09:44 (UTC+0100):
Felix Miata wrote:
# inxi -S System: Host: big41 Kernel: 4.12.14-lp151.28.67-default arch: x86_64 bits: 64 Console: pty pts/0 Distro: openSUSE Leap 15.1 # zypse lilo | elilo | package | 3.16-lp151.3.1 | x86_64 | OSS | lilo | package | 24.2-lp151.2.3 | x86_64 | OSS
Ah good point Felix - my lilo is from leap 15.2
It may have survived in your 15.2 from its upgrade from 15.1, but it wasn't provided by 15.2, unless from some optional repo mine doesn't have configured. I've never had reason to have lilo on any *SUSE installation. I'm still using Legacy Grub everywhere I'm not using UEFI & GPT, which here means most of 30+ multiboot PCs. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 2023-02-22 10:01, Felix Miata wrote:
Per Jessen composed on 2023-02-22 09:44 (UTC+0100):
Felix Miata wrote:
# inxi -S System: Host: big41 Kernel: 4.12.14-lp151.28.67-default arch: x86_64 bits: 64 Console: pty pts/0 Distro: openSUSE Leap 15.1 # zypse lilo | elilo | package | 3.16-lp151.3.1 | x86_64 | OSS | lilo | package | 24.2-lp151.2.3 | x86_64 | OSS
Ah good point Felix - my lilo is from leap 15.2
It may have survived in your 15.2 from its upgrade from 15.1, but it wasn't provided by 15.2, unless from some optional repo mine doesn't have configured.
I've never had reason to have lilo on any *SUSE installation. I'm still using Legacy Grub everywhere I'm not using UEFI & GPT, which here means most of 30+ multiboot PCs.
"rpm -qi lilo" will tell where it came from - if that system is working. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Felix Miata wrote:
Per Jessen composed on 2023-02-22 09:44 (UTC+0100):
Felix Miata wrote:
# inxi -S System: Host: big41 Kernel: 4.12.14-lp151.28.67-default arch: x86_64 bits: 64 Console: pty pts/0 Distro: openSUSE Leap 15.1 # zypse lilo | elilo | package | 3.16-lp151.3.1 | x86_64 | OSS | lilo | package | 24.2-lp151.2.3 | x86_64 | OSS
Ah good point Felix - my lilo is from leap 15.2
It may have survived in your 15.2 from its upgrade from 15.1, but it wasn't provided by 15.2, unless from some optional repo mine doesn't have configured.
Hmm, this is from my 15.2 system: per@office38:~> rpm -qf /sbin/lilo lilo-24.2-lp152.3.8.x86_64 office38:~ # rpm -qi lilo Name : lilo Version : 24.2 Release : lp152.3.8 Architecture: x86_64 Install Date: Mon Jun 15 11:17:03 2020 Group : System/Boot Size : 302126 License : BSD-3-Clause Signature : RSA/SHA256, Sat May 16 19:44:33 2020, Key ID b88b2fd43dbdc284 Source RPM : lilo-24.2-lp152.3.8.src.rpm Build Date : Sat May 16 19:44:25 2020 Build Host : lamb02 Relocations : (not relocatable) Packager : https://bugs.opensuse.org Vendor : openSUSE URL : https://github.com/openSUSE/lilo Summary : The Linux Loader, a Boot Menu
I've never had reason to have lilo on any *SUSE installation.
We only ever use lilo - I can type up a config from memory, it's just way easier. I'm old fashioned :-) -- Per Jessen, Zürich (10.1°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
Per Jessen composed on 2023-02-22 10:11 (UTC+0100):
Felix Miata wrote:
I've never had reason to have lilo on any *SUSE installation.
We only ever use lilo - I can type up a config from memory, it's just way easier. I'm old fashioned :-)
So do/are most Slackware users. The way I remember it, any defect in lilo.conf that resulted in no boot meant boot some rescue system so as to be able to chroot, fix lilo.conf, then execute lilo. With Grub in many if not most cases, a boot config problem can be cured from within the Grub shell so a boot can proceed from a minor on-the-fly edit. That difference to me is like comparing a hand crank start model T to the first Lincoln. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
Felix Miata wrote:
Per Jessen composed on 2023-02-22 10:11 (UTC+0100):
Felix Miata wrote:
I've never had reason to have lilo on any *SUSE installation.
We only ever use lilo - I can type up a config from memory, it's just way easier. I'm old fashioned :-)
So do/are most Slackware users. The way I remember it, any defect in lilo.conf that resulted in no boot meant boot some rescue system so as to be able to chroot, fix lilo.conf, then execute lilo.
That's roughly it, but any defect in the config will show the minute you run lilo. Besides, how much can you get wrong? This is the minimum config: boot = /dev/sda image = /boot/vmlinuz root = /dev/sda1 initrd = /boot/initrd
That difference to me is like comparing a hand crank start model T to the first Lincoln.
Don't get me wrong - I am in no way arguing that anybody else should use lilo, but for me, booting an installer over pxe, chroot'ing and typing in those four lines in vim, then 'lilo' - that's just way easier than any grub incantation. Of course, here's my age showing again, I just don't like all those wrappers upon wrappers upon wrappers. I prefer KISS and a thorough understanding what I'm doing. When I don't understand, I ask Andrei. -- Per Jessen, Zürich (11.7°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
Per Jessen composed on 2023-02-22 04:49 (UTC-0500):
any defect in the config will show the minute you run lilo.
Not the the defect that is valid but provides something different from what you intended.
Besides, how much can you get wrong? This is the minimum config:
boot = /dev/sda image = /boot/vmlinuz root = /dev/sda1 initrd = /boot/initrd
But you can't amend on the fly. If I want some troubleshooting parameter or a different runlevel, it takes only seconds at runtime to edit Grub on the fly.
That difference to me is like comparing a hand crank start model T to the first Lincoln.
Don't get me wrong - I am in no way arguing that anybody else should use lilo, but for me, booting an installer over pxe, chroot'ing and typing in those four lines in vim, then 'lilo' - that's just way easier than any grub incantation.
That's easier than a few seconds to edit one line, maybe two, to make a temporary/one-shot troubleshooting adjustment?
Of course, here's my age showing again, I just don't like all those wrappers upon wrappers upon wrappers. I prefer KISS and a thorough understanding what I'm doing. When I don't understand, I ask Andrei.
Fine when you have time to wait, which can be infinite with Andrei. ;) I like KISS too, which is why on 100% of installations without UEFI/GPT I'm still using Legacy Grub - menu.lst or Grub shell, nothing else, unless you include that darling openSUSE Gfxboot with penguin set to 100. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
Felix Miata wrote:
Per Jessen composed on 2023-02-22 04:49 (UTC-0500):
any defect in the config will show the minute you run lilo.
Not the the defect that is valid but provides something different from what you intended.
I guess - if I mistype something in the kernel arguments - it can be a little complicated with a Xen server.
Besides, how much can you get wrong? This is the minimum config:
boot = /dev/sda image = /boot/vmlinuz root = /dev/sda1 initrd = /boot/initrd
But you can't amend on the fly. If I want some troubleshooting parameter or a different runlevel, it takes only seconds at runtime to edit Grub on the fly.
Sorry, I don't understand. I edit lilo.conf, run 'lilo', then reboot. afaik, it's no different with grub ? Or when you're booting up you mean? works fine with lilo too.
That difference to me is like comparing a hand crank start model T to the first Lincoln.
Don't get me wrong - I am in no way arguing that anybody else should use lilo, but for me, booting an installer over pxe, chroot'ing and typing in those four lines in vim, then 'lilo' - that's just way easier than any grub incantation.
That's easier than a few seconds to edit one line, maybe two, to make a temporary/one-shot troubleshooting adjustment?
I don't really understand what you are talking about. Above, I am talking about fixing a system that isn't booting. For instance, my current leap 15.5 installation. Otherwise, it's typically situations that involve changing the hardware, moving root disks and such. -- Per Jessen, Zürich (14.7°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On 21.02.2023 20:23, Per Jessen wrote:
Apart from my own fat fingers, the pxe install of 15.5 is going well. currently less than 200 of 900 packages left.
context - pxe+ssh install, from local mirror, root+home filesystem is jfs.
Okay, all done before I finished typing.
Slightly exotic - I'm trying to boot with lilo, and I can't even run lilo. "No such file or directory".
(booted installer, chroot into new system with bind mounts):
discompi8:/ # lilo -V bash: /sbin/lilo: No such file or directory discompi8:/ # l /sbin/lilo -rwxr-xr-x 1 root root 186896 May 16 2020 /sbin/lilo* discompi8:/ # strace lilo -V execve("/sbin/lilo", ["lilo", "-V"], 0x7ffc8e28c2e8 /* 40 vars */) = -1 ENOENT (No such file or directory) strace: exec: No such file or directory +++ exited with 1 +++
Granted, I have probahly not installed anything on real iron with lilo in two-three years or more, I must be missing something.
bor@localhost:~> ./office38-lilo -V bash: ./office38-lilo: No such file or directory bor@localhost:~> file office38-lilo office38-lilo: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, BuildID[sha1]=3a7c211899dafdc1080dd1ebc0714ed17ac1b55e, for GNU/Linux 3.2.0, stripped bor@localhost:~> ll /lib/ld-linux.so.2 ls: cannot access '/lib/ld-linux.so.2': No such file or directory bor@localhost:~> grep -w PRETTY_NAME /etc/os-release PRETTY_NAME="openSUSE Leap 15.4" bor@localhost:~>
Andrei Borzenkov wrote:
bor@localhost:~> ./office38-lilo -V bash: ./office38-lilo: No such file or directory bor@localhost:~> file office38-lilo office38-lilo: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, BuildID[sha1]=3a7c211899dafdc1080dd1ebc0714ed17ac1b55e, for GNU/Linux 3.2.0, stripped bor@localhost:~> ll /lib/ld-linux.so.2 ls: cannot access '/lib/ld-linux.so.2': No such file or directory
Yeah, I have just reached that point myself :-( I copied over the needed libs from another box, and it's all working. I guess I have really not done a real iron installation (except for various arm boards) from scratch since leap 15.1 - where lilo was available and the 32bit runtime was installed as well. Next step is to install the 32bit runtime on $subj. Thanks for the extra pair of eyes. -- Per Jessen, Zürich (10.8°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
Per Jessen wrote:
Granted, I have probahly not installed anything on real iron with lilo in two-three years or more, I must be missing something.
Indeed - as already reported yesterday, I had neglected to install the 32bit runtime. So, zypper in glibc-32bit libdevmapper-32bit. All sorted. One last hurdle - I had to manually unblacklist 'jfs' and rebuild the initrd. No big deal, I think that's to be expected. Status: leap 15.5 beta is running fine here, albeit text-only. -- Per Jessen, Zürich (10.2°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
participants (4)
-
Andrei Borzenkov -
Carlos E. R. -
Felix Miata -
Per Jessen