CentOS - May 2016 - Reduce existing CentOS 7 installation to "Minimal install" - services?

On 05/06/2016 09:33 AM, Nicolas Kovacs wrote:
> Le 06/05/2016 08:50, Nicolas Kovacs a ?crit :
>> Now what would be the simple systemd equivalent of doing that? E. g. on
>> any CentOS installation (be it graphical, "Web Server",
"File Server",
>> whatever), strip down services to the status that they're at just
after
>> installing a "Minimal Install"?
>
> PS: I gave this a spin on two sandbox machines here. One with a full
> GNOME GUI installation, one with a "Web Server" profile. On both,
I
> defined "systemctl set-default multi-user.target", then I
stripped the
> system with my script. Upon reboot, startup hangs, and in my journal, I
> get a lot of "Failed to parse ACL" errors.
>
> I don't know if it's related to this:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1268628
>
>  From here on, I'm clueless.
you're probably removing too many packages, eg some key package is a dep 
of MINIMAL but not in MINIMAL, and "yum remove" removes it and all its
dependants.
Maybe add "yum install $MINIMAL" after your yum remove command.
Or replace yum remove with "rpm -e" to see if and who in $SUPPRIMER
has
deps in MINIMAL.

Le 06/05/2016 11:13, Nicolas Thierry-Mieg a ?crit :
> you're probably removing too many packages, eg some key package is a
dep
> of MINIMAL but not in MINIMAL, and "yum remove" removes it and
all its
> dependants.
> Maybe add "yum install $MINIMAL" after your yum remove command.
> Or replace yum remove with "rpm -e" to see if and who in
$SUPPRIMER has
> deps in MINIMAL.
I gave it another spin, this time with rpm -e $SUPPRIMER. Got no error
messages, rpm -e simply wiped all non-essential packages. So I don't
think the problem comes from some removed minimal package.

This time I activated startup messages. Booting gets stuck right after
mounting /boot. I'll try to reproduce it, since I can't copy/paste it.

[  OK  ] Mounted /boot.
[ TIME ] Timed out waiting for device
dev-mapper-centos_amandine\x2dhome.device.
[DEPEND] Dependency failed for /home.

And then quite a few lines, and booting into emergency mode.

Any suggestions?

Niki

-- 
Microlinux - Solutions informatiques durables
7, place de l'?glise - 30730 Montpezat
Web  : http://www.microlinux.fr
Mail : info at microlinux.fr
T?l. : 04 66 63 10 32

On 05/06/2016 06:46 AM, Nicolas Kovacs wrote:
> Le 06/05/2016 11:13, Nicolas Thierry-Mieg a ?crit :
>> you're probably removing too many packages, eg some key package is
a dep
>> of MINIMAL but not in MINIMAL, and "yum remove" removes it
and all its
>> dependants.
>> Maybe add "yum install $MINIMAL" after your yum remove
command.
>> Or replace yum remove with "rpm -e" to see if and who in
$SUPPRIMER has
>> deps in MINIMAL.
> 
> I gave it another spin, this time with rpm -e $SUPPRIMER. Got no error
> messages, rpm -e simply wiped all non-essential packages. So I don't
> think the problem comes from some removed minimal package.
> 
> This time I activated startup messages. Booting gets stuck right after
> mounting /boot. I'll try to reproduce it, since I can't copy/paste
it.
> 
> [  OK  ] Mounted /boot.
> [ TIME ] Timed out waiting for device
> dev-mapper-centos_amandine\x2dhome.device.
> [DEPEND] Dependency failed for /home.
> 
> And then quite a few lines, and booting into emergency mode.
> 
> Any suggestions?
> 
> Niki
> 
Maybe add a:

yum groupinstall core



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
URL:
<http://lists.centos.org/pipermail/centos/attachments/20160506/ce6baf48/attachment-0001.sig>

On Fri, May 06, 2016 at 11:13:10AM +0200, Nicolas Thierry-Mieg
wrote:
> 
> you're probably removing too many packages, eg some key package is a
> dep of MINIMAL but not in MINIMAL, and "yum remove" removes it
and
> all its dependants.
Just as an example of this, and one that RH may move into an update
sooner or later.  Fedora 24's minimal comes with NetworkManager.  I always
remove it and use network.  So, on Fedora 24, which is admittedly in beta,
/etc/resolv.conf is now a part of NetworkManager, a symbolic link
 to /var/run/NetworkManager/resolv.conf. So,if one removes NetworkManager
or even disables it, name resolution no longer works. 

It seems to me that the easiest thing would be to quickly run a minimal
install in VirtualBox, and if you remove anything, keep an eye on it, or,
as was suggested, below.
> Or replace yum remove with "rpm -e" to see if and who in
$SUPPRIMER
> has deps in MINIMAL.
-- 
Scott Robbins
PGP keyID EB3467D6
( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 )
gpg --keyserver pgp.mit.edu --recv-keys EB3467D6