From owner-freebsd-small Sat Jun 27 09:02:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA26157 for freebsd-small-outgoing; Sat, 27 Jun 1998 09:02:14 -0700 (PDT) (envelope-from owner-freebsd-small@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA26150 for ; Sat, 27 Jun 1998 09:02:06 -0700 (PDT) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with SMTP id SAA29302; Sat, 27 Jun 1998 18:04:15 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Sat, 27 Jun 1998 18:04:14 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Dinesh Nair cc: Mike Smith , freebsd-small@FreeBSD.ORG Subject: Re: Flashes and BIOS (was Re: I'm back.) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 27 Jun 1998, Dinesh Nair wrote: > > On Fri, 26 Jun 1998, Andrzej Bialecki wrote: > > > I have to display my total ignorance here: I'm not sure what happens to > > the interrupt vectors once FreeBSD is booted - are they stored somewhere? > > are they changed at all? I kind of vaguely remember them being located > > somewhere near the 0:0 right after the POST completes (in real mode, just > > i've written software - originally for win95 but works for any x86 OS > using the partition model - which allows a user to encrypt and lock a > harddrive. data and booting is disallowed unless a smartcard and the > proper password is inserted. > > implemented this by dicking around with int13 hook on bootup to insert a > hook into my routines so i could do on-the-fly encryption and decryption. > i've got the assembler code still with me. Yes, I know that much - what I wasn't sure about was what FreeBSD does to the interrupt vector table on loading... (for curious: it leaves it intact). Besides, once the kernel is running in protected mode, it's nontrivial to call real-mode BIOS routines. > > > {dial,net,isp}/{devfs,nodevfs} > > > > but this starts to be messy... Perhaps I'll come up with a feature-level > > configurator instead of defining separate types with their own > > it would, andrzej. suggest that i keep 2.2.6 non-devfs as it's not too > stable on this strain anyway. otoh, based on jordan's postings, we're > expecting the 2.2.x tree to be fully merged into the 3.0-RELEASE by end > of this year. would need to consolidate both our versions then. its > currently easy as the differences are not too great. Ok, that's fine. Andrzej Bialecki --------------------+--------------------------------------------------------- abial@nask.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } Research & Academic | "Be open-minded, but don't let your brains to fall out." Network in Poland | All of the above (and more) is just my personal opinion. --------------------+--------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message