On Sun, 27 Dec 2009 20:39:19 -0600, "David C. Rankin"
wrote:
> Guys,
>
> After the recent discussion about arch working well on old hardware, I
> decided to dump a suse 10.3 install on an old AMD K6-2/450 and install
arch
> on it. I downloaded the net install iso i686. I knew if it was truly
i686
On Sun, 2009-12-27 at 20:39 -0600, David C. Rankin wrote:
> Guys,
>
> After the recent discussion about arch working well on old hardware, I
> decided to dump a suse 10.3 install on an old AMD K6-2/450 and install arch
> on it. I downloaded the net install iso i686. I knew if it was truly i686 i
Guys,
After the recent discussion about arch working well on old hardware, I decided
to dump a suse 10.3 install on an old AMD K6-2/450 and install arch on it. I
downloaded the net install iso i686. I knew if it was truly i686 it wouldn't
install -- and it didn't.
My question is which Arch dow
This looks like something that was there from a previous update and
isn't there in a recent install. Nvm!
On Sun, Dec 27, 2009 at 2:54 PM, Evangelos Foutras wrote:
> On 27/12/2009 09:43 μμ, Trav wrote:
>>
>> The past few updates i've noticed that $MYSQLD_ARGS specified in
>> /etc/conf.d/mysqld is
On 26/12/2009 09:53 μμ, Evangelos Foutras wrote:
On 26/12/2009 10:55 πμ, Tobias Powalowski wrote:
Hi guys,
small rebuild,
added Jan's intel i915 patch and changed radeon kms to be disabled by
default.
Upstream changes:
http://kernelnewbies.org/LinuxChanges
Arch Linux bugfixes/feature requests:
On 27/12/2009 09:43 μμ, Trav wrote:
The past few updates i've noticed that $MYSQLD_ARGS specified in
/etc/conf.d/mysqld isn't being used on /etc/rc.d/mysqld start.. is
this a bug or is it used somewhere else? I've searched the init script
and haven't seen any mention of the args at all.
I've alw
The past few updates i've noticed that $MYSQLD_ARGS specified in
/etc/conf.d/mysqld isn't being used on /etc/rc.d/mysqld start.. is
this a bug or is it used somewhere else? I've searched the init script
and haven't seen any mention of the args at all.
I've always just fixed it myself by adding $MY
In makechrootpkg, build dirs are chowned to nobody before we move files
to "$uniondir/build". This could lead to failure If the files are
supposed to be dynamically upgraded when we run makepkg.
A common use-case is when we upgrade $pkgver in git,svn PKGBUILDS.
Signed-off-by: Nezmer
---
makechr
On Sat, Dec 26, 2009 at 11:25 PM, Dwight Schauer wrote:
> Won't extra/glew work?
>
> $ pacman -Ss glew
> extra/glew 1.5.1-1
> A cross-platform C/C++ extension loading library
>
By the way, since Arch does not split binaries/headers/libraries,
there are several cases when you need libfoo, you h
9 matches
Mail list logo