Michael Smith wrote:
> > One way to obtain this information is to write a program
> > that uses vm86() calls to read the first N sectors of a
> > BIOS disk, then read the same area using the protected mode
> > drivers. When you get a unique MD5 hash match between the
> > BIOS and the boot device,
> One way to obtain this information is to write a program
> that uses vm86() calls to read the first N sectors of a
> BIOS disk, then read the same area using the protected mode
> drivers. When you get a unique MD5 hash match between the
> BIOS and the boot device, you're there.
This won't work
Dmitry Konyshev wrote:
>Could anyone please tell me if there's any way to find out which
>device the system booted from in a user application. The loader
>sets loaddev and currdev vars, but I see no way to transfer them to
>the user environment.
Luigi Rizzo posted patches to commu
>Could anyone please tell me if there's any way to find out which
>device the system booted from in a user application. The loader
>sets loaddev and currdev vars, but I see no way to transfer them to
>the user environment.
kenv(8) allows you to read the kernel/loader environment.
On Mon, Apr 01, 2002 at 09:11:03PM +0400, Maxim Konovalov wrote:
...
> >Could anyone please tell me if there's any way to find out which
> >device the system booted from in a user application. The loader
...
> In recent -current we have sysctl machdep.guessed_bootdev.
recently merged to -
On 20:34+0400, Apr 1, 2002, Dmitry Konyshev wrote:
> Hello hackers,
>
>Could anyone please tell me if there's any way to find out which
>device the system booted from in a user application. The loader
>sets loaddev and currdev vars, but I see no way to transfer them to
>the user e
Hello hackers,
Could anyone please tell me if there's any way to find out which
device the system booted from in a user application. The loader
sets loaddev and currdev vars, but I see no way to transfer them to
the user environment.
--
Best regards,
Dmitry
7 matches
Mail list logo