current kernel-- config issues

Hi;

I'm trying to get the -current kernel built so I can give
the latest userland a try;

However I'm unable to get even the minimal kernel to config.
 It looks like it was last modified middle Nov 2006.

I'm using -current userland from July 2005, from the latest
install CD from netbsd.org.  I don't see a pkgsrc tool
bundle which will update the config app itself...

Thanks for comments.  I'm sure it's my fault somehow.  I
haven't edited this particualt INSTALL kernel, although I
did first try adding the USB support pieces to a copy of it
(with the same errors-- and I get the same errors with
GENERIC).

I haven't done this for a while, but I've made this all work
before...

------------
qube# ls
CVS/            GENERIC         INSTALL         files.cobalt
   majors.cobalt   std.cobalt
qube# less INSTALL
qube# config INSTALL
../../../../conf/files:5: syntax error
../../../../conf/files:168: syntax error
../../../../ipkdb/files.ipkdb:5: syntax error
../../../../miscfs/procfs/files.procfs:3: syntax error
*** Stop.
qube# pwd
/usr/src/sys/arch/cobalt/conf
qube# which config
/usr/bin/config
-------------

also, while I'm here, is this all I need to add to get USB
support going?  I have a NEC chipset USB card installed.
Strangely, running adjustkernel with this in place comments
it all out :/
I'm following instructions I found for adding USB to 3.0.
--------
#####added 022307

options SOSEND_NO_LOAN
# USB Controller and Devices
options         USBVERBOSE      # verbose USB device
autoconfig messages

# PCI USB controllers
# The EHCI is not ready for prime time.
#ehci*  at pci? dev ? function ?        # Enhanced Host
Controller
ohci*   at pci? dev ? function ?        # Open Host
Controller
uhci*   at pci? dev ? function ?        # Universal Host
Controller (Intel)

# CardBus USB controllers
#ehci*  at cardbus? dev ? function ?    # Enhanced Host
Controller
#ohci*  at cardbus? dev ? function ?    # Open Host
Controller

# USB bus support
#usb*   at ehci?
usb*    at ohci?
usb*    at uhci?

# USB Hubs
uhub*   at usb?
uhub*   at uhub? port ? configuration ? interface ?

# USB Generic driver
ugen*   at uhub? port ?

# USB Mass Storage
umass*  at uhub? port ? configuration ? interface ?
scsibus* at umass?

####end added022307
---------------------

And adding to majors:
-----
device-major  usb    char 55      usb
device-major  uhid    char 56      uhid
device-major  ulpt    char 57      ulpt
device-major  ugen    char 64      ugen
device-major  ucom    char 66      ucom
device-major  urio    char 70      urio
device-major  uscanner  char 75      uscanner
------


Thanks in advance for the education.

Brian

On 2/23/07, bmcewencomcast.net <bmcewencomcast.net> wrote:
> ------------
> qube# ls
> CVS/            GENERIC         INSTALL        
files.cobalt    majors.cobalt   std.cobalt
> qube# less INSTALL
> qube# config INSTALL
> ../../../../conf/files:5: syntax error
> ../../../../conf/files:168: syntax error
> ../../../../ipkdb/files.ipkdb:5: syntax error
> ../../../../miscfs/procfs/files.procfs:3: syntax error
> *** Stop.
> qube# pwd
> /usr/src/sys/arch/cobalt/conf
> qube# which config
> /usr/bin/config
> -------------

(Caution, non developer speaking.)

I think this is the kind of thing you see when the kernel
source and
userland toolchain are not matched or close enough to the
same.

This is why I prefer to download the entire source tree,
then use
build.sh to first build the toolchain, then the kernel and
other
stuff. You are practically guaranteed to not have problems
with the
toolchain itself that way. User errors unfortunately are
something
else 

> also, while I'm here, is this all I need to add to get
USB support going?

I'd also like to know this, and I'd also like it to be part
of the
default kernel since it's been so long that we have worked
around the
"firmware kernel boot" limitations by booting the
bootloader.

Andy

On 2/23/07, Andy Ruhl <acruhlgmail.com> wrote:
> On 2/23/07, bmcewencomcast.net <bmcewencomcast.net> wrote:
> > also, while I'm here, is this all I need to add to
get USB support going?
>
> I'd also like to know this, and I'd also like it to be
part of the
> default kernel since it's been so long that we have
worked around the
> "firmware kernel boot" limitations by booting
the bootloader.

Let me know how this testing goes and I'll add it.  At this
point, I'm
likely to be adding another config file for netbooting on
the grounds
that things were blown out when the unfortunately
minimalistic 2nd
stage.  (We also lost the ability to boot/run off of the
second drive
with that introduction, fixing it is on my absurdly long
todo list.)

-=erik.