Just announced an updated version with some changes listed at:
https://www.elivecd.org/news/releases/beta/elive-3-8-1-beta-released/
comments and feedbacks about this version welcome here 
3 Likes
Dang !!! I was just getting used to my current setup. 
how do we easily upgrade to the new kernel & last elieve version, from a current 64 bits install without running the new installer from a USB stick ?
Apparently it's disadvised to upgrade to the 5.3 kernel.
Mine got updated to 5.3 on the first day Buster was updated using "apug". I'm not sure if that is still the case.
You can install a later kernel yourself if you want to but it might create havoc on your installed system.
Only do so if you're encountering hardware problems you need to solve or if there's a security advise to do it.
Use "apse linux-image" to see what's available and then "api linux-image-xxxxx", where xxxxx is the chosen image version. Make sure the version is similar to the one you already have.
1 Like
~ ❯❯❯ apse kernel-image
Sorting... Done
Full Text Search... Done
~ ❯❯❯
sorry my bad.
Should be linux-image all over.
tks
JF
~ ❯❯❯ apse linux-image
Sorting... Done
Full Text Search... Done
linux-headers-4.19.0-5-amd64/buster,now 4.19.37-5 amd64 [installed]
Header files for Linux 4.19.0-5-amd64
linux-headers-4.19.0-6-686/stable 4.19.67-2+deb10u1 i386
Header files for Linux 4.19.0-6-686
linux-headers-4.19.0-6-686-pae/stable 4.19.67-2+deb10u1 i386
Header files for Linux 4.19.0-6-686-pae
linux-headers-4.19.0-6-amd64/stable 4.19.67-2+deb10u1 amd64
Header files for Linux 4.19.0-6-amd64
linux-headers-4.19.0-6-cloud-amd64/stable 4.19.67-2+deb10u1 amd64
Header files for Linux 4.19.0-6-cloud-amd64
linux-headers-4.19.0-6-rt-686-pae/stable 4.19.67-2+deb10u1 i386
Header files for Linux 4.19.0-6-rt-686-pae
linux-headers-4.19.0-6-rt-amd64/stable 4.19.67-2+deb10u1 amd64
Header files for Linux 4.19.0-6-rt-amd64
linux-headers-5.2.0-0.bpo.2-amd64/buster 5.2.9-2~bpo10+1 amd64
Header files for Linux 5.2.0-0.bpo.2-amd64
linux-headers-5.3.0-0.bpo.2-686/buster-backports 5.3.9-2~bpo10+1 i386
Header files for Linux 5.3.0-0.bpo.2-686
linux-headers-5.3.0-0.bpo.2-686-pae/buster-backports 5.3.9-2~bpo10+1 i386
Header files for Linux 5.3.0-0.bpo.2-686-pae
linux-headers-5.3.0-0.bpo.2-amd64/buster-backports 5.3.9-2~bpo10+1 amd64
Header files for Linux 5.3.0-0.bpo.2-amd64
linux-headers-5.3.0-0.bpo.2-cloud-amd64/buster-backports 5.3.9-2~bpo10+1 amd64
Header files for Linux 5.3.0-0.bpo.2-cloud-amd64
linux-image-4.19.0-5-amd64-unsigned/buster,now 4.19.37-5 amd64 [installed]
Linux 4.19 for 64-bit PCs
linux-image-4.19.0-6-686/stable 4.19.67-2+deb10u1 i386
Linux 4.19 for older PCs (signed)
linux-image-4.19.0-6-686-dbg/stable 4.19.67-2+deb10u1 i386
Debug symbols for linux-image-4.19.0-6-686
linux-image-4.19.0-6-686-pae/stable 4.19.67-2+deb10u1 i386
Linux 4.19 for modern PCs (signed)
linux-image-4.19.0-6-686-pae-dbg/stable 4.19.67-2+deb10u1 i386
Debug symbols for linux-image-4.19.0-6-686-pae
linux-image-4.19.0-6-686-pae-unsigned/stable 4.19.67-2+deb10u1 i386
Linux 4.19 for modern PCs
linux-image-4.19.0-6-686-unsigned/stable 4.19.67-2+deb10u1 i386
Linux 4.19 for older PCs
linux-image-4.19.0-6-amd64/stable 4.19.67-2+deb10u1 amd64
Linux 4.19 for 64-bit PCs (signed)
linux-image-4.19.0-6-amd64-dbg/stable 4.19.67-2+deb10u1 amd64
Debug symbols for linux-image-4.19.0-6-amd64
linux-image-4.19.0-6-amd64-unsigned/stable 4.19.67-2+deb10u1 amd64
Linux 4.19 for 64-bit PCs
linux-image-4.19.0-6-cloud-amd64/stable 4.19.67-2+deb10u1 amd64
Linux 4.19 for x86-64 cloud (signed)
linux-image-4.19.0-6-cloud-amd64-dbg/stable 4.19.67-2+deb10u1 amd64
Debug symbols for linux-image-4.19.0-6-cloud-amd64
linux-image-4.19.0-6-cloud-amd64-unsigned/stable 4.19.67-2+deb10u1 amd64
Linux 4.19 for x86-64 cloud
linux-image-4.19.0-6-rt-686-pae/stable 4.19.67-2+deb10u1 i386
Linux 4.19 for modern PCs, PREEMPT_RT (signed)
linux-image-4.19.0-6-rt-686-pae-dbg/stable 4.19.67-2+deb10u1 i386
Debug symbols for linux-image-4.19.0-6-rt-686-pae
linux-image-4.19.0-6-rt-686-pae-unsigned/stable 4.19.67-2+deb10u1 i386
Linux 4.19 for modern PCs, PREEMPT_RT
linux-image-4.19.0-6-rt-amd64/stable 4.19.67-2+deb10u1 amd64
Linux 4.19 for 64-bit PCs, PREEMPT_RT (signed)
linux-image-4.19.0-6-rt-amd64-dbg/stable 4.19.67-2+deb10u1 amd64
Debug symbols for linux-image-4.19.0-6-rt-amd64
linux-image-4.19.0-6-rt-amd64-unsigned/stable 4.19.67-2+deb10u1 amd64
Linux 4.19 for 64-bit PCs, PREEMPT_RT
linux-image-5.2.0-0.bpo.2-amd64/buster 5.2.9-2~bpo10+1 amd64
Linux 5.2 for 64-bit PCs (signed)
linux-image-5.3.0-0.bpo.2-686/buster-backports 5.3.9-2~bpo10+1 i386
Linux 5.3 for older PCs (signed)
linux-image-5.3.0-0.bpo.2-686-dbg/buster-backports 5.3.9-2~bpo10+1 i386
Debug symbols for linux-image-5.3.0-0.bpo.2-686
linux-image-5.3.0-0.bpo.2-686-pae/buster-backports 5.3.9-2~bpo10+1 i386
Linux 5.3 for modern PCs (signed)
linux-image-5.3.0-0.bpo.2-686-pae-dbg/buster-backports 5.3.9-2~bpo10+1 i386
Debug symbols for linux-image-5.3.0-0.bpo.2-686-pae
linux-image-5.3.0-0.bpo.2-686-pae-unsigned/buster-backports 5.3.9-2~bpo10+1 i386
Linux 5.3 for modern PCs
linux-image-5.3.0-0.bpo.2-686-unsigned/buster-backports 5.3.9-2~bpo10+1 i386
Linux 5.3 for older PCs
linux-image-5.3.0-0.bpo.2-amd64/buster-backports 5.3.9-2~bpo10+1 amd64
Linux 5.3 for 64-bit PCs (signed)
linux-image-5.3.0-0.bpo.2-amd64-dbg/buster-backports 5.3.9-2~bpo10+1 amd64
Debug symbols for linux-image-5.3.0-0.bpo.2-amd64
linux-image-5.3.0-0.bpo.2-amd64-unsigned/buster-backports 5.3.9-2~bpo10+1 amd64
Linux 5.3 for 64-bit PCs
linux-image-5.3.0-0.bpo.2-cloud-amd64/buster-backports 5.3.9-2~bpo10+1 amd64
Linux 5.3 for x86-64 cloud (signed)
linux-image-5.3.0-0.bpo.2-cloud-amd64-dbg/buster-backports 5.3.9-2~bpo10+1 amd64
Debug symbols for linux-image-5.3.0-0.bpo.2-cloud-amd64
linux-image-5.3.0-0.bpo.2-cloud-amd64-unsigned/buster-backports 5.3.9-2~bpo10+1 amd64
Linux 5.3 for x86-64 cloud
linux-image-686/stable 4.19+105+deb10u1 i386
Linux for older PCs (meta-package)
linux-image-686-dbg/stable 4.19+105+deb10u1 i386
Debugging symbols for Linux 686 configuration (meta-package)
linux-image-686-pae/stable 4.19+105+deb10u1 i386
Linux for modern PCs (meta-package)
linux-image-686-pae-dbg/stable 4.19+105+deb10u1 i386
Debugging symbols for Linux 686-pae configuration (meta-package)
linux-image-amd64/buster-backports 5.3.9-2~bpo10+1 amd64
Linux for 64-bit PCs (meta-package)
linux-image-amd64-dbg/buster-backports 5.3.9-2~bpo10+1 amd64
Debugging symbols for Linux amd64 configuration (meta-package)
linux-image-amd64-signed-template/buster 4.19.37-5 amd64
Template for signed linux-image packages for amd64
linux-image-cloud-amd64/buster-backports 5.3.9-2~bpo10+1 amd64
Linux for x86-64 cloud (meta-package)
linux-image-cloud-amd64-dbg/buster-backports 5.3.9-2~bpo10+1 amd64
Debugging symbols for Linux cloud-amd64 configuration (meta-package)
linux-image-i386-signed-template/stable 4.19.67-2+deb10u1 i386
Template for signed linux-image packages for i386
linux-image-rt-686-pae/stable 4.19+105+deb10u1 i386
Linux for modern PCs (meta-package), PREEMPT_RT
linux-image-rt-686-pae-dbg/stable 4.19+105+deb10u1 i386
Debugging symbols for Linux rt-686-pae configuration (meta-package)
linux-image-rt-amd64/buster-backports 5.2+107~bpo10+1 amd64
Linux for 64-bit PCs (meta-package), PREEMPT_RT
linux-image-rt-amd64-dbg/buster-backports 5.2+107~bpo10+1 amd64
Debugging symbols for Linux rt-amd64 configuration (meta-package)
Once installed and you find it does not work as expected you can always to choose to boot up with your older kernel through "advance options ..." in the Grub boot menu.
tks
do you know which one in the list is the right one ?
Depends on the hardware you've got.
Just use the one with the same naming scheme as your current one.
In your case you have "linux-image-4.19.0-5-amd64-unsigned/buster,now 4.19.37-5 amd64 [installed]" according to your output so:
"linux-image-5.2.0-0.bpo.2-amd64"
Should be the one.
Where I'm taking @Thanatermesis stand that 5.3.0 isn't advisable + Elive 3.8.1 Beta comes with the 5.2 kernel too.
And might as well do as the installer asks and install the headers too. This is beta after all and you need them to have the necessary modules built.
After that you need to reboot to use the new kernel.
1 Like
It definitely uses much less ram compared to 3.0 stable in a VirtualBox VM—3.0 was just slow 
Great work @Thanatermesis!!!
On a first off:
I notice that the "terminal" option in the menu is still set to "x-terminal-emulator".
This does not have a coherent icon in the dock when opened, terminology does.
I propose to have it set to "terminology" seeing it works fine now that E17 isn't there anymore.
It's simply better to have a proper icon.
1 Like
the integrated elive-upgrader tool will take care of everything needed 
, in other words, you don't need to
BTW i dont suggest upgrade kernel to the version 5.3, is a bit buggy, this is fixed in the new installer (to not allow it to be upgraded automatically)
thanks for the feedback e17 is a bit slow in rendering, we will see if the future e23 is improved on that sense 
ok this is a bit tricky and not easy to implement it correctly.... basically the thing is that x-terminal-emulator is assigned to a default terminal, in the Live boot time, if your machine has low resources its automatically switched to urxvt, if you have enought minimal resources is using terminology
this means that to make it correctly dynamic, is needed to use x-terminal-emulator instead of one those two
1 Like
Hmmm, this is on my X1 carbon Thinkpad with plenty of resources.
IIRC there was a period where terminology broke stuff for e16 and I thus suspected that was a reason why it wasn't enabled.
Apparently the auto switching (or setting to default) of terminology is broken in E16.
- It makes the DE look stupid IMO.
On E23 it works fine.
Or am I the only one with this issue? 
well just installed uefi version as an upgrade on previous install worked perfect no hicups thanks guys
1 Like
How would you do the advertised "install from harddisk"? Or was that functionality removed a while ago?
Well that FROM functionality was never there but "install TO harddisk" has. Look in the menus under the "Elive" category if it doesn't pop-up automagically.
1 Like
Oops, I was checking out old versions of the site on this wayback machine site:
https://forum.elivelinux.org/t/3-8-1-beta-experiences/1671
and I misunderstood. It said you could use your live media from your existing Elive install to reinstall.
No media needed: do you want to reinstall Elive but you don’t want to use a cdrom or USB? you can boot the live mode directly from your hard disk in an automated way and install it without problems
Sorry about the interruption
I manually upgarded to 5.2.0.0 and it's working well
~ ❯❯❯ uname -a
Linux Elive-Desktop 5.2.0-0.bpo.2-amd64 #1 SMP Debian 5.2.9-2~bpo10+1 (2019-08-25) x86_64 GNU/Linux
Well, not exactly sure about the wording on old versions of the site but ......
you can indeed create a Live-USB from your installed system through a menu option in the Elive category.
What it does is create/write the flashdrive for you using an available .iso or downloading one from the net.
It is NOT a copy of your existing installation.
