From Newsgroup: alt.os.linux.debian

System description
1. Dell Latitude E6410
2. Grub 2.04-20 [label displayed above boot menu]
Debian Bullseye [11.1] on SDA1
Debian Stretch [9.13] on SDA7 - my day-to-day system
3. 13 GB swap space available at sda5

Questions

When I boot to Stretch, error/warning messages go by to fast to read.
Can they be retrieved after system is running?

How do I automatically enable swap when booting?

[This preparation for updating browser and OS]

TIA

--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.debian

On 2024-02-07, Richard Owlett wrote:

System description
1. Dell Latitude E6410
2. Grub 2.04-20 [label displayed above boot menu]
Debian Bullseye [11.1] on SDA1
Debian Stretch [9.13] on SDA7 - my day-to-day system
3. 13 GB swap space available at sda5

Questions

When I boot to Stretch, error/warning messages go by to fast to read.
Can they be retrieved after system is running?

Should be in /var/log/boot or dmesg. I can't remember if stretch uses
systemd, but if it does, you'll likely need some invocation of
journalctl (but I don't have a system to verify a quick google search,
so don't want to lead too far astray)

How do I automatically enable swap when booting?

have an entry in /etc/fstab to load the swap.

UUID=[THE_UUID] none swap sw 0 0

or with your /dev/sda5

/dev/sda5 none swap 0 0
--
|_|O|_|
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.debian

On 02/07/2024 09:30 AM, Dan Purgert wrote:

On 2024-02-07, Richard Owlett wrote:

System description
1. Dell Latitude E6410
2. Grub 2.04-20 [label displayed above boot menu]
Debian Bullseye [11.1] on SDA1
Debian Stretch [9.13] on SDA7 - my day-to-day system
3. 13 GB swap space available at sda5

Questions

When I boot to Stretch, error/warning messages go by to fast to read.
Can they be retrieved after system is running?

Should be in /var/log/boot or dmesg. I can't remember if stretch uses systemd, but if it does, you'll likely need some invocation of
journalctl (but I don't have a system to verify a quick google search,
so don't want to lead too far astray)

How do I automatically enable swap when booting?

have an entry in /etc/fstab to load the swap.

UUID=[THE_UUID] none swap sw 0 0

or with your /dev/sda5

/dev/sda5 none swap 0 0

The last line works fine.
Was an obsolete entry of "UUID=[THE_UUID] none swap sw 0 0" form.
Now boots *FASTER* and without any error/warning messages ;}!
Thanks.


--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.debian

On 2/7/24 13:36, Richard Owlett wrote:

On 02/07/2024 09:30 AM, Dan Purgert wrote:

On 2024-02-07, Richard Owlett wrote:

System description
-a-a-a 1. Dell Latitude E6410
-a-a-a 2. Grub 2.04-20-a-a-a [label displayed above boot menu]
-a-a-a-a-a-a-a-a-a Debian Bullseye [11.1] on SDA1
-a-a-a-a-a-a-a-a-a Debian Stretch-a [9.13] on SDA7 - my day-to-day system >>> -a-a-a 3. 13 GB swap space available at sda5

Questions

When I boot to Stretch, error/warning messages go by to fast to read.
Can they be retrieved after system is running?

Should be in /var/log/boot or dmesg.-a I can't remember if stretch uses
systemd, but if it does, you'll likely need some invocation of
journalctl (but I don't have a system to verify a quick google search,
so don't want to lead too far astray)

How do I automatically enable swap when booting?

have an entry in /etc/fstab to load the swap.

-a-a-a-a UUID=[THE_UUID]-a none-a swap sw-a 0 0

or with your /dev/sda5
-a-a-a-a /dev/sda5-a none-a swap-a 0-a 0

The last line works fine.
Was an obsolete entry of "UUID=[THE_UUID]-a none-a swap sw-a 0 0" form.
Now boots *FASTER* and without any error/warning messages ;}!
Thanks.

I use Devuan (and a few others) with such lines

# file /etc/fstab
/dev/sda7 / ext4 defaults 0 0
/dev/sda10 swap swap defaults,nofail 0 0
/dev/sdb15 /0/adt ext4 defaults,nofail 0 2
/dev/sdc9 /0/local ext4 defaults,nofail 0 2
#

The 'nofail' means that a no-find of an otherwise unessential mount will
NOT stall/fail the boot. I used device-names in the above to prevent line-breaks but actually use UUID because with several SATA disks
plugged-in all the time device-name confusion is not unthinkable. I
always thought that there should be a kernel argumewnt to massively slow
down the boot and arm 2 keys for interventions: one for snapshots and
another for stepping the process *when I want to trouble-shoot it*.


--- Synchronet 3.21d-Linux NewsLink 1.2