Please Help. Thank you very much.



============ Log ===========

Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following packages were automatically installed and are no longer required:
  efibootmgr libefivar0 libllvm5.0 libqmi-glib1 libqpdf17
Use 'apt autoremove' to remove them.
The following packages will be upgraded:
  file firefox flashplugin-installer libexif12 libmagic1
  libpulse-mainloop-glib0 libpulse0 libpulsedsp libsnapd-glib1 opera-stable
  pulseaudio pulseaudio-module-bluetooth pulseaudio-module-x11
  pulseaudio-utils tzdata
15 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 108 MB of archives.
After this operation, 18.2 MB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
  opera-stable
E: There were unauthenticated packages and -y was used without --allow-unauthenticated

2011-2012 Toshiba Satellite L750D - Windows 7... 4GB RAM... little AMD 2-core... 500GB HDD

Windows disk management shows MBR.

Belarc Advisor finds:  Boot Mode: Legacy BIOS in UEFI (Secure Boot not supported)

I've searched BIOS/firmware pages and do not find CSM or any other indication of disk-type switches.  It seems like this Hitachi HDD is GPT/UEFI but the firmware limits it to BIOS/MBR.  There is no 'Secure Boot's switch.  There is a "Normal/Fast" boot switch set "Normal".  Nothing else other than an "Enabled" USB Legacy to facilitate using mouse/keyboard not OS supported for USB.

I'm asking so I can install Linux Lite the way I'd like to with least potential for problems... fixings... reinstalls... ???
---------------------------------------------------

What I want to do:

Linux-only machine to be used as backup for other computers, and so Sarah can learn a little Linux, and to install other Linux OS just to see what they are like.  There would be NO shared data between OS's. Machine would not be used as backup storage for other computers either.

It looks to me like I can set up /, swap, /home and be done.  I'd set it that way so /home could be made smaller from the end of the disk and the new/unallocated space be used for another /, /home (same 'Name', same 'location', different user is what I think would work to avoid configuration problems).

What I see as needing to know is how to structure the partitions.  My reference for this is https://wiki.archlinux.org/index.php/Partitioning  About 2/3's down the page is a series of partition charts relative to firmware/disk with partition recommendations.  I think this machine is the third type... "BIOS/GPT". 

So, I could use some advice and am happy to have views.
---------------------------------------------

I should say...  I've been running Linux since Ubuntu 6.06.  I've got a ton of Linux stuff in my head but don't actually know anything and will be a beginning beginner with Linux the rest of my days. I've set up three different Windows dual boots that all ended in Linux-only machines.  The last (this one) is Linux multi-boot with a shared data partition (/mnt/data via "OldFred" at Ubuntu Forums). I haven't done any of the mentioned without pretty serious step by step help... and that's what I'd like more of now.

Mike

   

I do not believe that there are any extra kernels to remove.  This fixed a previous problem I had, but the errors started again and I am up to several now.  Here is the latest:  Thanks for any help

Here is my disk allocation:
root = 26 GB free
home = 37 GB free
I made boot about 30 MB

When I click on File manager I get no drive size info

===========================
Install Updates Error log
===========================
Install Updates could not successfully download and install available updates.
Go to https://www.868212.xyz/forums/ and paste the log below into a new or existing thread for assistance.

============ Log ===========

Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following packages will be upgraded:
  libpam-systemd libsystemd0 libsystemd0:i386 libudev1 systemd systemd-sysv
  udev
7 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 4,624 kB of archives.
After this operation, 12.3 kB of additional disk space will be used.
Get:1 http://us.archive.ubuntu.com/ubuntu bionic-updates/main i386 libsystemd0 i386 237-3ubuntu10.40 [224 kB]
Get:2 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libsystemd0 amd64 237-3ubuntu10.40 [207 kB]
Get:3 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 systemd amd64 237-3ubuntu10.40 [2,913 kB]
Get:4 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpam-systemd amd64 237-3ubuntu10.40 [107 kB]
Get:5 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libudev1 amd64 237-3ubuntu10.40 [56.7 kB]
Get:6 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 udev amd64 237-3ubuntu10.40 [1,102 kB]
Get:7 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 systemd-sysv amd64 237-3ubuntu10.40 [14.4 kB]
Fetched 4,624 kB in 1s (5,000 kB/s)
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 275642 files and directories currently installed.)
Preparing to unpack .../libsystemd0_237-3ubuntu10.40_amd64.deb ...
De-configuring libsystemd0:i386 (237-3ubuntu10.39) ...
Unpacking libsystemd0:amd64 (237-3ubuntu10.40) over (237-3ubuntu10.39) ...
Preparing to unpack .../libsystemd0_237-3ubuntu10.40_i386.deb ...
Unpacking libsystemd0:i386 (237-3ubuntu10.40) over (237-3ubuntu10.39) ...
Preparing to unpack .../systemd_237-3ubuntu10.40_amd64.deb ...
Unpacking systemd (237-3ubuntu10.40) over (237-3ubuntu10.39) ...
Setting up libsystemd0:amd64 (237-3ubuntu10.40) ...
Setting up libsystemd0:i386 (237-3ubuntu10.40) ...
Setting up systemd (237-3ubuntu10.40) ...
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 275642 files and directories currently installed.)
Preparing to unpack .../libpam-systemd_237-3ubuntu10.40_amd64.deb ...
Unpacking libpam-systemd:amd64 (237-3ubuntu10.40) over (237-3ubuntu10.39) ...
Setting up libpam-systemd:amd64 (237-3ubuntu10.40) ...
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 275642 files and directories currently installed.)
Preparing to unpack .../libudev1_237-3ubuntu10.40_amd64.deb ...
Unpacking libudev1:amd64 (237-3ubuntu10.40) over (237-3ubuntu10.39) ...
Setting up libudev1:amd64 (237-3ubuntu10.40) ...
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 275642 files and directories currently installed.)
Preparing to unpack .../udev_237-3ubuntu10.40_amd64.deb ...
Unpacking udev (237-3ubuntu10.40) over (237-3ubuntu10.39) ...
Preparing to unpack .../systemd-sysv_237-3ubuntu10.40_amd64.deb ...
Unpacking systemd-sysv (237-3ubuntu10.40) over (237-3ubuntu10.39) ...
Setting up systemd-sysv (237-3ubuntu10.40) ...
Setting up udev (237-3ubuntu10.40) ...
update-initramfs: deferring update (trigger activated)
Setting up linux-firmware (1.173.18) ...
update-initramfs: Generating /boot/initrd.img-4.15.0-99-generic

