SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I was bored last night and wanted to play with qemu and have a look at some of the stuff I don't use like plasma (much better than the last kde but still a bit pants).
I created a 16GB cow2 disk and booted from the usb install image. I setup a single partition (no swap) and ran through a full install using defaults from my local mirror of slackware64-current. It installed fine but when starting up kde it warned me of a full disk. I was surprised to see 100% usage in df - although there was still a few hundred megabytes left.
The biggest package is grub2 but that's a bug fixed in 2.06 which is still in beta. Next are kernel-source, rust, and kernel-firmware.
Anyway I just thought it was a point of interest.
PS little perl script to find installed package sizes. Handles hardlinks but assumes one filesystem.
Code:
#!/usr/bin/perl
$root='/';
$pkgs='/var/log/packages';
my %inodes;
opendir(DIR,$pkgs);
while (my $name = readdir(DIR)) {
next if ($name =~ m/^\./);
#print $name."\n";
open (PKG, $pkgs.'/'.$name);
while (my $line = <PKG>) {
last if ($line =~ m/^FILE LIST:/);
}
my $total = 0;
while (my $path = <PKG>) {
chop $path;
next if ($path =~ m@/$|^install@);
my @s = lstat($root.$path);
$total += $s[7] if !defined $inode{$s[1]};
$inode{$s[1]} = 1;
}
print $total."\t".$name."\n";
close(PKG);
}
closedir(DIR);
I noticed that recently setting up a laptop for Wife's friend,
(a Slackware64) - w/o KDE, installed size is 13G!
Friends, we're rolling in the deep :-D
put this 16GB Slackware full installation on a 8GB device, as big is the eMMC from two of my netbooks - and to remain enough space for a light web-browsing.
I for one I did this, but I am curious about on what design will go the OP.
Last edited by LuckyCyborg; 04-26-2021 at 01:34 AM.
Distribution: Mainly Devuan, antiX, & Void, with Tiny Core, Fatdog, & BSD thrown in.
Posts: 5,489
Rep:
Yeah, Slack installs everything.....the main reason I changed (to Debian/Debian based) distros - I don't need everything - just what I use on a daily basis, even now it's less than 3GB installed.
I started out using Linux when RedHat 4.2 installed only 45MB, (OK, it was just command line, but even so)....
put this 16GB Slackware full installation on a 8GB device, as big is the eMMC from two of my netbooks - and to remain enough space for a light web-browsing.
For a full installation, I'd have to cheat and use the current live slack (assuming the netbook can do 64bit which I imagine it won't). Just use persistence on the USB stick and put a swap partition and a data partition on the eMMC.
Here's a nickle kid, go buy yourself a better computer!
I was trying to see the relevance in your answer. It does not make sense. You must be one of those blabbering buffoons that just need to generate some noise every now and then.
For a full installation, I'd have to cheat and use the current live slack (assuming the netbook can do 64bit which I imagine it won't). Just use persistence on the USB stick and put a swap partition and a data partition on the eMMC.
Well, my take was a F2FS partition for root (aka /) because the old generation of eMMC device, and putting the /usr content on a squashfs file generated on another system (and reference rysnc tree prepared on a portable USB hard drive) . This required also modifications on initrd, of course.
I chosen this solution because this way the /etc content was editable as usual, I can freely test different kernels (without /usr/src/linux-x.y.z which is not included anyway) because the /lib was also natively writable, and more important: the /home was just standard and writable.
BTW, this way I got around 5GB occupied by system (including the Plasma5 from KTown), leaving around 3GB for user data - more than enough for web browsing and watching YouTube.
Last edited by LuckyCyborg; 04-26-2021 at 05:30 AM.
BTW, this way I got around 5GB occupied by system (including the Plasma5 from KTown), leaving around 3GB for user data - more than enough for web browsing and watching YouTube.
That is impressive and I'll do some reading out of interest.
I imagine that the use of a compressed file system means higher processor load as parts of the compressed file system are uncompressed when being loaded into RAM so a trade off (as always).
That is impressive and I'll do some reading out of interest.
I imagine that the use of a compressed file system means higher processor load as parts of the compressed file system are uncompressed when being loaded into RAM so a trade off (as always).
Yes, of course there's a CPU load trade off, BUT it's lighter than when using also an UNION FS (in the USB live style), and in other hand, overall, the system feels much more responsive, as those old eMMC have only around 50MB/s read rate, then the compressed data is loaded much faster.
Around 3 times faster, in my subjective opinion.
Last edited by LuckyCyborg; 04-26-2021 at 06:10 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.