November 2013 - Arch-general - lists.archlinux.org

[arch-general] Initramfs fallback render
by Ismael Bouya 17 Nov '13

17 Nov '13

Hi all, I have always learnt that it was good practice (to use sudo instead of root su and), when we use sudo, to completely disable root login (by disabling his password). However when we need to boot into "fallback mode", initramfs asks for root password! Is there a standard/automated way to ask/permit another user via initramfs in Archlinux? If not, how do you deal with that usually? Thanks in advance for your response! Regards, -- Ismael

7 13

Re: [arch-general] [arch-dev-public] Dropping bluez4
by Andreas Radke 13 Nov '13

13 Nov '13

Am Sat, 12 Oct 2013 16:28:56 +0200 schrieb Tom Gundersen <teg(a)jklm.no>: > Hi guys, > > Once pulseaudio and bluedevil moves out of [testing], the only > official package depending on bluez4 will be blueman. > > As blueman was last released two years ago, and last upstream activity > was more than one year ago and that bluez4 is no longer developed > upstream at all, I suggest dropping both of them from the > repositories. > > Any objections? > > Cheers, > > Tom > I've done some work and research on bluez lately. I can confirm my adapters to work with bluez 5.10 and gnome-bluetooth (connecting to headset + smartphone) that has already moved to extra. I couldn't make it work with kde+bluedevil that is in testing. Also it seems not possible to use plain bluetoothctl to pair (works sometimes)/connect(never working here) your device and use plain alsa/obex. This is an annoying situation for any other desktop apart from Gnome. Blueman is broken and for many users not even starting. No idea about our networkmanager bluetooth support. Fedora 20 has switched over to only use bluez v5, OpenSuSE is also using it. We should search further how to solve kde and plain console situation. Is Bluez4 still required to use with obexd? If not we can drop it and focus on improving bluez5 support. Best would be to get bluez connecting to devices from console or/and to have a desktop independent frontend like this approach: http://mail.xfce.org/pipermail/xfce4-dev/2013-July/030408.html -Andy

5 4

[arch-general] Sourcing /etc/rc.conf in configs and .install scripts
by Karol Blazewicz 12 Nov '13

12 Nov '13

