This rapidly becomes obvious while using the browser. Opening the preferences editor is the pime example, click on one of the options in the tree panel and it may take a moment to render the forms on the pane. Resizing the window will cause the page to reflow just like the browser does, and if you watch a build that has a console turned on, you get:
WEBSHELL+= 5 WEBSHELL+= 6 ...
messages as the main UI window gets drawn, when dialogs show up, when you use the DOM and CSS to show/hide form input elements, etc.
After finding stuff like this using smartfilter I'm really not too concerned.
We searched on "sex" on a major search engine and started clicking down the list of hits. By hit #9, we were looking at"Amanda's Gallery," a page of explicit photos from "Amanda's Senior Year in High School" where she apparently spent a great deal of time with her clothes off. "Upskirts, freecam, sex diary" - all were allowed by SmartFilter.
Not to bad here, I can still get pr0n
To illustrate the problems that censorware manufacturers have, we went back to the Wiretap archive. This archive contains public domain text like George Washington's Farewell Address, Mark Twain's Tom Sawyer, and most of Shakespeare's tragedies - all of which were blocked in September. Now that it is unblocked, SmartFilter is happy to show us "how-to" instructions on having sex with a horse, making drugs, and even building an atomic bomb.
And I can even get high, fool around with a horse, then build a nuclear weapon when I'm done! After they deposit all that nuclear waste a Yucca Mountain I'll be ready to go!
Over here at Seattle University we've got a whole lot of crap for network access. First, we had two (or three) Class Bs that were given up so we could run NAT long, long ago.
Up until this week, our Internet connection was a pair of Frame relay links (barf) and we now have a pair of T1's for the staff/faculty, and a single T1 for the student dorms.
ALL of the dorms run on hubs (10bT, that's approximately 2000 students.
Earlier this year, Instant Messaging was banned in the name of "bandwidth consumption." Some of the staff noticed that nothing changed, so they turned it right back on.
Lately, several ports have started to become blocked, but I have been too busy to find out which (need to nmap an AOL server.) Likely canidates include:
UT
Q1
QW
Q2
Q3
Napster
MSN gaming zone
Battlenet
God knows what else
In short, I am very displeased with how the network is run at Seattle University. I like the CSSE program they have here, but this kind of crap REALLY starts to piss me off.
Up until last friday my average download speed was between 1.8K/s and 2.1K/s which is really very sad for a school of our size. That damn NAT box pisses me off the most. I would really like to have the opportunity to run a web server/mail server, but no dice.
The push-pin is a much better investment in computing power than a crusoe. For the price of the Crusoe you can buy several hundred push-pins which can be used to poke or stab your way into getting someone ELSE to buy you the Crusoe. Or two.
Bandwidth is only limited by the size of your pipe. Now we only have the little problem of encoding the stream and we're all set. Besides, the garden hose interface is already backwards compatible with almost 100% of existing installations, and even works with ancient peripherals. It can also be daisy-chained for near infinite lengths (if you have a good interface) and supports mid-hose taps to create a string of sprinklers.
Most importantly, when you attach your garden hose to a sprinkler you have a great way to keep yourself cool on those really hot days when your air conditioning goes out and you just can't stand the heat from your CPU a moment longer.
In FreeBSD all package/port supplied config files are stored in/usr/local/etc/*, and all auto-load scripts for a package/port are stored in/usr/local/etc/rc.d/*.
It is up to the user to update their config files when they update the port, which is the same way it works for updating the entire system from source (cd/usr/src && make buildworld && make installworld)
For updating world there is a handy utility called mergemaster that performs diffs between the install/etc and the/etc in the source tree, which makes the update very quick and easy.
I suppose the reasoning behind this was that if you are going to be upgrading your software, you should be smart enough to avoid blowing away your configuration files, and will be smart enough to adjust them appropriately. It'll probably be improved round about when the new package system is introduced (sometime in the future.)
The FreeBSD ports system is really easy to use. First you can look for a port you want to install. Say I want to install an irc client:
cd/usr/ports && make search key="irc" | more
This will give me a list of all different ports/packages that contain "irc" in the name. I see bitchx, so I type "cd irc/bitchx" then "make install clean" (I clean to remove all of the object files I don't need.) This will install any dependencies that I may need to run BitchX as well. There are a few "meta-ports" such as KDE or apache13-php4 that will automatically install and configure several ports that you would normally have to combine by hand.
After a few months I may want to update my bitchx port, so I install cvsup ("cd/usr/ports/net/cvsup-bin && make install clean"), cvsup my ports tree (check the FreeBSD handbook, or edit/usr/share/examples/cvsup/ports-supfile and "cvsup/usr/share/examples/cvsup/ports-supfile") to get the all new ports tree.
Now that I have this nice new ports tree I will need to see if the version of bitchx has been upgraded. I can use the pkg_version utility (in 4.0-CURRENT, not sure about earlier versions, I think it was a port) and type "pkg_version | grep \<" to get a list of all my packages that are out of date.
I notice that bitchx happens to be out of date, so I pkg_delete the old bitchx and "cd/usr/ports/irc/bitchx && make install clean" to get the new version.
The ports system even handles multiple versions of FreeBSD. Some packages may only run under the 3.x and earlier branches, but haven't been properly fixed and patches for 4.0-current, so they will be marked as broken in -current in the makefile, and will be uncompilable for users of current unless they want to fix the port.
If you need to reinstall a port that is the same version as the current port version, make && make deinstall && make reinstall will do the job.
Looking into the future, The FreeBSD Project is hoping to replace the current ports architecture and replace it with something even better. Shorter term solution may include changing the current directory structure and flattening it down to a category directory with a Makefile that will fetch the necessary directories it needs when you type make <portname> to save on download and install time.
It is nice to see the BSDs getting the respect and press they have deserved for so long.
<RANT>What I am curious about is how Slashdot seems to secret away BSD articles in the BSD section that have equal merit as any Linux article that graces the main page. For example, the previous BSD-only articles announced 4.0-RC. At the same time, RedHat 6.2-beta was announced (within a day or so) and it graced the main page. Why wasn't 4.0-RC put up on the main page?
If Slashdot is "news for nerds" and "stuff that matters" shouldn't that news be weighted equally? Perhaps a "Linux" section is needed for articles about Linux that don't need to grace the main page. Maybe I should just ignore Slashdot and go read DDN instead. Ok, enough</RANT>
Just daisy chain with bridging (they have should have bridging in Linux, its OPTIONS BRIDGE in FreeBSD) and all you do is go in to one, out to the next. Just like running a three player quake game with two serial ports. (back in the day)
Of course this does require two 1Gbit NICs for all but the end machines...
I've been running -current for quite some time now, and I haven't had any kernel panics for quite some time. Reading the lists no other people have had any major problems either. This stability feels very...odd for something that is SUPPOSED to crash every now and again.
Seen several months ago in Popular Science
on
NASA Gets Smart
·
· Score: 1
I think...
The article mentioned use of an inflatable module to replace the Russian module if it was not available. The module's design allows it to be lightweight and easily transportable, you just put it in orbit and fill it with air.
Other uses of the module's design would be on a Mars or Moon mission for a temporary residence.
One part of the article I don't agree with was that you need graphs and chart wiz-bangs to figure out what your system is doing.
I was writing a PHP3 script on my machine and I accidentally created an infinite loop. Not realizing this I hit the refresh button on netscape and after a few seconds I heard the disk start spinning. The page should have been up by now, so I switched to a text console and typed top, apache had gobled up about 110M of memory.
I find that top displays information in a much easier to read format than NT4's task viewer. Other tools such as vmstat give quick access to any information I want. I've played with NT4's system monitor (??) that displays graph and other histories of various stats and find it more difficult to configure than poking through a man page for which cryptic letter combination from vmstat will tell me how many page faults I've had.
Rah! Rah! Go DeCSS! Rah! Rah! Go DeCSS! Rah! Rah! Go DeCSS! We'll kick your ass! You know we can, And if we don't Your DVDs we'll can.
-- Attempting to make up for a precieved lack of content... This slashdot article seems utterly pointless. More like a raise the masses and create flame wars and DARN to HECK all of the people who won't allow you to play your DVD on your non-windows alternative system of choice which just so happens to be ever so superior to the EXCREMENT that flows forth from the EVIL lair of Microsoft.
I want the laser that draws straight on the retina. These displays will be even better than the LCD head mount, all you will see is a thin wire that runs out just above the eye. They could be worn as a visor, or in a pair of glasses as well, and nobody would be able to tell that you were using any type of VDU other than the wire running down the side of your neck.
Monitors can be turned into handy solar ovens. Carefully remove the front glass plate, being careful not to destroy the rest of the glass inside. Line with tinfoil and place in front of the fire. Instant oven.
Cat5 can be used for tripwires to discourage those pesky looters, or in longer lengths to build a cable bridge across those deep mountain gorges.
Stacked computer cases can be used to create walls and barricades. By plugging the ventilation holes the dead air space can be put to good use as insulation. A few large office buildings should contain enough to build a comfortable dwelling.
Computer power cords can make excellent weapons by using the three-prong end as a mace or whip. Especially useful are power strips with a convenient handle and cord attached. Mice also fall into this category.
CDs can make mirrors, frisbee of death, or can be broken in half and used as a slashing tool. Whole they will also function as primitive shovels. Breakage will not be too big of a problem, especially with the vast stockpiles of AOL and other ISP CDs.
Floppy disks can be ripped apart and the inside cloth covering can be used for fire starting material. Making "disk bombs" will also effectively start fires. Save the tiny springs inside, you never know when they will be useful in bandit-discouraging traps.
They reported that the superbug strains proliferated when exposed to radioactive waste mixtures commonly found at weapons sites. The superbug does not neutralize radioactivity in metals.
What the bug probably does is takes the radioactive elements and removes them from the other toxic elements. If you had a compound of (I'm no chemist here) mercury, cadmium and uranium, the bug would break it down into a uranium compound, a mercury compound and a cadmium compound. This will allow you to easily process and dispose of all three without having to separate them by other means.
Think about processing some huge lump of data, or writing code. Its easier to break the problem up into small, easy to process pieces and work your way through rather than writing everything into the main() function. It is easier to process uranium that it is to process uranium, cadmium, and mercury all mixed into one compound.
IIRC, the problem with radioactivity and living tissue is that the radiation breaks down the weak hydrogen links in the DNA (I read all this long ago, sorry for mistakes) and the DNA reforms itself into arrangements that don't allow the cell to function properly, killing it, or mutates it in such a way that its offspring don't function properly, killing them, or cause a malfunction like cancer.
Previous studies have demonstrated that its radiation resistance probably involves thousands of genes. Even when hundreds of portions of DNA are damaged by radiation, the microorganism can usually repair itself in a matter of hours, using redundant genetic codes to keep (hmm, article trimmed, not my fault)
This is the coolest part about the bacteria, it prevents the malfunctioning that plague other organisms, like humans. Sign me up for gene therapy like this!!
Now I can prove that there are ETs in the senate scene. And I'll be able to look for all of the other add-ins. I wonder if there are anything like the backwards bounty hunters. An excellent movie to watch in slow motion during those large crowd scenes.
The brightness will also be from Santa giving his test run about the sky. He'll probably be going about in his excercise clothes, shorts and tank-top. Due to the cold at the north pole, Santa will be white as a ghost, and make an excellent reflective surface to add the extra bit of brightness.
4.0-current is starting to look real cool. For the inside scoop, you should check out the -current mailing list archives at FreeBSD.org, but here are a few things:
The new sysinstall will have the CAPABILITY to support X installs. The talk on -current is all for having a fancy dancy configurator, but they don't want to leave the possiblity out. (The sysinstall that exists now is utterly horrible for changing, but it does a whole lot of stuff)
The ata driver is nearing completion and will replace the old wd driver. This means UDMA-66 support and other goodies.
Sound is being wrapped up into a new pcm driver, with support for most PCI sound cards, and work on the mmap support is improving.
A lot of drivers are being turned into KLDs, I'm able to load and unload nfs, msdos, vesa, various ethernet cards, USB (doesn't work too well yet), netgraph, cd9660, yadda yadda yadda.
I also here talk of after 4.0 FreeBSD will get a new ports/packages system. The ports tree is the best part of FreeBSD: cd/usr/ports/type/port && make install clean makes installing software hassle free. I don't know how it could get BETTER but that's what they're saying.
The Pentium III processor sets a new baseline for high-performance business desktop computing, and is also available for entry-level workstations and servers. And now, the new mobile Pentium III processor enables greater productivity on the go, at speeds of up to 500 MHz.
Right here, straight from the source. 500MHz is the max that a PIII will do. The rest must be overclocked. I hope that those of you who bought >500MHz chips don't melt 'em.
Optional on-chip 256Kb cache running at full speed
SSE instructions
CPUID
I don't have any pictures of the P2 vs. PIII dies, but I'm certain they are NOT the same. There are enough changes, minute though they may be, to consider P2 and P3 different lines.
Slashdot Mirror
This rapidly becomes obvious while using the browser. Opening the preferences editor is the pime example, click on one of the options in the tree panel and it may take a moment to render the forms on the pane. Resizing the window will cause the page to reflow just like the browser does, and if you watch a build that has a console turned on, you get:
...
WEBSHELL+= 5
WEBSHELL+= 6
messages as the main UI window gets drawn, when dialogs show up, when you use the DOM and CSS to show/hide form input elements, etc.
He's probably refering to an area West of Seattle, i.e. Redmond...(Or the home of BG himself.)
We searched on "sex" on a major search engine and started clicking down the list of hits. By hit #9, we were looking at"Amanda's Gallery," a page of explicit photos from "Amanda's Senior Year in High School" where she apparently spent a great deal of time with her clothes off. "Upskirts, freecam, sex diary" - all were allowed by SmartFilter.
Not to bad here, I can still get pr0n
To illustrate the problems that censorware manufacturers have, we went back to the Wiretap archive. This archive contains public domain text like George Washington's Farewell Address, Mark Twain's Tom Sawyer, and most of Shakespeare's tragedies - all of which were blocked in September. Now that it is unblocked, SmartFilter is happy to show us "how-to" instructions on having sex with a horse, making drugs, and even building an atomic bomb.
And I can even get high, fool around with a horse, then build a nuclear weapon when I'm done! After they deposit all that nuclear waste a Yucca Mountain I'll be ready to go!
SUSE - Geeko Mozilla's layout engine: Gecko Hmm...
Over here at Seattle University we've got a whole lot of crap for network access. First, we had two (or three) Class Bs that were given up so we could run NAT long, long ago.
Up until this week, our Internet connection was a pair of Frame relay links (barf) and we now have a pair of T1's for the staff/faculty, and a single T1 for the student dorms.
ALL of the dorms run on hubs (10bT, that's approximately 2000 students.
Earlier this year, Instant Messaging was banned in the name of "bandwidth consumption." Some of the staff noticed that nothing changed, so they turned it right back on.
Lately, several ports have started to become blocked, but I have been too busy to find out which (need to nmap an AOL server.) Likely canidates include:
In short, I am very displeased with how the network is run at Seattle University. I like the CSSE program they have here, but this kind of crap REALLY starts to piss me off.
Up until last friday my average download speed was between 1.8K/s and 2.1K/s which is really very sad for a school of our size. That damn NAT box pisses me off the most. I would really like to have the opportunity to run a web server/mail server, but no dice.
The push-pin is a much better investment in computing power than a crusoe. For the price of the Crusoe you can buy several hundred push-pins which can be used to poke or stab your way into getting someone ELSE to buy you the Crusoe. Or two.
Bandwidth is only limited by the size of your pipe. Now we only have the little problem of encoding the stream and we're all set. Besides, the garden hose interface is already backwards compatible with almost 100% of existing installations, and even works with ancient peripherals. It can also be daisy-chained for near infinite lengths (if you have a good interface) and supports mid-hose taps to create a string of sprinklers.
Most importantly, when you attach your garden hose to a sprinkler you have a great way to keep yourself cool on those really hot days when your air conditioning goes out and you just can't stand the heat from your CPU a moment longer.
In FreeBSD all package/port supplied config files are stored in /usr/local/etc/*, and all auto-load scripts for a package/port are stored in /usr/local/etc/rc.d/*.
It is up to the user to update their config files when they update the port, which is the same way it works for updating the entire system from source (cd /usr/src && make buildworld && make installworld)
For updating world there is a handy utility called mergemaster that performs diffs between the install /etc and the /etc in the source tree, which makes the update very quick and easy.
I suppose the reasoning behind this was that if you are going to be upgrading your software, you should be smart enough to avoid blowing away your configuration files, and will be smart enough to adjust them appropriately. It'll probably be improved round about when the new package system is introduced (sometime in the future.)
The FreeBSD ports system is really easy to use. First you can look for a port you want to install. Say I want to install an irc client:
cd /usr/ports && make search key="irc" | more
This will give me a list of all different ports/packages that contain "irc" in the name. I see bitchx, so I type "cd irc/bitchx" then "make install clean" (I clean to remove all of the object files I don't need.) This will install any dependencies that I may need to run BitchX as well. There are a few "meta-ports" such as KDE or apache13-php4 that will automatically install and configure several ports that you would normally have to combine by hand.
After a few months I may want to update my bitchx port, so I install cvsup ("cd /usr/ports/net/cvsup-bin && make install clean"), cvsup my ports tree (check the FreeBSD handbook, or edit /usr/share/examples/cvsup/ports-supfile and "cvsup /usr/share/examples/cvsup/ports-supfile") to get the all new ports tree.
Now that I have this nice new ports tree I will need to see if the version of bitchx has been upgraded. I can use the pkg_version utility (in 4.0-CURRENT, not sure about earlier versions, I think it was a port) and type "pkg_version | grep \<" to get a list of all my packages that are out of date.
I notice that bitchx happens to be out of date, so I pkg_delete the old bitchx and "cd /usr/ports/irc/bitchx && make install clean" to get the new version.
The ports system even handles multiple versions of FreeBSD. Some packages may only run under the 3.x and earlier branches, but haven't been properly fixed and patches for 4.0-current, so they will be marked as broken in -current in the makefile, and will be uncompilable for users of current unless they want to fix the port.
If you need to reinstall a port that is the same version as the current port version, make && make deinstall && make reinstall will do the job.
Looking into the future, The FreeBSD Project is hoping to replace the current ports architecture and replace it with something even better. Shorter term solution may include changing the current directory structure and flattening it down to a category directory with a Makefile that will fetch the necessary directories it needs when you type make <portname> to save on download and install time.
It is nice to see the BSDs getting the respect and press they have deserved for so long.
<RANT>What I am curious about is how Slashdot seems to secret away BSD articles in the BSD section that have equal merit as any Linux article that graces the main page. For example, the previous BSD-only articles announced 4.0-RC. At the same time, RedHat 6.2-beta was announced (within a day or so) and it graced the main page. Why wasn't 4.0-RC put up on the main page?
If Slashdot is "news for nerds" and "stuff that matters" shouldn't that news be weighted equally? Perhaps a "Linux" section is needed for articles about Linux that don't need to grace the main page. Maybe I should just ignore Slashdot and go read DDN instead. Ok, enough</RANT>
You actually turn your machine off?
Scratches head Why? http://www.uptimes.net
Just daisy chain with bridging (they have should have bridging in Linux, its OPTIONS BRIDGE in FreeBSD) and all you do is go in to one, out to the next. Just like running a three player quake game with two serial ports. (back in the day)
Of course this does require two 1Gbit NICs for all but the end machines...
Grr. RH 6.2-beta is no more important than 4.0-beta. What gives?
I've been running -current for quite some time now, and I haven't had any kernel panics for quite some time. Reading the lists no other people have had any major problems either. This stability feels very...odd for something that is SUPPOSED to crash every now and again.
I think...
The article mentioned use of an inflatable module to replace the Russian module if it was not available. The module's design allows it to be lightweight and easily transportable, you just put it in orbit and fill it with air.
Other uses of the module's design would be on a Mars or Moon mission for a temporary residence.
One part of the article I don't agree with was that you need graphs and chart wiz-bangs to figure out what your system is doing.
I was writing a PHP3 script on my machine and I accidentally created an infinite loop. Not realizing this I hit the refresh button on netscape and after a few seconds I heard the disk start spinning. The page should have been up by now, so I switched to a text console and typed top, apache had gobled up about 110M of memory.
I find that top displays information in a much easier to read format than NT4's task viewer. Other tools such as vmstat give quick access to any information I want. I've played with NT4's system monitor (??) that displays graph and other histories of various stats and find it more difficult to configure than poking through a man page for which cryptic letter combination from vmstat will tell me how many page faults I've had.
Rah! Rah! Go DeCSS!
Rah! Rah! Go DeCSS!
Rah! Rah! Go DeCSS!
We'll kick your ass!
You know we can,
And if we don't
Your DVDs we'll can.
--
Attempting to make up for a precieved lack of content... This slashdot article seems utterly pointless. More like a raise the masses and create flame wars and DARN to HECK all of the people who won't allow you to play your DVD on your non-windows alternative system of choice which just so happens to be ever so superior to the EXCREMENT that flows forth from the EVIL lair of Microsoft.
I want the laser that draws straight on the retina. These displays will be even better than the LCD head mount, all you will see is a thin wire that runs out just above the eye. They could be worn as a visor, or in a pair of glasses as well, and nobody would be able to tell that you were using any type of VDU other than the wire running down the side of your neck.
They reported that the superbug strains proliferated when exposed to radioactive waste mixtures commonly found at weapons sites. The superbug does not neutralize radioactivity in metals.
What the bug probably does is takes the radioactive elements and removes them from the other toxic elements. If you had a compound of (I'm no chemist here) mercury, cadmium and uranium, the bug would break it down into a uranium compound, a mercury compound and a cadmium compound. This will allow you to easily process and dispose of all three without having to separate them by other means.
Think about processing some huge lump of data, or writing code. Its easier to break the problem up into small, easy to process pieces and work your way through rather than writing everything into the main() function. It is easier to process uranium that it is to process uranium, cadmium, and mercury all mixed into one compound.
IIRC, the problem with radioactivity and living tissue is that the radiation breaks down the weak hydrogen links in the DNA (I read all this long ago, sorry for mistakes) and the DNA reforms itself into arrangements that don't allow the cell to function properly, killing it, or mutates it in such a way that its offspring don't function properly, killing them, or cause a malfunction like cancer.
Previous studies have demonstrated that its radiation resistance probably involves thousands of genes. Even when hundreds of portions of DNA are damaged by radiation, the microorganism can usually repair itself in a matter of hours, using redundant genetic codes to keep (hmm, article trimmed, not my fault)
This is the coolest part about the bacteria, it prevents the malfunctioning that plague other organisms, like humans. Sign me up for gene therapy like this!!
Now I can prove that there are ETs in the senate scene. And I'll be able to look for all of the other add-ins. I wonder if there are anything like the backwards bounty hunters. An excellent movie to watch in slow motion during those large crowd scenes.
The brightness will also be from Santa giving his test run about the sky. He'll probably be going about in his excercise clothes, shorts and tank-top. Due to the cold at the north pole, Santa will be white as a ghost, and make an excellent reflective surface to add the extra bit of brightness.
4.0-current is starting to look real cool. For the inside scoop, you should check out the -current mailing list archives at FreeBSD.org, but here are a few things:
The new sysinstall will have the CAPABILITY to support X installs. The talk on -current is all for having a fancy dancy configurator, but they don't want to leave the possiblity out. (The sysinstall that exists now is utterly horrible for changing, but it does a whole lot of stuff)
The ata driver is nearing completion and will replace the old wd driver. This means UDMA-66 support and other goodies.
Sound is being wrapped up into a new pcm driver, with support for most PCI sound cards, and work on the mmap support is improving.
A lot of drivers are being turned into KLDs, I'm able to load and unload nfs, msdos, vesa, various ethernet cards, USB (doesn't work too well yet), netgraph, cd9660, yadda yadda yadda.
I also here talk of after 4.0 FreeBSD will get a new ports/packages system. The ports tree is the best part of FreeBSD: cd /usr/ports/type/port && make install clean makes installing software hassle free. I don't know how it could get BETTER but that's what they're saying.
Intel(R) Pentium(R) III processor- Advanced Processor Technology for Powerful DesktopPC
The Pentium III processor sets a new baseline for high-performance business desktop computing, and is also available for entry-level workstations and servers. And now, the new mobile Pentium III processor enables greater productivity on the go, at speeds of up to 500 MHz.
Right here, straight from the source. 500MHz is the max that a PIII will do. The rest must be overclocked. I hope that those of you who bought >500MHz chips don't melt 'em.
Changes from P2 to PIII:
I don't have any pictures of the P2 vs. PIII dies, but I'm certain they are NOT the same. There are enough changes, minute though they may be, to consider P2 and P3 different lines.