Ron Gibson wrote:
> I've never found myself in that position with Slackware. Every release
> has been usable by my best recollection.

I do recall minor problems (or should I say 'unreasonable defaults')
that made me skip 10.0 and 10.1 and stay on 9.1.

However, you're right. It's hard to install new version of Slackware
when the current one you have works so good.


--
Milan Babuskov
http://home.gna.org/vodovod

On Mon, 02 Jul 2007 09:30:31 +0200, Milan Babuskov wrote:

> I do recall minor problems (or should I say 'unreasonable defaults')
> that made me skip 10.0 and 10.1 and stay on 9.1.

> However, you're right. It's hard to install new version of Slackware when
> the current one you have works so good.

You know we are spoiled. Look into other linux distro NG's and you see
people struggling trying to get MANY things working we take for granted.

One major distro, for example, was using the latest greatest gcc and so
on.

One problem. It would fail to compile about half of the apps I usually
compile from source. Hell when it *would* compile, it choked on their own
version of checkinstall failing on the build RPM section for cripes
sake.

Biy that's bad when Linux can't compile a source package due to a
mix of broken compilers and bad libs.

Needless to say I'm done playing with that distro.

--
Linux Help: http://rsgibson.com/linux.htm
Email - rsgibson@verizon.borg
Replace borg with net

Ron Gibson <rsgibson@verizon.net> trolled:
> On Mon, 02 Jul 2007 09:30:31 +0200, Milan Babuskov wrote:

