NetBSD 4.0 release config

I'm just trying to cross-compile a new hpcsh kernel using
the NetBSD 
4.0 release sources on an i386 machine.  It works fine if I
use the 
default GENERIC config that comes with 4.0, but it won't
handle some 
of the options I had in my previous (3.99.8) kernel.  Here
is a diff 
between the version that worked (i.e., with the offending
options 
commented out), and the version I would have liked to
compile.

132c132
< file-system	SMBFS		# experimental - CIFS; also needs
nsmb (below) - uncomment jmw
---
> #file-system	SMBFS		# experimental - CIFS; also needs
nsmb (below) - uncomment jmw
163,168c163,168
< options         NFS_BOOT_BOOTSTATIC 
< options        
NFS_BOOTSTATIC_MYIP=""192.168.0.165""

< #options        NFS_BOOTSTATIC_GWIP
"1.2.3.254" 
< #options        NFS_BOOTSTATIC_MASK
"255.255.255.0" 
< options        
NFS_BOOTSTATIC_SERVADDR=""192.168.0.162"&qu
ot; 
< options        
NFS_BOOTSTATIC_SERVER=""hpnetbsd:/honk/export/680
current_nfs"" 
---
> #options         NFS_BOOT_BOOTSTATIC 
> #options        
NFS_BOOTSTATIC_MYIP=""192.168.0.165""

> ##options        NFS_BOOTSTATIC_GWIP
"1.2.3.254" 
> ##options        NFS_BOOTSTATIC_MASK
"255.255.255.0" 
> #options        
NFS_BOOTSTATIC_SERVADDR=""192.168.0.162"&qu
ot; 
> #options        
NFS_BOOTSTATIC_SERVER=""hpnetbsd:/honk/export/680
current_nfs"" 
337c337
< pseudo-device	irframetty		# IrDA frame line discipline
---
> #pseudo-device	irframetty		# IrDA frame line
discipline
344c344
< pseudo-device	nsmb			# experimental - SMB requester -
uncommented jmw
---
> #pseudo-device	nsmb			# experimental - SMB requester -
uncommented jmw


You see that the options build.sh didn't like (because it
couldn't 
find the corresponding *.c source files) were for smbfs
support, 
static boot support, and irda support.  Is the fact that
these don't 
work anymore intentional, or were these sources somehow
inadvertently 
omitted?  I'm particularly keen on getting the smbfs support
going, 
and also the static boot.  I never actually used the IRDA
support, 
though I had included it in my kernel config, so I haven't
really even 
verified for myself that it works.

Any advice would be appreciated here.

Is anyone else running 4.0 release on a Jornada 680/690?

Thanks,
Mike

On Wed, Dec 26, 2007 at 13:13:52 -0500, Michael Wileman
wrote:

> I'm just trying to cross-compile a new hpcsh kernel
using the NetBSD 
> 4.0 release sources on an i386 machine.  It works fine
if I use the 
> default GENERIC config that comes with 4.0, but it
won't handle some 
> of the options I had in my previous (3.99.8) kernel. 
Here is a diff 
> between the version that worked (i.e., with the
offending options 
> commented out), and the version I would have liked to
compile.
> 
> 132c132
> < file-system	SMBFS		# experimental - CIFS; also
needs nsmb 
> (below) - uncomment jmw
> ---
> >#file-system	SMBFS		# experimental - CIFS; also
needs nsmb 
> >(below) - uncomment jmw
> 163,168c163,168
> < options         NFS_BOOT_BOOTSTATIC 
> < options        
NFS_BOOTSTATIC_MYIP=""192.168.0.165""

> < #options        NFS_BOOTSTATIC_GWIP
"1.2.3.254" 
> < #options        NFS_BOOTSTATIC_MASK
"255.255.255.0" 
> < options        
NFS_BOOTSTATIC_SERVADDR=""192.168.0.162"&qu
ot; 
> < options         
>
NFS_BOOTSTATIC_SERVER=""hpnetbsd:/honk/export/680
current_nfs"" ---
> >#options         NFS_BOOT_BOOTSTATIC 
> >#options        
NFS_BOOTSTATIC_MYIP=""192.168.0.165""

