:Now we've gone and got forked, can someone please give us examples of cvsup
:files for those that want to follow 4-current and those that want to follow
:3-stable.
:
:Thanks!
It's real simple. The -stable is the 3.x branch. This is the branch
that Jordan just created tonight. So, fo
:
:Ah, excellent. If my tests of Luoqi's fix work, I'll commit it as
:part of my big VM commit to -4.x, and also commit this and a few
:other simple VM bug fixes to -3.x.
Oops, there is still something broken. I think getblk() needs to be
reorganized completely, there are s
Now we've gone and got forked, can someone please give us examples of cvsup
files for those that want to follow 4-current and those that want to follow
3-stable.
Thanks!
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
:>...
:> having to check for B_DELWRI in bread(), breadn(), and nfs_bioread()
:> by forcing getblk() to handle the B_DELWRI condition.
:>
:> Cool. I'll replace my nfs_bioread() patch with this one and test it
:> before committing all this stuff to the -4.x branch ( which I will al
> > > I'm not sure about anybody else here, but to my mind a "Winblows on C:
> > > drive and let's try out FreeBSD on the second disk" configuration should
> > > really be supported seamlessly.
> >
> > You're more than welcome to propose a technical solution that solves
> > the problem.
>
> OK,
On Wednesday, 20 January 1999 at 23:00:34 -0800, Matthew Dillon wrote:
>> Sorry, Matt, the patch in my previous email was fatally flawed. Try this one
>> below. The two printf() messages don't necessarily come out in pairs and
>> it's not just NFS bufs' B_CACHE bits are cleared, so my comment about
:Sorry, Matt, the patch in my previous email was fatally flawed. Try this one
:below. The two printf() messages don't necessarily come out in pairs and
:it's not just NFS bufs' B_CACHE bits are cleared, so my comment about
:vm_page_is_valid() check in my previous message was wrong and the check is
On Thursday, 21 January 1999 at 7:19:39 +0100, Andreas Klemm wrote:
> On Thu, Jan 21, 1999 at 12:09:00PM +1030, Greg Lehey wrote:
>> On Wednesday, 20 January 1999 at 19:33:54 +0100, Andreas Klemm wrote:
>>> On Tue, Jan 19, 1999 at 11:00:55PM -0800, Matthew Dillon wrote:
Hmm. Interes
On Thu, Jan 21, 1999 at 12:09:00PM +1030, Greg Lehey wrote:
> On Wednesday, 20 January 1999 at 19:33:54 +0100, Andreas Klemm wrote:
> > On Tue, Jan 19, 1999 at 11:00:55PM -0800, Matthew Dillon wrote:
> >>
> >> Hmm. Interesting, it's dying trying to fsync an FFS vnode. Are you
> >> by any
>Hang on a second... I think you might be putting words in my
> mouth... I'm not saying that the nfs boot floppy is the One True
> Boot Floppy. I see no reason why we can't have a netboot.flp and
> a dskboot.flp created.
The slicing that's being contemplated at the moment is actually
"install
>
> Do you have egcs or gcc-2.8 or anything else installaed that installs
> /usr/local/bin/g++?
>
yes, that's the one I really recently installed
I was suspecious about it, but now you confirmed it.
> Such extra compilers from ports tend to break. Make sure you use
> /usr/bin/g++.
>
Thanks
--
> I guess it depends on how fancy we want to get. Here are some examples
> that I've been rolling around; some are fanciful, some practical)
>
> dev_generic device (eg. dev_sio)
> bus_bus support (eg. bus_pci)
> netif_ network interface (eg. net
> On Wed, Jan 20, 1999 at 07:19:15PM -0800, David O'Brien wrote:
> [..]
> > etc? This is what the original poster suggested, and nobody has really
> > given a good response what is wrong with the "grouping" being expressed
> > in the modules' name. Mike Smith and Andrzej Bialecki have given good
hi,
Hang on a second... I think you might be putting words in my
mouth... I'm not saying that the nfs boot floppy is the One True
Boot Floppy. I see no reason why we can't have a netboot.flp and
a dskboot.flp created.
If you really want to make things easier for the beginner, why
not provi
[snips]
> As to whether a boot.flp from an earlier SNAP will "work just the same,"
> I don't know.
>
> Cheers,
> david
> --
> David Wolfskill UNIX System Administrator
> d...@whistle.com voice: (650) 577-7158 pager: (650) 371-4621
I used a 3.0-RELEASE boot.flp to loa
The new swapper and a bunch of VM stuff I've been sitting
on is going to be committed into the new -current tree tonight.
These changes also include the most recent NFS fix ( of two.. the
one prior to this one has already been committed ). This fix and
numerous other minor VM
On Wed, 20 Jan 1999, Mike Smith wrote:
> > I was just pointing out that having things in subdirectories
> > is better than having a zillion files piled into a single directory.
>
> I'm torn between agreeing that it's tidier and disagreeing on the
> grounds that it's much more of a pain to admini
On Wednesday, 20 January 1999 at 23:34:52 -0500, Mike Tancsa wrote:
> At 02:51 PM 1/21/99 +1030, Greg Lehey wrote:
>> On Wednesday, 20 January 1999 at 23:15:15 -0500, Mike Tancsa wrote:
>>>
>>> Am I the only one seeing this ?
>>
>> Yes, I think so.
>> I would guess that you cvsupped in the window b
At 02:51 PM 1/21/99 +1030, Greg Lehey wrote:
>On Wednesday, 20 January 1999 at 23:15:15 -0500, Mike Tancsa wrote:
>>
>> Am I the only one seeing this ?
>
>Yes, I think so.
>I would guess that you cvsupped in the window between 16:25:48 PST,
>when I committed the new Makefile, and 16:31:31 PST, when
On Wednesday, 20 January 1999 at 23:15:15 -0500, Mike Tancsa wrote:
>
> Am I the only one seeing this ?
Yes, I think so.
> Current as a few hrs ago...
>
> /usr/src/sys/modules/mfs/../../ufs/mfs/mfs_vfsops.c:68: warning:
> `mfs_rootsize' defined but not used
> /usr/src/sys/modules/vinum/../../dev
On Wed, Jan 20, 1999 at 07:19:15PM -0800, David O'Brien wrote:
[..]
> etc? This is what the original poster suggested, and nobody has really
> given a good response what is wrong with the "grouping" being expressed
> in the modules' name. Mike Smith and Andrzej Bialecki have given good
> reasons
Am I the only one seeing this ? Current as a few hrs ago...
/usr/src/sys/modules/mfs/../../ufs/mfs/mfs_vfsops.c:68: warning:
`mfs_rootsize' defined but not used
/usr/src/sys/modules/vinum/../../dev/vinum/vinum.c:324: warning:
initialization from incompatible pointer type
/usr/src/sys/modules/vin
Why not just follow the directory structure under /sys?
Afterall, we are talking about kernel stuff here.
On Wed, Jan 20, 1999 at 10:58:13AM -, p...@originative.co.uk wrote:
[..]
> I don't think subdirectories based on bus type is a good idea, it
> doesn't really fit the granularity we're p
>
>
> I recently used "make world" to update make system to ELF. The make world
> finished successfully everything appears to function correctly except when
> I try to recompile my kernel. make depend works but once I get to 'make'
> it will compile for a while then stop when it gets to db_aout.
I recently used "make world" to update make system to ELF. The make world
finished successfully everything appears to function correctly except when
I try to recompile my kernel. make depend works but once I get to 'make'
it will compile for a while then stop when it gets to db_aout.o and say
No
I've just committed a new version of Vinum with a large number of
changes. It works fine here, much better than the old version, but
there's just a possibility that things may go wrong. If you have
trouble, please let me know immediately.
One way you can shoot yourself in the foot: the `read' co
> Perhaps something more along the lines of:
>
> /modules<- empty, except for directories
> /console<- console related modules
> blank_saver.ko, daemon_saver.ko, fade_saver.ko, green_saver.ko,
Gross. What is wrong with:
saver_*.ko
device_*.ko
linu
> I'm wondering if an earlier boot.flp, say from the 1/6/99 SNAP, will
> work just the same? Thanks.
Normally, a boot.flp of about the same time will work fine. You just
need to go into the Options and change the release name string.
The 1/6/99 boot.flp is broken. /boot/* can't be found. This
I installed the 19990112 snap late last night with no problems using
the 2 disk install. Worked great. Its now been upgraded to current.
On Thu, 21 Jan 1999, Daniel O'Connor wrote:
> The boot.flp is broken..
> Try the 2 disk install (ie kern.flp and mfsroot.flp)
>
> They boot, but when I got s
> Hello all,
>
> I got a nagging question...
> Very often when trying to compile packages I find myself editing
> makefiles and having to add really obvious include paths like
> /usr/local/include or /usr/X11R6/include in order to get the
> package installed.
> Now I wonder, why doesn't the system
>If I hop on my soapbox, I'd really like to see a single floppy
> network install which supports nfs(which I also re-enable on the
> normal boot.flp since it fits on the 2.88M image).
The problem is that there are too many people standing on too many
different soapboxes. Each and every one o
Hello all,
I got a nagging question...
Very often when trying to compile packages I find myself editing
makefiles and having to add really obvious include paths like
/usr/local/include or /usr/X11R6/include in order to get the
package installed.
Now I wonder, why doesn't the system itself have the
Well, FWIW, I've been modifying my local 'make release' to produce
a 2.88M boot floppy, which I then use as the boot image when I burn a
CD of the SNAP. Works like a champ.
Thus, the isofs creation is a straight run of the code in
examples/worm and cdrecord:
sh /usr/share/examples/worm/ma
On 21-Jan-99 Matt Behrens wrote:
> From 19990112? I had no such problems on three different systems.
Hmm.. OK..
Maybe pilot error :)
---
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them
On Wed, Jan 20, 1999 at 03:36:14PM -0800, Mike Smith wrote:
> [KLD module file locations]
> > I was just pointing out that having things in subdirectories
> > is better than having a zillion files piled into a single directory.
> I'm torn between agreeing that it's tidier and disagreeing on the
>
All: Sorry the boot.flp has been broken for this long, but I've had
other distractions lately. I will make it work once more, somehow
or other, and just keep your eyes on current.freebsd.org over
the next few days. When it returns to 1.44MB in size again, give
it a try. :)
- Jordan
To Unsubscri
>Date: Wed, 20 Jan 1999 17:50:58 -0800 (PST)
>From: "Richard J. Dawes"
>The "boot.flp" in 3.0.0-19990112-SNAP/floppies is 2880K, which of course
>won't work. [I think this was acknowledged earlier by JKH, but has gone
>unfixed.] I'm wondering if an earlier boot.flp, say from the 1/6/99
>SNAP, w
On Wed, Jan 20, 1999 at 05:58:01PM +0100, Dag-Erling Smorgrav wrote:
> Mike Nguyen writes:
> > I noticed that NetBSD is switching over to using /etc/nsswitch.conf (like
> > Slowlaris, PH-UX, etc.). Would it be a good idea to do this for FreeBSD too
> > (when I first started using FreeBSD, it took
> Hello!
>
> The "boot.flp" in 3.0.0-19990112-SNAP/floppies is 2880K, which of course
> won't work. [I think this was acknowledged earlier by JKH, but has gone
> unfixed.] I'm wondering if an earlier boot.flp, say from the 1/6/99
> SNAP, will work just the same? Thanks.
Use the two-floppy inst
>From 19990112? I had no such problems on three different systems.
(System #3 had a lot of other unrelated problems, like a loose
ethernet cable and mislabelled jumpers on drives, but none of them
were 19990112-related.) :)
On Thu, 21 Jan 1999, Daniel O'Connor wrote:
: On 21-Jan-99 Richard J. D
On Wednesday, 20 January 1999 at 19:33:54 +0100, Andreas Klemm wrote:
> On Tue, Jan 19, 1999 at 11:00:55PM -0800, Matthew Dillon wrote:
>>
>> Hmm. Interesting, it's dying trying to fsync an FFS vnode. Are you
>> by any chance running NFS ( client *or* server ) on this box?
>
> No, no NFS
Mike Smith writes:
> > > A single directory holding module files.
> >
> > Blech :-)
>
> Put aside the aesthetics for a moment, and try to raise some real,
> practical objections. I'm continually battling my own temptation to
> make the whole module thing more complex, but if you've got really
On 21-Jan-99 Richard J. Dawes wrote:
> The "boot.flp" in 3.0.0-19990112-SNAP/floppies is 2880K, which of course
> won't work. [I think this was acknowledged earlier by JKH, but has gone
> unfixed.] I'm wondering if an earlier boot.flp, say from the 1/6/99
> SNAP, will work just the same? Th
Hello!
The "boot.flp" in 3.0.0-19990112-SNAP/floppies is 2880K, which of course
won't work. [I think this was acknowledged earlier by JKH, but has gone
unfixed.] I'm wondering if an earlier boot.flp, say from the 1/6/99
SNAP, will work just the same? Thanks.
--Rich
To Unsubscribe: send mai
I have been experimenting with moving a 2.2.6-RELEASE system to 3.0
(-current for now, but probably moving towards -stable). Not wanting
to totally trash my current system until I have the new one working,
I've been building 3.0 on a second disk [mounted as /3.0 on my 2.x
system].
I'm using CTM '
On Wed, 20 Jan 1999, Mike Smith wrote:
> > The option of putting the second drive
> > as slave on the primary interface would work, however anybody that knows
> > anything about IDE (read somebdy interested in trying FreeBSD) would put
> > it on the second interface for speed reasons.
>
> Er, you
At 03:46 PM 1/20/99 -0800, Mike Smith wrote:
>> >It looks like M_WAITOK will either return non-NULL or panic; it
>> >shouldn't be capable of returning NULL. Ideally, it shouldn't panic
>> >either (why is it only that M_WAITOK can panic, and M_NOWAIT can't?).
>>
>> Because failures for M_NOWAIT
>Bear with the ignorance a moment; how is a full map any different to no
>more kmem space?
I'd call them the same. The map is kmem_map for malloc(), and running
out of space in that map is fatal. When the map fills up, it is usually
not really full, it is just so fragmented that contiguous spac
On Wed, 20 Jan 1999, Archie Cobbs wrote:
> > > I like this idea (subdirectories) better.. it will last longer :-)
> >
> > It's a really bad idea, because it requires you to classify things. It
> > also makes it much harder to administer. In addition, classifications
> > are bad (witness the n
> >It looks like M_WAITOK will either return non-NULL or panic; it
> >shouldn't be capable of returning NULL. Ideally, it shouldn't panic
> >either (why is it only that M_WAITOK can panic, and M_NOWAIT can't?).
>
> Because failures for M_NOWAIT are normal (all pages may be in use,
> and the cal
>It looks like M_WAITOK will either return non-NULL or panic; it
>shouldn't be capable of returning NULL. Ideally, it shouldn't panic
>either (why is it only that M_WAITOK can panic, and M_NOWAIT can't?).
Because failures for M_NOWAIT are normal (all pages may be in use,
and the caller is not p
[KLD module file locations]
> I was just pointing out that having things in subdirectories
> is better than having a zillion files piled into a single directory.
I'm torn between agreeing that it's tidier and disagreeing on the
grounds that it's much more of a pain to administer. "Where is tha
> Would someone PLEASE tell us all if malloc can really return NULL now with
> flags & M_WAITOK? I've gotten contradictory answers...
I went back and looked at the code again.
It looks like M_WAITOK will either return non-NULL or panic; it
shouldn't be capable of returning NULL. Ideally, it sh
Would someone PLEASE tell us all if malloc can really return NULL now with
flags & M_WAITOK? I've gotten contradictory answers...
Brian Feldman_ __ ___ ___ ___
gr...@unixhelp.org _ __ ___ | _ ) __| \
http://www.fre
Hello!
What is new tag for -STABLE?
RELENG_3_1 ?
Rgdz,
Осокин Сергей aka oZZ,
o...@etrust.ru
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
>I noticed that NetBSD is switching over to using /etc/nsswitch.conf (like
>Slowlaris, PH-UX, etc.). Would it be a good idea to do this for FreeBSD too
>(when I first started using FreeBSD, it took me a long time to figure out the
>analogous file for hostname lookups was /etc/host.conf) -- it seem
Mike Smith writes:
> > > When I first started writing KLD, I had a vague notion that there would be
> > > a simple directory structure under /modules, e.g.:
> > >
> > > /modules
> > > pci/
> > > ncr.ko
> > > ...
> > >
> I'm not sure about anybody else here, but to my mind a "Winblows on C:
> drive and let's try out FreeBSD on the second disk" configuration should
> really be supported seamlessly.
You're more than welcome to propose a technical solution that solves
the problem.
> The option of putting the sec
(This is mainly for Luoqi, John, or David, or anyone who understands
struct buf's and NFS).
I see some other weirdness in bread() relating to NFS as well.
int
bread(struct vnode * vp, daddr_t blkno, int size, struct ucred * cred,
struct buf ** bpp)
{
struct buf *bp;
> > When I first started writing KLD, I had a vague notion that there would be
> > a simple directory structure under /modules, e.g.:
> >
> > /modules
> > pci/
> > ncr.ko
> > ...
> > isa/
> >
Try this. In nfs_bioread(), nfs/nfs_bio.c:
Before, it was:
if (getpages && !(bp->b_flags & B_VMIO)) {
#ifdef DIAGNOSTIC
printf("nfs_bioread: non vmio buf found, discarding\n");
Try changin the if() to this:
if (
:ok, here are some instructions which -- I hope -- reproduce it
:(I haven't found a *nice* way; this is the ridiculous way):
:
:NFS server and client are completely 3.0-CURRENT
:(of CTM src-cur.3712.gz) with Luoqi's NFS fix. The server has all
:(physical) file systems mounted with softupdates exce
> >
> > > Is "make clean" really necessary? A "make depend" ought to be
> > > sufficient, I would think.
> >
> > I think that's an attempt to protect people who've upgraded from STABLE
> > and haven't gotten used to ``config -r''?
>
> config -r? I'd be highly suprised if this was needed at all
On Tue, Jan 19, 1999 at 11:00:55PM -0800, Matthew Dillon wrote:
>
> Hmm. Interesting, it's dying trying to fsync an FFS vnode. Are you
> by any chance running NFS ( client *or* server ) on this box?
No, no NFS compiled in and am not using it. See my kernel config.
> First, if eith
I am experiencing two rather cosmetic issues with how the ISDN subsystem
starts up. The first is, that when you enable isdnd, syslogd is not yet
running. So isdnd outputs a whole lot of garbage (basically the whole
configuration) to the console.
This patch to /usr/src/usr.sbin/i4b/isdnd/log.c solv
Dag-Erling Smorgrav wrote:
>
> Mike Nguyen writes:
> > I noticed that NetBSD is switching over to using /etc/nsswitch.conf (like
> > Slowlaris, PH-UX, etc.). Would it be a good idea to do this for FreeBSD too
> > (when I first started using FreeBSD, it took me a long time to figure out
> > the
>
On Thu, 21 Jan 1999 01:03:21 +0800, Peter Wemm wrote:
> The first machine has been doing 'config -n' since 1996
Don't get me wrong, config _usually_ works for us without ``-r''. But we
got bitten once or twice and have since opted for ``config -r'', since
that's what fixed things for us when we
As p...@originative.co.uk wrote...
> > -Original Message-
> > From: Peter Jeremy [mailto:peter.jer...@auss2.alcatel.com.au]
> > Sent: Wednesday, January 20, 1999 6:21 AM
> > To: freebsd-current@FreeBSD.ORG
> > Subject: Re: Directory structure on current.freebsd.org
> >
> >
> > Oliver From
Sheldon Hearn wrote:
>
>
> On Thu, 21 Jan 1999 00:29:54 +0800, Peter Wemm wrote:
>
> > 'make depend' really does work, and is quite safe. Cleaning the tree
> > should be a very rare requirement.
>
> Perhaps the chap sitting next to me and I are just unlucky. Between the
> two of us, we've nee
Mike Nguyen writes:
> I noticed that NetBSD is switching over to using /etc/nsswitch.conf (like
> Slowlaris, PH-UX, etc.). Would it be a good idea to do this for FreeBSD too
> (when I first started using FreeBSD, it took me a long time to figure out the
> analogous file for hostname lookups was /e
Peter Wemm writes:
> config -r? I'd be highly suprised if this was needed at all for 99% of the
> time. The only time that I've been aware of it being needed was quite some
> time ago when there was an option that got removed - if people were using
> it, that option wouldn't get cleaned out fro
On Thu, 21 Jan 1999 00:29:54 +0800, Peter Wemm wrote:
> 'make depend' really does work, and is quite safe. Cleaning the tree
> should be a very rare requirement.
Perhaps the chap sitting next to me and I are just unlucky. Between the
two of us, we've needed to use ``config -r'' three times si
Sheldon Hearn wrote:
>
>
> On Wed, 20 Jan 1999 07:21:23 PST, John Polstra wrote:
>
> > Is "make clean" really necessary? A "make depend" ought to be
> > sufficient, I would think.
>
> I think that's an attempt to protect people who've upgraded from STABLE
> and haven't gotten used to ``config
On Wed, 20 Jan 1999 07:21:23 PST, John Polstra wrote:
> Is "make clean" really necessary? A "make depend" ought to be
> sufficient, I would think.
I think that's an attempt to protect people who've upgraded from STABLE
and haven't gotten used to ``config -r''?
Ciao,
Sheldon.
To Unsubscribe:
In article <199901191140.uaa23...@zodiac.mech.utsunomiya-u.ac.jp>,
Kazutaka YOKOTA wrote:
> I have committed another syscons update.
>
> Because one new file has been added to the source tree, and one file
> has changed location, I have to ask you to run config() before you
> compile the kernel
I noticed that NetBSD is switching over to using /etc/nsswitch.conf (like
Slowlaris, PH-UX, etc.). Would it be a good idea to do this for FreeBSD too
(when I first started using FreeBSD, it took me a long time to figure out the
analogous file for hostname lookups was /etc/host.conf) -- it seems
con
> The next option is configuring my master drive on the secondary interface
> as wd1 instead of wd2.
This works fine. I guess the real solution is to make the IDE disk scan
the same as we do for SCSI, which also happens to be the same as the
BIOS does. We possible need a config syntax like
contro
On Tue, Jan 19, 1999 at 11:00:55PM -0800, Matthew Dillon wrote:
[...]
> ::But there's still something wrong: When shutting down the server
> ::it still sometimes panics in vinvalbuf() complaining 'bout dirty
> ::pages. On the client side vi dies of SEGV (edited file and
> ::/var/tmp/vi.recover on n
Hi folks,
I'm finding turds in src/games/{advanture,hack,phantasia}/ and would
like to prevent buildworld from producing them.
Looks to me as though the turds are produced by a broken build-tools
rule in their Makefiles.
Anyone know wtf these games contribute to buildworld's bootstrapping?
:-)
From: Archie Cobbs
>Doug Rabson writes:
>> > Might it be a good idea to choose a consistent naming scheme for the
>> > modules? I'd think so because it would help blind loading at the boot
>> > prompt. If you choose names it the following format:
>> >
>> > type_name
>> > saver_warp
>> > saver_dae
> -Original Message-
> From: Archie Cobbs [mailto:arc...@whistle.com]
> Sent: Wednesday, January 20, 1999 6:13 AM
> To: d...@nlsystems.com
> Cc: gelde...@mediaport.org; curr...@freebsd.org
> Subject: Re: KLD naming
>
>
> Doug Rabson writes:
> > > Might it be a good idea to choose a consis
>
> FYI, when I rcp (actually, rsync) a certain makefile (ppp -alias), I
> get lots of these, and it never completes:
>
> Warning: CCP: deflink: Incorrect ResetAck (id 49, not 50) ignored
> Warning: CCP: deflink: Incorrect ResetAck (id 49, not 50) ignored
> Warning: CCP: deflink: Unexpected Reset
> -Original Message-
> From: Peter Jeremy [mailto:peter.jer...@auss2.alcatel.com.au]
> Sent: Wednesday, January 20, 1999 6:21 AM
> To: freebsd-current@FreeBSD.ORG
> Subject: Re: Directory structure on current.freebsd.org
>
>
> Oliver Fromme wrote:
> >In releases/snapshots they're called
David Green-Seed wrote:
> Here's my problem:
>
> at 10:21pm PST (Jan 19th 1998) I cvsupped world, rebuilt, installed the new
> boot blocks, and did a first-time install of an ELF kernel. Unfortunately,
> I'm
> dual-booting with windows 95 using fbsdboot.exe - which I just discovered
> does not
Here's my problem:
at 10:21pm PST (Jan 19th 1998) I cvsupped world, rebuilt, installed the new
boot blocks, and did a first-time install of an ELF kernel. Unfortunately,
I'm
dual-booting with windows 95 using fbsdboot.exe - which I just discovered
does not work with an ELF kernel.
Has anyone en
85 matches
Mail list logo
