I never owned a NeXT, but then again I never liked their gui either:-)
Btw, ever owned a 633MHz Alpha with 512MB and 20GB harddisk? That's what I'm currently sitting at. And I even put the thing together. Thrilling, eh?
$ cat/proc/cpuinfo cpu : Alpha cpu model : EV56 cpu variation : 0 cpu revision : 0 cpu serial number : Linux_is_Great! system type : Ruffian system variation : 0 system revision : 0 system serial number : MILO-0000 cycle frequency [Hz] : 633262060 est. timer frequency [Hz] : 1024.00 page size [bytes] : 8192 phys. address bits : 40 max. addr. space # : 127 BogoMIPS : 629.14 kernel unaligned acc : 0 (pc=0,va=0) user unaligned acc : 855938 (pc=120051e90,va=1209a03cf) platform string : N/A
They don't. Linux still uses partially invalid asm code which used to work on gcc 2.7.2, but fails with a better compiler such as egcs 1.1.x. The egcs team has decided to _not_ support the broken code from Linux.
Fortunately, SuSE is the best Linux distribution when it comes to built-in ISDN support. You need to install the i4l packet (at least) and configure your card using yast - I tried this once and it worked immediately. That should be even easy for beginners (I'm used to i4b on FreeBSD/NetBSD systems which I'd consider expert-only).
And please use the SuSE support database which probably contains answers for your questions:
the technically illiterate - wants funky colors, great design, wants to be protected from the "not very functional on the inside." Probably runs Windoze 98 and knows 100 Bill Gates jokes. Someone above used the term "mom" for them.
the knowledgeable person - uh, you probably know yourself better than I can describe it. You want to have the power to do everything with your hardware (and software) and don't like to be limited by these "cool cases." You know how to use cables correctly in the inside of a standard case and help other people to get up running their PeeCees
With M$ expertise in this field, I would not wonder, if legacy 32-bit applications would not run anymore on their 64-bit O/S. But if I am not mistaken, Sun's UltraSparcs can still run old 32-bit apps even if switched into 64-bit mode. The Linux port to that platform contains also code to enable this kind of backwards compatibility.
libc5 - older, proven to be robust in very "traditional" areas, lacks modern features. It is maintained only for bug fixes.
glibc 2.0 - has many new features such as NSS and completely thread-safety, the latest release is 2.0.7pre6. That is the release you want on your server
glibc 2.1 - the latest and greatest; glibc 2.1.0 contains some "issues" which make it unuseable on production machines. The next release (we are already at 2.1.1pre3) will fix most obvious bugs, but I wouldn't swear on this one within the next weeks (maybe months).
In my administrator job I don't count on bleeding edge software - it bites too often. IMHO the ideal Linux server will run currently 2.0.36 (2.2.x will mature) together with glibc 2.0.7pre6 as primary C library.
Have a good night.
Re:I can't believe they pay people to write this
on
ABCNews GNOME Acticle
·
· Score: 1
Just an observation which may be right or wrong: I have seen now several articles which get the history totally wrong. They were all about GNOME and Miguel, but I have never read an article about KDE or another Unix desktop environment which was flawed so much. I'll probably blame the new popularity of Linux/Unix for this ``effect.''
Turning off a service guarantees you that this service cannot be exploited. That does not mean it is exploitable, but you reduce the chance of a breakin through that single service.
There are a number of services which have a bad security reputation. Especially finger is a service almost nobody really needs, so it is safer to simply turn it off. The same rule applies to many other things such as talk, all r* services, netstat and probably more.
Don't forget that is not a kernel issue, but an user-level issue. Exploits generally exploit errors in daemons (such as sendmail, ftpd etc). So, if your ftpd is exploitable, it does not matter whether it runs under FreeBSD or Linux.
D.H. Brown Associates added Caldera Systems and Red Hat Linux distributions into its ongoing analysis of several operating systems
What do you think is an "analysis of several operating systems?" A single comparison between NT and Linux? news.com only cites some small pieces from the whole analysis and I bet you have not read all of the text. Jump on news.com, if you need to waste the energy of your puberty.
Btw, learn some rhetoric. Saying there is "no comparison" and appending a "there is a comparison" is plain stupid.
The author (D.H. sth) addressed commercial ready packages, not your self made solution (fake, mon, some shell scripts). From that perspective, Linux lacks support for such features.
Also, the author did not compare Linux to NT, but to other operating systems, such as Solaris. I think it was Linus himself who said not long ago that Linux' SMP capabilities will be comparable to Solaris in 3 years or so. It currently scales to double (maybe quad) boxes for IO bound processes. But that is all.
You lack fundamental knowledge in respect to the Alpha platform. If you would follow linux-kernel, you would know that only 1GB is currently supported on that specific platform. There are some people working on this problem.
No, they don't say "Linux sucks", even if you would like to read that out of context. It is a comparison between high end operating systems, you should be proud that our Linux has entered that realm.
If old technology is still useful, why should not we maintain it? ISA for example: Why the hell would a soundcard need the power of the PCI bus? Or ISDN cards. Or modem cards. They all don't need a 33MHz bus. The only benefit is the automatic IO assignment...
Well, you need friends who have access to Digital Unix' libraries then. The OSF version of Netscape is a typical Netscape, mostly stable, but crashes sometimes.
Before I got the libraries I used a P166 as a Netscape "server." Worked, albeit not as fast as my 633MHz Alpha.
Libc5 has thread support. It is not included, but glibc 2.x has also separate linuxthreads packages.
Libc5 is discontinued (according to H.J. Lu) because libc5 does the job, but it does not do the job good enough. Quote from release.libc6 out of the libc5 package:
The Linux C library 5 is phasing out. I am only maintaining it for very serious bug fixes only. People who want new features and other improvements should use the Linux C library 6, aka, the GNU C library 2.
I don't know how old it is, but it is way older than MS' SMS. You can basically push packages to other systems by using the rdist facility. This can be exactly used for that purposes you refer to.
Most bigger sites contain out of dynamic content where static content (as served by sendfile) does not play a big role (you only need a big pipe for e.g. pictures). I said this already in the kernel discussion, but Linus contradicts himself here - it is a new interface and one which needs improvement.
Slashdot Mirror
I never owned a NeXT, but then again I never liked their gui either :-)
/proc/cpuinfo
Btw, ever owned a 633MHz Alpha with 512MB and 20GB harddisk? That's what I'm currently sitting at. And I even put the thing together. Thrilling, eh?
$ cat
cpu : Alpha
cpu model : EV56
cpu variation : 0
cpu revision : 0
cpu serial number : Linux_is_Great!
system type : Ruffian
system variation : 0
system revision : 0
system serial number : MILO-0000
cycle frequency [Hz] : 633262060 est.
timer frequency [Hz] : 1024.00
page size [bytes] : 8192
phys. address bits : 40
max. addr. space # : 127
BogoMIPS : 629.14
kernel unaligned acc : 0 (pc=0,va=0)
user unaligned acc : 855938 (pc=120051e90,va=1209a03cf)
platform string : N/A
Uh? You are describing SSL/TLS. Go get mod_ssl for Apache and Fortify to enable 128-bit ciphers in all Netscape browsers.
They don't. Linux still uses partially invalid asm code which used to work on gcc 2.7.2, but fails with a better compiler such as egcs 1.1.x. The egcs team has decided to _not_ support the broken code from Linux.
There are various ISDN Howtos in the support database, I picked out the right ones for your SuSE Version:
English version
German version
Fortunately, SuSE is the best Linux distribution when it comes to built-in ISDN support. You need to install the i4l packet (at least) and configure your card using yast - I tried this once and it worked immediately. That should be even easy for beginners (I'm used to i4b on FreeBSD/NetBSD systems which I'd consider expert-only).
And please use the SuSE support database which probably contains answers for your questions:
German and English search
When and in with regard to what?
It boils down to two groups
- the technically illiterate - wants funky colors, great design, wants to be protected from the "not very functional on the inside." Probably runs Windoze 98 and knows 100 Bill Gates jokes. Someone above used the term "mom" for them.
- the knowledgeable person - uh, you probably know yourself better than I can describe it. You want to have the power to do everything with your hardware (and software) and don't like to be limited by these "cool cases." You know how to use cables correctly in the inside of a standard case and help other people to get up running their PeeCees
I will always choose the later groupWith M$ expertise in this field, I would not wonder, if legacy 32-bit applications would not run anymore on their 64-bit O/S. But if I am not mistaken, Sun's UltraSparcs can still run old 32-bit apps even if switched into 64-bit mode. The Linux port to that platform contains also code to enable this kind of backwards compatibility.
Because it is not out yet?
But the number of prereleases (17 or more) should produce a very good kernel.
- libc5 - older, proven to be robust in very "traditional" areas, lacks modern features. It is maintained only for bug fixes.
- glibc 2.0 - has many new features such as NSS and completely thread-safety, the latest release is 2.0.7pre6. That is the release you want on your server
- glibc 2.1 - the latest and greatest; glibc 2.1.0 contains some "issues" which make it unuseable on production machines. The next release (we are already at 2.1.1pre3) will fix most obvious bugs, but I wouldn't swear on this one within the next weeks (maybe months).
In my administrator job I don't count on bleeding edge software - it bites too often. IMHO the ideal Linux server will run currently 2.0.36 (2.2.x will mature) together with glibc 2.0.7pre6 as primary C library.Have a good night.
Just an observation which may be right or wrong: I have seen now several articles which get the history totally wrong. They were all about GNOME and Miguel, but I have never read an article about KDE or another Unix desktop environment which was flawed so much. I'll probably blame the new popularity of Linux/Unix for this ``effect.''
Turning off a service guarantees you that this service cannot be exploited. That does not mean it is exploitable, but you reduce the chance of a breakin through that single service.
There are a number of services which have a bad security reputation. Especially finger is a service almost nobody really needs, so it is safer to simply turn it off. The same rule applies to many other things such as talk, all r* services, netstat and probably more.
Don't forget that is not a kernel issue, but an user-level issue. Exploits generally exploit errors in daemons (such as sendmail, ftpd etc). So, if your ftpd is exploitable, it does not matter whether it runs under FreeBSD or Linux.
Oh man.
D.H. Brown Associates added Caldera Systems and Red Hat Linux distributions into its ongoing analysis of several operating systems
What do you think is an "analysis of several operating systems?" A single comparison between NT and Linux? news.com only cites some small pieces from the whole analysis and I bet you have not read all of the text. Jump on news.com, if you need to waste the energy of your puberty.
Btw, learn some rhetoric. Saying there is "no comparison" and appending a "there is a comparison" is plain stupid.
Oh man. Who gave that post such a high rating??
The author (D.H. sth) addressed commercial ready packages, not your self made solution (fake, mon, some shell scripts). From that perspective, Linux lacks support for such features.
Also, the author did not compare Linux to NT, but to other operating systems, such as Solaris. I think it was Linus himself who said not long ago that Linux' SMP capabilities will be comparable to Solaris in 3 years or so. It currently scales to double (maybe quad) boxes for IO bound processes. But that is all.
You lack fundamental knowledge in respect to the Alpha platform. If you would follow linux-kernel, you would know that only 1GB is currently supported on that specific platform. There are some people working on this problem.
No, they don't say "Linux sucks", even if you would like to read that out of context. It is a comparison between high end operating systems, you should be proud that our Linux has entered that realm.
If old technology is still useful, why should not we maintain it? ISA for example: Why the hell would a soundcard need the power of the PCI bus? Or ISDN cards. Or modem cards. They all don't need a 33MHz bus. The only benefit is the automatic IO assignment...
Well, you need friends who have access to Digital Unix' libraries then. The OSF version of Netscape is a typical Netscape, mostly stable, but crashes sometimes.
Before I got the libraries I used a P166 as a Netscape "server." Worked, albeit not as fast as my 633MHz Alpha.
The first entry in the rdist's ChangeLog is from 1992 when it was already at V6.0. It seems to have been distributed within BSD4.3 and older.
rsync is fairly new in comparison. A paper on the rsync algorithm is from 1996 (also included in the rsync distribution as tech_report.tex).
Libc5 has thread support. It is not included, but glibc 2.x has also separate linuxthreads packages.
Libc5 is discontinued (according to H.J. Lu) because libc5 does the job, but it does not do the job good enough. Quote from release.libc6 out of the libc5 package:
The Linux C library 5 is phasing out. I am only maintaining it for
very serious bug fixes only. People who want new features and other
improvements should use the Linux C library 6, aka, the GNU C library
2.
If Win9x decides to overwrite some bytes in areas it does not own, it does not have to change the partition table.
I don't know how old it is, but it is way older than MS' SMS. You can basically push packages to other systems by using the rdist facility. This can be exactly used for that purposes you refer to.
Most bigger sites contain out of dynamic content where static content (as served by sendfile) does not play a big role (you only need a big pipe for e.g. pictures). I said this already in the kernel discussion, but Linus contradicts himself here - it is a new interface and one which needs improvement.
It's old, antique and does not do particular jobs very well (especially thread handling). That is why I run glibc 2.1 even on older Pentium systems.