Arch Linux

ccchris

Member

Registered: 2006-09-25

Posts: 16

pacman -Syu, always new kernel, time consuming

Hi, being new to Arch linux and loving the idea of pacman and being able to upgrade my system in a few seconds I have only one irritation.

It seems that a new kernel is available every time I pacman -Syu (once a week) and everytime I have to compile a new truecrypt/nvidia/vmware module thus making the upgrading process more time consuming (read PITA).

Am I supposed to put the kernel on the "blacklist" in pacman.conf and only uppgrade it when I really need it?

In other threads I read that people upgrade everyday and they didn't seem to be bothered.

Or am I just lazy?

tomk

Forum Fellow

From: Ireland

Registered: 2004-07-21

Posts: 9,839

Re: pacman -Syu, always new kernel, time consuming

You can IgnorePkg it if you want, but if rebuilding external modules is your problem, remember you don't have to rebuild truecrypt and nvidia for every .y kernel update. Both of these are official Arch packages and we rebuild them for .x changes only e.g. 2.6.17 -> 2.6.18. The same may apply to your vmware modules - don't rebuild without trying your existing versions first.

iphitus

Forum Fellow

From: Melbourne, Australia

Registered: 2004-10-09

Posts: 4,927

Re: pacman -Syu, always new kernel, time consuming

It seems that a new kernel is available every time I pacman -Syu (once a week) and everytime I have to compile a new truecrypt/nvidia/vmware module thus making the upgrading process more time consuming (read PITA).

truecrypt and nvidia are now in the repos, so that's two you no longer have to rebuild yourself. vmware is pretty simple, just run the script. you could put it in /etc/rc.local if you want and have it run on boot and that would save the trouble with that as well.

pacman -S nvidia truecrypt

both in [extra]

James

ccchris

Member

Registered: 2006-09-25

Posts: 16

Re: pacman -Syu, always new kernel, time consuming

Ah, I just saw that truecrypt now is in extra, I guess I can put up with running the vmware-config script every now and then.

don't rebuild without trying your existing versions first.

Never thought about that, always been recompiling the modules whenever there's a new kernel version.

Thanks :-)

tomk

Forum Fellow

From: Ireland

Registered: 2004-07-21

Posts: 9,839

Re: pacman -Syu, always new kernel, time consuming

I guess I can put up with running the vmware-config script every now and then.

I just rebuild the modules. I have a PKGBUILD for it - it's here if you're interested. Change pkgver, _realver, and _kernver as required.

sweiss

Member

Registered: 2004-02-16

Posts: 635

Re: pacman -Syu, always new kernel, time consuming

I put the kernel on my IgnorePkg even though I usually update it whenever an update is available. I think that's the right way to do it, as you need to be aware of a new kernel version. I wouldn't want to miss a kernel upgrade when there are a lot of packages available.

---

Some PKGBUILDs: http://members.lycos.co.uk/sweiss3

stonecrest

Member

From: Boulder

Registered: 2005-01-22

Posts: 1,190

Re: pacman -Syu, always new kernel, time consuming

pacman -Syu --ignore kernel26

---

I am a gated community.

cdhotfire

Member

From: Ocala, Florida

Registered: 2006-02-13

Posts: 151

Re: pacman -Syu, always new kernel, time consuming

pacman -Syu --ignore kernel26

genius!

---

[img]http://www.barbarawood.com/guestbook/images/smilies/koolaid.gif[/img]
"Ooooh Yaaaa!"