> >##options        NFS_BOOTSTATIC_GWIP
"1.2.3.254" 
> >##options        NFS_BOOTSTATIC_MASK
"255.255.255.0" 
> >#options        
NFS_BOOTSTATIC_SERVADDR=""192.168.0.162"&qu
ot; 
> >#options         
>
>NFS_BOOTSTATIC_SERVER=""hpnetbsd:/honk/export
/680current_nfs"" 
> 337c337
> < pseudo-device	irframetty		# IrDA frame line
discipline
> ---
> >#pseudo-device	irframetty		# IrDA frame line
discipline
> 344c344
> < pseudo-device	nsmb			# experimental - SMB 
> requester - uncommented jmw
> ---
> >#pseudo-device	nsmb			# experimental - SMB 
> >requester - uncommented jmw
> 
> 
> You see that the options build.sh didn't like (because
it couldn't 
> find the corresponding *.c source files) were for smbfs
support, 
> static boot support, and irda support.  Is the fact
that these don't 
> work anymore intentional, or were these sources somehow
inadvertently 
> omitted?  I'm particularly keen on getting the smbfs
support going, 
> and also the static boot.  I never actually used the
IRDA support, 
> though I had included it in my kernel config, so I
haven't really even 
> verified for myself that it works.
> 
> Any advice would be appreciated here.

What are the error messages when you try to compile that
config?  I've
tweaked GENERIC to include the options you want and the
kernel
compiled just fine.

SY, Uwe
-- 
uwestderr.spb.ru                       |       Zu Grunde
kommen
http://snark.ptc.spbu.
ru/~uwe/          |       Ist zu Grunde gehen

On Thu, 27 Dec 2007, Valeriy E. Ushakov wrote:

> On Wed, Dec 26, 2007 at 13:13:52 -0500, Michael Wileman
wrote:
>
>> I'm just trying to cross-compile a new hpcsh kernel
using the NetBSD
>> 4.0 release sources on an i386 machine.  It works
fine if I use the
>> default GENERIC config that comes with 4.0, but it
won't handle some
>> of the options I had in my previous (3.99.8)
kernel.  Here is a diff
>> between the version that worked (i.e., with the
offending options
>> commented out), and the version I would have liked
to compile.
>>
>> Any advice would be appreciated here.
>
> What are the error messages when you try to compile
that config?  I've
> tweaked GENERIC to include the options you want and the
kernel
> compiled just fine.

Thanks, Uwe.  The error messages were all about missing
files.  It 
turns out that none of the tar archive source collections is
complete 
except for -current.  When I downloaded one set of the 4.0
sources 
then updated it using CVS, everything compiled with no
problem.  I 
don't know why all the files weren't in the archives.

I avoided using the -current sources because someone else I
know who 
works in the NetBSD project told me that -current was
undergoing some 
major changes, and now might not be a good time to use it
unless I 
wanted to participate in the debugging. 

Mike

On Wed, Dec 26, 2007 at 20:02:19 -0500, Michael Wileman
wrote:

> I avoided using the -current sources because someone
else I know who 
> works in the NetBSD project told me that -current was
undergoing some 
> major changes, and now might not be a good time to use
it unless I 
> wanted to participate in the debugging. 



I dearly wish I had more time ATM to play with the
power-management
work by Jared and Joerg that hit the trunk recently so that
hpcsh has
real suspend.

Re IrDA you mentioned in your original message - I still
need to make
scif(4) support more that one port and then I think irda
should just
work.

PS: www, rat races work...

SY, Uwe
-- 
uwestderr.spb.ru                       |       Zu Grunde
kommen
http://snark.ptc.spbu.
ru/~uwe/          |       Ist zu Grunde gehen

On Thu, 27 Dec 2007, Valeriy E. Ushakov wrote:

> On Wed, Dec 26, 2007 at 20:02:19 -0500, Michael Wileman
wrote:
>
>> I avoided using the -current sources because
someone else I know who
>> works in the NetBSD project told me that -current
was undergoing some
>> major changes, and now might not be a good time to
use it unless I
>> wanted to participate in the debugging. 
>
> 
>
> I dearly wish I had more time ATM to play with the
power-management
> work by Jared and Joerg that hit the trunk recently so
that hpcsh has
> real suspend.
>
> Re IrDA you mentioned in your original message - I
still need to make
> scif(4) support more that one port and then I think
irda should just
> work.

Real suspend would be a killer app.  As it is now, I shut
down netbsd 
every time I get on a plane and reboot later to save the
battery. 
IrDA working would be fun, too.  I still have one of those
old cell 
phones which can be used as a GPRS modem over IR, but that
would 
really just be the icing on the cake.

I'll be happy if I just manage to upgrade my 3.99.8 system
to 4.0 
(plus moving it to a much larger CF) without major
headaches.  Stay 
tuned.

Mike