- Arch-general - lists.archlinux.org

[arch-general] Problem vmware 10 when I updated kernel arch
by Maykel Franco 25 Feb '14

25 Feb '14

Hi, my version kernel is 3.13.5-1 ARCH and I have updated the arch. When I run the vmware, I get this error: 2014-02-24T00:07:54.226+01:00| vthread-3| I120: using /sbin/gcc for preprocess check 2014-02-24T00:07:54.237+01:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "3.13.5-1-ARCH". 2014-02-24T00:07:54.237+01:00| vthread-3| I120: The header path "/lib/modules/3.13.5-1-ARCH/build/include" for the kernel "3.13.5-1-ARCH" is valid. Whoohoo! 2014-02-24T00:07:54.292+01:00| vthread-3| I120: Invoking modinfo on "vmnet". 2014-02-24T00:07:54.293+01:00| vthread-3| I120: "/sbin/modinfo" exited with status 256. 2014-02-24T00:07:54.477+01:00| vthread-3| I120: Setting destination path for vmnet to "/lib/modules/3.13.5-1-ARCH/misc/vmnet.ko". 2014-02-24T00:07:54.478+01:00| vthread-3| I120: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar". 2014-02-24T00:07:54.484+01:00| vthread-3| I120: Successfully extracted the vmnet source. 2014-02-24T00:07:54.484+01:00| vthread-3| I120: Building module with command "/sbin/make -j4 -C /tmp/modconfig-VUc3wF/vmnet-only auto-build HEADER_DIR=/lib/modules/3.13.5-1-ARCH/build/include CC=/sbin/gcc IS_GCC_3=no" 2014-02-24T00:07:56.956+01:00| vthread-3| W110: Failed to build vmnet. Failed to execute the build command. Can I help me please?? Thanks in advanced.

2 2

[arch-general] libreoffice-writer upgrade
by Myra Nelson 25 Feb '14

25 Feb '14

After the latest writer upgrade (version 4.2.1-1), lowriter fails to run. I get the following error message when trying to start it from a console. /usr/lib/libreoffice/program/soffice.bin: error while loading shared libraries: libtubeslo.so: cannot open shared object file: No such file or directory I've googled the missing library and had no luck finding it and I've found no other bug reports any where. Downgrading to libreoffice-writer-4.1.5-1 cures the problem. Sorry for the noise. Myra -- Life's fun when your sick and psychotic!

3 4

[arch-general] NetworkManager 0.9.8.8-2 does not work with systemd 208
by Austin Lund 24 Feb '14

24 Feb '14

After my last upgrade I noticed that the NetworkManager service was failing. The error message was that NetworkManager could not load because it couldn't find libsystemd.so.0. I'm running systemd 208-11. The unified systemd library is in 209, irrc. Systemd 209 isn't available in core yet, but nevertheless, the dependencies in NetworkManager should have been updated. Solution to the problem is to force NetworkManager to 0.9.8.8-1.

5 5

Re: [arch-general] arch-general Digest, Vol 112, Issue 26
by Hugo Rabson 24 Feb '14

24 Feb '14

> On Feb 22, 2014, at 22:48, arch-general-request(a)archlinux.org wrote: > > Are you trying to build a full-featured Live desktop environment for > chromebooks? I'm thinking about it, but I'm not sure if it's needed. I've written one script to generate an ArchLinux|ARM bootable USB/SD card-based installation; another, to generate a Debian installation. In each case, it goes from shell command to usable installation in about half an hour. It works for the Samsung Chromebook (ARM 7-based). It might work for other ARM-based systems; I don't know. In each case, the OS is installed on an external device, which means it is awfully close to being a "live CD" (not a CD, but you get the point). The principal advantage of a 'live' device would be non-permanence of user data. I've had a look at porting Tails to the ARM platform. It would be nontrivial, but it could be done. Still, I'm happier with the idea of working with ArchLinux, not Debian (or Tails). ArchLinux's kernel sources are available and easy to modify (by me), whereas I've had no luck with Debian's kernel. If the root partition of the device is encrypted, do we really need it to be 'live' at all? Does anyone actually want a live version of ArchLinux for ARM systems, or would a freely available and easy-to-build-at-home external SD card or thumb drive do? What is the problem we're trying to solve? Depending on our objective - privacy, disaster recovery, or merely mucking about with a Chromebook without nuking its internal drive - we might not need the live capability. Comments? -Hugo

2 1

[arch-general] How to reboot remotely without hanging ssh session?
by David C. Rankin 23 Feb '14

23 Feb '14

Guys, I remote administer one arch server and after moving to systemd I haven't found a way to reboot without hanging the ssh session. Prior to system, we could simply pass the shutdown command via ssh and the ssh session would complete/close before reboot took place: i.e. $ ssh remote.host.org "sudo shutdown -r now" However with systemd, using "systemctl reboot" the ssh session hangs until the remote host reboot or a timeout occurs. Is there a better way to reboot a remote server and avoid this? -- David C. Rankin, J.D.,P.E.

10 10

[arch-general] nginx in a linux container
by arnaud gaboury 23 Feb '14

23 Feb '14

Hi all, I have a running container managed by systemd-nspawn. I want now install/set up nginx inside it, following Arch wiki. gab@dahlia ➤➤ ~ # mkdir $JAIL/dev mkdir: cannot create directory ‘/srv/hhtp/dev’: No such file or directory <<<<< ??? gab@dahlia ➤➤ ~ % ls -al / drwxr-xr-x 4 root root 4.0K May 31 2013 srv/ gab@dahlia ➤➤ ~ % ls -al /srv drwxr-xr-x 2 root root 4.0K May 31 2013 http/ Where do this issue comes form ? Thank you for help

