A Latvian and english Linux tiny operating system. used by golf & dvd lovers
You are not logged in.
Computer hardware is always thought to be identity that defines you. Possession is the identity, So, Microsoft and Intel thought that a boat anchor is the way to identify you as the owner of all the data transmission on the internet.
We started to rein in the data transmission by telephone company since 2005, By edgeQam transceivers on all paths, satellite and fiber optics by radio on glass?
Now, in WiFi traffic control, Your WiFi MAC address and ip address assignment by router identifies you and your data transmission. Thus, security is now based on trust, knowing who you are. MAC address is movable from computer to computer. But its like your credit card.
So, UEFI is too late and perhaps redundant in security provision, and not applicable on public computers.
WiFi cards are like credit cards, identity is easily traced. And you can have as many WiFi cards you can afford. MAC address is easily traced, whereas UEFI can not be traced.
Security provided by secrecy is not secure by trust. It is a fallacy for hackers to exist. If you violated trust, people will know not to trust you. History of your data transmission such as Nigerian letter can be traced by law enforcement.
Security by secrecy does not work and never secure for long. Changing MAC address is just buying a new WiFi card, history of data transfer is recorded by telephone companies(email address and name traceable)..
Obviously UEFI depends on ascii codes for the keycode to work.
We are now proposing pixel RGB transmission as data then character recognition to read ascii codes. Fax machines do pixel transmission unlike teletype machines and the invention of ascii codes.
Tablets today are moving data like fax machines(digital camera pictures). We have to change the way we design computers.
The fact that each person may have more than one computer, make MAC address more important to be taxed. In the old days, cableTV is sold to each household. And $100/mo was too expensive to bear.
The cost of wiring to every house on the street is a big investment sometimes never paid off.
Today, if wifi traffic control can be managed, each house hold will be sold wifi isp $10 per computer per month. And several people in each household will subscribe several computers each to hook up to internet for ipTV or cableTV.
This is the reason for cableTV to quickly adapt to wireless connection from the street, instead of wiring into each house.
UEFI is the puzzle for Linux distros. RedHat decided to pay Microsoft to use it. Ubuntu thought they could have their own UEFI.
The problem is that Win8 is RT OS. Neither RedHat or Ubuntu is RT OS.
RT OS works with packet switching to transfer data and command instruction to firmware of peripherals in the tablet.
So, the UEFI is a packet format that has its contents run USB firmware in the tablet. To use the UEFI, you basically have the Win8 operating system installed. Then your apps generate packets to function.
Hard RT OS is just defined number of data channels and devices run in time shared slots. RT OS can have random number of data channels or just one channel. Then devices are run sequentially.
Have fun. Android going with Linux kernels are going away from RT OS structure unless hal and dbus are used with posix packets convertible to UEFI format. Nothing fancy, but there are plenty of packet conversion done by packet programmers.
iBMPC uses bios and disk operating system. But now a days, the architecture of computer systems are changing. Operating systems are browser not disk operating system. So, UEFI boot manager instead of bios boot loader for disk operating system confuses all the open source developers.
UEFI starts with windows boot manager instead of grub which is on the disk drive partition zero sector. Windows boot manager is in the bios. When booting, bios will have a choice of windows boot manager firmware of another Linux boot manager in the bios. Bios now uses php to output verbose of boot manager name.
The way UEFI bios works has to also allow USB ambiguous device to boot with firmware and drivers in the bios. Such as USB cdrom or keys(flash memory not encryption)? Boot from USB Linux keys grub sector confirmed by php grub name in the browser operating system? USB keys can contain encryption to make computer more secure if website needs to registered or recognize your computer in video encryption in cookies. You recognized the video picture frome the big data website sent to you to tell you your computer is registered in the website server.
UEFI computers had to have bios manufacturer to write a special bios for the operating system(browser) and boot device drivers from USB bus.
Once new bios for UEFI architecture is understood, new phoenix bios had to be written for tablets or smartphones and hardware can be more secure. UEFI is not going away, it is going to be tried out on iBMPC desktops and laptops for security affirmation booting from USB keys that is not left in your computers.
You carry your own USB key, during booting will confirm Bank of America account and computer is booted. If Bank of America account is denied, then the computer stopped booting.
So, you now understand the difference of Uefi booting bios. Grub has to be in the bios not disk sector zero.
Otherwise you have to boot windows after you boot Uefi bios.
At this moment microsoft Uefi bios can boot windows and redhat rfel.
If you want to boot other operating system you need specially written Uefi bios for that operating system name in php language.
There is no mystery about Uefi bios not booting the correct name in php language match?