Re: [Vectorlinux-devel] 64-bit Linux and Kernel 2.6.16

[uel a. <ue...@gm...>]

I havent  been able to get 2.6.16 downloaded yet I am stuck with subpar
internet for few days while they rewire my house.
most of the day  have no internet at all.
I tried slamd64 a little while baack and it seemed pretty stable.
have you thought about trying that one?

On 3/23/06, Tony Brijeski <tb...@gm...> wrote:
>
> After another day with Kanotix 64 and some more testing, I found quite a
> few things to be unstable and crashing.  Multimedia is crap - the media
> players crash.  IVTV drivers do not work - compile but do not work.  Lots=
 of
> KDE bugs that cause many things to segfault.
>
> The speed was great but the instability sucks.  Might give gentoo 64 a
> shot next - lol.
>
> Has anyone tried the 2.6.16 kernel yet?
>
>
>
> On 3/22/06, Tony Brijeski <tb...@gm...> wrote:
> >
> >
> >
> > On 3/22/06, Sriram Durbha < sri...@gm...> wrote:
> > >
> > >
> > >
> > > On 3/22/06, Tony Brijeski < tb...@gm...> wrote:
> > > >
> > > >
> > > > Kanotix and Kanotix 64 are live cd's that you can install - they
> > > > were originally based on Knoppix.  I still think the LiveCD with in=
stall
> > > > option is the way to go in the future.
> > > >
> > > >
> > > >
> > > I am so glad you also think like this. unfortunately when i had put
> > > this idea forth it was in a different thread and did not get enough
> > > momentum. however, thanks to uel's work, now every one is realizing t=
he
> > > benefits of liveCD with install option.  also some how our liveCD exp=
erience
> > > is really not comparable to many others, though our core OS is mileas=
 ahead
> > > of other offerings.
> > > But since this is our first liveCD , we can come across several areas
> > > of improvement.
> > >
> >
> >
> > I've always been a fan of Live CD's.  Thats why I created the first few
> > live cd's for VL.  They were as much a selfish venture as they were to =
allow
> > people to have a portable VL.  Uel took it one step further by working =
on
> > the install portion and that is exactly what was needed.  I would imagi=
ne
> > with the next generation of the kernel - 2.8.x, most of the current VL
> > userbase will not be able to run it anyway.  Lots are having issues wit=
h the
> > 2.6 kernel as it is.  2.8.x will no doubt be optimized and built around
> > the 64-bit platform even though the kernel is a multiarch thing.
> >
> > as for my thoughts on 64bit.  for a long time to come,  most people wil=
l
> > > still buy 32 bit systems for home/soho use.  but most new systems mig=
ht be
> > > multi-core. say after 3 years from now, i would suspect most new mach=
ines
> > > will still be 32 bit but multi core.  For most desktop applications[
> > > photoshop, media encodeers not included ] 32 bit cpus are more than e=
nough.
> > > and the address space too. infact apple did some research and found t=
hat
> > > graphics performance actually slowed down if they made a complete swi=
tch to
> > > 64 bit arch.!!
> > >
> >
> > Everywhere up here in Canada is selling 64-bit systems as standard righ=
t
> > now.
> >
> > Intel is the only ones that are staying with 32-bit for now and since
> > apple is using them, it makes marketing sense for them to say 64-bit is=
n't
> > as good.  As far as gaming performance, it has everything to do with th=
e
> > drivers and nvidia is still having some issues with their drivers but t=
hey
> > are improving.  They do have the EM64T which are basically just P4's th=
at
> > are cloning AMD64 instruction set.
> >
> > 64-bit AMD's have been here for 3 years already and with Vista just
> > around the corner, 64-bit will be the standard by years end.
> >
> > No doubt 32-bit will be around for a while but it will not be the
> > standard.
> >
> >
> > so we can happily tag along with slack for some time to come.  but
> > > ofcourse if we do want to make a 64 bit os it would be cool :) ;
> > > cheers
> > > ram
> > >
> >
> > I have a feeling Slackware will die unless it goes to 64-bit.  Most of
> > the userbase that has the savvy to run a stock slackware setup will mos=
t
> > likely also be the folks that build their own systems and will be going=
 to
> > 64-bit soon if not already like myself.  All the reading I have done on
> > 64-bit distros mainly pointed to SuSE as the best choice.  While it may=
 be
> > easier than running debian, it was nowhere near as responsive.  Having =
a
> > 64-bit CPU and seeing what it can do has spoiled me.  I still run SOHO =
on 2
> > boxes at home(wife's laptop - p3-500 and kids desktop - p3 1G) and it r=
uns
> > great.  I also have it still on my new box as it is completely setup fo=
r
> > everything I need it to do and won't be getting rid of it anytime soon.
> >
> > The same thing happened when P4 and AthlonXP came out - folks were happ=
y
> > with their P3's and Athlon's but once they saw the difference and PC ve=
ndors
> > starting only shipping the new CPU's, they were forced to go with them.
> >
> >
> > To give you an idea of how debian 64-bit linux runs on my humble 64-bit
> > system, I would liken it to how regular VL with icewm ran on my AthlonX=
P
> > 2400+ - very quick and almost instant response.  A big difference from =
SuSE
> > 64-bit.
> >
> > My main hard drive on my 64-bit system is now about to die and I will b=
e
> > replacing it with a sata drive which is at least 200GB in size so I wil=
l
> > have lots of "devel" and "play" space.  It will also free up my slave d=
rive
> > which has SOHO on it for other uses.
> >
> >
>