So I hope someone plans on protecting this "Open Source Network" from all the kiddies of the world... Otherwise, ncsu.edu is gonna be banned at all major routers.
Hooray for RedHat exploits.
UT vastly superior? UT was a rehashed Unreal engine. Q3 was a completely new engine, not to mention, it was polished when it was released. Tim Sweeny and friends just sorta shoved UT out the door and patched it up later... and it shipped with some serious bugs.
As for id shipping 3 copies of Q3, they did that for a reason, if you've ever read anything about it anywhere (hello Slashdot). They shipped it in 3 boxes to do demographics, and to determine if writing software for the Mac and for Linux was a feasible idea.
Not to mention, EPIC announced UT/after/ Carmack mentioned that they were doing a multi-player only game with bots. Then some EPIC employee had the balls to smart off about how id was copying them (single guy stuck on planet, forced to kill everything looking for a key to get out... sound familiar?). Of course, this was the great plan flamewar that got Steed's plan rights revoked.
And another thing, UT supports D3D (evil empire graphics standard), while Q3 supports OpenGL (everyone's favorite graphics platform, not to mention, it's open).
So, it doesn't suprise me to find this on Slashdot.
As a person who studys at and works for a university, I can say that Oxford did the right thing. As it is, universities don't have all that much money, especially for lawyers. This also has nothing to do with censorship. The university owns the machines. The students don't pay for their access. When you get your account, you sign an agreement saying that you give the university the right to your data, especially if they're getting sued over it.
Netscape never can run multiple instances. 'killall' is just a giant awk/perl script, depending on how old it is. One of the downsides of 'killall' is that it only goes on the last part of the binary name. So, if you've got something running (netscape) named communicator-4.72.bin, but it contains 'netscape' in the path, then 'killall' won't nuke it.
All the 'Kill Netscape' progs on freshmeat.net look at the whole path, so they can grab anything that contains a certain string.
But yes, the script isn't exactly robust. It actually was a one-liner, but I cleaned it up for readability.
This is one of those things that shows that Linus most definitely does have a clue.
Except his solution to this problem is pretty clue--. He suggests "running something like 'tar' on shutdown and boot" to handle devfs permissions. When multiple people thought the idea was totally stupid, he replied that running a startup and shutdown script wouldn't be all that bad...
Obviously, Linus never took catastrophic failure into consideration.
I think you should just be glad that this didn't turn into a holywar/flamewar like most BSD articles posted to Slashdot do.
Personally, I like being able to read comments that are intelligent and thoughtful, rather than "Linux RuLeZ! BSD SUX!"
I was also surprised by the relatively intelligent posts made on the last article about the merger. I honestly expected it to be a complete waste of time reading the comments.
I may have to change my opinion about Slashdot if this trend continues.:)
FreeBSD will not run VMWare, because VMWare uses a kernel module under Linux. Last I checked, FreeBSD can't use Linux kernel modules. Until VMWare writes a native version for FreeBSD, we'll just have to use bochs or freevmware at http://www.freevmware.org.
While all of you were so pissed that Linux couldn't use it, you seem to have forgotten that the rinky-dink intro javascript also denied users of a lot more OS's than Linux. Try BeOS, FreeBSD, NetBSD, OpenBSD, HP-UX, Solaris, NeXTStep, IRIX, BSD/OS, OSF, OS/2, and just about any other OS you can think of that doesn't run on a PC or isn't Windows. Stop your bitching and look at the big picture.
Now that the docs are available...
on
Free Books Online
·
· Score: 1
When can we expect a CVS repository for the Linux kernel code? CVSup is much better than downloading the patches, imho.
Umm... I'm running XFree 3.9.16 on my FreeBSD machine, and I get TrueType just fine. Before that I was running the Xftt server patches for 3.3.x. In fact, 3.9.16 was easier to compile than the Xftt server. I'm not sure that there's an entry in ports for it yet, but it's a pretty simple task if you read the docs.
Should RedHat really be doing all these "changes" to the kernel and applications now? Are we going to be stuck with another horrible standard like RPM? Which, by the way, no matter how good you say it is, it's still the wrong way to do it.
I think RedHat is getting a big head over this whole IPO thing. I don't really think them buying Cygnus is a GoodThing(tm) either. egcs has been incorporated into the FreeBSD source tree. RedHat's software has never been know to be even remotely portable. (Trust me. I've tried it) What will happen when RedHat starts "making changes" to the egcs code base? Are we going to end up with a compiler that only works with the Linux 2.3.78-ac256 kernel?
Is it really necessary to announce every kernel patch? It's not like Alan Cox isn't going to release 8 more next week. Like we really need to know that 2.2.11-ac12 is out...
The biggest problem I see with this book is that there is no mention of writing portable code. Linux programs, in particular, lack in this area. #include <linux.h> just doesn't cut it when it comes to trying to run software across multiple platforms.
Multi-Processing The K7's use of the EV6 protocol also opens a door for AMD into the world of multi-processor systems, an area that Intel has had a lock on for the last several years. The EV6 implements point-to-point topology. This means that if there are multiple processors within the system, each gets a dedicated connection to the chipset. Intel based multi-processor systems must share a bus interconnected with the chipset. This is the technology that Intel has refused to share licensing for an so has pushed x86 CPU manufacturers away from developing multi-processor systems. This technology of Intel's is also limited to the use of only four processors within a given system. AMD's development of the EV6 protocol for x86 processors opens systems up to use as many as 16 processors provided the memory bus architecture can support it. Even though each processor gets a dedicated connection to the chipset is must share a system bus from the chipset to main memory. This will step up development of larger and faster memory types than current 64-bit access SDRAM. You can be assured that AMD will be developing for a variety of new memory types like RAMBUS, DRDRAM or DDR SDRAM.
How is this BS? They used a standard benchmark (SPECint, SPECfp) designed to test _different_ CPUs with the same benchmark.
If you run ZiffDavis benchmarks on a Sparc, it's gonna say that an Intel chip is faster, because the ZiffDavis benchmarks are written for Intel chips.
I seem to also remember that a month or so ago when QuakeIII came out, somehow TomsHardware had benchmarks for it, even though the 'timedemo' and 'timerefresh' commands were _broken_.
Yep it supports SMP. The cool thing about it is, it uses memory bank interleaving. The memory still runs at 100Mhz, but the CPU's skip between banks, essentially reducing the memory bottleneck of SMP machines.
Some of AMD's documents about the K7 went over this in detail, but it seems AMD took most of those docs down. Anyone have them?
Slashdot Mirror
So I hope someone plans on protecting this "Open Source Network" from all the kiddies of the world... Otherwise, ncsu.edu is gonna be banned at all major routers. Hooray for RedHat exploits.
UT vastly superior? UT was a rehashed Unreal engine. Q3 was a completely new engine, not to mention, it was polished when it was released. Tim Sweeny and friends just sorta shoved UT out the door and patched it up later... and it shipped with some serious bugs.
/after/ Carmack mentioned that they were doing a multi-player only game with bots. Then some EPIC employee had the balls to smart off about how id was copying them (single guy stuck on planet, forced to kill everything looking for a key to get out... sound familiar?). Of course, this was the great plan flamewar that got Steed's plan rights revoked.
As for id shipping 3 copies of Q3, they did that for a reason, if you've ever read anything about it anywhere (hello Slashdot). They shipped it in 3 boxes to do demographics, and to determine if writing software for the Mac and for Linux was a feasible idea.
Not to mention, EPIC announced UT
And another thing, UT supports D3D (evil empire graphics standard), while Q3 supports OpenGL (everyone's favorite graphics platform, not to mention, it's open).
So, it doesn't suprise me to find this on Slashdot.
As a person who studys at and works for a university, I can say that Oxford did the right thing. As it is, universities don't have all that much money, especially for lawyers. This also has nothing to do with censorship. The university owns the machines. The students don't pay for their access. When you get your account, you sign an agreement saying that you give the university the right to your data, especially if they're getting sued over it.
All the 'Kill Netscape' progs on freshmeat.net look at the whole path, so they can grab anything that contains a certain string.
But yes, the script isn't exactly robust. It actually was a one-liner, but I cleaned it up for readability.
In reality, this would work as well:
#/bin/sh
kill -9 `ps -ax | grep $1 | grep `whoami` | head -1 | awk '{print $1} '`;
And this one will get anything owned by you, instead... plus it doesn't try to kill itself. Yay for Bourne Shell.
pid=`ps -ax | grep $1 | head -1 | awk '{print $1} '`
kill -9 $pid
echo "Killed $1, pid: $pid"
now you can run ./killg netscape
Except his solution to this problem is pretty clue--. He suggests "running something like 'tar' on shutdown and boot" to handle devfs permissions. When multiple people thought the idea was totally stupid, he replied that running a startup and shutdown script wouldn't be all that bad...
Obviously, Linus never took catastrophic failure into consideration.
I think you should just be glad that this didn't turn into a holywar/flamewar like most BSD articles posted to Slashdot do.
:)
Personally, I like being able to read comments that are intelligent and thoughtful, rather than "Linux RuLeZ! BSD SUX!"
I was also surprised by the relatively intelligent posts made on the last article about the merger. I honestly expected it to be a complete waste of time reading the comments.
I may have to change my opinion about Slashdot if this trend continues.
10 PRINT "LINUX RULEZ!!@@!!"
20 GOTO 10
Then we'll be really cool.
FreeBSD will not run VMWare, because VMWare uses a kernel module under Linux. Last I checked, FreeBSD can't use Linux kernel modules. Until VMWare writes a native version for FreeBSD, we'll just have to use bochs or freevmware at http://www.freevmware.org.
While all of you were so pissed that Linux couldn't use it, you seem to have forgotten that the rinky-dink intro javascript also denied users of a lot more OS's than Linux. Try BeOS, FreeBSD, NetBSD, OpenBSD, HP-UX, Solaris, NeXTStep, IRIX, BSD/OS, OSF, OS/2, and just about any other OS you can think of that doesn't run on a PC or isn't Windows.
Stop your bitching and look at the big picture.
When can we expect a CVS repository for the Linux kernel code? CVSup is much better than downloading the patches, imho.
Umm... I'm running XFree 3.9.16 on my FreeBSD machine, and I get TrueType just fine. Before that I was running the Xftt server patches for 3.3.x. In fact, 3.9.16 was easier to compile than the Xftt server. I'm not sure that there's an entry in ports for it yet, but it's a pretty simple task if you read the docs.
Should RedHat really be doing all these "changes" to the kernel and applications now? Are we going to be stuck with another horrible standard like RPM? Which, by the way, no matter how good you say it is, it's still the wrong way to do it.
I think RedHat is getting a big head over this whole IPO thing. I don't really think them buying Cygnus is a GoodThing(tm) either. egcs has been incorporated into the FreeBSD source tree. RedHat's software has never been know to be even remotely portable. (Trust me. I've tried it) What will happen when RedHat starts "making changes" to the egcs code base? Are we going to end up with a compiler that only works with the Linux 2.3.78-ac256 kernel?
NSI has had that notice for the last month.
You Slashdot guys gotta read your e-mail more often. 2 late news stories in one day (see l0pht article).
And so is the 4.0-19990809-CURRENT iso image.
Is it really necessary to announce every kernel patch? It's not like Alan Cox isn't going to release 8 more next week. Like we really need to know that 2.2.11-ac12 is out...
I hope TwoFish gets it. Bruce Schneier makes women's knees weak. That, and it's a badass algorithm.
The biggest problem I see with this book is that there is no mention of writing portable code. Linux programs, in particular, lack in this area. #include <linux.h> just doesn't cut it when it comes to trying to run software across multiple platforms.
simple, use the X forwarding in ssh.
3w3 R an 3l33t hax0r. 3y3 ph33r 3w3 and j00r p0ss3.
unF
From http://www.super7.net/cpus/AMD/K7/ k7preview1.htm:
Multi-Processing
The K7's use of the EV6 protocol also opens a door for AMD into the world of multi-processor systems, an
area that Intel has had a lock on for the last several years. The EV6 implements point-to-point topology. This
means that if there are multiple processors within the system, each gets a dedicated connection to the
chipset. Intel based multi-processor systems must share a bus interconnected with the chipset. This is the
technology that Intel has refused to share licensing for an so has pushed x86 CPU manufacturers away from
developing multi-processor systems. This technology of Intel's is also limited to the use of only four
processors within a given system. AMD's development of the EV6 protocol for x86 processors opens
systems up to use as many as 16 processors provided the memory bus architecture can support it. Even
though each processor gets a dedicated connection to the chipset is must share a system bus from the
chipset to main memory. This will step up development of larger and faster memory types than current 64-bit
access SDRAM. You can be assured that AMD will be developing for a variety of new memory types like
RAMBUS, DRDRAM or DDR SDRAM.
How is this BS? They used a standard benchmark (SPECint, SPECfp) designed to test _different_ CPUs with the same benchmark.
If you run ZiffDavis benchmarks on a Sparc, it's gonna say that an Intel chip is faster, because the ZiffDavis benchmarks are written for Intel chips.
I seem to also remember that a month or so ago when QuakeIII came out, somehow TomsHardware had benchmarks for it, even though the 'timedemo' and 'timerefresh' commands were _broken_.
Here's the story on Blue's.
You sure you still want those benchmarks from Tom?
Yep it supports SMP. The cool thing about it is, it uses memory bank interleaving. The memory still runs at 100Mhz, but the CPU's skip between banks, essentially reducing the memory bottleneck of SMP machines.
Some of AMD's documents about the K7 went over this in detail, but it seems AMD took most of those docs down. Anyone have them?
Woo. And this is that "non-biased" article that everyone was whining for. Wow. They sure do get results around here.
I wonder what they would say if you said you were running BSD/OS, AIX, or SunOS. Perhaps they're just excluding the free OS's?
Either way, DSL has nothing to do with operating systems, since it's just a little router...
FreeBSD has a feature that allows you to have more filesystem than disk. It's actually pretty useful (argh, filled up / ).
Check the FreeBSD handbook entry for how to do it:
http://www.freebsd.org/FAQ/FAQ52.html#52