Re: make release produces unbootable boot floppies, no boot loader, no /kernel

[Jordan K. Hubbard]

I've been taking the last few days off, but I intend to get to
this this week and fix whatever's broken.  Don't panic. :)

> On Mon, Jan 18, 1999 at 09:52:26PM -0800, Mike Smith wrote:
> > > Hi ! Bad news, make release still produces non bootable floppies.
> > > I cvsupped yesterday evening at 8pm and did a make world and
> > > make release 
> > > 
> > > Now I tried the boot.flp image from the ftp subdir in /R/
> > > 
> > > First error message
> > >   No /boot/loader
> > > Then the typical "boot banner"
> > > 2nd error message
> > >   No /kernel
> > > When typing ?
> > >   . .. kernel.gz
> > > When typing kernel.gz to load this kernel
> > >   invalid format
> > 
> > Of course, it's gzipped.
> > 
> > > Well, there is _still_ something wron, believe me.
> > 
> > The single-floppy install is broken.  Use the two-floppy install as 
> > I've been encouraging people to do now since the 12th.
> 
> This sounds like booting/installing from CD-ROM is currently
> impossible as well ???
> 
>   Andreas ///
> 
> -- 
> Andreas Klemmhttp://www.FreeBSD.ORG/~andreas
>  What gives you 90% more speed, for example, in kernel compilation ?
>   http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html
>  "NT = Not Today" (Maggie Biggs)  ``powered by FreeBSD SMP''
> 
> To Unsubscribe: send mail to majord...@freebsd.org
> with "unsubscribe freebsd-current" in the body of the message


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

How should I config the atkbdc device

[Chan Yiu Wah]

Hello,

I just finished the compilation of the whole system with ctm source upto
src-cur.3712 and found the keyboard freezed after system boot up. I would 
like to know the usage of atkbdc device which I think is the cause of the
keyboard freeze.  Any idea ?

cheers

Clarence

To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

KLD cannot load dependent modules

[Julian Elischer]

If I load a module A
then try load a module B that requires a function in A
it fails because it cannot find the symbol..
is this a known problem?

(A real bummer if so)

julian





To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: aic (adaptec 152x) still not supported in -current?

[NAKAGAWA Yoshihisa]

> I'd love to see the aic supported, mostly for my notebook.  However,
> no one seems to have a confluance of time, information and talent to
> write the driver, or even port the other one in all its gory.

If CAMed aic driver is available, SlimSCSI support is very
easy. First of all, we need CAMed aic driver.

--
NAKAGAWA, Yoshihisa
y-nak...@nwsl.mesh.ad.jp
nakag...@jp.freebsd.org

To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Building a new system to current

[Geoff Rehmet]

Hi,
 
I'm in the process of setting up a new FreeBSD-current
box, starting with 3.0 Release, and moving to current.
One question I have, is whether to go to the ELF kernel
before I recompile the world with current source.
 
 
My plan is as follows:
- Load 3.0-RELEASE (done)
- archive and delete all a.out tools (done)
- update to the new bootblocks (done)
- move to ELF kernel
- CVSup to current
- rebuild the world
- come up on current
 
I have tarred up all the a.out libraries and tools, to
try and make sure that I don't install anything that
depends on a.out.  Hopefully, I will not have to go
back on that!
 
Apart from the comments in src/UPDATING,
Peter Wemm's ELF day web page, and Robert
Nordiers page on the new bootblocks, can anyone
think of anything I should take into account?
 
regards,
Geoff (hoping to be hacking again soon!)

--
Geoff Rehmet, The Internet Solution - Infrastructure 
tel: +27-11-283-5462, fax: +27-11-283-5401 mobile: +27-83-292-5800
email: geo...@is.co.za 
URL: http://www.is.co.za   

 

To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: Building a new system to current

[Mike Smith]

> Hi,
>  
> I'm in the process of setting up a new FreeBSD-current
> box, starting with 3.0 Release, and moving to current.
> One question I have, is whether to go to the ELF kernel
> before I recompile the world with current source.
>  
>  
> My plan is as follows:
> - Load 3.0-RELEASE (done)
> - archive and delete all a.out tools (done)
> - update to the new bootblocks (done)
> - move to ELF kernel

Installing the Jan 12th snapshopt gives you all of this already, and no 
a.out cruft anywhere in sight.

> Apart from the comments in src/UPDATING,
> Peter Wemm's ELF day web page, and Robert
> Nordiers page on the new bootblocks, can anyone
> think of anything I should take into account?

Nothing immediately obvious - you've taken a slightly longer path but I 
think you'll end up in the right place.

-- 
\\  Sometimes you're ahead,   \\  Mike Smith
\\  sometimes you're behind.  \\  m...@smith.net.au
\\  The race is long, and in the  \\  msm...@freebsd.org
\\  end it's only with yourself.  \\  msm...@cdrom.com



To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

C++ compliler unable to produce excutables

[Joss Roots]

Hi there,
Some ports are complaining during early configuration
phase using configure that c++ compiler is unable to
produce excutables, and the options are -O -pipe
is there anything I am missing here, as this is the
first time I hear this complain, please help.
thanks

- MAY THE FORCE BE WITH YOU.~o  .^.
  ___   o~ .00 )