gzip: stdout: No space left on device
E: mkinitramfs failure cpio 141 gzip 1
update-initramfs: failed for /boot/initrd.img-4.15.0-99-generic with 1.
dpkg: error processing package linux-firmware (--configure):
installed linux-firmware package post-installation script subprocess returned error exit status 1
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Processing triggers for systemd (237-3ubuntu10.40) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
Processing triggers for dbus (1.12.2-1ubuntu1.1) ...
Processing triggers for ureadahead (0.100.0-21) ...
ureadahead will be reprofiled on next reboot
Processing triggers for initramfs-tools (0.130ubuntu3.9) ...
update-initramfs: Generating /boot/initrd.img-4.15.0-99-generic

gzip: stdout: No space left on device
E: mkinitramfs failure cpio 141 gzip 1
update-initramfs: failed for /boot/initrd.img-4.15.0-99-generic with 1.
dpkg: error processing package initramfs-tools (--configure):
installed initramfs-tools package post-installation script subprocess returned error exit status 1
E: Sub-process /usr/bin/dpkg returned an error code (1)

I have been asked by a friend to help them move over to Linux. In the past I have used L Lite and I thought that would be a good distro for him. I installed version 5.0 RC1 on one of his laptops, no problem. But, today when I tried to install updates I did have  some problems. First was a problem with process 2887 which was causing some kind of lock to be set. I managed to kill that one. Then I had to run dpkg configure. And then fix-broken install. OK. I have now  been able to install all the updates and Lite is now up to date.
I have been using Linux for 20 years now. I do not pretend to be an expert, but I did manage to sort out the above. However there is no way that my friend could have managed all that. Am I missing something here? Perhaps the final version will have updating working properly. Or perhaps from now on it will just work. I can test that next time there are  some  updates available. And I do realise that I must install the final version for him once it is ready.
Any comments/advice gratefully received.

It has been a while since my last up-grade. I would appreciate if a Linux savvy person could give us a review on saving samba files, and  settings with locations. This would make a speeder upgrade without having to search other Linux forums sites.

Thanks and hope you are all good.

I am setting up Linux Lite 4.8 for an older relative, who is not computer literate, so I would like to hide the 'Delete' option from the right-click menu, because they don't know the different between 'Delete' and 'Move to Trash'.

I have two drives:
1. File System
2. Storage (NTFS)

Storage (/dev/sdb) is mounted at /media/myname/Storage


When I reboot my PC, Storage does not auto-mount, even though I have checked the setting to mount at startup. I still have to click it and type in my password for it to mount. I've tried sudo chmod -R 777 /dev/sdb and sudo chmod -R 777 /media/myname/Storage, but nothing has changed.

Perferably, I want it to just stay mounted at all times.

Have LLOS for about 3 months now and have made a few tweaks to personalize my system.  I am using 4.84 64 bit that has kernel 4.15.088.  I see that there are several perhaps newer kernels available.  None of these install when I check for updates.  Should I try installing any of them and is there a change log that lists the differences between them all.

Thanks

Hi Folks, I am not very clever with these things and rely heavily on the good folks who populate these forums!
My only previous experience has been using Linux Mint which I have had on several old machines.

With this lock down and being totally alone, I have dusted off a very old laptop which has Windows XP on it.
For some reason it will not boot into windows, I tried a USB stick with Linux Mint 17 32bit, but it wouldn't "see" the USB at Boot, so I enabled "Legacy Support" in BIOS but still the drive was ignored at Boot, so I finally tried an old disk copy of Linux lite which did boot after a few complaints.
I was really trying to find out just why XP wasn't booting, but I guess that was expecting too much of my tiny brain!

As Clint Eastwood used to say in Dirty Harry, "...a man's gotta know his limitations!"

Having taken the line of least resistance, I am now wanting to install either Linux lite or another Lite distro on this machine but first, I would like to be able to activate the WiFi card. It is a Linksys Wireless G Notebook Adapter Model WPC54G and slide into a PCI card slot in the laptop.
It was working just fine with Windows XP, and I recall using it with Mint a long time ago but now with this install Linux 3.13.0-24-generic(i686) I can't find out how to install the driver.
Can anyone help me please?

Hey,

I've been using linux lite 3.8 for around 4 months now. Before 3 months or so there came an update of linux kernal 4.4.112 to 4.4.178. After the update the mesa driver was updated
from 17.2.4 to 18.0.5.

The issue is that now when i play any video in vlc there is occasional fluttering which is kinda bugging.. It worked perfect with Mesa 17.2.4.

I tried changing the kernal as I thought mesa drivers come with kernals (not very linux savvy ;D) but even after changing kernal the mesa version remained the same and videos still flutters.

I did search on google about updating the mesa driver, but all are telling to add a "ppa:ubuntu-x-swat/updates", but there is no new updates & I'm still in mesa driver 18.0.5

Please help to fix the issue. There is no new updates so can anyone help to downgrade the mesa driver to 17.2.4 (if thats the best solution)