I noticed a few configs and .install scripts mention /etc/rc.conf (mostly it's just '. /etc/rc.conf'), even though initscripts are not supported anymore. For example locale.sh from filesystem package has elif [ -r /etc/rc.conf ]; then LANG=$(. /etc/rc.conf 2>/dev/null; echo "$LOCALE") fi Should I open a bug report for this?

4 6

[arch-general] Should outdated changelogs be removed from the packages?
by Karol Blazewicz 12 Nov '13

12 Nov '13

Should outdated changelogs be removed from the packages? I'm guessing that this was the reason for removing the changelog from parcelite: https://bugs.archlinux.org/task/37105 https://projects.archlinux.org/svntogit/community.git/commit/trunk?h=packag… htop's changelog has been removed earlier: https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=package… even though it wasn't outdated, probably because the maintainer didn't want to maintain it anymore.

2 1

[arch-general] selinux groups not working
by piruthiviraj natarajan 09 Nov '13

09 Nov '13

I am trying to install selinux on my system from Timothee's repos. But I am only able to install package group "selinux" but the *selinux-system-utilities, **selinux-userspace, **selinux-policies* and *selinux-extras* package groups doesn't seem to be working. [root@arch ~]# pacman -S selinux-system-utilities selinux-userspace selinux-policies selinux-extras error: target not found: selinux-system-utilities error: target not found: selinux-userspace error: target not found: selinux-policies error: target not found: selinux-extras [root@arch ~]# I know I can install from AUR but I was of the expectation that this should work from the http://repo.siosm.fr/$repo/ repos.

3 5

[arch-general] linux-firmware upgrade altered grub
by Anthony Campbell 08 Nov '13

08 Nov '13

My laptop has dual boot with Arch and Debian. I normally have it set so that it defaults to booting Arch. After an upgrade yesterday which I'm pretty sure included linux-firmware I found that boot reversed the order and there were some other unwanted effects too. I reinstalled grub and grub.cfg and things went back to normal. Is this something to expect after such an upgrade? Is it documented somewhere? -- Anthony Campbell - ac(a)acampbell.org.uk http://www.acupuncturecourse.org.uk http://www.smashwords.com/profile.view/acampbell https://itunes.apple.com/ca/artist/anthony-campbell/id73235412

3 5

[arch-general] can't locally sign Siosm key selinux
by piruthiviraj natarajan 06 Nov '13

06 Nov '13

Hi *Timothée Ravier*, I tried locally signing your key. But this is what I get pacman-key --lsign-key C8D83B6AE4B8685A7290545FDB27818F78688F83 -> Locally signing key C8D83B6AE4B8685A7290545FDB27818F78688F83... ==> ERROR: C8D83B6AE4B8685A7290545FDB27818F78688F83 could not be locally signed. But adding the key was sucessful. pacman-key --add /home/archie/Downloads/siosm_gpg.pub ==> Updating trust database... gpg: next trustdb check due at 2014-01-22 I am not sure how to do this. I read your links but coudn't get around it.

2 1

Re: [arch-general] systemd --test
by Wayne S 05 Nov '13

05 Nov '13

At 11/4/2013 10:43 AM, you wrote: >On Mon, Nov 4, 2013 at 4:07 PM, Wayne S <linux(a)zuik.net> wrote: >> my apologies for improperly sending email to list. >> >> My question is how to properly use systemd --test: >> >> From the website: http://www.freedesktop.org/wiki/Software/systemd/TipsAndTricks/ >> >> It suggests to run this to see what would execute on boot for a unit: >> >> # systemd --test --system --unit=multi-user.target >> >> If I run this as root, I get command not found. So it is not in $PATH. >> >> If I run as root I get don't run as root: >> >> # /usr/lib/systemd/systemd --test --system --unit=multi-user.target >> Don't run test mode as root. >> >> If I run as user, I get a bunch of errors: >> >> $ /usr/lib/systemd/systemd --test --system --unit=multi-user.target >> systemd 208 running in system mode. (+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ) >> Failed to set hostname to <arch-t3400>: Operation not permitted >> Failed to open /dev/tty0: Permission denied >> Failed to create root cgroup hierarchy: Permission denied >> Failed to allocate manager object: Permission denied >> >> Is there a way to use this command properly? >> >> Wayne > >I'm not a systemd guru, but try 'systemctl list-dependencies multi-user.target'. Thanks, I did run that command but did not see, for instance, shorewall, in the list. Also '$man systemd' says --test can be used to "determine startup sequence, dump it and exit." for debugging purposes. Perhaps this can only be used during an actual system boot on the boot loader command line? Wayne

1 0

Re: [arch-general] systemd --test
by Karol Blazewicz 04 Nov '13

04 Nov '13

On Mon, Nov 4, 2013 at 4:07 PM, Wayne S <linux(a)zuik.net> wrote: > my apologies for improperly sending email to list. > > My question is how to properly use systemd --test: > > From the website: http://www.freedesktop.org/wiki/Software/systemd/TipsAndTricks/ > > It suggests to run this to see what would execute on boot for a unit: > > # systemd --test --system --unit=multi-user.target > > If I run this as root, I get command not found. So it is not in $PATH. > > If I run as root I get don't run as root: > > # /usr/lib/systemd/systemd --test --system --unit=multi-user.target > Don't run test mode as root. > > If I run as user, I get a bunch of errors: > > $ /usr/lib/systemd/systemd --test --system --unit=multi-user.target > systemd 208 running in system mode. (+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ) > Failed to set hostname to <arch-t3400>: Operation not permitted > Failed to open /dev/tty0: Permission denied > Failed to create root cgroup hierarchy: Permission denied > Failed to allocate manager object: Permission denied > > Is there a way to use this command properly? > > Wayne I'm not a systemd guru, but try 'systemctl list-dependencies multi-user.target'.

3 2

[arch-general] systemd --test
by Wayne S 04 Nov '13

04 Nov '13

my apologies for improperly sending email to list. My question is how to properly use systemd --test: >From the website: http://www.freedesktop.org/wiki/Software/systemd/TipsAndTricks/ It suggests to run this to see what would execute on boot for a unit: # systemd --test --system --unit=multi-user.target If I run this as root, I get command not found. So it is not in $PATH. If I run as root I get don't run as root: # /usr/lib/systemd/systemd --test --system --unit=multi-user.target Don't run test mode as root. If I run as user, I get a bunch of errors: $ /usr/lib/systemd/systemd --test --system --unit=multi-user.target systemd 208 running in system mode. (+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ) Failed to set hostname to <arch-t3400>: Operation not permitted Failed to open /dev/tty0: Permission denied Failed to create root cgroup hierarchy: Permission denied Failed to allocate manager object: Permission denied Is there a way to use this command properly? Wayne

1 0