Static Email   : osiris2...@yahoo.com   /|   o~ /)(
Bouncing Email : r...@isis.dynip.com   / |   | \
Web Site   : http://isis.dynip.com:80 (Frames) ___/  |  /   \
Anon FTP Site  : ftp://isis.dynip.com:21 (anonymous)  |  /''___/ /   |
Gopher Site: gopher://isis.dynip.com:70   | /'''/___/|
Network News   : isis.dynip.com (Read, Post, Xfer)  __|/'''/
Mailing Lists  : majord...@isis.dynip.com (public)
pgp key: finger r...@isis.dynip.com


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: Building a new system to current

[geoffr]

Mike Smith writes :
> 
> Installing the Jan 12th snapshopt gives you all of this already, and no 
> a.out cruft anywhere in sight.
After a bit of thought - I think I will take this advice.
Blowing the achine I have installed away is quicker than
trying to juggle some of the recent changes!

geoff.

-- 
Geoff Rehmet,
The Internet Solution
geo...@is.co.za; ge...@rucus.ru.ac.za; c...@freebsd.org
tel: +27-83-292-5800

To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

help (3.0.0-19990112 nightmare)

[Didier Derny]

hi,

I tried to upgrade my system (FreeBSD-3.0 december)
with 3.0.0-19990112.

I'm using 2 scsi drivers for FreeBSD

SCSIID 1  for my work system
SCSIID 2  for my test system

I'm always installing a new version on my test drive (SCSIID 2)
with the (SCSIID 1) drive disconnected. the I reconnect my work drive
(standard boot) and I boot the new system with
1:da(1,a)/kernel (now 1:da(1,a)/boot/loader)


1- book ok
2- installation interrupted while probing devices
   (I've not been able to get any useful message [reboot too fast])
3- boot by mistake on the root floppy disk
   then inserted the boot floppy disk
   (boot ok, upgrade apparently ok)
4- no label on the disk after the upgrade
5- I reinstalled everything startting from the root+boo+mfsroot
   everything worked fined.
6- I now unable to boot (refuse to mount / writable)
   apparently the disk with SCSIID-2 is not recognized as da1s1a
   even if it booted in read only from this disk.

If you have any idea ?

thanks for your help


Didier Derny   | FreeBSD 3.0-CURRENT Site
Email: did...@omnix.net| Microsoft Free Computer.



To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

make aout-to-elf died in src/gnu/usr.bin/texinfo/doc

[Wolfram Schneider]

I tried `make aout-to-elf' last sunday (17th Jan). Make died
in src/gnu/usr.bin/texinfo/doc

The Makefile started the elf binary `../makeinfo/makeinfo'
But the elf linker was not yet ready ...

-- 
Wolfram Schneider  http://freebsd.org/~w/ 

To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: aic (adaptec 152x) still not supported in -current?

[Daniel C. Sobral]

"Kenneth D. Merry" wrote:
> 
> > At the moment, looking in LINT, it looks like aic still isn't
> > supported. Is that true? Does anyone know whether it will be?
> 
> It's true that it isn't supported yet.  We are planning on supporting it.
> Brian Beattie is the one working on it, you should probably ask him how
> it is coming along.  I have no idea when support will appear.
> 
> If you want SCSI support any time soon, I would suggest getting a supported
> card.  An ISA Advansys card might be a good, cheap substitute for your
> 6360/6260 board.

I was under the impression that SlimSCSI was 152x-compatible. PCMCIA
SCSI support is very lacking in FreeBSD-current. (Soon to be
-stable!)

--
Daniel C. Sobral(8-DCS)
d...@newsguy.com

If you sell your soul to the Devil and all you get is an MCSE from
it, you haven't gotten market rate.


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: KLD cannot load dependent modules

[Doug Rabson]

On Tue, 19 Jan 1999, Julian Elischer wrote:

> 
> If I load a module A
> then try load a module B that requires a function in A
> it fails because it cannot find the symbol..
> is this a known problem?
> 
> (A real bummer if so)

The module B needs to have A as a dependancy.  Use KMODDEPS to do this.
Something like this should work in the Makefile:

KMOD=   modB
SRCS=   ...
KMODDEPS= modA
KLDMOD=t
NOMAN=t
.include 


The linker will only resolve symbols against the files in the dependancy
list (and the kernel).

--
Doug Rabson Mail:  d...@nlsystems.com
Nonlinear Systems Ltd.  Phone: +44 181 442 9037



To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: linuxthreads, gimp 1.1+, dies

[brian]

Brian Feldman suggested:
> Try compiling with debugging info, get a coredump, and debug with the binary
> that has the full debugging symbols.

Gimp (CVS) compiled with 
CFLAGS="-g -D_THREAD_SAFE -I/usr/local/include -L/usr/local/lib -O2 -m486 -pipe 
-lpthread"

Brian Litzinger wrote:
>>Everything compiles and it runs.  However, various operations crash...

Every crash I've generated since adding -g as been in the app/tile_cache.c
code.  Seems to be some problem in the list management.

I recompiled that particular file using the non-thread version and have
not been able to cause a crash, so I'll look more closely at that file.

Thanks for the help,

-- 
Brian Litzinger 

To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: NFS problem found - pleaes try this patch.

[Bjoern Fischer]

On Mon, Jan 18, 1999 at 10:05:50AM -0500, Luoqi Chen wrote:
> The check is correct and should be there, the B_CACHE bit was cleared because
> I made a mistake when setting the valid bit in the vm page.
[...]
> Note the calculation of ev, the original code was a round-up and I changed it
> to round-down in my -r1.188 commit (I thought it was a bug in the original
> code, but it was actually me who didn't understand the nfs code well enough).

The patch seems to solve the problem as nfs behaves as it did
prior to -r1.188. Thanks.

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 nfs fs) generating a wrong sized recover
file. After that the server panics on shutdown. Without triggering
the bug it shuts down gracefully.

I'll try to receipe a situation for easily reproducing this.

  Bjoern

-- 
-BEGIN GEEK CODE BLOCK-
GCS d--(+) s++: a- C+++(-) UBLOSI$ P+++(-) L+++(-) !E W- N+ o>+
K- !w !O !M !V  PS++  PE-  PGP++  t+++  !5 X++ tv- b+++ D++ G e+ h-- y+ 
--END GEEK CODE BLOCK--

To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

RE: Building a new system to current

[Berend de Boer]

>> - update to the new bootblocks (done)
>> - move to ELF kernel

> Installing the Jan 12th snapshopt gives you all of this already, and
> no a.out cruft anywhere in sight.

Warning: make world doesn't upgrade the bootblocks as I just detected. I
tried disklabel -B before but it complained that the device was busy (of
course).

Time to read the fallback section )-:

Groetjes,

Berend.


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: NFS problem found - pleaes try this patch.

[Sheldon Hearn]

On Tue, 19 Jan 1999 11:38:50 +0100, Bjoern Fischer wrote:

> But there's still something wrong: When shutting down the server
> it still sometimes panics in vinvalbuf() complaining 'bout dirty
> pages.

I'm not sure this has anything to do with NFS. I got this after last
night's fresh world and kernel install. The vinvalbuf message occured
after the ``syncing disks ...done'' message but before the ``Rebooting''
message and.

However, I cannot reproduce the message since that reboot, with or
without NFS activity.

Ciao,
Sheldon.

To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: KLD cannot load dependent modules

[Peter Wemm]

Doug Rabson wrote:
> On Tue, 19 Jan 1999, Julian Elischer wrote:
> 
> > 
> > If I load a module A
> > then try load a module B that requires a function in A
> > it fails because it cannot find the symbol..
> > is this a known problem?
> > 
> > (A real bummer if so)
> 
> The module B needs to have A as a dependancy.  Use KMODDEPS to do this.
> Something like this should work in the Makefile:
> 
>   KMOD=   modB
>   SRCS=   ...
>   KMODDEPS= modA
>   KLDMOD=t
>   NOMAN=t
>   .include 
> 
> The linker will only resolve symbols against the files in the dependancy
> list (and the kernel).

I've been thinking that this could be improved.  Yes, following the 
dependency list first for resolving symbols is right, I think there should 
be a fallback global search.

Specific example (which is probably going to change today, but it's a good 
example):

- wd.c has got hooks for the ATAPI code.
- The ATAPI code can be build either statically or as a module.
- ATAPI clients (acd, wfd, wst etc) therefore depend either on the kernel or 
the atapi module.  If the atapi module was statically configured, and the 
acd driver depended on the atapi file, it would eventually fail due to 
conflicts.
- However, if the acd driver didn't depend on atapi (the file), then a 
kernel compiled without it would be unable to load acd.ko regardless of 
whether atapi.ko had been previously loaded, because acd.ko won't see the 
symbold in atapi.ko.

Does this description of the problem make sense?  I think the symbol
resolution should do a global search once the dependency list is exhausted.

Cheers,
-Peter



To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: Building a new system to current

[Robert Nordier]

Berend de Boer wrote:
> >> - update to the new bootblocks (done)
> >> - move to ELF kernel
> 
> > Installing the Jan 12th snapshopt gives you all of this already, and
> > no a.out cruft anywhere in sight.
> 
> Warning: make world doesn't upgrade the bootblocks as I just detected. I
> tried disklabel -B before but it complained that the device was busy (of
> course).

A "Device busy" is most likely due to specifying the full path of a
block device

disklabel -B /dev/da0s2a

The best approach is to specify just the drive

disklabel -B da0

or the slice, if you have more than one FreeBSD slice per drive

disklabel -B da0s3

-- 
Robert Nordier

To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

HEADS UP: another syscons update

[Kazutaka YOKOTA]

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 next time, and "make clean depend all" in your
kernel compile directory.  No need to update the kernel config file
this time, though.

Sorry for this inconvenience.

Kazu

To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

sys/kern/kern_linker.c patch

[Ustimenko Semen]

Imagine:

I'm trying to unload KLD module, it is busy:

# kldunload -n ntfs
kldunload: can't unload file: Device busy

After this point i'll never get module unloaded becouse
kldunload() in sys/kern/kern_linker.c has already decremeted
lf->userrefs. I'll get only this messages:

# kldunload -n ntfs
Jan 18 17:10:13 ws21 /kernel: linkerunload: attempt to unload file which
was not loaded by user
kldunload: can't unload file: Device busy

Here is patch.
*** kern_linker.c.orig  Mon Jan 18 17:22:39 1999
--- kern_linker.c   Mon Jan 18 16:40:33 1999
***
*** 653,660 
error = EBUSY;
goto out;
}
-   lf->userrefs--;
error = linker_file_unload(lf);
  } else
error = ENOENT;
  
--- 653,662 
error = EBUSY;
goto out;
}
error = linker_file_unload(lf);
+   if(error)
+   goto out;
+   lf->userrefs--;
  } else
error = ENOENT;
  


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

KLD naming

[Jeroen C. van Gelderen]

Hi,

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_daemon

the modules of one type will sort together in a directory listing. This is a
change that will make FreeBSD more user friendly I think.

Cheers,
Jeroen


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: linuxthreads, gimp 1.1+, dies

[Jeremy Lea]

Hi,

On Tue, Jan 19, 1999 at 02:45:39AM -0800, br...@worldcontrol.com wrote:
> Gimp (CVS) compiled with
> CFLAGS="-g -D_THREAD_SAFE -I/usr/local/include -L/usr/local/lib -O2 -m486
> -pipe -lpthread"

Hmm, if you're using the libpthread from lt.tar.com, and you installed it
according to the instructions, then that should read:

> CFLAGS="-g -D_THREAD_SAFE -DLINUXTHREADS -I/usr/local/include
> --L/usr/local/lib -O2 -m486 pipe -lpthread"

So it picks up the correct header.  But I doubt you would have got it
compiled without that?  Also, are you using glib11-devel/gtk11-devel ports
linked against libpthread?  By default the ports link against libc_r.

Also, the linuxthreads stuff needs libc to be reentrant, from what I
understand, and Richard hasn't released (or finished) those patches yet.

Regards,
 -Jeremy

PS Your mailer is setting a bogus followup's line... or mine is misreading
it...

-- 
  |If I was not so weak, if I was not so cold,
--+--  If I was not so scared of being broken, growing old,
  |I would be. I would be... frail.
  | - jars of clay / much afraid / frail

To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: sys/kern/kern_linker.c patch

[Ustimenko Semen]

Sorry for self reply.

Patch isn't good enougth:-) becouse linker_file_unload()
deallocates lf structure's memory... so lf->userrefs-- may cause
page fault or whatever else. (I wonder how that didn't happened)

Look at this one:

*** kern_linker.c.orig  Mon Jan 18 17:22:39 1999
--- kern_linker.c   Mon Jan 18 18:14:28 1999
***
*** 655,660 
--- 655,662 
}
lf->userrefs--;
error = linker_file_unload(lf);
+   if(error)
+   lf->userrefs++;
  } else
error = ENOENT;
  



To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: NFS problem found - pleaes try this patch.

[D. Rock]

This patch seems to fix my NFS problems. I started a make release yesterday
and it is still running (It's a slow machine). No problems so far.
The chroot dir is NFSv2/UDP mounted.

Thanks,

Daniel

Luoqi Chen schrieb:
> 
> The check is correct and should be there, the B_CACHE bit was cleared because
> I made a mistake when setting the valid bit in the vm page.
> 
> Index: vfs_bio.c
> ===
> RCS file: /home/ncvs/src/sys/kern/vfs_bio.c,v
> retrieving revision 1.192
> diff -u -r1.192 vfs_bio.c
> --- vfs_bio.c   1999/01/12 11:59:34 1.192
> +++ vfs_bio.c   1999/01/18 14:45:33
> @@ -2171,7 +2171,7 @@
> (vm_offset_t) (soff & PAGE_MASK),
> (vm_offset_t) (eoff - soff));
> sv = (bp->b_offset + bp->b_validoff + DEV_BSIZE - 1) & 
> ~(DEV_BSIZE - 1);
> -   ev = (bp->b_offset + bp->b_validend) & ~(DEV_BSIZE - 1);
> +   ev = (bp->b_offset + bp->b_validend + DEV_BSIZE - 1) & 
> ~(DEV_BSIZE - 1);
> soff = qmax(sv, soff);
> eoff = qmin(ev, eoff);
> }
> 
> Note the calculation of ev, the original code was a round-up and I changed it
> to round-down in my -r1.188 commit (I thought it was a bug in the original
> code, but it was actually me who didn't understand the nfs code well enough).
> 
> -lq
> 
> To Unsubscribe: send mail to majord...@freebsd.org
> with "unsubscribe freebsd-current" in the body of the message

To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: C++ compliler unable to produce excutables

[Martin Cracauer]

In , Joss 
Roots wrote: 
> Hi there,
> Some ports are complaining during early configuration
> phase using configure that c++ compiler is unable to
> produce excutables, and the options are -O -pipe
> is there anything I am missing here, as this is the
> first time I hear this complain, please help.
> thanks

Do you have egcs or gcc-2.8 or anything else installaed that installs
/usr/local/bin/g++? 

Such extra compilers from ports tend to break. Make sure you use
/usr/bin/g++. 

If it still fails, please post the log of error messages and the usual
stuff `uname -a` and such.

Martin
-- 
%
Martin Cracauer  http://www.cons.org/cracauer/
BSD User Group Hamburg, Germany http://www.bsdhh.org/

To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: New syscons + XFree 3.3.3.1 = problem?

[Oliver Fromme]

 > >but that doesn't happen any-
 > >more.  Instead, it uses the current one (i.e. if I'm on ttyv3
 > >and start X, it uses ttyv3).  Is this intentional, or is it a
 > >bug?

Oops...  I'm very sorry for the confusion...  it was all my
fault.  There were as many gettys configured in in /etc/ttys
as MAXCONS in the kernel, so XFree wasn't able to allocate an
unused vty, obviously.  Disabling one getty solved the problem.

Maybe this pitfall could be documented somewhere...  But then
again, maybe I'm the only one who's too dumb to get it right.
:-]

Regards
   Oliver

-- 
Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany
(Info: finger userinfo:o...@dorifer.heim3.tu-clausthal.de)

"In jedem Stück Kohle wartet ein Diamant auf seine Geburt"
 (Terry Pratchett)

To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: make release produces unbootable boot floppies, no boot loader, no /kernel

[Drew Derbyshire]

Mike Smith wrote:

> > This sounds like booting/installing from CD-ROM is currently
> > impossible as well ???
>
> That's correct.  We're looking at having to move to a harddisk
> emulation mode to get this back on track.

Would a 2.88M virtual floppy for the CD-ROM boot image be a quick fix, or is
it too much work?


--
Drew Derbyshire UUPC/extended e-mail:  softw...@kew.com
   Telephone:  617-279-9812

"I get by with a little help from my friends . . ."  - Lennon/McCartney



To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: NFS problem found - pleaes try this patch.

[Bjoern Fischer]

On Tue, Jan 19, 1999 at 01:01:34PM +0200, Sheldon Hearn wrote:
[...]
> > But there's still something wrong: When shutting down the server
> > it still sometimes panics in vinvalbuf() complaining 'bout dirty
> > pages.
> 
> I'm not sure this has anything to do with NFS. I got this after last
> night's fresh world and kernel install. The vinvalbuf message occured
> after the ``syncing disks ...done'' message but before the ``Rebooting''
> message and.

Then why is the panic on the server triggered by the vi SEGV?
No vi SEGV -> server goes down normally;
vi SEGV -> server panics on shutdown.

> However, I cannot reproduce the message since that reboot, with or
> without NFS activity.

It is somewhat tricky. There's actually only one file I've got that
causes vi to SEGV (and the server to panic on shutdown). I'll
have to look into vi source to find out how the vi.recover file
is created. Maybe some locking is involvled, too.

  Bjoern

-- 
(sig_t*)NULL

To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: make release produces unbootable boot floppies, no boot loader, no /kernel

[Brian J. McGovern]

Wouldn't it be possible to use a 2.88MB boot image? Most of the documentation
I've read states that this should be supportable on machines that understand
2.88MB floppies Or, have we outgrown that already?
-Brian

To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: linuxthreads, gimp 1.1+, dies

[Richard Seaman, Jr.]

On Mon, Jan 18, 1999 at 06:27:18PM -0800, br...@worldcontrol.com wrote:

> I running gimp -unstable (CVS 1/17/1998) and FreeBSD -current
> (1/17/1998) with
> 
> CFLAGS= -O2 -m486 -pipe -DCOMPAT_LINUX_THREADS -DVM_STACK
> COPTFLAGS= -O -pipe -DCOMPAT_LINUX_THREADS -DVM_STACK
> 
> and linuxthreads port from http://lt.tar.com.
> 
> recompiled glib, gtk+ and gimp which works fine reasonably
> well without threads.
> 
> with threads
> CFLAGS="-D_THREAD_SAFE -I/usr/local/include -L/usr/local/lib -O2 -m486 -pipe 
> -lpthread"
> 
> Everything compiles and it runs.  However, various operations crash 
> for example:

Thanks for the report.  I'll look into it, though it may be a day or two
before I can get to it.  

One question, I assume you compiled glib and gtk+ with linuxthreads also?
If so, can you send me the makefile (and any other) mods you made to do
the compile?  Thanks.

-- 
Richard Seamman, Jr.  email: d...@tar.com
5182 N. Maple Lanephone: 414-367-5450
Chenequa WI 53058 fax:   414-367-5852

To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: How should I config the atkbdc device

[Kevin G. Eliuk]

On Tue, 19 Jan 1999, Chan Yiu Wah wrote:

> Hello,
> 
> I just finished the compilation of the whole system with ctm source upto
> src-cur.3712 and found the keyboard freezed after system boot up. I would 
> like to know the usage of atkbdc device which I think is the cause of the
> keyboard freeze.  Any idea ?
> 

Look at http://www.freebsd.org/~yokota/sc_update.txt, that should be all you 
need.

-- 
  Regards,
  Kevin G. Eliuk

Discover Rock Solid, Discover FreeBSD  |  http://www.FreeBSD.Org


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: linuxthreads, gimp 1.1+, dies

[Richard Seaman, Jr.]

On Tue, Jan 19, 1999 at 02:06:13PM +0200, Jeremy Lea wrote:

> On Tue, Jan 19, 1999 at 02:45:39AM -0800, br...@worldcontrol.com wrote:
> > Gimp (CVS) compiled with
> > CFLAGS="-g -D_THREAD_SAFE -I/usr/local/include -L/usr/local/lib -O2 -m486
> > -pipe -lpthread"
> 
> Hmm, if you're using the libpthread from lt.tar.com, and you installed it
> according to the instructions, then that should read:
> 
> > CFLAGS="-g -D_THREAD_SAFE -DLINUXTHREADS -I/usr/local/include
> > --L/usr/local/lib -O2 -m486 pipe -lpthread"
> 
> So it picks up the correct header.  But I doubt you would have got it
> compiled without that? 

Actually, the new version, in FreeBSD "ports" form, doesn't require 
-DLINUXTHREADS anymore, but it does require -I/usr/local/include to
pick up the right header, since it installs a pthread.h into 
/usr/local/include.  This conflicts with the pthread.h in /usr/include.

> Also, are you using glib11-devel/gtk11-devel ports
> linked against libpthread?  By default the ports link against libc_r.

Right.

> Also, the linuxthreads stuff needs libc to be reentrant, from what I
> understand, and Richard hasn't released (or finished) those patches yet.

libc is partly re-entrant, partly not.  It depends on what calls you're 
making.  As a rule of thumb, wherever the pthread spec calls for a "_r"
function (eg. readdir_r), the underlying function is not thread safe,
and either the "_r" function is missing or is not threadsafe itself
(eg. localtime_r exists in libc -- recent versions -- but is not thread
safe).  strrok_r is an exception, I think.


-- 
Richard Seamman, Jr.  email: d...@tar.com
5182 N. Maple Lanephone: 414-367-5450
Chenequa WI 53058 fax:   414-367-5852

To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: make release produces unbootable boot floppies, no boot loader, no /kernel

[Mike Smith]

> Wouldn't it be possible to use a 2.88MB boot image? Most of the documentation
> I've read states that this should be supportable on machines that understand
> 2.88MB floppies Or, have we outgrown that already?

How many systems have you seen with 2.88MB floppy drives?

-- 
\\  Sometimes you're ahead,   \\  Mike Smith
\\  sometimes you're behind.  \\  m...@smith.net.au
\\  The race is long, and in the  \\  msm...@freebsd.org
\\  end it's only with yourself.  \\  msm...@cdrom.com



To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: make release produces unbootable boot floppies, no boot loader, no /kernel

[David E. Cross]

I think the 2.88MB suggestion was an alternative to going to a 'Hard Drive'
type solution for bootable CDROMs (from a jkh post earlier).  Since most 
bioses support 2.88MB floppies (regardless of if the hardware exists on the
person's machine), wouldn't it be possible to have the 'boot.flp' for a 
bootable CDROM be one of these?

(Personally, I think going to the Hard Disk method is the right-way; this could
be a short term band-aid though.)
--
David Cross

To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

�����: Running old program on 3.0-RELEASE

[Igor Shulgin]

>> I recently installed 3.0-RELEASE on existing 2.1.0-RELEASE.
>> After that one program does not run any more.
>
>You probably did not update the contents of /etc, as one must by hand.
>This would not create the a.out search paths properly and leads to this
>exact error.

By the way, file /etc/rc.conf did not exist in 2.1.0-RELEASE and was
completely (I think) maden during installation.

Was it more practical for me to remove old /etc (/usr/lib , other dirs)
before upgrade from 2.1 to 3.0?
Should I do it in future?

Does installation on existing system use (or consider) old configuration by
whatever manner?
I mean more close subsequence of versions than extreme case of 2.1->3.0 .

There were 2 lines in my file /etc/rc.conf :
ldconfig_paths="/usr/lib/compat /usr/X11R6/lib /usr/local/lib"
ldconfig_paths_aout="/usr/lib/compat/aout /usr/X11R6/lib/aout
/usr/local/lib/aout"

After several advices in maillist freebsd-current I _move_ /usr/lib/compat to
ldconfig_paths_aout . Not copy because there are no ELF-files in my
/usr/lib/compat .
Is it OK?

Sorry for importunity.

--- With good wishes,
  Igor Shulgin

>- Jordan




To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: mounting double-ended SCSI disks

[Bill Trost]

Satoshi Asami writes:
However, if I try to mount it from B read-only while A is mounting
it read-write, it succeeds.  This looks dangerous, as A writing data
onto the disk could cause B's cache to go stale without B knowing
it.

Just about as dangerous al letting A mount it read-only, and then B
mounting it read-write.  Only in this case, nobody has a chance to know
that something is amiss, and since you probably are letting this happen
automatically at OS startup, the chances of a RO mount being followed by
a RW one are about the same as the other way 'round.

You're going to have the problem regardless of whether mount pays
attention to the clean flag.  If you are worried about a RO mount
getting corrupted, don't modify the partition out from under it on
another machine.

To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: SOFTUPDATES

[Alfred Perlstein]

On Tue, 12 Jan 1999, Bruce Evans wrote:

> >Does softupdates give any gain over async?
> >I have /usr/src and /usr/obj both mounted async, noatime, and it does
> >seem to be rather nicely fast over default mountops.
> 
> Async isn't fully async in FreeBSD (some directory operations are still
> sync), so softupdates is much faster in some cases.  Fully async async
> seems to be a little faster than softupdates.

That's very arbitrary, softupdates can collaps and queue operations and be
much faster, it just depends on your operations.

-Alfred

> 
> Bruce
> 
> To Unsubscribe: send mail to majord...@freebsd.org
> with "unsubscribe freebsd-current" in the body of the message
> 


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

compat22 ???

[Joao Carlos Mendes Luis]

Hi,

  Installing the latest 3.0-SNAP, I just discovered that I cannot run
the netscape binaries anymore.  It stops claiming not to find
/usr/libexec/ld.so, but obviously it would not find a.out libraries
neither.  :)

  Maybe we need a compat22 distribution before 3.1 release.

Jonny

--
Joao Carlos Mendes LuisM.Sc. Student
jo...@jonny.eng.br Universidade Federal do Rio de Janeiro
"This .sig is not meant to be politically correct."

To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

readdir & cd9660 & direntp->d_type == bug?

[Alexander Leidinger]

Hi,

dirp = opendir("/cdrom");
direntp = readdir(dirp);

results in 
direntp->d_type == DT_UNKNOWN
for every kind of directoryentry, even if it is a directory or file.

The man page didn't say it didn't work with CDs, so I assume it should
work ( ;) ).

current from "Sun Jan 17",

Bye,
Alexander.

-- 
"Darth Vader sleeps with a Teddywookie."
  Fortune cookie
http://netchild.home.pages.de/A.Leidinger @ wurzelausix.cs.uni-sb.de


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: KLD cannot load dependent modules

[Doug Rabson]

On Tue, 19 Jan 1999, Peter Wemm wrote:

> Doug Rabson wrote:
> > On Tue, 19 Jan 1999, Julian Elischer wrote:
> > 
> > > 
> > > If I load a module A
> > > then try load a module B that requires a function in A
> > > it fails because it cannot find the symbol..
> > > is this a known problem?
> > > 
> > > (A real bummer if so)
> > 
> > The module B needs to have A as a dependancy.  Use KMODDEPS to do this.
> > Something like this should work in the Makefile:
> > 
> > KMOD=   modB
> > SRCS=   ...
> > KMODDEPS= modA
> > KLDMOD=t
> > NOMAN=t
> > .include 
> > 
> > The linker will only resolve symbols against the files in the dependancy
> > list (and the kernel).
> 
> I've been thinking that this could be improved.  Yes, following the 
> dependency list first for resolving symbols is right, I think there should 
> be a fallback global search.
> 
> Specific example (which is probably going to change today, but it's a good 
> example):
> 
> - wd.c has got hooks for the ATAPI code.
> - The ATAPI code can be build either statically or as a module.
> - ATAPI clients (acd, wfd, wst etc) therefore depend either on the kernel or 
> the atapi module.  If the atapi module was statically configured, and the 
> acd driver depended on the atapi file, it would eventually fail due to 
> conflicts.
> - However, if the acd driver didn't depend on atapi (the file), then a 
> kernel compiled without it would be unable to load acd.ko regardless of 
> whether atapi.ko had been previously loaded, because acd.ko won't see the 
> symbold in atapi.ko.
> 
> Does this description of the problem make sense?  I think the symbol
> resolution should do a global search once the dependency list is exhausted.

This makes a lot of sense.  I think this is what Mike is trying to address
in his new module-based instead of file-based dependancy scheme.

--
Doug Rabson Mail:  d...@nlsystems.com
Nonlinear Systems Ltd.  Phone: +44 181 442 9037



To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: KLD naming

[Doug Rabson]

On Tue, 19 Jan 1999, Jeroen C. van Gelderen wrote:

> Hi,
> 
> 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_daemon
> 
> the modules of one type will sort together in a directory listing. This is a
> change that will make FreeBSD more user friendly I think.

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/
if_ed.ko
...
...

Including the type in the filename instead might be a better idea though.

--
Doug Rabson Mail:  d...@nlsystems.com
Nonlinear Systems Ltd.  Phone: +44 181 442 9037



To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: make release produces unbootable boot floppies, no boot loader, no /kernel

[Mike Smith]

> Mike Smith wrote:
> 
> > > This sounds like booting/installing from CD-ROM is currently
> > > impossible as well ???
> >
> > That's correct.  We're looking at having to move to a harddisk
> > emulation mode to get this back on track.
> 
> Would a 2.88M virtual floppy for the CD-ROM boot image be a quick fix, or is
> it too much work?

The 10M image is so little extra work that its worth doing it properly. 
 I just have to get this damn drive off to Robert...

-- 
\\  Sometimes you're ahead,   \\  Mike Smith
\\  sometimes you're behind.  \\  m...@smith.net.au
\\  The race is long, and in the  \\  msm...@freebsd.org
\\  end it's only with yourself.  \\  msm...@cdrom.com



To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: make release produces unbootable boot floppies, no boot loader, no /kernel

[Robert Nordier]

Mike Smith wrote:
> > Mike Smith wrote:
> > 
> > > > This sounds like booting/installing from CD-ROM is currently
> > > > impossible as well ???
> > >
> > > That's correct.  We're looking at having to move to a harddisk
> > > emulation mode to get this back on track.
> > 
> > Would a 2.88M virtual floppy for the CD-ROM boot image be a quick fix, or is
> > it too much work?
> 
> The 10M image is so little extra work that its worth doing it properly. 
>  I just have to get this damn drive off to Robert...

... and then Robert has to find some damn time to look at it. :-)

Anyway, drop me a line when it goes off.  Around 4-5 weeks seems
fairly promising at the moment.

-- 
Robert Nordier

To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: make release produces unbootable boot floppies, no boot loader, no /kernel

[Brian J. McGovern]

Actually, about half a dozen. Lots More if you include LS-120 drives in the
list... But, the main point I'm driving at is to still be able to build 
bootable CDs without too much playing...
-Brian

To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: Incorrect EAGAIN & select() exceptions

[Brian Somers]

Just in case anyone's been losing sleep over this, it was pilot error!
bde@ pointed out the problem, and cron confirmed it :-/

> Hi,
> 
> Something weird is happening in -current.  I installed world, a 
> kernel and bootblocks on Jan 6 - I can't say for sure that it wasn't 
> happening before this as I usually do all ppp testing via the 
> loopback interface on a single machine for convenience.
> 
> Yesterday, I tried using ppp on the above -current via a tty and got 
> two weird results, both happen at random intervals, but are 
> reasonably easy to reproduce.
> 
> 1.  I select() on a tty descriptor for reading (and writing & 
> exceptions).  Select comes back with the read descriptor set, 
> I do a read() and get -1 with errno EAGAIN.  This must be 
> wrong !
> 
> 2.  I select() on a tty descriptor for reading, writing and 
> exceptions and get the exception fd_set bit set.  This has never 
> happened before, and it was only a few weeks ago that I even had 
> ppp not always abend when an exception is detected.
> 
> Does anybody know what's going on (before I look into things further) ?
> Help would be appreciated if anyone has any su{spicions,gestions}.
> 
> Cheers.
> -- 
> Brian   
>   
> Don't _EVER_ lose your sense of humour !



To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

make world dying

[Aaron D. Gifford]

I'm still trying to upgrade from 3.0-RELEASE to 3.0-CURRENT
unsuccessfully.  It used to die in perl, then that was fixed, but for
the past 2 days, it has been dying in /usr/src/sys/boot/i386/libi386. 
Is this a known problem?  Yes, I'm a CURRENT newbie, but hopefully only
until the split to 3.1 when I can hopefully then play with 3.1-STABLE.

Are questions such as the above better addressed to -questions or
-current?

Thanks.

Hoping to catch a cvsup when the source tree will build,
Aaron out.

To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Booting -current with new loader

[John Saunders]

Hi,

I have had no success in booting -current with the new loader. I can boot
the kernel directly by entering 1:wd(2,a)/kernel at the boot prompt. 
However if I enter either 1:wd(1,a)/boot/loader (the default) or
1:wd(2,a)/boot/loader I get the loader started but the kernel won't boot. 
The the second case commands like source and ls don't work unless I set
currdev=disk2s1a: and then it works. I have tried setting rootdev to lots
of things but the kernel _always_ tried to mount wd1s1a as the root
filesystem. It seems to ignore the rootdev flag. The kernel has been built
with "config kernel root on wd2" but even this is ignored. 

The only solution I have is bypass the loader all-together, but I really
wanted a splash screen :( Or possibly use config to make my second disk
appear as wd1 instead of wd2 (not tried yet because I consider it an ugly
hack). 

Cheers.
--++
. | John Saunders  - mailto:j...@nlc.net.au(EMail) |
,--_|\|- http://www.nlc.net.au/  (WWW) |
   /  Oz  \   |- 02-9489-4932 or 041-822-3814  (Phone) |
   \_,--\_/   | NHJ NORTHLINK COMMUNICATIONS - Supplying a professional,   |
 v| and above all friendly, internet connection service.   |
  ++


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: Booting -current with new loader

[Mike Smith]

> The only solution I have is bypass the loader all-together, but I really
> wanted a splash screen :( Or possibly use config to make my second disk
> appear as wd1 instead of wd2 (not tried yet because I consider it an ugly
> hack). 

Try "set num_ide_disks=-1" in the loader.

-- 
\\  Sometimes you're ahead,   \\  Mike Smith
\\  sometimes you're behind.  \\  m...@smith.net.au
\\  The race is long, and in the  \\  msm...@freebsd.org
\\  end it's only with yourself.  \\  msm...@cdrom.com



To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: ufs async

[Terry Lambert]

> Hey gang:
> 
> Somebody mentioned the other day that UFS async isn't entirely async, and
> that directories are (always) sync.  Is that true?

No.

The default is sync metadata and async user data, with the assumption
that the user will have taken a CS 203 class and know about two stage
commit for database/index integrity, if they care about their data.

With the "sync" option, all data, both metadata and user data, is written
synchronously.

With the "async" option, all data, both metadata and user data, is
written asynchronously.

Put another way:

default:A seat belt for you, but not the passenger
sync:   A seat belt for you and your passenger
async:  You are both strapped to the bumper

There's also soft updates.  The point of soft updates is to ensure
ordering for maximal data ingrity (default ensures only metadata
integrity by ordering metadata operations, sync assures only that
writes occur in order, but that user data/metadata dependencies are
not assured because of implied dependecies between file contents,
and async implies no data integrity whatsoever).

Basically, soft updates is just a more efficient way of ensuring
operations occur in order (like the USL "DOW" -- Delayed Ordered
Writes -- technology, which is under patent, only more efficient).

So...

soft updates:   A seat belat and an air bag for both you
and your passenger


Terry Lambert
te...@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.

To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: ufs async

[Peter Jeremy]

Terry Lambert  wrote:
>Put another way:
>
>   default:A seat belt for you, but not the passenger
>   sync:   A seat belt for you and your passenger
Terry forgot to mention that you also have to come to a dead stop every
10 feet and check that the wheel bolts are all tight :-).

>   async:  You are both strapped to the bumper
And the brakes don't work.

>   soft updates:   A seat belt and an air bag for both you
>   and your passenger

Peter

To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: Booting -current with new loader

[Daniel C. Sobral]

John Saunders wrote:
> 
> I have had no success in booting -current with the new loader. I can boot
> the kernel directly by entering 1:wd(2,a)/kernel at the boot prompt.
> However if I enter either 1:wd(1,a)/boot/loader (the default) or
> 1:wd(2,a)/boot/loader I get the loader started but the kernel won't boot.
> The the second case commands like source and ls don't work unless I set
> currdev=disk2s1a: and then it works. I have tried setting rootdev to lots
> of things but the kernel _always_ tried to mount wd1s1a as the root
> filesystem. It seems to ignore the rootdev flag. The kernel has been built
> with "config kernel root on wd2" but even this is ignored.

You failed to mention your disk configuration...

--
Daniel C. Sobral(8-DCS)
d...@newsguy.com

If you sell your soul to the Devil and all you get is an MCSE from
it, you haven't gotten market rate.


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: make world dying

[Chris Timmons]

Hmmm, I zapped my /usr/obj clean around 1100PST 19/Jan/1999 and made world
just fine.  Try starting with an empty /usr/obj.  

You can pretty much glean from reading -current whether or not most people
are building it or if it is broken.  -questions is more for general
freebsd issues.

-Chris

On Tue, 19 Jan 1999, Aaron D. Gifford wrote:

> I'm still trying to upgrade from 3.0-RELEASE to 3.0-CURRENT
> unsuccessfully.  It used to die in perl, then that was fixed, but for
> the past 2 days, it has been dying in /usr/src/sys/boot/i386/libi386. 
> Is this a known problem?  Yes, I'm a CURRENT newbie, but hopefully only
> until the split to 3.1 when I can hopefully then play with 3.1-STABLE.
> 
> Are questions such as the above better addressed to -questions or
> -current?
> 
> Thanks.
> 
> Hoping to catch a cvsup when the source tree will build,
> Aaron out.
> 
> To Unsubscribe: send mail to majord...@freebsd.org
> with "unsubscribe freebsd-current" in the body of the message
> 


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: make world dying

[Matthew Dillon]

:Hmmm, I zapped my /usr/obj clean around 1100PST 19/Jan/1999 and made world
:just fine.  Try starting with an empty /usr/obj.  
:
:You can pretty much glean from reading -current whether or not most people
:are building it or if it is broken.  -questions is more for general
:freebsd issues.
:
:-Chris
:
:On Tue, 19 Jan 1999, Aaron D. Gifford wrote:
:
:> I'm still trying to upgrade from 3.0-RELEASE to 3.0-CURRENT
:> unsuccessfully.  It used to die in perl, then that was fixed, but for
:...

I updated my tree last night and was able to do a buildworld without
mishap, but I already had a mostly -current install.  However, I do
not recall there being a specific problem with libi386.

The only other thing I can think of is that I'm doing an ELF build,
and I suppose it is possible that the A.OUT build is broken and the
ELF build is not.

-Matt

Matthew Dillon 


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

RE: Booting -current with new loader

[Thomas T. Veldhouse]

FYI.  That had no affect for me at all.  I was able to pass the kernel the
rootdev by:

boot -rootdev kernel

but then I had a problem when it came time to mount root as read/write.  It
mounted read-only successfully and then bailed because it couldn't remount
as read/write.  num_ide_disks=-1 seemed to have absolutely no affect at all.

Tom Veldhouse
ve...@visi.com

> -Original Message-
> From: owner-freebsd-curr...@freebsd.org
> [mailto:owner-freebsd-curr...@freebsd.org]on Behalf Of Mike Smith
> Sent: Tuesday, January 19, 1999 4:33 PM
> To: John Saunders
> Cc: freebsd-current@FreeBSD.ORG
> Subject: Re: Booting -current with new loader
>
>
> > The only solution I have is bypass the loader all-together, but I really
> > wanted a splash screen :( Or possibly use config to make my second disk
> > appear as wd1 instead of wd2 (not tried yet because I consider
> it an ugly
> > hack).
>
> Try "set num_ide_disks=-1" in the loader.
>
> --
> \\  Sometimes you're ahead,   \\  Mike Smith
> \\  sometimes you're behind.  \\  m...@smith.net.au
> \\  The race is long, and in the  \\  msm...@freebsd.org
> \\  end it's only with yourself.  \\  msm...@cdrom.com
>
>
>
> To Unsubscribe: send mail to majord...@freebsd.org
> with "unsubscribe freebsd-current" in the body of the message
>


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: make world dying

[Robert Nordier]

Aaron D. Gifford wrote:
> I'm still trying to upgrade from 3.0-RELEASE to 3.0-CURRENT
> unsuccessfully.  It used to die in perl, then that was fixed, but for
> the past 2 days, it has been dying in /usr/src/sys/boot/i386/libi386. 
> Is this a known problem?  Yes, I'm a CURRENT newbie, but hopefully only
> until the split to 3.1 when I can hopefully then play with 3.1-STABLE.

A good plan is to include the actual diagnostic, together with some
context, if you run into a problem.  For instance:

| /usr/obj/elf/usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr  -o
| boot2.ld -P 1 boot2.bin
| kernel: ver=0.87 size=6d0 load=9000 entry=9010 map=16M pgctl=1:1
| client: fmt=bin size=143c text=0 data=0 bss=0 entry=0
| output: fmt=bin size=1d0c text=200 data=1b0c org=0 entry=0
| 244 bytes available
| dd if=boot2.ld of=boot2 obs=7680 conv=osync 2>/dev/null
| ===> sys/boot/i386/libi386
| make: don't know how to make machine/ansi.h. Stop
| *** Error code 2
| 
| Stop.

That way, if it's not a known problem, but some form of pilot error,
you may get some useful help anyway.

-- 
Robert Nordier

To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Directory structure on current.freebsd.org

[Oliver Fromme]

Hi,

Please excuse me if this is the wrong place to ask this kind
of things...

I'm wondering whether it might be a good idea to rename the
directories "current" and "releng22" on {current,releng22}
.freebsd.org to "FreeBSD-current" and "FreeBSD-stable", as
they are named on ftp.freebsd.org.

That would be more consistent, and it would make life a bit
easier for some of the mirror sites which mirror releases
and snaps on the same server, like ftp7.de.freebsd.org.

Regards
   Oliver

-- 
Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany
(Info: finger userinfo:o...@dorifer.heim3.tu-clausthal.de)

"In jedem Stück Kohle wartet ein Diamant auf seine Geburt"
 (Terry Pratchett)

To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: Directory structure on current.freebsd.org

[Oliver Fromme]

Sorry for replying to my own mail...

In list.freebsd-current I wrote:
 > I'm wondering whether it might be a good idea to rename the
 > directories "current" and "releng22" on {current,releng22}
 > .freebsd.org to "FreeBSD-current" and "FreeBSD-stable", as
 > they are named on ftp.freebsd.org.

I just noticed that the naming of the architecture directories
isn't consistent either:

In releases/snapshots they're called "axp" and "x86", while in
ports they're called "alpha" and "i386".

Personally I prefer the latter (because "Alpha" is more well-
known and 'catchy' than "AXP", and "x86" could imply that we're
running on 286, too, and it's more in line with "sparc64"),
but at least the naming should be consistent.

Just my 0.02 Euro...

Regards
   Oliver

-- 
Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany
(Info: finger userinfo:o...@dorifer.heim3.tu-clausthal.de)

"In jedem Stück Kohle wartet ein Diamant auf seine Geburt"
 (Terry Pratchett)

To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: Booting -current with new loader

[John Saunders]

On Wed, 20 Jan 1999, Daniel C. Sobral wrote:

> John Saunders wrote:
> > I have had no success in booting -current with the new loader. I can boot
> > the kernel directly by entering 1:wd(2,a)/kernel at the boot prompt.
> > However if I enter either 1:wd(1,a)/boot/loader (the default) or
> > 1:wd(2,a)/boot/loader I get the loader started but the kernel won't boot.
> > The the second case commands like source and ls don't work unless I set
> > currdev=disk2s1a: and then it works. I have tried setting rootdev to lots
> > of things but the kernel _always_ tried to mount wd1s1a as the root
> > filesystem. It seems to ignore the rootdev flag. The kernel has been built
> > with "config kernel root on wd2" but even this is ignored.
> 
> You failed to mention your disk configuration...

Opps, 2 drives, both as IDE master, one on primary and one on secondary.
Also a CDROM as secondary slave. Also to make matters worse 2 SCSI drives.
The complete mapping is...
BIOS number FreeBSD name
0x80wd0
0x81wd2
0x82da0
0x83da1
For the moment I am not trying to do anything with the SCSI drives,
although da1 has a FreeBSD slice. Both wd0 and da0 re FAT32 Winblows.

New information...

I have been able to get the kernel into single user mode, where mount /
barfs about not being able to mount /dev/wd2s1a on / because the
filesystem is different. However an ls shows it _did_ get the right one,
it just thinks it's wrong. Also curiously the normal boot-time message
"changing root device to wd2s1a" doesn't appear. I can get this far using
2 methods...

Booting using 1:wd(1,a)/boot/loader
Then at the loader type
load kernel
set currdev=disk3s1a:
boot
With this both currdev and loaddev are initially set to disk2s1a:

Or boot using 1:wd(2,a)/boot/loader
Then at the loader type
set currdev=disk2s1a:
load kernel
set currdev=disk3s1a:
boot
With this both currdev and loaddev are initially set to disk3s1a: The
loader is also unable to access files (ls, source, help, load, etc) until
I set currdev to disk2s1a:

It seems that I need currdev=disk2s1a: so that the loader can load files,
and I need currdev=disk3s1a: so that the kernel will mount root. Two
conflicting requirements.

I'm off now to play now with rootdev and boot_askname.

Cheers.
--++
. | John Saunders  - mailto:j...@nlc.net.au(EMail) |
,--_|\|- http://www.nlc.net.au/  (WWW) |
   /  Oz  \   |- 02-9489-4932 or 041-822-3814  (Phone) |
   \_,--\_/   | NHJ NORTHLINK COMMUNICATIONS - Supplying a professional,   |
 v| and above all friendly, internet connection service.   |
  ++


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: KLD naming

[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_daemon
> > 
> > the modules of one type will sort together in a directory listing. This is a
> > change that will make FreeBSD more user friendly I think.
> 
> 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/
>   if_ed.ko
>   ...
>   ...

I like this idea (subdirectories) better.. it will last longer :-)
Witness the explosion of the ports tree.

You should then be able to load a module "isa/if_ed.ko" etc
and have it work (no leading slash).

In fact, we can implement this (maybe it already works) before
coming to a final decision on what the actual layout should be.

-Archie

___
Archie Cobbs   *   Whistle Communications, Inc.  *   http://www.whistle.com

To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: Directory structure on current.freebsd.org

[Peter Jeremy]

Oliver Fromme  wrote:
>In releases/snapshots they're called "axp" and "x86", while in
>ports they're called "alpha" and "i386".

I agree that having two different names is confusing.

DEC (or Compaq) literature seems to use both Alpha and AXP - I'm not
sure that either is an especially better choice.

> "x86" could imply that we're
>running on 286, too, and it's more in line with "sparc64"),

I personally find "i386" a pain because it is used to specify both an
architecture (IA-32) and a particular implementation (80386) of that
architecture.  In some cases it may not be clear which is meant.

It's worthwhile noting that Sun use "x86" to specify their Intel
port.

Peter

To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

panic: vinvalbuf: dirty bufs (during reboot, several times)

[Andreas Klemm]

Hi !

Since one or two weeks my system panics shortly before completely
going down. Services like squid and inn take a little longer than
usual to finish, I hear much disk activity.

This happens usually if the system ran a day or so.

What can I do to help ? Compile Kernel with debug infos ?

BTW, yes I run an ELF kernel. Can't say exactly, if it's behaving
like this after completely migrating to ELF.

innd: server SHUTDOWN received
boot() called on cpu#1
syncing disks 8 7 1 done
panic: vinvalbuf: dirty bufs
mp_lock = 0001, cpuid = 0 lapic.id = 0100
Debugger ("panic")

trace:
Debugger
panic
vinvalbuf
vclean
vflush
ffs_flushfiles
ffs_unmount
dounmount
vfs_unmountall
boot
reboot
syscall
Xint0x80_syscall

Copyright (c) 1992-1999 FreeBSD Inc.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
FreeBSD 3.0-CURRENT #1: Mon Jan 18 19:26:39 CET 1999
r...@titan.klemm.gtn.com:/home/src/sys/compile/TITAN
Timecounter "i8254"  frequency 1193182 Hz
CPU: Pentium Pro (686-class CPU)
  Origin = "GenuineIntel"  Id = 0x619  Stepping=9
  Features=0xfbff
real memory  = 100663296 (98304K bytes)
avail memory = 94658560 (92440K bytes)
Programming 24 pins in IOAPIC #0
FreeBSD/SMP: Multiprocessor motherboard
 cpu0 (BSP): apic id:  1, version: 0x00040011, at 0xfee0
 cpu1 (AP):  apic id:  0, version: 0x00040011, at 0xfee0
 io0 (APIC): apic id:  2, version: 0x00170011, at 0xfec0
Preloaded elf kernel "kernel" at 0xf02dd000.
Probing for devices on PCI bus 0:
chip0:  rev 0x02 on pci0.0.0
chip1:  rev 0x01 on pci0.7.0
vga0:  rev 0x01 int a irq 19 on pci0.11.0
xl0: <3Com 3c900 Etherlink XL 10BaseT Combo> rev 0x00 int a irq 18 on pci0.12.0
xl0: Ethernet address: 00:60:97:aa:3a:db
xl0: selecting BNC port, half duplex
ahc0:  rev 0x00 int a irq 17 on pci0.13.0
ahc0: aic7880 Single Channel A, SCSI Id=7, 16/255 SCBs
ahc1:  rev 0x03 int a irq 16 on pci0.14.0
ahc1: aic7870 Single Channel A, SCSI Id=7, 16/255 SCBs
Probing for devices on the ISA bus:
sc0 on isa
sc0: VGA color <16 virtual consoles, flags=0x0>
ed0 at 0x280-0x29f irq 10 maddr 0xd8000 msize 16384 on isa
ed0: address 00:00:c0:5a:98:2a, type WD8013EPC (16 bit) 
atkbdc0 at 0x60-0x6f on motherboard
atkbd0 irq 1 on isa
psm0 irq 12 on isa
psm0: model Generic PS/2 mouse, device ID 0
sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa
sio0: type 16550A
sio1 at 0x2f8-0x2ff irq 3 on isa
sio1: type 16550A
lpt0 at 0x378-0x37f irq 7 on isa
lpt0: Interrupt-driven port
lp0: TCP/IP capable interface
pcm0 at 0x220 irq 5 drq 1 on isa
WARNING: sb: misconfigured secondary DMA channel
fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
fdc0: FIFO enabled, 8 bytes threshold
fd0: 1.44MB 3.5in
isic0 at 0xd80 irq 9 flags 0x3 on isa
isic0: Teles S0/16.3
isic0: ISAC 2085 Version A1/A2 or 2086/2186 Version 1.1 (IOM-2) (Addr=0x960)
isic0: HSCX 82525 or 21525 Version 2.1 (AddrA=0x160, AddrB=0x560)
vga0 at 0x3c0-0x3df maddr 0xa msize 131072 on isa
npx0 on motherboard
npx0: INT 16 interface
APIC_IO: Testing 8254 interrupt delivery
APIC_IO: routing 8254 via pin 2
IP packet filtering initialized, divert enabled, rule-based forwarding enabled, 
logging limited to 100 packets/entry
i4b: ISDN call control device attached
i4bisppp: 4 ISDN SyncPPP device(s) attached
i4bctl: ISDN system control port attached
i4bipr: 4 IP over raw HDLC ISDN device(s) attached (VJ header compression)
i4btel: 2 ISDN telephony interface device(s) attached
i4brbch: 4 raw B channel access device(s) attached
i4btrc: 4 ISDN trace device(s) attached
ccd0-3: Concatenated disk drivers
DUMMYNET initialized (980901) -- size dn_pkt 48
Waiting 8 seconds for SCSI devices to settle
SMP: AP CPU #1 Launched!
sa0 at ahc0 bus 0 target 4 lun 0
sa0:  Removable Sequential Access SCSI-2 device 
sa0: 4.807MB/s transfers (4.807MHz, offset 8)
da3 at ahc0 bus 0 target 1 lun 0
da3:  Fixed Direct Access SCSI-2 device 
da3: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled
da3: 1006MB (2061108 512 byte sectors: 64H 32S/T 1006C)
cd0 at ahc0 bus 0 target 5 lun 0
cd0:  Removable CD-ROM SCSI-2 device 
cd0: 10.0MB/s transfers (10.0MHz, offset 8)
cd0: Attempt to query device size failed: NOT READY, Medium not present
cd1 at ahc0 bus 0 target 6 lun 0
cd1:  Removable CD-ROM SCSI-2 device 
cd1: 10.0MB/s transfers (10.0MHz, offset 15)
cd1: Attempt to query device size failed: NOT READY, Medium not present
da1 at ahc1 bus 0 target 1 lun 0
da1:  Fixed Direct Access SCSI-2 device 
da1: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled
da1: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C)
da2 at ahc1 bus 0 target 2 lun 0
da2:  Fixed Direct Access SCSI-2 device 
da2: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled
da2: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C)
da0 at ahc0 bus 0 target 0 lun 0
da0:  Fixed Direct Access SCSI-2 device 
da0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled
da0: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C)
WARN

Re: Booting -current with new loader

[John Saunders]

I wrote:
> I'm off now to play now with rootdev and boot_askname.

Well, if I let the standard boot process occur, then I stop the loader and
set rootdev=disk3s1a: I can get the kernel running in single user mode
but mount refuses to remount / as rw. It's curious that the message about
changing the root device doesn't occur, time for debug output in the
kernel.

BTW boot_askname doesn't :-) I read some comments in the kernel source
to the effect "maybe we should prompt for a boot device here" so I
didn't expect it to work.

The next option is configuring my master drive on the secondary interface
as wd1 instead of wd2.

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. 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.

Cheers.
--++
. | John Saunders  - mailto:j...@nlc.net.au(EMail) |
,--_|\|- http://www.nlc.net.au/  (WWW) |
   /  Oz  \   |- 02-9489-4932 or 041-822-3814  (Phone) |
   \_,--\_/   | NHJ NORTHLINK COMMUNICATIONS - Supplying a professional,   |
 v| and above all friendly, internet connection service.   |
  ++

To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: Directory structure on current.freebsd.org

[Satoshi Asami]

Sorry I'm jumping into this in the middle.

 * Oliver Fromme  wrote:
 * >In releases/snapshots they're called "axp" and "x86", while in
 * >ports they're called "alpha" and "i386".

I'm not sure where this "axp/x86" thing is coming from, but we are
using "alpha" and "i386" in ports (and /usr/src/sys) because that's
what "uname -m" returns.

Satoshi

To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: panic: vinvalbuf: dirty bufs (during reboot, several times)

[Matthew Dillon]

:Hi !
:
:Since one or two weeks my system panics shortly before completely
:going down. Services like squid and inn take a little longer than
:usual to finish, I hear much disk activity.
:
:This happens usually if the system ran a day or so.
:
:What can I do to help ? Compile Kernel with debug infos ?
:
:BTW, yes I run an ELF kernel. Can't say exactly, if it's behaving
:like this after completely migrating to ELF.
:
:innd: server SHUTDOWN received
:boot() called on cpu#1
:syncing disks 8 7 1 done
:panic: vinvalbuf: dirty bufs
:mp_lock = 0001, cpuid = 0 lapic.id = 0100
:Debugger ("panic")
:
:trace:
:Debugger
:panic
:vinvalbuf
:...

Hmm.  Interesting, it's dying trying to fsync an FFS vnode.   Are you
by any chance running NFS ( client *or* server ) on this box?

Bjoern had a comment relating to the same sort of problem, which
I include below:

::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 nfs fs) generating a wrong sized recover
::file. After that the server panics on shutdown. Without triggering
::the bug it shuts down gracefully.
::
::I'll try to receipe a situation for easily reproducing this.
::
::  Bjoern

We have a couple of possibilities.

First, if either of you are compiling up your own kernels, please
remember that if you are using SOFTUPDATES, the SOFTUPDATES code
does *NOT* reside in /usr/src/sys but instead resides in 
/usr/src/contrib/sys ... when you update your kernel, also make sure
that /usr/src/contrib/sys is updated.

With that out of the way, if the vinvalbuf() problem still occurs
our best bet is if Bjoern can give us a repeatable vi SEGV / shutdown
sequence that results in the panic.

If I can reproduce it on one of my machines, I can probably figure out
what is going on.  If both of you are running NFS, it could possibly be
the NFS server forgetting to unbusy a page somewhere.  If you aren't
running NFS, it could be an actual bug in FFS somewhere(!).

-Matt

Matthew Dillon 



To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message