- Arch-general - lists.archlinux.org

[arch-general] Protected symlinks in kernel 3.6
by mike cloaked 04 Oct '12

04 Oct '12

With kernel 3.6 in testing, and with the new protected symlinks feature being on by default, I wondered if anyone has seen any problems running this kernel as a direct result of this new feature? https://lkml.org/lkml/2012/10/3/473 It would be nice to know of any problems so that anyone running the new kernel will be aware of places to look to change permissions (or switch this feature off) ahead of installing the new package? -- mike c

2 1

[arch-general] kernel 3.6 feedback
by Genes MailLists 04 Oct '12

04 Oct '12

kernel 3.6-1 testing report: I am running 3.6 from testing on 3 machines. 1 laptop and 2 desktops. All are fully updated from testing repo. 1 of the desktop didn't come up right - seemed to have trouble with root filesystem (initiscripts still not systemd). On second reboot it came up fine. No logs obviously - will report if any further issues arise. Could be a coincidental hardware problem I suppose. Other desktop and laptop are both totally fine. laptop has intel on board graphics and sandy bridge i7 with intel 6300 wifi (lenovo w520). gene

5 8

[arch-general] Full mailing-list moderation
by Allan McRae 04 Oct '12

04 Oct '12

People just do not learn... All post to the mailing list are now moderated. As this takes time away from us actually maintaining the distribution, this will only occur intermittently. Allan

2 1

[arch-general] mkinitcpio: mdadm_udev Hook
by Simon Perry 03 Oct '12

03 Oct '12

Hi, I've just been re-installing a box, and saw that the wiki says regarding using the mdadm_udev hook: > "This is the preferred method of mdadm assembly (rather than using the > above mdadm hook). " I've tried to use the mdadm_udev hook, but the devices get named: > normal md0 (/boot) is md127 > normal md1 (encrypted, then lvm with swap and / on it ) is md126 I found this out with "cat /proc/partitions" once my box failed to boot and dropped to the initramfs shell. Seems pretty random, the first actual device isn't even the lowest number. There doesn't seem to be any documented way to have my raid1 devices named so I can use: > cryptdevice=/dev/md1:crypt in my kernel arg line. The only way to get things to work is to use the mdadm hook and have my devices specified in /etc/mdadm.conf Can I rely on md127 and md126 being the same across every boot, and therefore resign myself to using this numbering (instead of the much nicer md0 and md1), and use it in my cryptdevice kernel arg and be done with it? Given this thread: https://bbs.archlinux.org/viewtopic.php?id=149358 And the comment: "I have little interest in supporting the mdadm hook. Assembly via udev is the preferred method here." What is the right way to do this? Cheers. -- Simon Perry (aka Pezz)

3 5

[arch-general] pacman update dependency problem today for kdegames
by mike cloaked 03 Oct '12

03 Oct '12

Today I tried to update with pacman -Syu I got this: :: Starting full system upgrade... resolving dependencies... warning: cannot resolve "kdegames-knavalbattle", a dependency of "kde-meta-kdegames" warning: cannot resolve "kdegames-ksnakeduel", a dependency of "kde-meta-kdegames" :: The following package cannot be upgraded due to unresolvable dependencies: kde-meta-kdegames Do you want to skip the above package for this upgrade? [y/N] I tried to find the two packages: [root@lapmike3 ~]# pacman -Ss kdegames-ksnakeduel [root@lapmike3 ~]# pacman -Ss kdegames-knavalbattle [root@lapmike3 ~]# Seems these don't exist!! I also don't have either package installed from any previous update or pacman install! What is the advice here? Wait for the update system to get fixed or carry on regardless and go ahead and update? Thanks -- mike c

1 1

[arch-general] GHC 7.6.1 now in [testing]
by Thomas Dziedzic 03 Oct '12

03 Oct '12

Hey everyone! It's that time again for arch to get the latest ghc! GHC 7.6.1 comes with a bunch of new and exciting features: http://www.haskell.org/ghc/docs/7.6.1/html/users_guide/release-7-6-1.html This morning, all the haskell packages should have been rebuilt against the latest ghc and I have moved all haskell pkgs to testing. One caveat is that cabal-install wasn't rebuilt but it should still work while upstream works on patching it for ghc 7.6.1 It took just under a month to do the full rebuild because of the amount of patching and coordination with upstream we had to do. I will let it sit in testing for a week so that aur maintainers for haskell pkgs have time to investigate and patch their packages. I would like to thank everyone who worked on this rebuild! Cheers!

1 0

[arch-general] systemd, running scripts after suspend/hibernate
by Mauro Santos 03 Oct '12

03 Oct '12

I have made the jump to systemd and I have been ironing a few things here and there, one of them is setting the HD advanced power management to a sane level to avoid excessive wear due to constant head parking. I've been able to achieve this by placing my script in /usr/lib/systemd/system-sleep, however 'man systemd-sleep' says: "Note that scripts or binaries dropped in /usr/lib/systemd/system-sleep/ are intended for local use only and should be considered hacks." This seems to imply that a service file should be used, what I can't figure out from the documentation or google searches is how to implement the functionality I want with a .service file, or if a service file is actually needed/recommended. Any pointers or help are welcome. -- Mauro Santos

