Re: [gentoo-user] What does xgetdefault use flag do
On Fri, May 31, 2013 at 5:58 AM, Peter Humphrey pe...@humphrey.ukfsn.org wrote: On Monday 27 May 2013 17:58:35 Alan McKinnon wrote: I also have no idea what small version means - it's not English, it doesn't parse, and it makes no sense. It is understandable if there is a small version of aterm. Perhaps aterm itself rather than multi-aterm? -- Peter I am still not sure if small means both small in size and small in features or just small in features. I did not build it both ways and compare, in fact, I built rxvt-unicode and the flag was completely irrelevant. Wasn't having one of my good days evidently. I have built several Gentoo systems over the last few months but they have been gentoo-hardened servers and routers. This is/was my first attempt at a desktop and it is exposing my lack of understanding of X in general. I am one of those people who find 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 with all the fixin's. Which is exactly what the description says and caused me to be a bit embarrassed for even have asked. By the way, this install runs great. I have 320GB hard drive on a Dual Core Dell laptop. I'm in the process of putting three seperate installs on it which will be identical except for one will be gentoo-hardened with SELinux, another using RBAC, and then this one as normal install. I believe there are some situation where RBAC has an advantage over SELinux and vice versa. I also want to try and build the RBAC system running LXC with SELinux inside the containers. I believe this is possible and would further isolate the containers from the base system. -- B G
Re: [gentoo-user] New install - Wayland and graphical login
On Saturday, 26 June 2021 08:19:24 BST Wols Lists wrote: > On 26/06/21 00:51, Michael wrote: > > Given your error, you appear to not have installed the requisite packages > > for the Plasma/KDE. It should have been installed as a dependency of > > plasma-workspace: > > Ah. Another piece of missing information ... I'll try that. I would have > thought that would have been pulled in seeing as I've got wayland and qt > use flags etc > > > $ qfile startplasma-wayland > > kde-plasma/plasma-workspace: /usr/bin/startplasma-wayland I am not clear 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/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/systemd (stable) [8] default/linux/amd64/17.1/desktop/plasma (stable) * [9] default/linux/amd64/17.1/desktop/plasma/systemd (stable) [10] default/linux/amd64/17.1/desktop/systemd (stable) [11] default/linux/amd64/17.1/developer (stable) [12] default/linux/amd64/17.1/no-multilib (stable) [13] default/linux/amd64/17.1/no-multilib/hardened (stable) [14] default/linux/amd64/17.1/no-multilib/hardened/selinux (stable) [15] default/linux/amd64/17.1/systemd (stable) [16] default/linux/amd64/17.0 (dev) [17] default/linux/amd64/17.0/selinux (dev) [18] default/linux/amd64/17.0/hardened (dev) [19] default/linux/amd64/17.0/hardened/selinux (dev) [20] default/linux/amd64/17.0/desktop (dev) [21] default/linux/amd64/17.0/desktop/gnome (dev) [22] default/linux/amd64/17.0/desktop/gnome/systemd (dev) [23] default/linux/amd64/17.0/desktop/plasma (dev) [24] default/linux/amd64/17.0/desktop/plasma/systemd (dev) [25] default/linux/amd64/17.0/developer (dev) [26] default/linux/amd64/17.0/no-multilib (dev) [27] default/linux/amd64/17.0/no-multilib/hardened (dev) [28] default/linux/amd64/17.0/no-multilib/hardened/selinux (dev) [29] default/linux/amd64/17.0/systemd (dev) [30] default/linux/amd64/17.0/x32 (dev) [31] default/linux/amd64/17.0/musl (exp) [32] default/linux/amd64/17.0/musl/hardened (exp) [33] default/linux/amd64/17.0/musl/hardened/selinux (exp) [34] default/linux/amd64/17.0/uclibc (exp) [35] default/linux/amd64/17.0/uclibc/hardened (exp) If you are looking for some minimalist desktop, a Plasma DE plus KDE applications with hundred of dependencies is probably not what you want. Also, I think Plasma DE and most DMs will pull in X11, because: a) they work both with X11 and wayland; b) many X11 applications can only run in X using XWayland. XWayland is an X Server running as a Wayland client to enable displaying native X11 client applications within a Wayland compositor environment. I haven't looked into it at any depth to see if you can strip a heavy DE like Plasma from all xserver dependencies - I'd guess you can't. > > If you have Gnome already installed then you can use the stanza for gnome- > > session instead. > > My use flags also contain -gtk -gnome ... gnome at least is on my list > of pet hates ... > > Cheers, > Wol OK, select the Plasma profile, then have a quick look at: https://wiki.gentoo.org/wiki/KDE You'll need to disable some USE flags of plasma-meta to avoid dragging in things you may not need/require, like 'display-manager', 'sddm', 'accessibility', etc. Eventually, after you update @world, add any kde-apps *-meta packages you need. However, if you intend to use wayland for the most minimalist of purposes, then you may want to consider something like Wayfire, instead of Plasma. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] New install - Wayland and graphical login
On 26/06/2021 10:28, Michael wrote: On Saturday, 26 June 2021 08:19:24 BST Wols Lists wrote: On 26/06/21 00:51, Michael wrote: Given your error, you appear to not have installed the requisite packages for the Plasma/KDE. It should have been installed as a dependency of plasma-workspace: Ah. Another piece of missing information ... I'll try that. I would have thought that would have been pulled in seeing as I've got wayland and qt use flags etc $ qfile startplasma-wayland kde-plasma/plasma-workspace: /usr/bin/startplasma-wayland I am not clear on your particular use case(s). Plasma desktop is usually installed by setting the appropriate make.profile: I just want a working systemd/wayland desktop system. So basically, a full-weight normal desktop. $ 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/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/systemd (stable) [8] default/linux/amd64/17.1/desktop/plasma (stable) * [9] default/linux/amd64/17.1/desktop/plasma/systemd (stable) I've got this one selected, /desktop/plasma/systemd [10] default/linux/amd64/17.1/desktop/systemd (stable) [11] default/linux/amd64/17.1/developer (stable) [12] default/linux/amd64/17.1/no-multilib (stable) [13] default/linux/amd64/17.1/no-multilib/hardened (stable) [14] default/linux/amd64/17.1/no-multilib/hardened/selinux (stable) [15] default/linux/amd64/17.1/systemd (stable) [16] default/linux/amd64/17.0 (dev) [17] default/linux/amd64/17.0/selinux (dev) [18] default/linux/amd64/17.0/hardened (dev) [19] default/linux/amd64/17.0/hardened/selinux (dev) [20] default/linux/amd64/17.0/desktop (dev) [21] default/linux/amd64/17.0/desktop/gnome (dev) [22] default/linux/amd64/17.0/desktop/gnome/systemd (dev) [23] default/linux/amd64/17.0/desktop/plasma (dev) [24] default/linux/amd64/17.0/desktop/plasma/systemd (dev) [25] default/linux/amd64/17.0/developer (dev) [26] default/linux/amd64/17.0/no-multilib (dev) [27] default/linux/amd64/17.0/no-multilib/hardened (dev) [28] default/linux/amd64/17.0/no-multilib/hardened/selinux (dev) [29] default/linux/amd64/17.0/systemd (dev) [30] default/linux/amd64/17.0/x32 (dev) [31] default/linux/amd64/17.0/musl (exp) [32] default/linux/amd64/17.0/musl/hardened (exp) [33] default/linux/amd64/17.0/musl/hardened/selinux (exp) [34] default/linux/amd64/17.0/uclibc (exp) [35] default/linux/amd64/17.0/uclibc/hardened (exp) If you are looking for some minimalist desktop, a Plasma DE plus KDE applications with hundred of dependencies is probably not what you want. Also, I think Plasma DE and most DMs will pull in X11, because: a) they work both with X11 and wayland; b) many X11 applications can only run in X using XWayland. XWayland is an X Server running as a Wayland client to enable displaying native X11 client applications within a Wayland compositor environment. I haven't looked into it at any depth to see if you can strip a heavy DE like Plasma from all xserver dependencies - I'd guess you can't. Not after a minimalist system, and if it pulls in X that's fine. (Actually, I've installed X, and at the moment it blows up on me, but if I can get Wayland working, I don't see the point in debugging it until I need to ...) If you have Gnome already installed then you can use the stanza for gnome- session instead. My use flags also contain -gtk -gnome ... gnome at least is on my list of pet hates ... Cheers, Wol OK, select the Plasma profile, then have a quick look at: https://wiki.gentoo.org/wiki/KDE You'll need to disable some USE flags of plasma-meta to avoid dragging in things you may not need/require, like 'display-manager', 'sddm', 'accessibility', etc. Eventually, after you update @world, add any kde-apps *-meta packages you need. However, if you intend to use wayland for the most minimalist of purposes, then you may want to consider something like Wayfire, instead of Plasma. I'll need something like sddm, because I'll have multiple users logged in simultaneously. I was trying to use qtgreet as per the "Wayland Landscape" page, but the package doesn't seem to exist ... I'd rather avoid gnome/gdm and gtkgreet, lightdm and sddm look like X11 (and I said I didn't want to debug it :-), and tuigreet looks like it might not support multi-user/multi-head. Still, if I can get plasma running, I can work from there ... Cheers, Wol
Re: [gentoo-user] re: multiple pkg instances within single pkg slot
On 15/07/2013 21:21, Alexander Kapshuk wrote:
On 07/15/2013 10:17 PM, Alan McKinnon wrote:
On 15/07/2013 20:43, Alexander Kapshuk wrote:
On 07/15/2013 09:23 PM, Alan McKinnon wrote:
On 15/07/2013 20:12, Alexander 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, scheduled for merge.
How do I resolve this conflict please?
That looks like partial output, there's information missing that says
why the conflict is happening. Please post the output of (run as root):
emerge -pv pambase
http://bpaste.net/show/114541/
emerge --info
http://bpaste.net/show/114540/
Please don't use pastebins here, they go away.
Post inline into the body of the mail.
Sorry about that. I wasn't aware of the policy.
I haven't installed a mail client yet. Just installed twm and xterm.
Is there any other way I can sent the info required to the mailing list?
Thanks.
Don't worry about it. It's not really a policy as such; it's more like
the way things have always been done. This list is a treasure trove of
useful postings that the rest of the internet finds useful for years to
come, so the regulars have come to expect pasted output to be inline.
Here's your emerge pambase output:
These are the packages that would be merged, in order:
Calculating dependencies ... done!
[ebuild N ] app-text/sgml-common-0.6.3-r5 126 kB
[ebuild N ] app-arch/unzip-6.0-r3 USE=bzip2 unicode -natspec
1,345 kB
[ebuild N ] app-arch/zip-3.0-r1 USE=bzip2 crypt unicode -natspec
1,258 kB
[ebuild N ] dev-libs/dbus-glib-0.100.2 USE=-debug -doc
-static-libs {-test} 732 kB
[ebuild N ] app-text/docbook-xml-dtd-4.1.2-r6:4.1.2 74 kB
[ebuild NS] sys-devel/autoconf-2.13:2.1 [2.69:2.5] 434 kB
[ebuild N ] dev-libs/nspr-4.9.5 USE=-debug 1,130 kB
[ebuild N ] dev-lang/spidermonkey-1.8.5-r4:0/mozjs185 USE=-debug
-minimal -static-libs {-test} 6,021 kB
[ebuild NS] x11-libs/gtk+-3.4.4:3 [2.24.17:2] USE=X cups
introspection (-aqua) -colord -debug -examples (-packagekit) {-test}
-vim-syntax (-wayland) -xinerama 12,554 kB
[ebuild N ] sys-auth/polkit-0.110 USE=gtk introspection nls pam
-examples -kde (-selinux) -systemd 1,358 kB
[ebuild N ] sys-auth/consolekit-0.4.5_p20120320-r1 USE=acl pam
policykit -debug -doc (-selinux) {-test} 101 kB
[ebuild N ] gnome-extra/polkit-gnome-0.105 304 kB
[ebuild U ] sys-auth/pambase-20120417-r2 [20101024-r2]
USE=consolekit* cracklib sha512 -debug -gnome-keyring -minimal -mktemp
-pam_krb5 -pam_ssh -passwdqc (-selinux) -systemd% 4 kB
[blocks B ] sys-apps/shadow-4.1.5-r1 (sys-apps/shadow-4.1.5-r1
is blocking sys-auth/pambase-20120417-r2)
Total: 13 packages (1 upgrade, 10 new, 2 in new slots), Size of
downloads: 25,435 kB
Conflict: 1 block (1 unsatisfied)
* IMPORTANT: 5 news items need reading for repository 'gentoo'.
* Use eselect news to read news items.
I suspect your original error was actually a conflict between shadow and
pambase and you probably snipped that part in error.
Try this first:
emerge -av1 shadow
it should upgrade shadow to 4.1.5.1-r1 just fine. Then:
emerge --sync
emerge -avuND world
and then emerge xfce (the original command).
If emerging shadow by itself gives an error, then just go onto sync and
emerging world, these days portage knows how to figure it's way round
all the conflicts (it wasn't always like that)
--
Alan McKinnon
alan.mckin...@gmail.com
Re: [gentoo-user] re: multiple pkg instances within single pkg slot
On 07/15/2013 10:31 PM, Alan McKinnon wrote:
On 15/07/2013 21:21, Alexander Kapshuk wrote:
On 07/15/2013 10:17 PM, Alan McKinnon wrote:
On 15/07/2013 20:43, Alexander Kapshuk wrote:
On 07/15/2013 09:23 PM, Alan McKinnon wrote:
On 15/07/2013 20:12, Alexander 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, scheduled for merge.
How do I resolve this conflict please?
That looks like partial output, there's information missing that says
why the conflict is happening. Please post the output of (run as root):
emerge -pv pambase
http://bpaste.net/show/114541/
emerge --info
http://bpaste.net/show/114540/
Please don't use pastebins here, they go away.
Post inline into the body of the mail.
Sorry about that. I wasn't aware of the policy.
I haven't installed a mail client yet. Just installed twm and xterm.
Is there any other way I can sent the info required to the mailing list?
Thanks.
Don't worry about it. It's not really a policy as such; it's more like
the way things have always been done. This list is a treasure trove of
useful postings that the rest of the internet finds useful for years to
come, so the regulars have come to expect pasted output to be inline.
Here's your emerge pambase output:
These are the packages that would be merged, in order:
Calculating dependencies ... done!
[ebuild N ] app-text/sgml-common-0.6.3-r5 126 kB
[ebuild N ] app-arch/unzip-6.0-r3 USE=bzip2 unicode -natspec
1,345 kB
[ebuild N ] app-arch/zip-3.0-r1 USE=bzip2 crypt unicode -natspec
1,258 kB
[ebuild N ] dev-libs/dbus-glib-0.100.2 USE=-debug -doc
-static-libs {-test} 732 kB
[ebuild N ] app-text/docbook-xml-dtd-4.1.2-r6:4.1.2 74 kB
[ebuild NS] sys-devel/autoconf-2.13:2.1 [2.69:2.5] 434 kB
[ebuild N ] dev-libs/nspr-4.9.5 USE=-debug 1,130 kB
[ebuild N ] dev-lang/spidermonkey-1.8.5-r4:0/mozjs185 USE=-debug
-minimal -static-libs {-test} 6,021 kB
[ebuild NS] x11-libs/gtk+-3.4.4:3 [2.24.17:2] USE=X cups
introspection (-aqua) -colord -debug -examples (-packagekit) {-test}
-vim-syntax (-wayland) -xinerama 12,554 kB
[ebuild N ] sys-auth/polkit-0.110 USE=gtk introspection nls pam
-examples -kde (-selinux) -systemd 1,358 kB
[ebuild N ] sys-auth/consolekit-0.4.5_p20120320-r1 USE=acl pam
policykit -debug -doc (-selinux) {-test} 101 kB
[ebuild N ] gnome-extra/polkit-gnome-0.105 304 kB
[ebuild U ] sys-auth/pambase-20120417-r2 [20101024-r2]
USE=consolekit* cracklib sha512 -debug -gnome-keyring -minimal -mktemp
-pam_krb5 -pam_ssh -passwdqc (-selinux) -systemd% 4 kB
[blocks B ]sys-apps/shadow-4.1.5-r1 (sys-apps/shadow-4.1.5-r1
is blocking sys-auth/pambase-20120417-r2)
Total: 13 packages (1 upgrade, 10 new, 2 in new slots), Size of
downloads: 25,435 kB
Conflict: 1 block (1 unsatisfied)
* IMPORTANT: 5 news items need reading for repository 'gentoo'.
* Use eselect news to read news items.
I suspect your original error was actually a conflict between shadow and
pambase and you probably snipped that part in error.
Try this first:
emerge -av1 shadow
it should upgrade shadow to 4.1.5.1-r1 just fine. Then:
emerge --sync
emerge -avuND world
and then emerge xfce (the original command).
If emerging shadow by itself gives an error, then just go onto sync and
emerging world, these days portage knows how to figure it's way round
all the conflicts (it wasn't always like that)
Thanks heaps.
I'll give that a whirl tomorrow and let you know how it went.
Re: [gentoo-user] Problem with Xsetup
Rajat Gujral schreef: Sorry forgot to attach the log :(( Hi holly, uwe Thanx for ur replies ... I was actually trying to install my sound driver when emerge automatically downloaded the newer version of kernel i.e 2.6.12-r10 telling me it has a better support for sound cards.. After the newer version was downloaded in /usr/src/ , i did make menuconfig to configure the kernel and save the .config file. Then make make modules_install to compile the kernel. After that i compiled the kernel and copied it to the /boot directory. But forgot to update the grub.conf file ... When rebooted the system i tried to start the X server but it always shows the same message till now..I thought there maybe some problem with the newer version. Then i realize i havent updated the grub.conf file and this was my older version being loaded so* *i make the link linux point towards older version. When i do a uname -a it shows me the older version i.e 2.6.12-r6 of the kernel . OK, this is where I'm a little confused. Would you, first of all, do an emerge -pv gentoo-sources This will not do anything (since you're using the --pretend switch); what I want to know is whether the 'symlink' USE flag is active (+, red) or inactive (-, blue), which will be revealed by the --verbose switch. If it was active, then when you emerged the upgraded kernel, the /usr/src/linux link was automatically adjusted to point to the -r10 kernel just installed, but if the USE flag is inactive, the link remained pointing to the -r6 kernel previously existing (I assume; if the USE flag was never active, and you never manually redirected the links, then /usr/src/linux could still be pointing to the first kernel you installed, for all I know). However, the target for the /usr/src/linux symlink is not likely relevant for this issue. More of relevance is the directory listing of /boot. So could you, second of all 1) mount /boot (if not mounted, and did you remember to mount /boot before installing the new kernel?) 2) post the output of la /boot (or ls -la /boot if you don't have the 'la' alias, but afaik, it's a default alias for ls -la). Oh, wait you install your kernels manually, and don't use 'make install', right? Well, let's look at the output anyway, just to know what exactly is going on. Anyway, what you need to do in order to get grub to recognize your new kernel is not to change the 'linux' link in /usr/src, but to change or add an entry in grub.conf to point to the new kernel. For instance, here's my grub.conf: default=0 timeout=10 splashimage=(hd0,1)/grub/grub-livecd2.xpm.gz title Gentoo_current (2.6.12-gentoo-r10) root (hd0,1) kernel /vmlinuz ro quiet root=/dev/hda5 video=vesafb:ywrap,mtrr,[EMAIL PROTECTED] splash=silent,fadein,theme:livecd-2005.1 CONSOLE=/dev/tty1 title Gentoo_prev (2.6.12-gentoo-r9) root (hd0,1) kernel /vmlinuz.old ro root=/dev/hda5 video=vesafb:ywrap,pmipal,mtrr,[EMAIL PROTECTED] splash=verbose,theme:emergence quiet CONSOLE=/dev/tty1 title Failsafe_current root (hd0,1) kernel /vmlinuz ro root=/dev/hda5 video=vesafb:ywrap,pmipal,mtrr,[EMAIL PROTECTED] emergency title SUSE LINUX 9.3 root (hd0,1) kernel /vmlinuz-2.6.11.4-20a-default real_root=/dev/hda6 vga=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 root root2048 sep 28 14:11 . drwxr-xr-x 23 root root 672 sep 14 14:06 .. -rw-r--r-- 1 root root 512 apr 27 14:23 backup_mbr lrwxrwxrwx 1 root root 1 apr 27 18:52 boot - . lrwxrwxrwx 1 root root 24 sep 15 23:35 config - config-2.6.12-gentoo-r10 -rw-r--r-- 1 root root 60418 mrt 24 2005 config-2.6.11.4-20a-default -rw-r--r-- 1 root root 31914 sep 15 23:35 config-2.6.12-gentoo-r10 -rw-r--r-- 1 root root 32555 jul 24 02:08 config-2.6.12-gentoo-r6 -rw-r--r-- 1 root root 32009 aug 28 19:18 config-2.6.12-gentoo-r9 lrwxrwxrwx 1 root root 23 sep 28 14:10 config.old - config-2.6.12-gentoo-r9 drwxr-xr-x 2 root root1024 aug 23 19:57 grub lrwxrwxrwx 1 root root 27 apr 27 14:23 initrd - initrd-2.6.11.4-20a-default -rw-r--r-- 1 root root 1365529 apr 27 14:23 initrd-2.6.11.4-20a-default -rw-r--r-- 1 root root 0 apr 29 00:47 .keep drwx-- 2 root root 12288 apr 27 14:13 lost+found -rw-r--r-- 1 root root 138240 apr 27 14:23 message -rw-r--r-- 1 root root 121 mrt 24 2005 README.vmlinux-2.6.11.4-20a-default.gz -rw-r--r-- 1 root root 68372 mrt 24 2005 symvers-2.6.11.4-20a-i386-default.gz lrwxrwxrwx 1 root root 28 sep 15 23:35 System.map - System.map-2.6.12-gentoo-r10 -rw-r--r-- 1 root root 708925 mrt 24 2005 System.map-2.6.11.4-20a-default -rw-r--r-- 1 root root 924836 sep 15 23:35