4 4

[arch-general] Building a live USB version of ArchLinux for ARM users
by Hugo Rabson 23 Feb '14

23 Feb '14

Is anyone interested in working with me to build a live USB edition and/or hardened ArchLinux for ARM users (specifically, users of ARM-based chromebooks)? It would be nontrivial but achievable. The question is, would anyone find the product useful? -Hugo

5 5

Re: [arch-general] [arch-dev-public] systemd 209 in [testing]
by Leonid Isaev 21 Feb '14

21 Feb '14

On Fri, 21 Feb 2014 10:24:39 +0100 Thomas Bächler <thomas(a)archlinux.org> wrote: > Am 20.02.2014 17:33, schrieb Dave Reisner: > > Hi all, > > > > I'm working on packaging the systemd 209 release, and I expect to have > > pkgrel=1 into [testing] in a few hours, barring any unforseen problems. > > It's a huge release (nearly 2000 commits since 208), and I don't > > anticipate that this will make it into [core]. > > This version works fine on my desktop, but fails on my laptop. The > initramfs works fine. While booting up the system, systemd hangs and > this appears in the journal: > > systemd[1]: Assertion '(x->type == SOURCE_MONOTONIC && y->type == > SOURCE_MONOTONIC) || (x->type == SOURCE_REALTIME && y->type == > SOURCE_REALTIME)' failed at src/libsystemd/sd-event/sd-event.c:264, > function latest_time_prioq_compare(). Aborting. > systemd[1]: Caught <ABRT>, dumped core as pid 317. > > As long this is turning into a thread about newly introduced issues in systemd... Udev 209 now tries to rename (I guess) all interfaces, including virtual: $ journalctl -u systemd-udevd.service PRIORITY=3 -o cat Could not apply link config to br0 Could not apply link config to vethQEP978 Could not apply link config to vethDR7OA5 Could not apply link config to vethW1QM0I Could not apply link config to vethC4240S Those are bridge and veth interfaces created by lxc userspace tools (2 containers/2 ifaces per container). Is this intended? Thanks, -- Leonid Isaev GPG key fingerprint: C0DF 20D0 C075 C3F1 E1BE 775A A7AE F6CB 164B 5A6D

1 0

[arch-general] Linux 3.13 status
by Thomas Bächler 20 Feb '14

20 Feb '14

Okay, it's been way too long. I don't really have the time to spend much time on the kernel right now, and neither does Tobias, so it's been sitting in [testing] for way too long. I am currently building 3.13.3-2 with a critical NFS fix and I intend to move that kernel to [core] very soon. Due to the keyboard changes, I'd like to make the following announcement: Linux 3.13 WARNING: PS/2 Keyboard support is now modular It has been requested that we make support for the i8042 keyboard and mouse controller modular. Some people get weird error messages because they don't have one and the manual probing slows down their boot. Tom took care of this on the kernel side (thank you) and the result finally landed in 3.13. In order to get keyboard input during early init, if you don't have it already, add the `keyboard` hook to the `HOOKS=` line in `/etc/mkinitcpio.conf`. It has been in the default configuration for some time. **WARNING**: There's a downside to all this: On some motherboards (mostly ancient ones, but also a few new ones), the i8042 controller cannot be automatically detected. It's rare, but some people will surely be without keyboard. You can detect this situation in advance: $ dmesg -t | grep ^i8042 i8042: PNP: No PS/2 controller found. Probing ports directly. If you have a PS/2 port and get this message, add `atkbd` to the `MODULES=` line in `mkinitcpio.conf` and run `mkinitcpio -P`. If you just noticed that you are without keyboard after rebooting, fear not! Simply add earlymodules=atkbd modules-load=atkbd to your kernel command line in your bootloader. I apologize for any inconvenience this transition may cause.

1 0

[arch-general] Linux container with systemd-nspawn
by arnaud gaboury 20 Feb '14

20 Feb '14

Hi all, I run systemd-git I manage a arch container using systemd-nspawn facilities. I am still strugling with the tty story on the container. The container is running and $ machinectl status dahlia output is correct. This output thus puzzles me: gabx@hortensia ➤➤ systemd/system % sudo loginctl -M dahlia SESSION UID USER SEAT 1 1000 gab seat0 c1 0 root seat0 c2 1000 gab seat0 c3 1000 gab seat0 c4 1000 gab seat0 c5 1000 gab seat0 c6 1000 gab seat0 c7 1000 gab seat0 c8 1000 gab seat0 Now reading machinectl man page, I shall be able to open a terminal session to the container. gabx@hortensia ➤➤ ~ # machinectl login dahlia Failed to start getty service: Unit container-getty(a)0.service failed to load: No such file or directory. On the host, I # cp /usr/lib/systemd/system/container-getty@.service to /etc/systemd/system/. I am not sure it is needed. >From the systemd mailing list : "systemd-getty-generator" will now look for $container_ttys set as an environment variable for PID 1. If that is set it will split the string up on whitespaces and start a getty on all ptys referenced. Note that this only supports ptys, not any other ttys. Example: "container_ttys=pts/5 pts/8 pts/15" and about systemd 209 : * If the $container_ttys environment variable is set, getty-generator will automatically spawn a getty for each listed tty. This is useful for container managers to request login gettys to be spawned on as many ttys as needed. Where shall I write such environment variable ? /etc/systemd/system.conf ? Is part of the job done inside the container (it is running systemd 208-11) ? Thank you for help

1 0