kde-3.2 has gone stable now... :D
--
[EMAIL PROTECTED] mailing list
Hi!
Michael Andreen <[EMAIL PROTECTED]> writes:
> I don't fully agree here, on of the things I do like about gentoo is the fact
> that you can run a mostly "stable" system while adding some bleeding edge on
> the top, It does of course require some more work then running plain x86 or
> ~x86, s
kde3.2 is marked stable now, i am emerging it now
Jason Lee wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 10 February 2004 06:04 pm, Michael W. Holdeman wrote:
OK I have never used the ACCEPT_KEYWORDS="~x86" before but I wanted
kde3.2 so I did it with emerge -u kde. All worke
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 10 February 2004 06:04 pm, Michael W. Holdeman wrote:
> OK I have never used the ACCEPT_KEYWORDS="~x86" before but I wanted
> kde3.2 so I did it with emerge -u kde. All worked well, and in fact I
> do love kde3.2. My problem is that now when
On February 10, 2004 07:05 pm, Ciaran McCreesh wrote:
> <[EMAIL PROTECTED]> wrote:
> | you can manually mask/unmask the various packages, but do yourself a
> | favour: DON'T run a partial ~x86/x86 system. it's just a world of
> | hurt. seriously, i'm running a full ~x86 system with very few
> |
On Tue, 10 Feb 2004 18:16:33 -0500 gabriel
<[EMAIL PROTECTED]> wrote:
| you can manually mask/unmask the various packages, but do yourself a
| favour: DON'T run a partial ~x86/x86 system. it's just a world of
| hurt. seriously, i'm running a full ~x86 system with very few
| problems, and what pr
On Wednesday 11 February 2004 00.16, gabriel wrote:
> On February 10, 2004 06:04 pm, Michael W. Holdeman wrote:
> > OK I have never used the ACCEPT_KEYWORDS="~x86" before but I wanted
> > kde3.2 so I did it with emerge -u kde. All worked well, and in fact I do
> > love kde3.2. My problem is that no
Michael writes:
> OK I have never used the ACCEPT_KEYWORDS="~x86" before but I wanted
> kde3.2 so I did it with emerge -u kde. All worked well, and in fact I do
> love kde3.2. My problem is that now when I run emerge -u world alot of
> what was upgraded for kde3.2 now wants to be downgraded? What
On February 10, 2004 06:04 pm, Michael W. Holdeman wrote:
> OK I have never used the ACCEPT_KEYWORDS="~x86" before but I wanted kde3.2
> so I did it with emerge -u kde. All worked well, and in fact I do love
> kde3.2. My problem is that now when I run emerge -u world alot of what was
> upgraded for
OK I have never used the ACCEPT_KEYWORDS="~x86" before but I wanted kde3.2 so
I did it with emerge -u kde. All worked well, and in fact I do love kde3.2.
My problem is that now when I run emerge -u world alot of what was upgraded
for kde3.2 now wants to be downgraded? What do I do for this?
I do
i had this problem about a week ago. emerging gcc for the first time
after switching to ~x86 resulted in something happening where many of
the g++ libs that are usually (iirc - im not at my computer right now)
put in /usr/lib/ were not there. basically i was getting the exact same
error messa
It broke on a "emerge world". I haven't deleted anything for some time.
I found the shlib, so I put it on my LD_LIBRARY_PATH. Much better!
I'll go back to the relative safety of X86.
--Kurt
Arne Vogel wrote:
Kurt Guenther wrote:
tumbleweed root # emerge
/usr/bin/python: error while loadin
Kurt Guenther wrote:
tumbleweed root # emerge
/usr/bin/python: error while loading shared libraries: libstdc++.so.5:
cannot open shared object file: No such file or directory
tumbleweed root #
I just emerged gcc-3.3.2-r6 and got the same error.
Is there a way to fix emerge?
run ldconfig
bye, chr
Kurt Guenther wrote:
tumbleweed root # emerge
/usr/bin/python: error while loading shared libraries: libstdc++.so.5:
cannot open shared object file: No such file or directory
tumbleweed root #
Try to 'locate libstdc++.so.5' and see if it's still there (the locate
DB could be outdated, so verify
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 04 February 2004 22:06, Kurt Guenther wrote:
> tumbleweed root # emerge
> /usr/bin/python: error while loading shared libraries: libstdc++.so.5:
> cannot open shared object file: No such file or directory
> tumbleweed root #
>
>
> Is there
begin quote
On Wed, 04 Feb 2004 17:06:01 -0500
Kurt Guenther <[EMAIL PROTECTED]> wrote:
> tumbleweed root # emerge
> /usr/bin/python: error while loading shared libraries: libstdc++.so.5:
>
> cannot open shared object file: No such file or directory
> tumbleweed root #
>
>
> Is there a way to
tumbleweed root # emerge
/usr/bin/python: error while loading shared libraries: libstdc++.so.5:
cannot open shared object file: No such file or directory
tumbleweed root #
Is there a way to fix emerge?
--Kurt
--
[EMAIL PROTECTED] mailing list
On Tuesday 03 February 2004 04:45 pm, Andrew Gaffney wrote:
> Rick [Kitty5] wrote:
> > Anyone running with ~x86 set system wide?
> >
> > Good, bad, simply broken?
>
> I've been running that way for nearly a year and hardly a problem.
> Although, its not for the faint of heart. If something breaks,
Rick [Kitty5] wrote:
Anyone running with ~x86 set system wide?
Good, bad, simply broken?
I've been running that way for nearly a year and hardly a problem. Although, its not for
the faint of heart. If something breaks, you really should know how to fix it.
--
Andrew Gaffney
Network Administrator
gabriel wrote:
On February 3, 2004 02:49 pm, Thomas T. Veldhouse wrote:
Generally pretty good. I wouldn't muck with it though unless you are
willing to get dirt on your hands and dig in when things do break (which
is fairly rare really). I think it is far more problematic to mix ~x86
and x86
On Tue, 03 Feb 2004 19:34:49 +
"Rick [Kitty5]" <[EMAIL PROTECTED]> wrote:
> Anyone running with ~x86 set system wide?
I'm running on ~x86 on my desktop for some 6 months without any major problem.
Of course, new ebuilds tend to get broken sometimes, but that's pretty rare and
you have to expe
On February 3, 2004 02:49 pm, Thomas T. Veldhouse wrote:
> Generally pretty good. I wouldn't muck with it though unless you are
> willing to get dirt on your hands and dig in when things do break (which
> is fairly rare really). I think it is far more problematic to mix ~x86
> and x86 then it is
Rick [Kitty5] wrote:
Anyone running with ~x86 set system wide?
Good, bad, simply broken?
Generally pretty good. I wouldn't muck with it though unless you are
willing to get dirt on your hands and dig in when things do break (which
is fairly rare really). I think it is far more problematic t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 03 February 2004 19:34, Rick [Kitty5] wrote:
> Anyone running with ~x86 set system wide?
>
> Good, bad, simply broken?
2 boxes, neither less than 2-3 days out of date, running fine.
(1 is a dell p4 with nvidia card, 5336 drivers, but no gra
Anyone running with ~x86 set system wide?
Good, bad, simply broken?
--
Rick
Kitty5 NewMedia http://Kitty5.com
POV-Ray News & Resources http://Povray.co.uk
TEL : +44 (01270) 501101 - ICQ : 15776037
PGP Public Key : http://pgp.kitty5.com
--
[EMAIL PROTECTED] mailing list
I compiled /dev/pts support and STILL kernel hangs mounting /proc ..
Does anyone have a suggestion???
On 12/24/03 5:38 PM, "George Hernandez" <[EMAIL PROTECTED]> wrote:
> On 12/24/03 3:01 AM, "Peter Ruskin" <[EMAIL PROTECTED]> wrote:
>
> Thanks peter... I think I had forgotten pts support.. So
On 12/24/03 3:01 AM, "Peter Ruskin" <[EMAIL PROTECTED]> wrote:
Thanks peter... I think I had forgotten pts support.. So I recompiled the
kernel right now.. Hopefully it will work.. So far I did have /proc as you
showed me and /dev/shm
Lets see what happes
> On Wednesday 24 Dec 2003 04:07, Georg
On 12/23/03 8:07 PM, "George Hernandez" <[EMAIL PROTECTED]> wrote:
My
Hello all.. Hopefully you guys can help me.
for some reason my box stalls at /proc..
I am running 2.4.23 kernel..
Here is my grub.conf file...
[grub.conf]
>
>
> default 0
> timeout 30
> splashimage=(hd0,0)/grub/splash.xpm
On Wednesday 24 Dec 2003 04:07, George Hernandez wrote:
> Hello all.. Hopefully you guys can help me.
> Here is my grub.conf file...
> [grub.conf]
>
>
> default 0
> timeout 30
> splashimage=(hd0,0)/grub/splash.xpm.gz
>
> title=Gentoo Linux
> root (hd0,0)
> kernel (hd0,0)/kernel-2.4.23 root=/dev/sda
Hello all.. Hopefully you guys can help me.
Here is my grub.conf file...
[grub.conf]
default 0
timeout 30
splashimage=(hd0,0)/grub/splash.xpm.gz
title=Gentoo Linux
root (hd0,0)
kernel (hd0,0)/kernel-2.4.23 root=/dev/sda3
[end]
Here is my fstab..
[fstab]
/dev/sda1 /boot
espite the flakiness, I've almost got gentoo installed. I just gotta get
grub to work and I'm set.
Thanks for the help,
Nathan Van Eps
>-Original Message-
>From: Roger Miliker [mailto:[EMAIL PROTECTED]
>Sent: Saturday, October 18, 2003 12:58 PM
>To: [EMAIL PROTECTED]
031018 Andrew Gaffney wrote:
> [EMAIL PROTECTED] wrote:
>> i cdn't boot the Gentoo CD 1 : kernel 2.4.21 doesn't like my hardware,
>> ie Athlon XP 2500+ & Soyo mobo (the same thing happened with Mdk 9.1 ).
>> i got install'n to start using Knoppix, tho' that caused another problem
>> when i removed
[EMAIL PROTECTED] wrote:
031018 Van Eps, Nathan D. (James Tower) wrote:
I can't get my LiveCD to boot.
I always get the error: "isolinux: Disk error 44, AX=4280, drive 9F".
Has anyone got that error before? Does anyone know what it means?
I've tried the "gentoo" and the "smp" kernel
and a bunch of
031018 Van Eps, Nathan D. (James Tower) wrote:
> I can't get my LiveCD to boot.
> I always get the error: "isolinux: Disk error 44, AX=4280, drive 9F".
> Has anyone got that error before? Does anyone know what it means?
> I've tried the "gentoo" and the "smp" kernel
> and a bunch of different permu
On Saturday 18 October 2003 19:36, Van Eps, Nathan D. (James Tower) wrote:
> Hello,
>
> I can't get my LiveCD to boot. I always get the error: "isolinux: Disk
> error 44, AX=4280, drive 9F". Has anyone got that error before? Does anyone
> know what it means?
>
> I've tried the "gentoo" and the "smp
Hello,
I can't get my LiveCD to boot. I always get the error: "isolinux: Disk error
44, AX=4280, drive 9F". Has anyone got that error before? Does anyone know
what it means?
I've tried the "gentoo" and the "smp" kernel and a bunch of different
permutations of the installation options. I have the
Yep. Thanks.
Chris
On Sun, 2003-06-22 at 14:42, Shawn wrote:
Turn off RenderAccell.
You're running nvidia drivers aren't you... ;]
On Thu, 2003-06-19 at 21:23, Chris van der Pennen wrote:
> Is anyone else getting weird icon corruption with the latest testing
> gtk2?
>
> Or is it just me
Turn off RenderAccell.
You're running nvidia drivers aren't you... ;]
On Thu, 2003-06-19 at 21:23, Chris van der Pennen wrote:
> Is anyone else getting weird icon corruption with the latest testing
> gtk2?
>
> Or is it just me being halfway through emerge -e world? ;)
>
> Chris
--
[EMAIL PROT
Is anyone else getting weird icon corruption with the latest testing gtk2?
Or is it just me being halfway through emerge -e world? ;)
Chris
signature.asc
Description: This is a digitally signed message part
39 matches
Mail list logo
