[gentoo-user] dev-libs/nss-3.90
hi, just noticed that night upgrade to [~amd64] dev-libs/nss-3.90 crashed firefox and thunderbird at start: both ABENDing with `illegal instruction' diagnostics. FF rebuild did not change behavior Downgrade to ~dev-libs/nss-3.89.1 cured the issue
[gentoo-user] www-client/chromium-63.0.3239.132
just noticed new use flag in recent stable chromium ebuild: $ quse -D jumbo-build local:jumbo-build:www-client/chromium: Combine source files to speed up build process. setting that significantly speeds up emerge time (tried it twice; the second attempt had the flag set) $ qlop -gHv -d `date +%Y-%m-%d` chromium chromium-63.0.3239.132: Fri Jan 19 03:15:43 2018: 1 hour, 47 minutes, 28 seconds chromium-63.0.3239.132: Fri Jan 19 06:11:06 2018: 1 hour, 16 minutes, 14 seconds chromium: 2 times not sure if it matters in that context, but I'm using distcc and do not have ccache though
Re: [gentoo-user] Firefox 57.0.4 without pulseaudio? Possible?
On 01/14/2018 07:17 AM, tu...@posteo.de wrote: > Is it posible to use Firefox wihout pulseaudio installed? > If "yes" -- how can I acchieche this? Yes it is possible; to achieve that you just have to use www-client/firefox, e.g compile it from source Due to dependencies (now ff is boud with dev-lang/rust which subsequently requires llvm and clang) compilation time is comparable to chromium
Re: [gentoo-user] Linode discontinuing Xen, migrating to KVM
On 10/03/2017 02:28 PM, Tanstaafl wrote: > On 10/3/2017, 1:27:45 AM, victor romanchuk <r...@persimplex.net> wrote: >> there are two files to change/check before migration >> >> * /etc/inittab :: console terminal (XEN PV domUs do use hvc console and >> KVM VM employ normal linux >> console) >> >> -c1:12345:/respawn:/sbin/agetty 38400 hvc0 linux >> +c1:12345:respawn:/sbin/agetty 38400 ttyS0 linux >> >> * /etc/fstab :: XEN PV do use xvdN volumes and KVM VM volume naming is >> canonical >> >> -/dev/xvdb none swap sw 0 0 >> +/dev/sdb none swap sw 0 0 >> >> the migration itself is automated; linode did it for me flawlessly: few >> minutes of downtime needed >> to convert images and to move them to different hardware (in my case) > Thanks - but I thought these were changed as part of the automated > process (from what I've read). > > Did you change yours manually? > I forgot it :) most likely it was performed by linode automation at least what I'm seeing now confirms that (both files were modified together): $ stat /etc/inittab /etc/fstab File: '/etc/inittab' Size: 1937 Blocks: 4 IO Block: 1024 regular file Device: 800h/2048d Inode: 102725 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2017-09-11 23:46:24.0 +0300 Modify: 2017-09-11 23:46:24.0 +0300 Change: 2017-09-11 23:46:24.0 +0300 Birth: - File: '/etc/fstab' Size: 1066 Blocks: 4 IO Block: 1024 regular file Device: 800h/2048d Inode: 102672 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2017-09-11 23:46:24.0 +0300 Modify: 2017-09-11 23:46:24.0 +0300 Change: 2017-09-11 23:46:24.0 +0300 Birth: - anyway I kept that in mind when preparing myself to switch to KVM: the configuration is unusual - 64bit kernel (supplied by linode) and 32bit userspace (minimalistic gentoo with very few packages and default x86 profile)
Re: [gentoo-user] Linode discontinuing Xen, migrating to KVM
hi On 10/02/2017 08:30 PM, Tanstaafl wrote: > One thing I do seem to recall is there was somewhere that I had to > define Xen as the virtualization environment being used, but I can't > remember where I did that. Was that in the kernel config? If so, their > tool should (hopefully) handle that change. > > Anyway, was hoping some kind souls here might give me a few things to > check and possibly do proactively to ensure a smooth transition. > there are two files to change/check before migration * /etc/inittab :: console terminal (XEN PV domUs do use hvc console and KVM VM employ normal linux console) -c1:12345:/respawn:/sbin/agetty 38400 hvc0 linux +c1:12345:respawn:/sbin/agetty 38400 ttyS0 linux * /etc/fstab :: XEN PV do use xvdN volumes and KVM VM volume naming is canonical -/dev/xvdb none swap sw 0 0 +/dev/sdb none swap sw 0 0 the migration itself is automated; linode did it for me flawlessly: few minutes of downtime needed to convert images and to move them to different hardware (in my case) hth
Re: [gentoo-user] Latest chromium-40 on ~x86
On 01/24/2015 07:44 PM, Peter Humphrey wrote: On Saturday 24 January 2015 16:43:41 Nils Holland wrote: I've been using chromium successfully on my ~x86 system for quite a long time, but starting with the last two updates that came in during the last few days (namely, chromium-40.0.2214.85 and chromium-40.0.2214.91), I started having problems. ---8 The question, thus, would probably be: Anyone using one of the recent chromium-40 versions on ~x86 or anywhere else and seeing something similar? Or probably someone who has experienced something like that before and could offer a guess what might be wrong here - a real bug, custom-cflags, or something entirely different? This is and amd64 box, not ~x86, but chromium-40.0.2214.91 is working fine here. It's not been running more than a few hours since today's upgrade, but at least it does run. Also amd64: I observed another issue with chromium-40.0.2214.91 -- it breaks X11 with compositing wm (i'm running compiz) when I activate any simple effect, e.g switch to another viewpoint or something like that. At now catched that with Nvidia; have not tried with i915 (yet). The X11 `breakage' freezes the screen, so I need to kill/restart X11 to proceed. The syslog writes lots of: Jan 24 20:30:41 gentoo kernel: [1829180.480065] NVRM: Xid (PCI::05:00): 13, Graphics Exception: ChID 0003, Class 8297, Offset 17b4, Data 0001 Jan 24 20:30:46 gentoo kernel: [1829185.546349] NVRM: Xid (PCI::05:00): 13, Graphics Exception: ChID 0003, Class 8297, Offset 17b4, Data 0001 The Xorg.0.log also shows an error (in nvidia driver): (EE) [mi] EQ overflow continuing. 200 events have been dropped. (EE) (EE) Backtrace: (EE) 0: /usr/bin/X (xorg_backtrace+0x48) [0x580338] (EE) 1: /usr/bin/X (QueuePointerEvents+0x52) [0x44c432] (EE) 2: /usr/lib64/xorg/modules/input/evdev_drv.so (0x7fcbb28c2000+0x571d) [0x7fcbb28c771d] (EE) 3: /usr/bin/X (0x40+0x71eb8) [0x471eb8] (EE) 4: /usr/bin/X (0x40+0x99dfa) [0x499dfa] (EE) 5: /lib64/libpthread.so.0 (0x7fcbb9eca000+0xfd30) [0x7fcbb9ed9d30] (EE) 6: /lib64/libc.so.6 (ioctl+0x7) [0x7fcbb8c1e237] (EE) 7: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7fcbb37ea000+0x116bec) [0x7fcbb3900bec] (EE) 8: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7fcbb37ea000+0x116ca7) [0x7fcbb3900ca7] (EE) 9: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7fcbb37ea000+0x1196e9) [0x7fcbb39036e9] (EE) 10: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7fcbb37ea000+0x12e181) [0x7fcbb3918181] (EE) 11: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7fcbb37ea000+0x13af8d) [0x7fcbb3924f8d] (EE) 12: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7fcbb37ea000+0x12c2a2) [0x7fcbb39162a2] (EE) 13: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7fcbb37ea000+0x54b567) [0x7fcbb3d35567] (EE) 14: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7fcbb37ea000+0x54bf30) [0x7fcbb3d35f30] (EE) 15: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7fcbb37ea000+0x54e2f8) [0x7fcbb3d382f8] (EE) 16: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7fcbb37ea000+0x55ccc5) [0x7fcbb3d46cc5] (EE) 17: /usr/bin/X (0x40+0x357fe) [0x4357fe] (EE) 18: /usr/bin/X (0x40+0x395da) [0x4395da] (EE) 19: /lib64/libc.so.6 (__libc_start_main+0xf5) [0x7fcbb8b62aa5] (EE) 20: /usr/bin/X (0x40+0x24d7e) [0x424d7e] (EE) [1829865.192] [mi] Increasing EQ size to 1024 to prevent dropped events. [1829865.193] [mi] EQ processing has resumed after 239 dropped events. [1829865.212] [mi] This may be caused my a misbehaving driver monopolizing the server's resources.
Re: [gentoo-user] Latest chromium-40 on ~x86
On 01/25/2015 04:29 PM, Volker Armin Hemmann wrote: Am 25.01.2015 um 11:08 schrieb victor romanchuk: On 01/24/2015 07:44 PM, Peter Humphrey wrote: On Saturday 24 January 2015 16:43:41 Nils Holland wrote: The question, thus, would probably be: Anyone using one of the recent chromium-40 versions on ~x86 or anywhere else and seeing something similar? Or probably someone who has experienced something like that before and could offer a guess what might be wrong here - a real bug, custom-cflags, or something entirely different? This is and amd64 box, not ~x86, but chromium-40.0.2214.91 is working fine here. It's not been running more than a few hours since today's upgrade, but at least it does run. Also amd64: I observed another issue with chromium-40.0.2214.91 -- it breaks X11 with compositing wm (i'm running compiz) when I activate any simple effect, e.g switch to another viewpoint or something like that. At now catched that with Nvidia; have not tried with i915 (yet). works fine with KDE and desktop effects turned on. Using xorg's amd drivers. Runs on for days without problems. Just emerged `subject' on notebook [adm64] with i915: behaves normally despite of compiz. Most likely something gets wrong with x11-drivers/nvidia-drivers-340.65 (the card is too old and incompatible with latest driver release) thanks
Re: [gentoo-user] Re: XFCE weather plugin does not work
On 10/18/2014 02:37 AM, David W Noon wrote: I have prepared some patches from the Xfce repository with line addressing to match the Gentoo sources tarball. I attach a tarball of theses patches that can be untarred in /etc/portage/patches/ applied. thank you
Re: [gentoo-user] How can I fix wrong boot order?
On 10/29/2013 10:47 PM, Jarry wrote: Hi Gentoo-users, I noticed strange message during boot-up of one of my servers: __ [snip] As you see, syslog-ng can not open conection to remote syslog collector. Reason seems to be quite clear: at the time when syslog-ng starts, enp3s0 interface is not up (only loopback). I do not know how this happened, but I think it has something to do with either sendmail, clamav, or dovecot. [snip] __ So how can I fix it on the 1st server, so that syslog-ng starts after network interface is up? Jarry disable explicit syslog-ng service startup from the runlevel (one would start anyway as a dependency) rc-update del syslog-ng does the trick victor
Re: [gentoo-user] re: automounting removable drives
On 10/07/2013 11:36 PM, Alexander Kapshuk wrote: Thanks for your responses. I'm sorry I forgot to mention that I do have xfce4-mount-plugin installed. box0=; equery list '*xfce*'|grep mount xfce-extra/xfce4-mount-plugin-0.6.4 But I still can't auto-mount my removable drives. So I thought that perhaps some further configuration had to be done. That question still remains, how do I do it? Thanks. hi, you need to emerge just one package: xfce-extra/thunar-volman (it may pull some dependencies); it does what you asked for victor
Re: [gentoo-user] Local root exploit (not?) working...
On 05/15/2013 08:35 PM, Jarry wrote: Actually, it does not (?) work on my box even with PERF_EVENTS, but when I compile run it (as non-root user), my system is instantly restarted. So it seems that gentoo-sources 3.7.10-r1 are at least partially affected. I hope to see fix soon! this is already reflected in the portage: gentoo-sources-3.7* removed from the tree with an advice to upgrade to 3.8.13 -- https://bugs.gentoo.org/show_bug.cgi?id=469854 victor
Re: [gentoo-user] Udev-197 : 4 show-stoppers
On 01/20/2013 12:51 PM, Philip Webb wrote: I just tried upgrading to udev-197 , which is supposed to be stable. There were multiple problems I'm now back with udev-171 . (1) Setting system clock using HW clock; can't access HW clock. (2) Mounting local filesystems; mount point /dev/shm doesn't exist. (3) 'startx' : no mouse or keys. (4) 'dhcpcd' hangs. I tried revdep-rebuild , recompiled util-linux kdelibs mesa xf86-input-evdev xorg-server , recompiled glibc nvidia-drivers , recompiled the kernel (3.5.3) to enable DEVTMPFS , checked 'news' (nothing relevant), checked my archive of gentoo-user msgs (nothing relevant), rebooted many times between all these efforts. Has anyone else encountered anything like this ? Does anyone have any advice ? just migrated to sys-fs/udev-197 - everything went smoothly and seems to work. the only observation at this time is absence of device file /dev/root whilst both /etc/mtab and /proc/mounts are referring to that device node: # grep root /etc/mtab /proc/mounts /etc/mtab:/dev/root / ext4 rw,relatime,commit=0 0 0 /proc/mounts:rootfs / rootfs rw 0 0 /proc/mounts:/dev/root / ext4 rw,relatime,data=ordered 0 0 [i'm running 3.6.11-gentoo, proprietary nvidia, sys-fs/mdadm, sys-fs/lvm2, with no initrd of any flavour; the system boots using legacy grub; the root filesystem is on softraid device] have i missed something? thank you -- victor
Re: [gentoo-user] Gentoo guest audio on Virtualbox
On 12/07/2012 05:26 PM, Mick wrote: On Monday 03 Dec 2012 10:53:16 Markos Chandras wrote: Any ideas? I also have a Windows Guest (Host settings Pulseaudio/Intel HD Audio) and the sound works there without problems. If you're running the binary VBox package I seem to recall that sound was broken a couple of years ago. Yep, here it is: https://bugs.gentoo.org/show_bug.cgi?id=310793 Crikey! 85 comments and still going. I hope they add it to the main tree soon. and the workaround proposed in that discussion still working too: --- /usr/portage/media-libs/libsdl/libsdl-1.2.15-r2.ebuild2012-08-27 22:01:20.0 +0400 +++ /usr/local/portage/media-libs/libsdl/libsdl-1.2.15-r2.ebuild 2012-08-30 10:52:06.303133205 +0400 @@ -108,7 +108,6 @@ --enable-timers \ --enable-file \ --enable-cpuinfo \ ---disable-alsa-shared \ --disable-esd-shared \ --disable-pulseaudio-shared \ --disable-arts-shared \ -- victor
Re: [gentoo-user] Want to seriously test a NEW hard drive
hi
Dale wrote, at 08/05/2012 04:45 PM:
Howdy,
I have heard of bonnie and friends. I also think dd could do some
testing too. Is there any other way to give this a good work and see if
it holds up? Oh, helpful hints with Bonnie would be great too. I have
never used it before. Maybe someone has some test that is really brutal.
some time ago i have played with bonnie++ to figure out my hard disk performance
using different filesystems and io schedulers. the script invokes 3 bonnie
instances; each instance runs its own set of tests: write/read/rewrite a 30gb
file followed with different file operations on 48k small files spread over 32
sub-directories:
#!/bin/bash
#
scratch=${1:-$(pwd)}
#
date
ft=$(df -Pl $scratch|tail -1|awk '{print $6}')
mnt=($(mount|grep $ft ))
dev=$(basename $(readlink -fn ${mnt[0]}))
sched=$(cat /sys/block/$dev/queue/scheduler|sed -e 's/.*\[//1' -e 's/\].*//1')
log=$dev-${sched}-${mnt[4]}
echo $log
rm -f ${log} ${log}.html
/usr/sbin/bonnie++ -p 3
/usr/sbin/bonnie++ -qd $scratch -n48:128K:16K:32 -ys -s30g -mg1 ${log}
/usr/sbin/bonnie++ -qd $scratch -n48:128K:16K:32 -ys -s30g -mg2 ${log}
/usr/sbin/bonnie++ -qd $scratch -n48:123K:16K:32 -ys -s30g -mg3 ${log}
wait
/usr/sbin/bonnie++ -p -1
bon_csv2html ${log} ${log}.html
date
this script worked around 30mins on a sata3 1tb drive. presuming your 3tb, you
may adjust the file size and/or number of bonnie instances to fill up the disk
space; then start the script and leave it running for a day. i guess this test
would be brutal enough and on completion the disk might be considered good :)
victor
Re: [gentoo-user] Xen virtual devices not working - no guests
hi Konstantinos Agouros wrote, at 02/05/2012 01:50 PM: and I checked that they are loaded. The real strange thing is, that I have an identical .config (regarding the xen stuff) on a 2nd box and all is fine. So I need to debug the hotplug scripts somehow to see what is going wrong. I tried to pass pci hardware (network intercaces) to the guest under 3.2 _this_ is working. the only place i'm seeing details about backend drivers activity is standard syslog output (/var/log/messages). i guess the domU creation at dom0 side goes as follows: * xm/xend (or xl/libxl - i did not migrate to one yet) queries xenstore for resources the domU is being assigned with * if xenstore succeeds with the inquiry it marks the resource as allocated and posts subsequent inquiry to dom0 kernel as a holder of all backend xen resources * the kernel performs particular resource initialization and generates an appropriate event * the event is handled by udev (/etc/udev/rules.d/xen-backend.rules) * udev processes a matching rule and calls userspace script (vif-setup for network backends and vscsi for block backends) attaching the resource to the domU being started. i believe all possible debugging should deal with these scripts my second guess is that real hardware passthrough works indentically i just uploaded everything related to a pure pv domU creation: http://pastebin.com/5m7C3QkX - it might be helpful to find the difference in your configuration victor
Re: [gentoo-user] Xen virtual devices not working - no guests
Konstantinos Agouros wrote, at 02/03/2012 09:01 PM: When I boot gentoo-sources 3.2.1 Dom0 boots, and DomUs would boot if they had no virtual block or network devices. Both backend device options are in the Dom0 kernel. Anybody has a hint on how to debug this? most likely this is due to dom0 misconfiguration. should be something like that (xen part): $ grep '^CONFIG.*XEN.*' /usr/src/linux-3.2.1-gentoo-r2/_dom0/.config CONFIG_XEN=y CONFIG_XEN_DOM0=y CONFIG_XEN_PRIVILEGED_GUEST=y CONFIG_XEN_PVHVM=y CONFIG_XEN_MAX_DOMAIN_MEMORY=128 CONFIG_XEN_SAVE_RESTORE=y CONFIG_PCI_XEN=y CONFIG_XEN_PCIDEV_FRONTEND=m CONFIG_XEN_BLKDEV_BACKEND=m CONFIG_XEN_NETDEV_BACKEND=m CONFIG_XEN_BALLOON=y CONFIG_XEN_DEV_EVTCHN=y CONFIG_XEN_BACKEND=y CONFIG_XENFS=y CONFIG_XEN_COMPAT_XENFS=y CONFIG_XEN_SYS_HYPERVISOR=y CONFIG_XEN_XENBUS_FRONTEND=m CONFIG_XEN_GNTDEV=m CONFIG_XEN_GRANT_DEV_ALLOC=m CONFIG_SWIOTLB_XEN=y CONFIG_XEN_TMEM=y CONFIG_XEN_PCIDEV_BACKEND=m running dom0 must have these modules loaded (compiled as modules in my config): $ lsmod|grep xen xen_netback20821 0 [permanent] xen_blkback16116 0 [permanent] victor
Re: [gentoo-user] About this graphite stuff
Alex Schuster wrote, at 01/29/2012 11:23 PM:
What are your impressions on this? Is it fun? Will there be a noticeable
speed difference? Do packages fail to build? We just had a 'Graphite
causing trouble' thread here, the problem was that dev-libs/cloog-ppl
has to be rebuilt when dev-libs/ppl has been updated. Can there be other
problems, which would make me waste much more time than I could
possibly gain by using these optimizations?
i'm using graphite on core-i7 (950), x86_64 since the release of gcc-4.4.5 and
consider it as 'just fun' - i did not observe significant speed difference but
it should depend on a software you're going to 'graphitize'. things installed on
my desktop are mostly for development (emacs, gdb, *sql, php, perl) with trivial
multimedia (mplayer with gnome frontend), a set of web browsers and ordinary
office framework: thunderbird, pidgin and libreoffice
just for reference these are CFLAGS from my /etc/make.conf:
CFLAGS=-O2 -g0 -march=core2 -msse4 -mcx16 -mpopcnt -msahf \
-ftree-loop-distribution -ftree-loop-linear -mmmx \
-floop-interchange -floop-strip-mine -floop-block -pipe
i do not use 'native' flag because that machine acts as distcc server for
several smaller core-ix computers
the only graphite incompatibility i've detected is x11-wm/compiz; however this
is easily worked around using portage environment quirks in
/etc/portage/env/x11-wm/compiz:
CFLAGS=-O2 -g0 -march=core2 -msse4 -mmmx -pipe
CXXFLAGS=${CFLAGS}
Re: [gentoo-user] gentoo-sources and xen blktap driver?
Konstantinos Agouros wrote, at 01/07/2012 03:51 PM: since xen got into the mainstream kernel the way to go is to use gentoo-sources for dom0 and the domUs. However the blktap modules are not there. Is there any way to get this to work? blktap drivers were excluded from kernel mainline since 3.x, these two threads from xen-users mailing list might put some light in that context: http://old-list-archives.xen.org/archives/html/xen-users/2011-07/msg00637.html http://old-list-archives.xen.org/archives/html/xen-users/2011-10/msg00065.html the latest sys-kernel/xen-sources containing working blktap (not blktap2) is 2.6.38 (this is buggy from my point of view; i'm still sitting on 2.6.34-r5 for production installations) victor
Re: [gentoo-user] bluetooth and headset with gentoo...
Tamer Higazi wrote, at 01/06/2012 09:17 AM:
however, I need to see it as an alsa device. this is my problem.
it's not a problem, according to alsa docs http://alsa.opensrc.org/.asoundrc
pcm.genius {
type bluetooth
}
pcm.genius-in {
type plug
slave {
pcm genius
rate 48000
}
}
ctl.genius {
type bluetooth
}
does it all: the headset works pretty good with audio apps i'm using in that
context: skype and mplayer -ao alsa:device=genius. however i have no clue on how
to integrate bluetooth audio with desktop (gnome2 in my case). without
pulseaudio of course. anyone did that?
victor
Re: [gentoo-user] bluetooth and headset with gentoo...
Tamer Higazi wrote, at 01/06/2012 11:14 AM:
People!
I am not a bluetooth expert how do I configure bluez to make a
permanent connection with the bluez headset???
I did:
pcm.jabra {
type bluetooth
}
[snip]
.asoundrc is an audio part of configuration. bebore that you have to:
* configure the kernel to support audio over bluetooth (these settings are for
3.x kernel, for earlier versions these are slightly deffer from showed):
CONFIG_BT=m
CONFIG_BT_L2CAP=y
CONFIG_BT_SCO=y
* install net-wireless/bluez
* configure and pair your headset with host bluetooth adapter using desktop
applet - net-wireless/blueman in my case, or manually - hcitool etc
* enjoy the result :)
hth
victor
Re: [gentoo-user] Two issues with OpenRC/baselayout2 migration on a hosted VM
Pandu Poluan wrote, at 12/13/2011 10:26 PM: On Dec 14, 2011 1:06 AM, Tanstaafl tansta...@libertytrek.org mailto:tansta...@libertytrek.org wrote: What should I set this to? Assuming that Linode is indeed using Xen, would it be: rc_sys=xenU ? AFAIK Linode uses Xen so xenU is correct. What I really want to know is what happens if we specify a 'wrong' rc_sys value... (I also want to know why 'rc -S' is so unhelpful, but not as much as the above.) i have looked through openrc sources and experimented a bit; the idea of rc_sys is simple: the contents of that variable affects 'keyword' dependencies in /etc/init.d/ scripts. the feature is documented, see runscript(8) for details, but apparently does not work as expected. i also did not find valuable 'keyword' dependencies in software packages i use thus considered that rc_sys might be set to any value with no side effects another thing i found is an $RC_SYS environment variable available to all scripts initiated by rc; that one is set to value defined in /etc/rc.conf or automatically detected if rc_sys is not explicitly set. the automatic detection is trivial, eg. if the directory /proc/xen does exist, then $SYS_RC is set to XENU. setting of $SYS_RC to XEN0 would be in case of /proc/xen existence and if contents of the file /proc/xen/capabilities is equal to control-d. all that stuff could be found in src/librc/librc.c i'm using $RC_SYS as a flag controlling start of xen dom0 daemons: rc_sys is commented out in /etc/rc.conf to let runscript autodetect the environment. all xen related stuff is started from /etc/local.d, like that: $ cat /etc/local.d/xen.start if [ x$RC_SYS = xXEN0 ]; then # start xenstored, xenconsole, configure xen networking etc else # do something else related to baremetal os boot fi this slightly speeds up boot process and produces more clear logs
Re: [gentoo-user] Re: Anyone using libreoffice 3.5.0.0 yet?
walt wrote, at 12/07/2011 02:40 AM: On 12/05/2011 09:41 AM, Paul Hartman wrote: Looks like the ebuild has been updated and now has -gtk3 by default. :) thank you for the update Yes, I just finished rebuilding it and all the painting problems are gone. No hacking needed :) Just be aware that some settings may get reset to default values and you need to look in the various preferences menus or toolbar settings to get back your favorite look and feel. Not a big deal as long as you know what to do about it. All of my usual settings are still available but I had to re-enable them before I was sure they weren't removed or broken. i was unable to find ones; apparently everything remained intact victor
Re: [gentoo-user] Anyone using libreoffice 3.5.0.0 yet?
Can anyone confirm or deny? i confirm. apart of these 'painting' issues in localc, observed both lowriter and localc crash during arbitrary pointer movements over menu items. it seems all that misbehavior is related to x11-libs/gtk+:3 after an hour of tries decided to switch back to libreoffice-3.4.4-r1; 3.5.0 is too fresh to use :) victor
Re: [gentoo-user] how can I disable renaming of root fs to /dev/root?
Jarry wrote, at 11/11/2011 09:37 PM:
Hi,
this is actually not problem but rather a matter of customs:
My new fresh installed system shows root-fs in df as
/dev/root, not actuall device (in my case /dev/md2).
I think I coud get used to it, but some software still needs
/dev/md2 (i.e. lilo), other does not find /dev/md2 anymore
and needs /dev/root to work properly (i.e. monit).
Moreover, in /etc/fstab I still have to use /dev/md2 as root
filesystem, while /etc/mtab shows only /dev/root.
I do not like such a mess and I'd like to put it in rather
consistent state where root filesystem has always the same
and only name. Is there some way to stop this renaming
of root filesystem to /dev/root and let it be as in old
baselayout1?
Jarry
try that patch (attached):
sometime ago i have found it in gentoo forums. probably did few modifications in
the original i found, cannot remember. it works for me for months with no
visible problems
victor
--- mtab.orig 2011-05-09 10:39:38.510430618 +0400
+++ /etc/init.d/mtab 2011-11-12 15:23:23.113980922 +0400
@@ -12,6 +12,9 @@
start()
{
+ # look in an easy way to where root is mounted from
+ ROOTFS=$(readlink -f /dev/root)
+
# /etc/mtab could be a symlink to /proc/mounts
if [ ! -w /etc/mtab -a -L /etc/mtab ]; then
eeinfo Skipping mtab update (non writeable symlink)
@@ -28,7 +31,8 @@
# makes / readonly and dismounts all tmpfs even if in use which is
# not good. Luckily, umount uses /etc/mtab instead of /proc/mounts
# which allows this hack to work.
- grep -v ^[^ ]* / tmpfs /proc/mounts /etc/mtab
+ grep -v ^[^ ]* / tmpfs /proc/mounts |
+ awk '$1 != rootfs {print}' | sed 's%/dev/root%'${ROOTFS}'%' /etc/mtab
# Remove stale backups
rm -f /etc/mtab~ /etc/mtab~~
Re: [gentoo-user] Xen 4.1.1 trouble
Konstantinos Agouros wrote, at 11/08/2011 02:14 PM: Hi, I upgraded one system from Xen 3.4.2 to 4.1.1. Now when I start a guest the whole machine instantly reboots. Are there any changes necessary so that this works? I didn't touch the configuration of the guest. It's a PV gentoo running either xen-sources-2.6.34 or .38. Konstantin if you're running pure pv domUs (with no real hardware support), this should be completely transparent for the hypervisor i'm running x86_64 xen-sources-2.6.34-r5 on both dom0 and domUs on Xen 4.1.2 (still using xend/xm interface): everything works stable enough. i have already switched to new hardware, upgraded xen, kernel configuration and versions whilst domU configs did not change for years the only significant improvement of recent xen (for small configurations: i dont have experience with more than 2 cpu sockets systems) is an enhanced support of vt-d (iommu); turn it off and re-try - there are many incompatibilities there probably causing xen to hang victor
Re: [gentoo-user] emerge dependence question
Zhang Jun wrote, at 11/06/2011 02:27 PM: # eselect editor list Available targets for the EDITOR variable: [1] /bin/nano [2] /bin/ed [3] /usr/bin/ex [4] /usr/bin/vi [ ] (free form) sanitize the EDITOR environment: eselect editor update then set a suitable one from the displayed list. as far as i know the @system requires at least one editor to be installed and set as default Something wants emacs, but it doesn't appear to be any of your installed package. What doe eselect editor list show? -- Neil Bothwick
Re: [gentoo-user] Hoping someone can help explain distcc to me
i had noticed that distcc is peevish about CFLAGS: these should be compatible on both client and server. in my case i made these similar on both machines (laptop is core2duo and desktop is core2quad; both are running amd64 arch) I don't think this is true - as long as the CHOST is identical, there should be no problem. CHOST defines the arch (i686, amd64, arm ..) whilst CFLAGS control gcc behavior and the binary code generation produced by compiler. in my case core2quad (q8300) i'm using in the desktop supports sse4.1 instruction set and notebook powered with core2duo (t7600) does not have that cpu feature. having option `-msse4.1' set in CFLAGS at desktop side will causes frequent compilation failures (initiated by distcc) or, in worst case - arbitrary crashes at notebook when running binaries compiled in distributed distcc environment yet another way to install packages on weak notebook running it on the same arch as desktop runs, - is to create binaries at powerful machine (while emerging or with quickpkg utility) and share $PKGDIR with laptop This means some extra work, and also use flags need to be compatible, but the speedup would be much bigger than with just distcc. What about exporting the whole root file system and mounting it on the fast desktop, chrooting and emerging? i do not insist the distcc is the only or most efficient way to maintain gentoo installation on a slow machine (having something more powerful nearby). just tried to explain how does distcc work victor
Re: [gentoo-user] Hoping someone can help explain distcc to me
Both machines contain distcc in FEATURES. It's not using
-march=native. I've tried various -jN values with no real difference
in performance.
only client (your laptop) machine should be distcc featured. for server
(desktop) that feature is useless
On the desktop, /etc/conf.d/distcc contains (among other things):
DISTCCD_OPTS=${DISTCCD_OPTS} --allow 192.168.0.0/24
DISTCCD_OPTS=${DISTCCD_OPTS} --listen 192.168.0.100
this is server distcc daemon configuration, one just instructs daemon on what
network interface to listen for incoming connections (interface with ip
192.168.0.100 in your case) and filter incoming distcc connections by source
address: allow only those coming from local network machines with ip addresses
192.168.0.1 to 192.168.0.254
then distccd have to be started: /etc/init.d/distccd start
And /etc/distccd/hosts contains:
192.168.0.0/24
this file configures distcc client behavior (actually the configuration can be
complex, see distcc man page for details), but in trivial case (for home
computing) it might look like:
192.168.0.100/6 127.0.0.1/1
e.g the client is able to send up to 6 distcc jobs to 192.168.0.100 and limit to
one job at local machine. client's /etc/make.conf has to have distcc feature
enabled (FEATURES=distcc). surely you can play with job distribution rules
around the network. `distcc --show-hosts` command displays what you configured.
the number of cuncurrently running jobs (-j flag) has to be not less than sum of
local and remote jobs
i had noticed that distcc is peevish about CFLAGS: these should be compatible on
both client and server. in my case i made these similar on both machines (laptop
is core2duo and desktop is core2quad; both are running amd64 arch)
yet another way to install packages on weak notebook running it on the same arch
as desktop runs, - is to create binaries at powerful machine (while emerging or
with quickpkg utility) and share $PKGDIR with laptop
hth
Re: [gentoo-user] OT: but cool - NASDAQ is gentoo powered
1 Desktop 1 Netbook (For holiday and during travel) 1 home server (running Xen with virtualized Gentoo instances) i own similar combination (the server is actually head/mouseless desktop powered by core i7 and equipped with 24gb of ram allowing to concurrently run number of gentoo and freebsd pv-machines); also renting a small gentoo powered vps running as mail/list/file server for personal use at work have no gentooine hardware :) -- victor
Re: [gentoo-user] Firmware exists but fails to load
it does not actually matter how you configured the driver -- built-in kernel or as module: everytime when driver operates the device, it checks whether firmware is loaded. Are you sure about that? AFAIK firmware loading is only attempted once, when the driver is first initialized. i'm not sure - just spent few minutes looking through the drivers/net/r8169.c code: the driver attempts to load firmware every time when opening a particular pci eth device functionality of /lib/udev/firmware is controlled by USE=extras. That might have been the case at some point but now sys-fs/udev-164-r2 and sys-fs/udev-171-r1 both install the firmware-related stuff (rules and helper) even with USE=-extras you are right (also reviewed contents of udev tarbal and appropriate ebuild code) - `extras' use flag just adds some runtime dependencies andrea thank you, victor
Re: [gentoo-user] Re: Firmware exists but fails to load
? Udev has been the standard way to service kernel firmware requests for quite some time. The relevant bit is in /lib/udev/rules.d/50-firmware.rules . Ok so that must be working on my laptop (automatically, i didn't configure anything) but failing on my desktop. However, udevd is only started after the kernel is loaded, and therefore will only load firmware for drivers which are built as modules. I tried compiling as a module, and it still failed. I'll go back and verify I haven't made a mistake, then check firmware.rules. it does not actually matter how you configured the driver -- built-in kernel or as module: everytime when driver operates the device, it checks whether firmware is loaded. if it does not or the firmware is not preloaded at kernel build time as a blob, the driver requests for firmware. the request is a generated kernel event which is handled in userspace by udev. the udev daemon processes event using mentioned above rule. the rule is trivial -- it starts a firmware loader utility (/lib/udev/firmware) with parameters passed within the event: device name and firmware file path. appropriate status is returned back to kernel and dispatched to the driver in your case the status is -2 (ENOENT) so it could be problem with either firmware blob file or firmware loader itself. functionality of /lib/udev/firmware is controlled by USE=extras. did you installed udev with extras support? again, firmware load is udev responsibility. you may diagnose all the stuff enabling udev debug output in /etc/udev/udev.conf finally i confirm that r8169 driver works fine on my notebook with 2.6.39 kernel
Re: [gentoo-user] USB-BT211 causing udev to fail, related to usb3, how to disable?
I have an ASUS USB-BT211 bluetooth dongle, I have never been able to make it work and it causes udev to fail at startup and sending the following msg to the syslog: 2011-08-13T09:45:30+02:00 poff udevd[5235]: timeout 'usb_id --export /devices/pci:00/:00:12.0/usb3' This seems to be related to usb3, however, neither the mobo (ASUS M4A79XTD EVO) nor the the installed kernel has usb3 support; if related to usb3 is expected. this dongle actually has atheros chip inside, so you have to add appropriate support in kernel (CONFIG_BT_ATH3K) and install sys-kernel/linux-firmware the issue is not related to usb3 (xhci). usb3 in that context means just port you're attaching the device to hth||
Re: [gentoo-user] [OT] NFSv4: 32-bit server versus 64-bit client?
I'm trying to be a good gentoo netizen by nfs-sharing /usr/portage between my three local gentoo machines, and failing :( After weeks of fiddling, I discovered today that my problems come from using a 32-bit machine to serve my two 64-bit NFS clients(!) (I'll mention up front that NFSv3 works perfectly -- only NFSv4 is bad.) this is due to different authentication methods used in nfs3 and nfs4 and does not rely on installation arch (32/64bit). you have to tune up nfs4 infrastructure. on both client and server make sure you have - nfs4 and inotify support in kernel - net-fs/nfs-utils installed with nfs4 support - grep NFS_NEEDED_SERVICES /etc/conf.d/nfs shows 'NFS_NEEDED_SERVICES=rpc.idmapd' - grep Domain /etc/idmapd.conf shows 'Domain = your local domain' - rpc.idmapd daemon is running (if it does not, restart nfs stack) - surely portage uid/gid are the same on all nfs-ed machines server side: /etc/exports: /usr/portage 192.168.1.0/24(async,no_root_squash,rw,no_subtree_check) client side: grep nfs /etc/fstab: server:/usr/portage /usr/portage nfs4 defaults,rw 0 1 consult rpc.idmapd(8) for details that way i'm sharing portage at home. works pretty good for months i've migrated to nfs4 hth
Re: [gentoo-user] Failure to compile 2.6.39-gentoo-r3
LD .tmp_vmlinux1 arch/x86/built-in.o: In function `microcode_init': microcode_core.c:(.init.text+0xaeb5): undefined reference to `init_intel_microcode' make: *** [.tmp_vmlinux1] Error 1 this should not happen: if you selected any module from the kernel tree to be built into the kernel (you did it for cpu firmware loader as it comes from previous message), the compiled code for every module pretended to be built into the kernel image is additively placed into built-in.o - actually the kernel tree contains built-in.o files for every kernel component, arch, mm, drivers, net etc. at the final build stage, all the object files are linked together producing vmlinux elf binary. i just tried to build test kernel with built-in firmware loader for x86 and x86_64 arches: both completed successfully so i guess you've got error due to some inconsistencies in the kernel directory. try it again from the scratch: * save somewhere out of kernel tree your current /usr/src/linux/.config * wipe out compeled and generated code from the kernel tree: cd /usr/src/linux; make mrproper * restore .config * make silentoldconfig * make words below are not directly related to the case, but proper behavior is to build cpu firmware loader as module (i presume the kernel is configured to load and unload modules: CONFIG_MICROCODE=m CONFIG_MICROCODE_INTEL=y CONFIG_MICROCODE_OLD_INTERFACE=y CONFIG_FW_LOADER=y * as you probably know microcode loader runs in userspace once at boot time (you have to emerge sys-apps/microcode-ctl and rc-update microcode_ctl boot) * microcode service script /etc/init.d/microcode_ctl at start loads kernel module 'microcode' * then the script starts microcode loader (data is in sys-apps/microcode-data) * at the end the script unloads microcode module thus freeing kernel resources (loaded data remains into cpu cache until reset) hth, victor
Re: [gentoo-user] Any way around Argument list too long?
it could be slightly less efficient comparing to plain `rm', but worked around
your problem:
find your-dir -ctime -1 -exec rm {} \;
basically `find' has a lot options filtering result set. these include
time/date, file name (regexp), file type and so on. consult man for details
victor
Grant wrote, at 07/17/2011 11:32 PM:
My crontab deletes all files of a certain type in a certain folder
with yesterday's date in the filename. It usually executes but
sometimes fails with:
/bin/rm: Argument list too long
What would you do about this?
- Grant
