Is Internet Explorer any less a part of Windows than the shell is a part of Unix? Where exactly do you draw the line? Discuss.
Does Unix require one type of shell over another? You could write init scripts that used csh, ksh, bash, tcsh, or something else entirely. You could use python interactively, or make emacs the default shell. There is no requirement of one over another fundamentally.
XSLT is not a procedural programming language. To quote the w3c, XSLT is a language for transforming XML documents into other XML documents. Sure, you might be able to use XSLT to generate HTML reports from the data generated by a query to a database storing XML, but you can't use XSLT alone to perform much other logic.
Daniel Robins' articles were very helpful for me to understand how XSLT ties in with other systems.
This is all great, but what about the simplest solution of all? CD-Rom Raid. Drives are cheap, use N and have them all read in parallel from N copies of the same disk. You could control this in software, and not even have to worry about building something exotic. If one file is being accessed on the disk array, then you get an Nx speedup. Up to N files could be accessed at once with no extra slowdown in access speed over a single drive. This would work for DVD drives too.
I challenge anyone to describe the plot of Akira in a way that is accessible to anyone. Come on folks, have you actually looked at the movie? It may be a great work of animation, but the story seems to be:
Kid rides around future city on motorcycle, gets mixed up with big, secret blob monster, girl gets absorbed by blob monster, scary stuffed animals, blob monster dies eventually, lots of gore and squish.
Perhaps this is some ancient Japanese folk legend that I don't know about?
Dual 12V battery pack with inverter could go in there too..
And there you have a nice, 40 pound laptop. I have a Compaq 'Portable' 286 that met your specs except for the batteries. Be sure that you use lead-acid. You wouldn't want to be too practical;)
Most ls implementations are ridiculously overengineered. Consider that it must be compatible with practically every other implementation of ls out there, so as not to break shell scripts written long ago. Thus, it contains a whole lot of legacy code that no one even wants to consider touching, for fear of hurting backwards compatability.
Perhaps it is just statically linked, so that if the libc is damaged, a core set of utilities still functions? This seems more likely than a lot of extra code. This is from my/usr/src/bin/ls directory:
1760 lines of code to provide all of the features that ls provides sounds about right.
Re:Slightly OT But..
on
30-pin SIMMs
·
· Score: 2, Funny
How do you run a computer in a freezer? Doesn't it get wet? Do you have to defrost it? Moreover, why do you run it in a freezer? Does it keep a grocery list? Does it run hot? Do you not have room? Does the freezer use it somehow? How does it get power?
If you didn't want anyone to ask, you shouldn't have mentioned it.
No, wait. The SMC doesn't have a 10Mbps WAN connection (but it's still great!) How about getting an old junker Linux box + 2 cheap 100Mbps cards, setup as a NAT box and use a 100Mbps switch in the inside. It would be a similar effect.
The SMC Barricade (SMC7004AWBR) has a 3 port, 100Mbps switch, an 802.11 access point, a print server that provides SMB and an lpr spool, can connect to an ethernet network or use an analog modem when you move off-campus. It's around $150.
I don't know of any C++ compiler that supports precompiled templates using the export keyword (I assume this is what you meant.) It is a difficult issue, I'm sure, but if you where to come up with a solution, the GCC developers would probably include it.
> POSIX.1 specifies sleep(3) be both thread-safe and cancellation-safe.
I don't think he's talking about sleep being thread-safe. I think he's talking about using sleep rather than a condition variable and a while loop to wait for access to a shared resource. The problem with using sleep is that it's entirely dependent on system load/ speed/ alignment of the moon. Code like that assumes that if it waits a certain amount of time, the resource will be free.
Imagine checking to see if a pool is dry, noticing that it is, coming back later and jumping in without looking. It might be full later, but it's much better to keep looking and not jump until the pool actually has water.
This type of thing is especially hard to debug when you upgrade your hardware and your software mysteriously fails. Suddenly, you're not sleeping long enough to get an exclusive lock on a shared resource.
I wonder if the US government is going to threaten a trade embargo with Taiwan until its government passes a DMCA-like law. But then again, could the US really afford such a trade ban with Taiwan? Almost everything is made there!
>If there's an update in one of the packages you
>use, you can publish that onto an ftp server,
>and then have the debian boxes patch themselves.
>Slackware can't do that, to the best of my
>knowledge. I used slackware intensively up to
>and including 7.1. It is a GREAT distrobution.
>Really. You're on your own, and if you fuck up
>it's usually you fucking up, not some
>inconsistent package management system. Use it
>if you want to learn Linux the hardcore way.
It seems to me that, if one needs to distribute software to many machines at once, there are easy ways to do it besides relying on a particular distribution's packaging tools. For instance, the unix labs at UT Austin use Debian, but most software (as far as I can tell) is actually stored on a central NFS server and run directly from that machine. It works great.
I administer several Slackware servers for our UT's student union. When I need to add a new piece of software or make an upgrade, I do it on a test server first (either compile a new package, or find it on Linuxmafia.) Once I ensure that it works, I run rsync on the other servers and viola!, they 'patch' themselves! Sometimes I have to run lilo if I upgrade the kernel on the other machines, but that's it.
>Zelda looks to be one of the first games
>to pit gamers in a convincing cartoon
>environment, complete with all the dazzling >
>animations, particle effects, and exaggerated
>look one would expect.
I don't think that the writer said it was _the_ first, just one of the first.
Cache? Pipeline? Branch prediction? Space to attach all of the wires for the busses? Designers sometimes waste space just to get all of the connections on there.
I don't know of any mac software that properly burns iso images. On another topic though, you should note that tomsrtbt is _not_ for burning onto CDs. It is meant to be copied onto a single floppy, from what I understand.
I'll agree. You should read the changelog and see if you're using any of the buggy modules in the first place before blindly upgrading. It looks like a bulk of the changes are in Win32 anyway.
It sounds like you have a service pack mindset, just applying patches without checking what they do. If a system is working and the features you use are not affected by a bug fix, why upgrade? Be a lazy, happy and smart sysadmin instead of a frantic, overworked and dumb one.
I can't attest that smoking causes yellow plastic - that is caused by natural degradation and ultraviolet light. However, if you're a non smoker, blowing the dust out of a smoker's computer can be quite a hazzard. I will usually take such a machine outside and blow it with an electric leaf blower, or I die in a coughing fit.
The dust particles seem stickier, but it's unclear whether this causes any more failures of mechanical components. Circuits are fairly resilient to dust, aside from added heat through insulation.
I've seen filthy mechanical parts, regardless of smoke, that I couldn't believe still worked. Printers are probably much more susceptible to smoking damage. Your best advice is to keep the ash tray off the CD tray and don't use your floppy as a cigarette holder.
Slashdot Mirror
From his webpage:
Co-Principal Inbestigator, COntext INtercharge (COIN) project
What's an inbestigator? This seems appropriate though:
Co-Director, PRoductivity From Information Technology (PROFIT) Program
Does Unix require one type of shell over another? You could write init scripts that used csh, ksh, bash, tcsh, or something else entirely. You could use python interactively, or make emacs the default shell. There is no requirement of one over another fundamentally.
XSLT is not a procedural programming language. To quote the w3c, XSLT is a language for transforming XML documents into other XML documents. Sure, you might be able to use XSLT to generate HTML reports from the data generated by a query to a database storing XML, but you can't use XSLT alone to perform much other logic.
/ li brary/us-gentoo/r works/usability/li brary/us-gent/o rks/usability/li brary/us-gentoo3/e rworks/usability/li brary/us-gentoo4/
Daniel Robins' articles were very helpful for me to understand how XSLT ties in with other systems.
http://www-106.ibm.com/developerworks/usability
http://www-106.ibm.com/develope
http://www-106.ibm.com/developerw
http://www-106.ibm.com/develop
This is all great, but what about the simplest solution of all? CD-Rom Raid. Drives are cheap, use N and have them all read in parallel from N copies of the same disk. You could control this in software, and not even have to worry about building something exotic. If one file is being accessed on the disk array, then you get an Nx speedup. Up to N files could be accessed at once with no extra slowdown in access speed over a single drive. This would work for DVD drives too.
The real trick is making copies of the disk!
Hey, that was pretty good. Thanks, I stand corrected.
I challenge anyone to describe the plot of Akira in a way that is accessible to anyone. Come on folks, have you actually looked at the movie? It may be a great work of animation, but the story seems to be:
Kid rides around future city on motorcycle, gets mixed up with big, secret blob monster, girl gets absorbed by blob monster, scary stuffed animals, blob monster dies eventually, lots of gore and squish.
Perhaps this is some ancient Japanese folk legend that I don't know about?
Dual 12V battery pack with inverter could go in there too..
;)
And there you have a nice, 40 pound laptop. I have a Compaq 'Portable' 286 that met your specs except for the batteries. Be sure that you use lead-acid. You wouldn't want to be too practical
Perhaps it is just statically linked, so that if the libc is damaged, a core set of utilities still functions? This seems more likely than a lot of extra code. This is from my /usr/src/bin/ls directory:
ozma:/usr/src/bin/ls$ wc *.c *.h
101 450 3116 cmp.c
751 2785 19142 ls.c
598 1881 13568 print.c
166 645 4587 util.c
62 409 2763 extern.h
82 518 3249 ls.h
1760 6688 46425 total
1760 lines of code to provide all of the features that ls provides sounds about right.
How do you run a computer in a freezer? Doesn't it get wet? Do you have to defrost it? Moreover, why do you run it in a freezer? Does it keep a grocery list? Does it run hot? Do you not have room? Does the freezer use it somehow? How does it get power?
If you didn't want anyone to ask, you shouldn't have mentioned it.
No, wait. The SMC doesn't have a 10Mbps WAN connection (but it's still great!) How about getting an old junker Linux box + 2 cheap 100Mbps cards, setup as a NAT box and use a 100Mbps switch in the inside. It would be a similar effect.
The SMC Barricade (SMC7004AWBR) has a 3 port, 100Mbps switch, an 802.11 access point, a print server that provides SMB and an lpr spool, can connect to an ethernet network or use an analog modem when you move off-campus. It's around $150.
Better yet, go here and make your own decision.
I don't know of any C++ compiler that supports precompiled templates using the export keyword (I assume this is what you meant.) It is a difficult issue, I'm sure, but if you where to come up with a solution, the GCC developers would probably include it.
> POSIX.1 specifies sleep(3) be both thread-safe and cancellation-safe.
I don't think he's talking about sleep being thread-safe. I think he's talking about using sleep rather than a condition variable and a while loop to wait for access to a shared resource. The problem with using sleep is that it's entirely dependent on system load/ speed/ alignment of the moon. Code like that assumes that if it waits a certain amount of time, the resource will be free.
Imagine checking to see if a pool is dry, noticing that it is, coming back later and jumping in without looking. It might be full later, but it's much better to keep looking and not jump until the pool actually has water.
This type of thing is especially hard to debug when you upgrade your hardware and your software mysteriously fails. Suddenly, you're not sleeping long enough to get an exclusive lock on a shared resource.
I wonder if the US government is going to threaten a trade embargo with Taiwan until its government passes a DMCA-like law. But then again, could the US really afford such a trade ban with Taiwan? Almost everything is made there!
>If there's an update in one of the packages you
>use, you can publish that onto an ftp server,
>and then have the debian boxes patch themselves.
>Slackware can't do that, to the best of my
>knowledge. I used slackware intensively up to
>and including 7.1. It is a GREAT distrobution.
>Really. You're on your own, and if you fuck up
>it's usually you fucking up, not some
>inconsistent package management system. Use it
>if you want to learn Linux the hardcore way.
It seems to me that, if one needs to distribute software to many machines at once, there are easy ways to do it besides relying on a particular distribution's packaging tools. For instance, the unix labs at UT Austin use Debian, but most software (as far as I can tell) is actually stored on a central NFS server and run directly from that machine. It works great.
I administer several Slackware servers for our UT's student union. When I need to add a new piece of software or make an upgrade, I do it on a test server first (either compile a new package, or find it on Linuxmafia.) Once I ensure that it works, I run rsync on the other servers and viola!, they 'patch' themselves! Sometimes I have to run lilo if I upgrade the kernel on the other machines, but that's it.
> this is MS trying to make money by selling a service.
To quote the article:
"We're not making money with these numbers. We want to make it as friction-free as possible to adopt this new platform."
So, who's making money? Could this be a bait-and-switch?
Try Dahle's CD-Rom shredder.
http://www.dahle.co.uk/product/new/20190.htm
>Zelda looks to be one of the first games
>to pit gamers in a convincing cartoon
>environment, complete with all the dazzling >
>animations, particle effects, and exaggerated
>look one would expect.
I don't think that the writer said it was _the_ first, just one of the first.
Cache? Pipeline? Branch prediction? Space to attach all of the wires for the busses? Designers sometimes waste space just to get all of the connections on there.
Wonderful advice. Thank you. 1024.
Don't you mean $10.28? That's 2^10 cents.
I don't know of any mac software that properly burns iso images. On another topic though, you should note that tomsrtbt is _not_ for burning onto CDs. It is meant to be copied onto a single floppy, from what I understand.
I'll agree. You should read the changelog and see if you're using any of the buggy modules in the first place before blindly upgrading. It looks like a bulk of the changes are in Win32 anyway.
It sounds like you have a service pack mindset, just applying patches without checking what they do. If a system is working and the features you use are not affected by a bug fix, why upgrade? Be a lazy, happy and smart sysadmin instead of a frantic, overworked and dumb one.
Tell me you weren't serious...
I can't attest that smoking causes yellow plastic - that is caused by natural degradation and ultraviolet light. However, if you're a non smoker, blowing the dust out of a smoker's computer can be quite a hazzard. I will usually take such a machine outside and blow it with an electric leaf blower, or I die in a coughing fit.
The dust particles seem stickier, but it's unclear whether this causes any more failures of mechanical components. Circuits are fairly resilient to dust, aside from added heat through insulation.
I've seen filthy mechanical parts, regardless of smoke, that I couldn't believe still worked. Printers are probably much more susceptible to smoking damage. Your best advice is to keep the ash tray off the CD tray and don't use your floppy as a cigarette holder.
Hey, silly. That 4:07 'clock' is just an icon for the xclock on the right, which reads 6:01, more or less.