build.sh builds kernels with different permissions?

[Lars Nordlund <lars.nordlund%hem.utfors.se@localhost>]

Hi

I am seeing something funny when building i386 release. This is what
caught my eye:

===> Successful make release
--- obj ---
===> Kernel copy:      
/home/lars/tmp/current-release/i386/binary/kernel/netbsd-GENERIC.gz
./build.sh: cannot create 
/home/lars/tmp/current-release/i386/binary/kernel/netbsd-GENERIC.gz: permission 
denied
===> build.sh ended:   Sat Jun  7 00:33:16 CEST 2008

Huh?

Looking closer I see this:

===> lars@laphroaig:~/tmp/current-release/iso %ll 
/home/lars/tmp/current-release/i386/binary/kernel/netbsd-XEN2_DOM0.gz 
/home/lars/tmp/current-release/i386/binary/kernel/netbsd-INSTALL_XEN2_DOMU.gz
-r--r--r--  1 lars  staff  2953406 Jun  7 00:32 
/home/lars/tmp/current-release/i386/binary/kernel/netbsd-INSTALL_XEN2_DOMU.gz
-rw-r--r--  1 lars  staff  4388286 Jun  7
00:31 /home/lars/tmp/current-release/i386/binary/kernel/netbsd-XEN2_DOM0.gz

It appears that most of the i386 kernels have a read-only chmodness.

Is it my setup or is it intentional? Anyone else see this?

This is the command I am using:

./build.sh -j 2 -m i386 -T /home/lars/tmp/current-tools_NetBSD-i386 -O 
/home/lars/tmp/current-obj_i386 -D /home/lars/tmp/current-dest_i386 -R 
/home/lars/tmp/current-release -u -U release releasekernel=GENERIC


Best regards,
        Lars Nordlund