You are not logged in.
tomk - no, it was procps - then it was udev too ![]()
Offline
I'll take your word for it, dibble. I sailed through the procps business with just those few error messages. udev clobbered me, on the other hand.
Offline
Would be nice if such problems could be posted at the archlinux.org-page and on the mailinglist.
I had two installations which could not connect to the internet and it costs me a lot of time to figure out.
Offline
Would be nice if such problems could be posted at the archlinux.org-page and on the mailinglist.
I had two installations which could not connect to the internet and it costs me a lot of time to figure out.
Heh, if you couldn't connect to the internet, how you going to see the posts on the main page / mailing list?
Kidding!
Seriously though, I guess it wouldn't be difficult for some of us to throw out mailing list threads for problems like the procps thing (which, I say again, caused me no problems, it was just some error messages... like the hotplug shpchp thing)
Offline
ok, procps is just annoyant on the bootscreen, but udev 60-1/3 are really perilous - may be it would a nice idea putting at least new packages which are part of the base system into testing ...
Offline
i agree with you tranxene on this udev matter, it should've been going to testing first,
but things have been getting better around here lately, a while back not even kernels or x went to testing and then it was not always so pleasant upgrades,
arch + gentoo + initng + python = enlisy
Offline