An example of ?

What I had in mind was probably an example of quick, error free and painless transition from Elilo to grub.
Mostly just an ill-considered comment...

I have just reread a few wise comments here on the forum
Except 2-3 parameters, I use the standard /etc/default/grub

e.g.
https://www.linuxquestions.org/quest...tc-4175699913/

https://www.linuxquestions.org/quest...on-4175705408/

2 members found this post helpful.

Thanks! I am actually happy with Elilo - I do not dual boot and kernel updates are simplicity itself!

So there is actually no rush to do so, but I have avoided grub long enough and should at least gain a working familiarity with it.

A question that comes to mind, possibly also ill-considered: Is there any reason you cannot leave a working Elilo in place for selection from the EFI firmware boot selector, and install a grub option alongside or in addition to it as the default? So if you have difficulty configuring grub you could manually boot via the EFI firmware and Elilo? As said I have not thought that all the way through but I am sure someone knows their way around well enough to offer an opinion if not a definitive answer!

EDIT: By the way, for other Elilo users, I use the Elilo chooser from here which was recommended long ago in another thread - makes Elilo menu selection very simple!

I do not plan hat far ahead. I keep my planning to 10 years out.

1 members found this post helpful.

https://www.youtube.com/watch?v=OZeJd5JPQro&t=1116s

This is a good tutorial for UEFI and GRUB on Slackware; I've used it. It works well.

1 members found this post helpful.

Has anyone mentioned going to Disney Land yet?

I had this exact behavior on a couple of HP laptops on 14.2, elilo v3.16. I replaced it with the elilo from 14.1--version 3.14, I think--and I got my row of penguins back.

How did you know that !! :hawkeyes:
I went there on Saturday with my son ...

1 members found this post helpful.

Is it true DisneyLand Paris (aka, Euro Disney) was built on the site of a old U.S. Army base? "They" were in the process of closing all of those post World War II installations when I first arrived in early 1968. IIRC, they were already closed, effective at the end of 1967, and were in the process of being returned to French ownership. Again, IIRC, they were "sold" back to the French for a token amount of one U.S. Dollar each (about 5 Francs, in those days).

Maybe, you probably know better than me
If there was a base at Marne-la-Vallée / Chessy

Well, this thread has certainly strayed off-topic.

Sooooo.... I'll throw in my 2cents worth on the new topic of boot loaders. ;-)

Plain-ol' lilo still works perfectly here on all of my systems
all of which are multi-boot setups.

Machines are... one P-II 266mhz, two intel DualCore, one intel i7)
(the P-II has slackware-14.0 all others are slackware64-current)

OpenDos v7.01 & slackware on the 1st HDD,
slackware on 2nd and even 3rd HDDs
with HDDs ranging in size from 10gig all the way to 1TB

All of the HDDs are partitioned and formatted with plain-ol' MBR booting.

Since even the i7 works 100% perfectly with this setup...
I see no purpose whatsoever in using EFI nor UEFI

I even experimented to see if it would work and sure-enough
lilo booted perfectly to Win10 installed on the 2nd HDD
in one of the intel DualCore machines.

As the old adage goes... If ain't broke, don't fix it. ;-)

----
Oh, here's lilo.conf for the machine with Win10

#Start LILO global section
lba32
boot = /dev/sda
map=/boot/map
append=" vt.default_utf8=0"
prompt
timeout = 50
vga = 858
# End LILO global section
#
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda1
label = SlackWare64
read-only # Partitions should be mounted read-only for checking
# Linux bootable partition config ends
#
# DOS bootable partition config begins
other = /dev/sda3
label = OpenDos_7.01
table = /dev/sda
# DOS bootable partition config ends
#
# Linux bootable partition config begins
image =/15.0b/boot/vmlinuz
root = /dev/sdb3
label = SlackWare64b
read-only # Partitions should be mounted read-only for checking
# Linux bootable partition config ends
#
# Wincrap bootable partition config begins
other = /dev/sdb1
label = WinCrap
table = /dev/sdb
# Wincrap bootable partition config ends

2 members found this post helpful.

So, kswapd can also swap things to a harddrive when there is no swap or the swap is full. It would basically move files that are in RAM that exist on the harddrive back to the harddrive. If interested, this askubuntu thread has more details.

It does seem like Firefox is doing more than simple caching and it sounds like there might be memory leaks. It really is unfortunate how far Firefox has strayed from its roots to be lean and mean. I mean, people are using Seamonkey instead of Firefox because a full "Internet Application Suite" that includes an email and IRC client is less resource intensive than a standalone browser. They started out because IE had stagnated and become a bloated POS, and it seems like Firefox is well on its way to do the same thing.

It is definitely not in -current. Pat even explained why it's not in current.

3 members found this post helpful.

It's strange really, because I have no issues with memory usage, I have plenty and I run very few things, so little memory is actually used, but despite that I had this issue. Perhaps it was not related to the Kernel at all, but other system components. I guess time will tell when Slackware 15 comes out and I use that as my main.

To be frank I hope I will never see that issue again, but on the other hand it would be nice to figure out exactly what it is and report it to the appropriate place to be investigated/fixed.

I was just asking myself, " I Wonder why Pat never included rEFInd" and now I know why.