Embedded systems may not have a full featured shell. So even relying on shell scripting won't help.
Embedded systems usually use busybox, which can support a full-featured shell (even bash specific extensions, optionally). Most of the embedded systems I've looked at include at least ash support, so if there's any need to do scripting, shell script is the obvious choice. Anything else is likely to require more system resources.
Actually, it's not legal to videotape/shoot photos inside of a McDonalds and the employees overreacted to this
I don't know about the law in France, but in the United States it is perfectly legal to photograph in any public place. That said, most citizens and law enforcement are ignorant of this fact, and people are routinely hassled for photography. Sometimes their photos are forcibly erased (which actually _is_ against the law). Places might have a "no photography" policy, and if they tell you to leave and you don't, then you are trespassing, but that is usually their only remedy under the law.
Besides, under normal circumstances this device does not save any information, and is not "videotaping" or "shooting photos". It's a bit like assaulting someone at a concert for wearing a hearing aid.
What about chain loading XP from the Canonical boot loader?
Secure Boot only looks at the first boot loader to see if it's certified. Whatever happens after that is anyone's guess.
--
BMO
It's not likely that the Canonical boot loader will allow chain loading XP. Any signed UEFI boot loader that boots an unsigned operating system will be doing so under threat of their own key being blacklisted.
Don't get me started if you need to get a machine in your datacenter with (*shudder* enterprise storage), you'd get more joy out of your year by crushing your balls under a hammer every day for a year.
Especially if you're the sort of person who likes that kind of thing.
Is this the last teenager still using AOL?
Yo man, are you the deadhead I'm thinking you're supposed to be?
My name is August West.
Good hello folks! It's wonderful to see we've made it onto Slashdot in-between releases again!
However, our website hardware is nearly toast, and is also co-located a long way away from where I live. It is an ancient VIA based system with a Celeron and 512MB of RAM. It also sports a Maxtor hard drive connected to a Promise Technology PCI IDE card, and LILO boots from a 3.5" floppy drive. Frankly, this wasn't really great hardware even when it was brand new, but it ran our site and mailing lists with excellent uptimes for over a decade in spite of that. It looks like the trouble could be a flaking Tulip based Ethernet card (getting DUP and dropped packets, and RX/TX errors). It was doing OK again after a reboot, but I'm having some trouble reaching it again for some reason.
We're looking for a new place to put the main site. Perhaps it could move to our other server, connie.slackware.com (in which case we need a PHP guru to port it to the latest version). There are other Slackware related servers that might be able to host us as well. To be honest, connie is also getting a little long in the tooth (that's a Pentium III with 256MB of RAM).
RIP bob.slackware.com, and long live Slackware!
To be an effective placebo, it has to be a believable placebo.
Thus, you have to dress it up with ritual or herbs or pins and needles or lots of water or whatever the method of convincing the patient that they're getting something that will help.
Actually, there was a study comparing a double-blind placebo with "here, take this sugar pill containing no active ingredients", and the placebo was just as effective even when the patient know it was a placebo.
Slackware is compiled for i486 and has been for a LOOOOOONG time.
Yes, but it was not until gcc started to output i486-specific opcodes whether you liked it or not. At that point, what the hell.
Do you have any idea how long it would take to just compile kernel on 386sx and 4MB of memory?
Seems to me that it was well under an hour. 386sx/16 with 4MB is the exact specs I used for my first year of Linux hacking, and I got along OK. My machine had one of the lowest recorded BogoMIPS ever (I think it was like 5).
Been meaning to boot that again... had it out to look last month. Maybe I should do a benchmark and report back.
Now, if he got it to run X, I might consider that a reasonable hack...but just running Linux...lame.
Most kids today can't write modelines.
An SX chip is merely a 386 without the floating point coprocessor.
Actually, the 386SX has a reduced data path width compared with the DX, but both could use an external 387 math coprocessor. It was not built in to any 386 CPU.
I had a 387 in my AMD 386DX-40 box... that was a great system. Pretty much stuck with AMD ever since, with a few exceptions.
On the other hand, this release includes essentially zero new features. Calling it a major release and incrementing the primary version number for what is essentially a security update is confusing to the point of making version numbers useless. This release doesn't even deserve a 4.1 IMO.
Call me crazy, but I thought they should have jumped right to Firefox 7.0.
The only truth here is that the article was written by a completely ignorant asshat.
This gives the impression that 2.6.40 is more than an incremental update. But 2.6.40 is an incremental update, so IMHO it should have stayed 2.6.40. Renaming it to 3.0 is just so random.
Try comparing the 2.0 kernel to the 3.0.0-rc1 kernel and then tell me again there's no justification for a major version bump.
Remember, UNIX spelled backwards is XINU. -- Mt.
