that to be a good thing and have learned a lot
this week.
I believe now that what that flag does is allows you to build a terminal
that is small, as in lightweight on resources. You can build it so that it
would not read the xdefaults files and run as a very no frills terminal
even if you ran an xserver built
on your particular use case(s). Plasma desktop is usually
installed by setting the appropriate make.profile:
$ eselect profile list
Available profile symlink targets:
[1] default/linux/amd64/17.1 (stable)
[2] default/linux/amd64/17.1/selinux (stable)
[3] default/linux/amd64/17.1/ha
/amd64/17.1/selinux (stable)
[3] default/linux/amd64/17.1/hardened (stable)
[4] default/linux/amd64/17.1/hardened/selinux (stable)
[5] default/linux/amd64/17.1/desktop (stable)
[6] default/linux/amd64/17.1/desktop/gnome (stable)
[7] default/linux/amd64/17.1/desktop/gnome
and xserver. As I went to emerge
xfce4 as
shown here http://wiki.gentoo.org/wiki/Xfce
emerge --ask xfce4-meta xfce4-notifyd, I got a slot conflict:
sys-ath/pambase-20101024-r2::gentoo, installed
sys-auth/pambase-20120417-r2::gentoo, scheduled for merge.
How do I resolve this conflict please
Kapshuk wrote:
Howdy,
Just installed the base system and xserver. As I went to emerge
xfce4 as
shown here http://wiki.gentoo.org/wiki/Xfce
emerge --ask xfce4-meta xfce4-notifyd, I got a slot conflict:
sys-ath/pambase-20101024-r2::gentoo, installed
sys-auth/pambase-20120417-r2::gentoo
=0x317 selinux=0 splash=silent resume=/dev/hda6 showopts
initrd /initrd-2.6.11.4-20a-default
But I use 'make install' to install my kernels, so 'vmlinuz' and
'vmlinuz.old' are symlinks to my current and previous kernels, as you
can see from the directory listing:
# la /boot
drwxr-xr-x 5
6 matches
Mail list logo
