Arch Linux

dyscoria

Member

Registered: 2008-01-10

Posts: 1,007

Removing Core Packages

For my next install of Arch, i'm planning to remove some core packages that I don't need, but i'm not sure if this will break the system (seeing as they're 'core' ). These are the packages i'm thinking of NOT installing:

cryptsetup - don't need encryption
dash - using bash
e2fsprogs - using ext3 on all partitions
jfsutils
lilo - using GRUB
lvm2 - not using LVM
mailx - not sending mail by command line
mdadm - only one harddrive
reiserfsprogs
vi - using nano
xfsprogs

Any advice you can give?

Thanks.

---

flack 2.0.6: menu-driven BASH script to easily tag FLAC files (AUR)
knock-once 1.2: BASH script to easily create/send one-time sequences for knockd (forum/AUR)

Allan

Pacman

From: Brisbane, AU

Registered: 2007-06-09

Posts: 11,402

Website

Re: Removing Core Packages

I think you still need e2fsprogs when using ext3 for things like fsck.  Other than that, I don't see many problems.  If you use sudo you may want to keep vi for setup with visudo.

---

PGP Key: F99FFE0FEAE999BD

dolby

Member

From: 1992

Registered: 2006-08-08

Posts: 1,581

Re: Removing Core Packages

mailx is still a dependency to logrotate in core until this moment. the one in testing doesnt need it and will soon be out of core. and yes e2fsprogs you need
personally i dont install cryptsetup, device-mapper,dhcpd,dmapi,jfsutils,lilo,lvm2,mdadm,pcmciautils,reiserfsprogs,xfsprogs,sdparm and nano
probably dash too on my next install

Last edited by dolby (2008-01-27 12:44:15)

---

There shouldn't be any reason to learn more editor types than emacs or vi -- mg (1)
[You learn that sarcasm does not often work well in international forums.  That is why we avoid it. -- ewaller (arch linux forum moderator)

nDray

Member

From: Portugal

Registered: 2007-01-21

Posts: 143

Website

Re: Removing Core Packages

i don't usually install lilo and pcmciautils, as well...

By removing base packages you have to pay special attention. There are few scripts in packages that use, lets say, "sed", but sed isn't listed as a dependency for that package, neither it needs to be. This is because devs assume that the whole base system is installed. It's even more than an assumption. It's a rule.

Last edited by nDray (2008-01-27 12:59:14)