Bug 13307

Could you send us the kernel configuration file you are using for this
kernel?

Nick

On Sat, 21 Aug 1999 andrew@grillet98.freeserve.co.uk wrote:

> 
> >Number:         13307
> >Category:       kern
> >Synopsis:       Cant build kernet for 2.2.8
> >Confidential:   no
> >Severity:       non-critical
> >Priority:       low
> >Responsible:    freebsd-bugs
> >State:          open
> >Quarter:        
> >Keywords:       
> >Date-Required:
> >Class:          sw-bug
> >Submitter-Id:   current-users
> >Arrival-Date:   Sat Aug 21 15:20:01 PDT 1999
> >Closed-Date:
> >Last-Modified:
> >Originator:     Andrew Grillet
> >Release:        2.2.8
> >Organization:
> Home
> >Environment:
> >Description:
> I am trying to build the kernel, and have encountered a pile
> of error messages. These originate in the SCSI area and
> many refer to undefined symbols in the text area
> most symbols are something like '_scsi_xxxx'
> I am trying to build the worm device, but failed symbols are
> also in scsi host adaaptor modules, eg aha.c, bt.c etc.
> 
> >How-To-Repeat:
> 
> I can repeat it by trying to build the kernel again. 
> 
> I think I may have done somthing wrong while trying to
> istall the worm device, but the instructions are probably wrong
> anyway - more instructions are needed.
> >Fix:
> Can't :-(
> 
> Andrew
> 
> 
> >Release-Note:
> >Audit-Trail:
> >Unformatted:
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-bugs" in the body of the message
> 
> 

-- 
e-Mail: n_hibma@webweaving.org

Hi Andrew,

Nick's already asked for your kernel config file, but something else
that'd be useful is for you to describe _exactly_ what commands you type
and _exactly_ what messages you get back from each command. Whether you
cut'n'paste or use something like script(1) doesn't reall matter, so
long as you provide more precise info.

Later,
Sheldon.

Sheldon Hearn wrote:
> 
> Hi Andrew,
> 
> Nick's already asked for your kernel config file, but something else
> that'd be useful is for you to describe _exactly_ what commands you type
> and _exactly_ what messages you get back from each command. Whether you
> cut'n'paste or use something like script(1) doesn't reall matter, so
> long as you provide more precise info.
> 
much ftping and hacking later, I have a copy of my conf file. I ahve
added some theoretically helpful comments explaining my understanding
of the state of affairs. 

It is quite possible that the problem lies in my grasp of what is going
on
rather than a defect in code. However, I regard the docs as a necessary
part of the system. - after all, if it don't work, it don't work :-)

I have a new problem - yesterday, I tried to send several e-mails
on this issue, including one to Nick Hibma. I got a message from
freeserve (my ISP) that I was not allowed to send the messages, but 
they may have been sent anyway!

This is NOT FreeBSD's fault, but may explain several copies of some
e-mails and none of others :-( [I blame B. Gates - its ALL his fault].

Andrew

Comment 4 Sheldon Hearn 1999-10-01 13:17:08 UTC

State Changed
From-To: open->feedback

Any news on this one, Andre? 
Andrew, even. Sorry. :-) 

Comment 5 Sheldon Hearn 1999-10-04 08:37:30 UTC

State Changed
From-To: feedback->closed

Originator says that Joerg won't be working on RELENG_2_2 and 
will eventually try RELENG_3. 

Comment 6 Sheldon Hearn 1999-10-04 08:37:30 UTC

Responsible Changed
From-To: freebsd-bugs->joerg

Apparently, Joerg's the man who might once have been in a position 
to look at this. :-)