>> I do recall minor problems (or should I say 'unreasonable
>> defaults') that made me skip 10.0 and 10.1 and stay on 9.1.

>> However, you're right. It's hard to install new version of
>> Slackware when the current one you have works so good.

> You know we are spoiled. Look into other linux distro NG's and you
> see people struggling trying to get MANY things working we take
> for granted.

Hardly. X doesn't even come ready to go in slackware. And the
default editor is elvis, for gawd's sakes. Printer setup is still a
bear.

> One major distro, for example, was using the latest greatest gcc
> and so on. One problem. It would fail to compile about half of
> the apps I usually compile from source. Hell when it *would*
> compile, it choked on their own version of checkinstall failing on
> the build RPM section for cripes sake.

And did it already have precompiled packages around for the apps you
were compiling? Probably. And compiled with the latest and
greatest gcc, as well.

cordially, as always,

rm

On 2007-07-02, Rhonda Moffat <rm@justlinux.ca> wrote:

> Hardly. X doesn't even come ready to go in slackware. And the
> default editor is elvis, for gawd's sakes. Printer setup is still a
> bear.

??? I've had zero probs with X.org. vi in any form sucks. Hardware
for Linux is still a crap shoot. For printers, pick a compatible
brand and app. Brother lasers using LPRng/apsfilter is trivial. The
one serious hardware pothole is scanners. Linux developers seem to
have completely abandoned this h/w segment.

It appears Linux is no longer alone. A check of various corners of
the web reveals more than a few h/w holes for Vista, also. The shine
is off the fruit over at Apple, too, as iphone(y) owners discover some
rotten issues in the barrel.

None of this is new or news. Look at railroads? An early technology
of a fire/ash/ember belching device towing a whole line of
combustibles. Doh! It's technology as usual.

nb

On Mon, 02 Jul 2007 08:38:46 -0500, notbob wrote:

>> Hardly. X doesn't even come ready to go in slackware. And the default
>> editor is elvis, for gawd's sakes. Printer setup is still a bear.

export EDITOR='/usr/bin/jed'

> ??? I've had zero probs with X.org. vi in any form sucks. Hardware for
> Linux is still a crap shoot. For printers, pick a compatible brand and
> app. Brother lasers using LPRng/apsfilter is trivial. The one serious
> hardware pothole is scanners. Linux developers seem to have completely
> abandoned this h/w segment.

More babble form that nut?

BTW, I recently bought an HP 5440. It took me over a month of digging to
figure out how to install the 'doze drivers - had to uninstall "NET
Framework" to get them to install (A note buried on HP's site) and hit
the reset button at the end to keep the files from being erased because
the driver software thought the installation had failed.

Same printer took 5 minutes to set it up with CUPS.

BTW, glad to see I'm not the only one whose been around a few years and
has no love for vi. I've been using jed for my CLI editor as long as
I've been using Slackware.

--
Linux Help: http://rsgibson.com/linux.htm
Email - rsgibson@verizon.borg
Replace borg with net

On Mon, 02 Jul 2007 10:26:42 +0000, Rhonda Moffat wrote:

>> You know we are spoiled. Look into other linux distro NG's and you
>> see people struggling trying to get MANY things working we take
>> for granted.

> Hardly. X doesn't even come ready to go in slackware.

Hogwash. Works fine.

> And the default editor is elvis, for gawd's sakes.

Yeah, that's hard to change, eh? Free clue: "export EDITOR="

> Printer setup is still a bear.

Yeah, it's a bitch to type "localhost:631" into your browser, eh?

> cordially, as always,

Smeg off, ignoramus.


--
"Ubuntu" -- an African word, meaning "Slackware is too hard for me".

Ron Gibson <rsgibson@verizon.net> trolled:
> On Mon, 02 Jul 2007 08:38:46 -0500, notbob wrote:

>>> Hardly. X doesn't even come ready to go in slackware. And the
>>> default editor is elvis, for gawd's sakes. Printer setup is
>>> still a bear.

> export EDITOR='/usr/bin/jed'

That's taking a giant step backwards, isn't it? Isn't jed a sugar
free, caffeine free, emacs? Or is that jove? We've never heard of
anyone who uses either. Joe, maybe. Vim is terrific and runs on
every platform.

>> ??? I've had zero probs with X.org. vi in any form sucks. Hardware for
>> Linux is still a crap shoot. For printers, pick a compatible brand and
>> app. Brother lasers using LPRng/apsfilter is trivial. The one serious
>> hardware pothole is scanners. Linux developers seem to have completely
>> abandoned this h/w segment.

> BTW, I recently bought an HP 5440. It took me over a month of
> digging to figure out how to install the 'doze drivers - had to
> uninstall "NET Framework" to get them to install (A note buried on
> HP's site) and hit the reset button at the end to keep the files
> from being erased because the driver software thought the
> installation had failed.

> Same printer took 5 minutes to set it up with CUPS.

And how long did it take to setup CUPS? We got a AOI printer with our
Dell PC, as a throwin. It's a clone of a lexmark and it is a
paperweight as far as linux is concerned. Works beautifully and
instantly with XP.

> BTW, glad to see I'm not the only one whose been around a few
> years and has no love for vi. I've been using jed for my CLI
> editor as long as I've been using Slackware.

vi was built to be integral to the unix OS. Once you learn it, vim
is very powerful.

We'll install jed for the hell of it and see what it is like. We
used to like a little known editor called "le" which had nice menus
and was very similar to a dos favourite called qedit. Qedit, Boxer
and Norton Editor are all beauties that we wish had been translated
and compiled for unix/linux.

cordially, as always,

rm

On Mon, 02 Jul 2007 08:38:46 -0500, notbob wrote:

>> Hardly. X doesn't even come ready to go in slackware. And the
>> default editor is elvis, for gawd's sakes. Printer setup is still a
>> bear.

> ??? I've had zero probs with X.org.

Same here.

> vi in any form sucks.

Blasphemy! Long live vim!

> Hardware for Linux is still a crap shoot. For printers, pick a compatible
> brand and app. Brother lasers using LPRng/apsfilter is trivial.

Brother lasers with CUPS is simple, too.


--
"Ubuntu" -- an African word, meaning "Slackware is too hard for me".

Ron Gibson wrote:
> You know we are spoiled. Look into other linux distro NG's and you see
> people struggling trying to get MANY things working we take for granted.

Agreed.

> One major distro, for example, was using the latest greatest gcc and so
> on.

You mean Ubu^H^H^HDebian? I think I ran into that. And I ditched Fedora
long time ago. Only distros that somewhat work for me (aside Slack) are
CentOS and Mandriva.

> Biy that's bad when Linux can't compile a source package due to a
> mix of broken compilers and bad libs.
>
> Needless to say I'm done playing with that distro.



--
Milan Babuskov
http://home.gna.org/vodovod

Ron Gibson wrote:
>
.... snip ...
>
> BTW, glad to see I'm not the only one whose been around a few
> years and has no love for vi. I've been using jed for my CLI
> editor as long as I've been using Slackware.

Wheee. Editor wars. Go crew, go.

--
<http://www.cs.auckland.ac.nz/~pgut001/pubs/vista_cost.txt>
<http://www.securityfocus.com/columnists/423>
<http://www.aaxnet.com/editor/edit043.html>
cbfalconer at maineline dot net



--
Posted via a free Usenet account from http://www.teranews.com