6 8

[arch-general] OT: Re: testing/systemd 191-1 failed to boot
by Felipe Contreras 03 Oct '12

03 Oct '12

On Wed, Oct 3, 2012 at 2:14 AM, nailz <nailzuk(a)gmail.com> wrote: > I too am fed up with all the dross and i only been here a few weeks, i > mean nobody is forcing anyone to use arch, if people dont agree with the > way its heading either jump ship to another distro , or god forbid maybe > even add something constructive to arch. Totally agree, because disagreements never lead to anything good... oh wait! it's the other way around: without dissent, there's no progress[1]. Actually, nailz's reply also had no technical aspect, and was not asking for help, so he should be banned as well, right? Unless the ban only applies to the people that disagree with the status quo, not the people that complain about the people that disagree with the status quo. In which case you would have to accept that the bans have nothing to do with the nature of the comments, but rather because a mod simply didn't like the comment. To me, and the merrian-webster dictionary, general means: general: involving, applicable to, or affecting the whole So, unpopular topics seem to fall under arch-general, because they still might affect the whole, even though some people (majority?) might not want it to. They can disagree with the unpopular opinion, but should not silence it. There is no arch-technical, or arch-help, or arch-off-topic. As for you, nailz, if you are feed up with this thread, don't read it, nobody is forcing you. You can even tell your client to ignore or mute the thread so your precious ears don't have to go through all this filthy dissent[2]. Note: I'm prefixing my mail with OT (off-topic), it might be a good practice for people with sensitive ears to filter these mails, but I'm sure I'll get banned for just proposing it. Lapidation sketch much? Cheers. [1] http://felipec.wordpress.com/2012/09/26/dissent/ [2] http://lmgtfy.com/?q=mute+thread -- Felipe Contreras

1 0

Re: [arch-general] testing/systemd 191-1 failed to boot (OT)
by Nicholas MIller 03 Oct '12

03 Oct '12

On Oct 2, 2012 7:15 PM, "nailz" <nailzuk(a)gmail.com> wrote: > > On 3 October 2012 00:18, Your Real Name <anoknusa(a)gmail.com> wrote: > > > On Mon, Oct 01, 2012 at 08:29:38PM +1000, Allan McRae wrote: > > > On 01/10/12 20:23, Jorge Almeida wrote: > > > > On Mon, Oct 1, 2012 at 6:49 AM, gt <static.vortex(a)gmx.com> wrote: > > > >> On Mon, Oct 01, 2012 at 11:49:05AM +1000, Allan McRae wrote: > > > >>> On 01/10/12 11:21, Armando M. Baratti wrote: > > > >>>> Authoritarian and despotic. > > > >>>> > > > >>>> My ban, please. > > > >>>> > > > >>> > > > >>> Done... and for two weeks because I had to look up what despotic > > meant. > > > >> > > > >> lol, always keep a dictionary handy. May I suggest sdcv. > > > > > > > > This poster should also be banned, since this post doesn't call for > > help > > > > nor offers it. > > > > > > > > Oops... Mine too... Now I've done it! > > > > > > > > ("The life of Brian", anyone? The lapidation sketch? Oops again: I hope > > > > Allan McRae is familiar with the word "lapidation", or it's two weeks > > > > for me too.) > > > > > > > > > > Lapidation fails when I can just punish everyone... I am more than > > > happy to just close the list again. > > > > > > I have not because I am not "prone to panic attacks". (Hi Pete! - here > > > is your answer who those emails go to) > > > > > > Allan > > > > > > > I'm down for seeing the list get closed again, or at least a banning > > free-for-all. > > The forum mods wouldn't tolerate this kind of childish bullshit; I don't > > see why > > the devs/ML mods need to. There are plenty of places online to complain, > > the support > > list doesn't need this. > > > > > [quote]the support > list doesn't need this.[/quote] > I too am fed up with all the dross and i only been here a few weeks, i > mean nobody is forcing anyone to use arch, if people dont agree with the > way its heading either jump ship to another distro , or god forbid maybe > even add something constructive to arch. > > > > -- > > > www.cirrusminor.info <http://cirrusminor.info> > <http://www.cirrusminor.info/> > <http://www.cirrusminor.info/> > > <http://www.cirrusminor.info/> Will a ban just cause you to be unable to post or will out also cause you to not receive list items during the ban

1 0

[arch-general] testing/systemd 191-1 failed to boot
by Zhengyu Xu 03 Oct '12

03 Oct '12

Dear all, After updating systemd to 191-1 in testing repo, I had following messages during booting and the process was stuck (crashed). [ 10.539416] systemd[1]: segfault at 7d ip b75a97b7 sp bfb0ece8 error 4 in libc-2.16.so[b752a000+1a4000] [ 10.539700] systemd[1]: Caught <SEGV>, core dump failed. Downgrade to 189-4 can solve this problem. I want to know if this is a personal problem or a general bug affecting others as well. Best regards, Z.

32 79