Slashdot Mirror
Blurring The Line Between BIOS And OS
Jon Kincade writes "The Register has an article about Phoenix Technologies cME software that allows users on anything from servers to embedded systems to run diagnostics, browse the web and other things without having to boot into a full fledged OS. The primary use seems to be recovery from system crashes. Also, this may explain why the Phoenix browser was asked to change its name a few months ago."
Command line browsing at it's best!
;-)
Look out ASCII porn here come the BIOSonly users of the world
Posting as directed.
Comment removed based on user account deletion
Phoenix Technologies is hoping PC manufacturers will latch on to its newest software to help solve PC problems and improve data security.
Phoenix, which creates BIOS software for many of the largest PC manufacturers, branched out this week with the new CME, or Core Managed Environment, software suite.
Where the BIOS (basic input/output system) provides a bridge between a PC's operating system and its hardware, CME will create protected areas on a PC's hard drive that can host sensitive data or applications that alleviate common problems, allowing the computers to run even if the operating system is damaged, the company said.
Phoenix, which will sell the software directly to PC makers for an undisclosed price, becomes the latest in a series of hardware and software makers trying to make PCs easier to use and more secure.
Intel, Transmeta, Via Technologies and Microsoft have recently launched new security initiatives. IBM has also been offering special data recovery software and a security chip in its new PCs. Collectively, the companies are seeking to better protect sensitive data, owned by companies or individuals, against thieves.
Although the security offers--including Intel's "LaGrande" technology, Transmeta's newest Crusoe processor and Via's Padlock--are built into chips or, in the case of Microsoft's Palladium project, into the operating system, Phoenix's CME will reside in a protected area on a PC's hard drive.
CME applications are intended to protect and recover PC users' data and to help the PC itself repair damaged software or connect to the Internet to download updates, the company said in a statement.
Phoenix will also offer versions of CME for embedded devices, such as industrial equipment, consumer electronics and servers.
Basic Input Output System
If you can do more advance operation through "BIOS", then the "BIOS" is no longer BASIC.
Therefore, it should no longer be called BIOS (Basic IOS)
Call it Embedded Operating System (EmbOS).
Just a thought!
Now that computers aren't coming with floppy drives, there better be something that users can do crash recovery from if the machines won't boot from cd....
Personally I'd like the choice of recovery cds/floppies.
A bit like the offerngs here?
[This Sig contains on viruses]
As usual, this just seems to be a case of stuff origionally designed for big expensive systems coming down to lower levels. IBM servers tend to have this functionality, hell on our F50 at work you can dial in using a modem when the AIX OS isnt running, the bios/firmware will take care of you. The AlphaPC164 i was jsut given suprised me by having a almost full unixlike OS as its firmware (SRM).
This has happened with SCSI, raid, SMP etc so it doesnt suprise me to find a BIOS that does more than normal, and in many cases it is a bonus, depending on wether it does certain things. I use serial consoles a lot, and would love to have a better way to talk to the computer at a really low level, without resorting to expensive hardware.
I agree.
The whole point of a "Basic Input/Output System" is for, well, basic I/O. It was meant to be a thin layer between the OS and the hardware.
While I agree that the technology can be improved upon, I don't think this is the proper direction to take.
I much prefer the route that Gigabyte has taken with their DualBIOS. If there is serious enough trouble with the OS, just boot to a CD with recovery tools on it. If there's a problem in the BIOS, you now have a spare. I don't see the necessity of a TCP/IP stack in the BIOS.
My $0.02.
-azmaveth
we used to buy the magazines, go to the stores and log on to the net to be eagerly greeted with hot new tech that made us want to immediately scrap the $10k worth of goodies we'd just bought the week before.
Now it seems that every day brings "innovations" that seem designed to further my intent to hang on to what I've got forever if I can manage it.
What's wrong with this picture?
KFG
When i am doing a fresh install of WIN2K and REDHAT on my comps (a once-in-6-months exercise) i make sure the machine is not even physically hooked up to the net untill i have a software firewall configured, up and running. I keep the firewall packages on CDs, along with config files, and ONLY AFTER these are setup, i go online to install other things, update drivers, etc (usually, only for win2k, not for redhat, which is trivial to bring back to my customized setup)...
;) ...
having TCP/IP built into the bios, with no firewalling support, and no possibility of frequent/safe upating, no easy way to check for "being" owned is a very bad idea. Also, Phoenix being a popular bios manufacturer, there will be a lot of worms targetting this bios tcp/ip stack.
I dont see a single genuine advantage of having all this crap in the BIOS anyway. I mean, if u hose ur drive, and need to go online for some critical information/software before u can bring ur comp back up, just keep a KNOPPIX cd handy. I personally think BIOS shud be thinning down even further, given none of the modern OSes really use most of the services, and the BIOS mostly just gets in their way. All the bios shud be capable of, is to bring up the OS, and then let the OS configure everything. It wud be so neat to have the OS kernel setup all the hardware, the powersaving policies, everything when it starts up. Of course, the best is to just have the OS kernel as the bios!! just throw this anachronism completely out. (yeah for ppl whos fav os is not linux, sumthing else might need to be worked out
Ghoul
Sigura Non Grata
HP/Compaq Servers and SUN have some similar things on their servers now. Although no web browser, and not technically BIOS. The Remote Insight Lights-out (RILo)boards provide great disaster recovery tools. Compaq An oldie but goodie is SUN Solaris PROM. Much more useful than BIOS.
I know people clammor for the good ole days of BIOS and CMOS, but now we just need to accept that these new products are going to be better.
what? what I thought we were in the trust tree in the nest, were we not?
I've always wondered why IEEE 1275 / OpenBIOS / OpenFirmware never caught on. IMO it is a much better and much more powerful alternative to the closed and aging BIOS found in most PC's. People are always complaining about "Closed" operating systems but don't bat an eye that their BIOS is closed...
Could this be the first version of a 'Auto-Updater' for future Palladium-enabled BIOSes?
"Evil will always triumph because good is dumb." -- Dark Helmet
What if they called it an OS on a chip?
Make it separate from the BIOS; but possibly on the same EEPROM chip; it will only load up if you hold down the F12 button (or something) when you boot.
Actually, newer Macs use OpenFirmware. I have it on both of my Macs, and they're both over two years old.
For a little bit of fun, hold down CMD+OPT+O+F at the boot chime. This will put you into the PROM, which is scriptable in Forth.
Given that board test and driver suites are written in OF, I don't see any reason at all why a web browser would be difficult. Text-only, perhaps -- but not terribly difficult.
There is also a project I noticed one day on Freshmeat that I think was called Retro Native Forth, for the IA32 arch. I wonder if that could be molded into an OF-like role on that platform?
unixkb.com -- articles on practical Unix issues.
I totally agree this is bad.
:-)
I understand Phoenix is trying to protect their business, but really, the days of the BIOS as it is should be over.
The BIOS is a legacy piece of crap that serves practically no purpose, but to boot the OS.
The services provided for the "Input/Output" go largely unused, mainly because the majority are 16 bit services and no modern OS has a way to call them in the first place (well, without a high latency). Even the 32 bit services go largely unused,- PCI for example is practically always implemented by a driver that does direct IO vs. calling the BIOS.
In other words, non of the most prominent operating systems call the BIOS for services such as RS-232, IDE, LPT, Video, you name it, after the apprioriate drivers are loaded.
The REAL purpose of the BIOS should be: initialize the hardware up to a point so that it can boot the OS. This means memory initialization, some timer and interrupt related stuff and whatever code is required for the boot devices (I personally think IDE and Ethernet are the most important, but I can see that USB and SCSI are important to a lot of people)
After that the BIOS should load the OS image and be done.
Don't think I'm making this thing up; I've actually implemented a boot loader that completely eliminated the need for a BIOS and it was very fast; ready to boot of the harddrive as soon as the harddrive was spin up (e.g. 3 seconds!)
LinuxBIOS is doing something similar.
Anyways, sorry for this little rant without any proper links or so, but I gotta go to be in time for Apres-Ski happy hour!
I am sorry, but this is absolutely true. The BIOS only exists as a concept on the PC. I like to give the Amiga OS as an example in this case.
(It was a single-user Multitasking, 32-bit OS, in late 80s to mid-90s. Last significant version was 3.1 in 1992 iirc, though 3.9 was released in 2001).
Let's take my A1200. What did it consist of? Well, it had the CPU, a custom chipset on the mainboard with DMA-accessible 2MB of RAM and an expansion slot. As you will see, there was hardware support for some things and then everything else was part of the OS:
Hardware-wise a number of protocols were supported, most importantly the mouse and AutoConfig. The mouse was simple. But AutoConfig was the plug'n'play of the 80s. (Introduced with Amiga3000 I think). It scanned the expansion bus (Think PCI bus). No, I should not say scan. It makes everything seem like windows scanning for hardware. It just sent a couple of signals on the bus and any devices that were there responded to acknowledge their presence, then the AutoConfig would ask them some stuff, like, if they had any ROM.
Now, what was interesting was that the A1200 itself had a (512k?) ROM, which contained basically the Kickstart and a large part of the OS (the kernel, disk operations and basic windowing system). The main part of the kickstart was the bootloader. Now, I don't see anything related to BIOS here. The sequence was basically
autoconfig->kickstart->kernel->?
Another interesting thing that hapenned around the same time that the kernel was loaded was what happenned to the ROMs that other devices that were connected on the bus declared. For example, my A1200 had a SCSI card addeed. The drivers for the OS were actually on a ROM on the SCSI card. When AutoConfig asked the card, it said it had a ROM. The same type of rom filesystem was used for the SCSI ROM and the Motherboard ROM. So, basically the ROM was looked at via the ROM filesystem and any libraries in there (the driver was just a shared library and shared device) were added to the system. Very simple.
So, I dunno if you would call AutoConfig a BIOS in itself. Or if you would call the ROM FileSystem part of a BIOS. In any case, the FileSystem concept was part of the OS, which used it to access all kinds of devices. The AutoConfig was an extremely simple protocol that could be done with a minimal amount of hardware. I think the specs are less than 20 pages in the Amiga Hardware Manual.
Anyway, all I see here is the hardware, some *standard protocols* that were implemented on the hardware itself, the bootloader and then the operating system itself.
BTW, Linux systems just ignore the BIOS completely, don't they?
I miss my rubber keyboard.(Homepage)