03-18-2011
Quote:
Originally Posted by
Chrisdot
After UEFI loads regular OS it becames useless.
And how do you propose to overcome this problem? Simply loading it in the kernel isn't enough to make it work. Once an OS loads, the environment's not right anymore.
Quote:
I think that "adding general-purpose UEFI support to Linux" is out of range.
Which is unfortunate since I think that's the only way you'd get linux to do what you want -- use UEFI devices exclusively so you don't have to use your own drivers and in doing so alter the machine's environment.
Quote:
Could you continue your tought? I have never heard about this.
DOS is an extremely simple operating system. It doesn't have or need device drivers for basic functionality and it doesn't modify the system environment much at all. It relies on BIOS calls(i.e. firmware code) almost exclusively instead.
The original IBM PC BIOS calls were rather limited in function though, so raw DOS doesn't get you anything
but disk+console+keyboard, and it's performance is poor compared to what real device drivers could do.
A DOS-like thing that fully utilized UEFI firmware capabilities could have much more features than DOS did. It wouldn't be anything like Linux but might be useful since you could still run many tools in it. You could check out LILO or GRUB to see how they use UEFI.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I just set up an ftp server with Red Hat 5.2. I am doing the work, I'm baby stepping, but it seems like every step I get stuck. Currently, I'm trying to set up a crontab job, but I'm getting the following message: /bin/sh: /usr/bin/vi: No such file or directory. I see that vi exists in /bin/vi,... (3 Replies)
Discussion started by: kwalter
3 Replies
2. Programming
Hi-
I need the cpp call that will tell me the full path to the app I'm running in. For example, I'm running in a loaded library for either mozilla or firefox, but would like to know the full path to the executable
/usr/bin/firefox
/usr/bin/mozilla
/usr/local/firefox1_5
etc...
(For... (4 Replies)
Discussion started by: erwinfletch
4 Replies
3. Linux
Hi all,
I am working on USB data monitoring on Fedora Core 9. Kernel 2.6.25 has a built-in module (the one that isn't loadable, but compiles and links statically with the kernel during compilation) to snoop USB data. It is in <kernel_source_code>/drivers/usb/mon/.
I need to know if I can... (0 Replies)
Discussion started by: anitemp
0 Replies
4. Shell Programming and Scripting
Okay, so I have two "Hello, world!" scripts, "test.pl" and "test.sh".
#!/bin/perl -w
use strict;
print "Hello, world!\n";
#!/bin/csh
echo Hello,\ world!
When I run test.pl, it runs instantly, always. When I run test.sh, it takes anywhere between 4 and 22 seconds!
I'd like to know what... (3 Replies)
Discussion started by: acheong87
3 Replies
5. UNIX for Dummies Questions & Answers
Hi,
I have a problem I don't understand with fuser.
I launch a simple shell script mysleep.sh:
I launch the command fuser -fu mysleep.sh but fuser doesn't return anything excepted:
mysleep:
Then I modify my script switching from #!/bin/sh to #!/bin/ksh
I launch the command fuser -fu... (4 Replies)
Discussion started by: Peuj
4 Replies
6. OS X (Apple)
Q1. I understand that /usr/local/bin means I can install/uninstall stuff in here and have any chance of messing up my original system files or effecting any other users. I created this directory myself.
But what about the directory I didn't create, namely /Users/m/bin? How is that directory... (1 Reply)
Discussion started by: michellepace
1 Replies
7. Programming
I have made an packet capture application running on intel machine, it is capturing packets with src address- 17.0.0.0 destination ip- 66.0.0.0, source port- 0, destination port- 0, and protocol- 0 what does these packets mean ?
The code written to interpreter captured bytes is given below.... (5 Replies)
Discussion started by: arunpushkar
5 Replies
8. Ubuntu
Is there any way to compile smbfs module in kernel 3.10 running Ubuntu 12.04 LTS. I did a 'make menuconfig' and it shows cifs. I found out online that smbfs is deprecated and replaced by cifs. I have an old system with kernel version 2.4 which only has smbfs (no cifs). Is it possible to compile... (1 Reply)
Discussion started by: Monil
1 Replies
9. AIX
Hi,
I am planning to install a version of Informatica on my AIX box. It requires a specific java build in pap6470_27sr2-20141101_01(SR2).
The current link for IBM 64-bit SDK for AIX®, JavaTM Technology Edition, Version 7 Release 1 has a more recent version in j7r164redist.7.1.0.75.bin.
Is... (4 Replies)
Discussion started by: meetpraveens
4 Replies
10. Shell Programming and Scripting
Some question about the usage of shell scripts:
1.) Are the commands of the base shell scripts a subset of bash commands?
2.) Assume I got a long, long script WITHOUT the first line.
How can I find out if the script was originally designed für "sh" or "bash"?
3.) How can I check a given... (3 Replies)
Discussion started by: pstein
3 Replies
dosif(4) Kernel Interfaces Manual dosif(4)
NAME
DOSIF - DOS interchange format
DESCRIPTION
The DOS Interchange Format (DOSIF) is the name given to the media format used by the DOS operating system. This format is based upon that
used in IBM PC and PC AT and HP Vectra systems.
Use the and commands to convert files between HP-UX and DOS file formats; see dos2ux(1). Use these utilities to retrieve information from
a DOSIF volume.
The dos*(1) utilities are the only HP-UX commands that can interact directly with the contents of a DOSIF volume. The only other way to
interact with the contents of a DOSIF volume is to use an HP-UX DOS emulation or coprocessor facility such as SoftPC or the DOS Coproces-
sor. The command cannot be used on a DOSIF volume because the operating system does not recognize it (see mount(1M)).
When constructing file names for the dos*(1) commands, start with the HP-UX path name of the DOSIF volume, then add a colon followed by the
file name:
or
This file naming convention is suitable for use only in arguments of the dos*(1) utilities. It does not constitute a legal path name for
any other use in HP-UX applications.
Metacharacters and can be used when specifying both HP-UX and DOS file names. These must be quoted when specifying a DOS file name,
because file name expansion is performed by the DOS utilities, not by the shell. The dos*(1) utilities expand file names as described in
regexp(5) in the section.
By convention, if the HP-UX device name and a trailing colon are specified, but no file or directory name is provided (for example, the
root of the DOS file system is assumed.
EXAMPLES
Example 1
Specify DOSIF file accessed through HP-UX special file
Example 2
Specify DOSIF file accessed through the DOS volume stored as HP-UX file
SEE ALSO
dos2ux(1).
dosif(4)