This is not all new, because there has been a theory called the "nemesis theory" which is an extension to the catastrophe theory. It states that there have been quite a lot of impacts on earth that more or less caused mass extinction. The impact that killed the dinosaurs is just one of them. Some scientists have found a strange cycle in those impacts of about 20 million years. They figured it must be caused by a small star, doubling with the sun. This sounds like more evidence for that theory.
"...the sad fact is that as it stands right now Linux is simply NOT at a level where my mother could use it..."
Ryan, KDE is getting there, fast. It's *the* GUI for newbies on UNIX. I'm a slacker and BSD'er, I use X only for funkyness, but KDE will rock your mother soon.
Whenever you stuck with rpm's, you're only option is to use rpm's to keep the database up to date. No way of telling the thing that you just added libfoo.bar.so.1.2.3 by *hand*...
And not the whole UNIX world is packing stuff in *yet another pkg format*...
The point is better made with debian, whose pkg format is even more obscure on the internet (Can't you remember all those site's saying "when we have time we'll make *.deb's"?).
Pkg management should be kept for the *base* of your system, and thus be reduced to a minimum.
It's not I want to piss off rpm's, it's just that I don't want my system to be dependant on a format.
Pkg management is a lie. If you ever find yourself administarting a commercial unix you won't find any rpm's.
No. What slackware needs is a good bootstrap building procedure like "make world" on bsd combined with some sort of simplified cvs, again, like bsd. I run FreeBSD and Slack, and FreeBSD impressed me with this.
That would kick the shit out of any other linux distro...
On account of rpm's and deb's, they make you lazy.
Read the comments on UCITA and you might draw the opposite conclusion. Forbidding reverse engineering could turn out in favour of monopolies and propiarty software houses. Take for instance a small thing like "gnokii" which has been written by reverse engineering calls to and from win software. It would be impossible to publish such code under UCITA, which explicitely forbids reverse engineering.
You were probably one of the few in France that saw it, since the wheather was terrible. It rained in Soisson in the morning. We had to drive to a place near Thionville (160 Km/h! Gendarmerie saw me and didn't even fine me;-) to find a spot with a tiny bit of blue sky. The moment the totallity started the sun was behind a cloud, but the sudden increase of darkness was amazing. Then, suddenly, the sky gave us a tiny part of blue sky, so I saw 15 seconds of corona. And we considered ourselves lucky!
It *looks* to me that all of this has been done in a sort of hurry, and is *not* the final license. Mind you, the guy posted a reply earlier on and made a very hasty fix. So I'd suggest giving him some time to figure out how and what.
#include's should *contain* something...
They call it an alpha release themself :)
Use Slack. Go to bugtraq and find out why
Better check bugtraq for RH specific bugs...
You DO know what bugtraq is, don't you ?
wayout
Uhhmm. Could you be more specific on that package-system? I rather curious... Website perhaps?
wayout
I'm 34, so "in my lifetime" is a rather optimistic view :-)
This is not all new, because there has been a theory called the "nemesis theory" which is an extension to the catastrophe theory. It states that there have been quite a lot of impacts on earth that more or less caused mass extinction. The impact that killed the dinosaurs is just one of them. Some scientists have found a strange cycle in those impacts of about 20 million years. They figured it must be caused by a small star, doubling with the sun. This sounds like more evidence for that theory.
wayout
Yep, it thoroughly seems like a "support test".
What this DOES say though is MS is worried about
games being ported to Linux.
"Much of the success of Linux, by the way, might be attributed to the fact that Linux folks are busy writing software instead of hanging out on IRC.."
Sorry Bruce but that is BS. Many, many Bot's are running from linux machines.
wayout
"...the sad fact is that as it stands right now Linux is simply NOT at a level where my mother could use
it..."
Ryan, KDE is getting there, fast. It's *the* GUI for newbies on UNIX. I'm a slacker and BSD'er, I use X only for funkyness, but KDE will rock your mother soon.
Whenever you stuck with rpm's, you're only option is to use rpm's to keep the database up to date. No way of telling the thing that you just added libfoo.bar.so.1.2.3 by *hand*...
And not the whole UNIX world is packing stuff in *yet another pkg format*...
The point is better made with debian, whose pkg format is even more obscure on the internet (Can't you remember all those site's saying "when we have time we'll make *.deb's"?).
Pkg management should be kept for the *base* of your system, and thus be reduced to a minimum.
It's not I want to piss off rpm's, it's just that I don't want my system to be dependant on a format.
1. Small, yet complete dist that remains true to Unix.
/tmp/.X11-unix bug.)
2. Installed from *.tgz packages, which means no new package format was used, and I can unpack slack even on a win machine..
3. Always the emphasis is on "robustness". You can check bugtraq for all RH's or Debian's bugs (e.g.
Inother words:
RH is for windows haters.
Slack is for Unix lovers.
Sorry if I sound rude but...
Pkg management is a lie. If you ever find yourself administarting a commercial unix you won't find any rpm's.
No. What slackware needs is a good bootstrap building procedure like "make world" on bsd combined with some sort of simplified cvs, again, like bsd. I run FreeBSD and Slack, and FreeBSD impressed me with this.
That would kick the shit out of any other linux distro...
On account of rpm's and deb's, they make you lazy.
Yeah, I have ported a slack 4.0 on my 386 halfway and find utils broke at me too.
It seems that there is a port on ftp://sagen.hoxnet.com that *has* find, but that i686 specific code in it..
Read the comments on UCITA and you might draw the
opposite conclusion. Forbidding reverse engineering could turn out in favour of monopolies and propiarty software houses. Take for instance a small thing like "gnokii" which has been written by reverse engineering calls to and from win software. It would be impossible to publish such code under UCITA, which explicitely forbids reverse engineering.
way_out
You were probably one of the few in France that saw it, since the wheather was terrible. It rained in Soisson in the morning. We had to drive to a place near Thionville (160 Km/h! Gendarmerie saw me and didn't even fine me ;-) to find a spot with a tiny bit of blue sky. The moment the totallity started the sun was behind a cloud, but the sudden increase of darkness was amazing. Then, suddenly, the sky gave us a tiny part of blue sky, so I saw 15 seconds of corona. And we considered ourselves lucky!
You seem to be more lucky, which place were you?
Search freshmeat.net for it. It's called boclient.
I use it to check my fakebo server.
And why the port? Isn't ssh enough?
"One thing that the article missed is the pride of hackerdom."
;-)
Quite so! A good UNIX war is about defending your pride rather than degrading your oponent.
I've read your comments and found them to be totally incomprehensible.
It *looks* to me that all of this has been done in a sort of hurry, and is *not* the final license. Mind you, the guy posted a reply earlier on and made a very hasty fix. So I'd suggest giving him some time to figure out how and what.
Give him a break
Hum.
...
I still see quite a lot of commercial fbsd's
XV is still included in RH. Thats an "unregistred" version.
heheheh
Checked it..
http://www.netmeg.net/jargon/terms/h.html#hack
The word "hack" comes from the 60's, and back then it meant what we now call an ugly hack, or a quick hack.
Besides: be glad the 80's are over. They only gave us Duran Duran