Tip: installing 16 on 4.3G partition or drive

Post Reply
Message
Author
User avatar
galen
Posts: 271
Joined: Thu Dec 15, 2016 1:37 pm

Tip: installing 16 on 4.3G partition or drive

#1 Post by galen »

4.3G seems to be the lower limit on partition size.
(no installing directly to a 4G USB stick)

here's what to do to keep the install size down.
Install to target partition.
boot up.
Terminal

Code: Select all

sudo tune2fs -m 0 /dev/[target-partition]
above reduces reserve disk space to zero %
run synaptic and do your updates,
close synaptic.
terminal run

Code: Select all

sudo apt-get autoremove
sudo apt-get autoclean
On my machine #2 iceWM did not work properly so I went with fluxbox,
removing icewm via synaptic
Linux user since 1999, on-line 1993
Dtop#1: XU20 AMD-FX6300, GT730
Dtop#2: MX19 AM3ATH2X2, GT218-8400
Ltop#1: MX21 T500
Ltop#2: MX19 T440
Ltop#3: MX19 NC6400
Ltop#4: XU18 NC4400
Ltop#5: Sparky32 T30 :turtle:
Ltop#6: MX21 Acer E5

fatmac
Posts: 11
Joined: Thu Sep 14, 2017 4:59 am

Re: Tip: installing 16 on 4.3G partition or drive

#2 Post by fatmac »

That limit is coded into the GUI installer, try using the command line installer to install to a 4GB pendrive.

skidoo
Posts: 753
Joined: Tue Sep 22, 2015 6:56 pm

Re: Tip: installing 16 on 4.3G partition or drive

#3 Post by skidoo »

galen wrote:

Code: Select all

sudo tune2fs -m 0 /dev/[target-partition]
above reduces reserve disk space to zero %
zero, for a boot partition, invites regrettable consequences.
If you insist on changing the default, perhaps 1% would be a safe/sane choice.
I'm not brave enough to tempt fate by choosing 1%; if you do so, I would be interested in hearing about the result.
man tune2fs
tune2fs

-m reserved-blocks-percentage
  • Set the percentage of the filesystem which may only be allocated by privileged processes.
    Reserving some number of filesystem blocks for use by privileged processes is done to avoid filesystem fragmentation, and to allow system daemons, such as syslogd(8), to continue to function correctly after non-privileged processes are prevented from writing to the filesystem.
    Normally, the default percentage of reserved blocks is 5%.

skidoo
Posts: 753
Joined: Tue Sep 22, 2015 6:56 pm

Re: Tip: installing 16 on 4.3G partition or drive

#4 Post by skidoo »

edit: removed unwarranted blather regarding apt-get autoremove

Today, checking sudo apt-get -s autoremove on my long-running antiX16 system, the output list is surprisingly short.
More importantly, I expect that the actual removal of these autoremove-listed packages would have been regrettable.
among the listed packages:
libssl1 (which is a dependency of many, including the pre-installed: advert-block-antix, wicd, ufw...)
libjte, libisofs, libisoburn1 {---- direct or indirect dependencies of xfburn, AFAICT
libvisual {--- gstreamer1.0-plugins-base {--- smtube

Can others, from within a healthy running antix16 system, confirm this?
Do you find libssl1, libjte... listed in the output of sudo apt-get -s autoremove ?
Last edited by skidoo on Sat Sep 16, 2017 10:28 pm, edited 1 time in total.

fatmac
Posts: 11
Joined: Thu Sep 14, 2017 4:59 am

Re: Tip: installing 16 on 4.3G partition or drive

#5 Post by fatmac »

This is what I get.

Code: Select all

 sudo apt-get -s autoremove
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages will be REMOVED:
  coinor-libcbc3 coinor-libcgl1 coinor-libclp1 coinor-libcoinmp1
  coinor-libcoinutils3 coinor-libosi1 libabw-0.1-1 libcdr-0.1-1
  libclucene-contribs1 libclucene-core1 libcmis-0.4-4 libe-book-0.1-1 libeot0
  libetonyek-0.1-1 libexttextcat-2.0-0 libexttextcat-data libfreehand-0.1-1
  libgltf-0.0-0 libharfbuzz-icu0 libhyphen0 liblangtag-common liblangtag1
  libmhash2 libmspub-0.1-1 libmwaw-0.3-3 libmythes-1.2-0 libnspr4 libnss3
  libodfgen-0.1-1 liborcus-0.8-0 libraptor2-0 librasqal3 librdf0
  libreoffice-style-galaxy librevenge-0.0-0 libvisio-0.1-1 libwpd-0.10-10
  libwpg-0.3-3 libwps-0.3-3 libyajl2
0 upgraded, 0 newly installed, 40 to remove and 3 not upgraded.
Remv coinor-libcoinmp1 [1.7.6+dfsg1-1]
Remv coinor-libcbc3 [2.8.12-1]
Remv coinor-libcgl1 [0.58.9-1]
Remv coinor-libclp1 [1.15.10-1]
Remv coinor-libosi1 [0.106.9-1]
Remv coinor-libcoinutils3 [2.9.15-3]
Remv libabw-0.1-1 [0.1.0-2]
Remv libcdr-0.1-1 [0.1.0-3]
Remv libclucene-contribs1 [2.3.3.4-4]
Remv libclucene-core1 [2.3.3.4-4]
Remv libcmis-0.4-4 [0.4.1-7]
Remv libe-book-0.1-1 [0.1.1-2]
Remv libeot0 [0.01-3]
Remv libetonyek-0.1-1 [0.1.1-2]
Remv libexttextcat-2.0-0 [3.4.4-1]
Remv libexttextcat-data [3.4.4-1]
Remv libfreehand-0.1-1 [0.1.0-2]
Remv libgltf-0.0-0 [0.0.2-2]
Remv libharfbuzz-icu0 [0.9.35-2]
Remv libhyphen0 [2.8.8-1]
Remv liblangtag1 [0.5.1-3]
Remv liblangtag-common [0.5.1-3]
Remv librdf0 [1.0.17-1+b1]
Remv librasqal3 [0.9.32-1]
Remv libmhash2 [0.9.9.9-7]
Remv libmspub-0.1-1 [0.1.1-2]
Remv libmwaw-0.3-3 [0.3.1-2+deb8u1]
Remv libmythes-1.2-0 [2:1.2.4-1]
Remv libnss3 [2:3.26-1+debu8u2]
Remv libnspr4 [2:4.12-1+debu8u1]
Remv libodfgen-0.1-1 [0.1.1-2]
Remv liborcus-0.8-0 [0.7.0+dfsg-9]
Remv libraptor2-0 [2.0.14-1]
Remv libreoffice-style-galaxy [1:4.3.3-2+deb8u7]
Remv libwps-0.3-3 [0.3.0-2]
Remv libwpg-0.3-3 [0.3.0-3]
Remv librevenge-0.0-0 [0.0.1-3] [libvisio-0.1-1:amd64 libwpd-0.10-10:amd64 ]
Remv libvisio-0.1-1 [0.1.0-2] [libwpd-0.10-10:amd64 ]
Remv libwpd-0.10-10 [0.10.0-2+b1]
Remv libyajl2 [2.1.0-2]

Code: Select all

$ uname -a
Linux itx 4.4.10-antix.1-amd64-smp #2 SMP PREEMPT Thu Feb 23 15:28:54 EET 2017 x86_64 GNU/Linux

skidoo
Posts: 753
Joined: Tue Sep 22, 2015 6:56 pm

Re: Tip: installing 16 on 4.3G partition or drive

#6 Post by skidoo »

fatmac, thanks for checking. Your list looks familiar ~~ safe-to-remove leftovers immediately after I had uninstalled LibreOffice.
Although the packages on that 10mo-old install I tested are not fully up-to-date, I didn't realize it had become frankendebian-ized.

edit:
I sorted it out. "libssl1" is not the complete package name. Two packages were installed on that system: "libssl1.0.0" and "libssl1.0.2".
Nothing other than "transmission-gtk" (which had been uninstalled) depended on the latter; it was indeed safe to remove.
I performed belated package updates; doing so solved the remaining listed items.

Post Reply

Return to “antiX”