[9fans] compiling a pcauth kernel

[9fans] compiling a pcauth kernel

[Rob Ristroph]

[-- Attachment #1: Type: text/plain, Size: 2299 bytes --]


Hi everybody,

I am attempting to follow the directions in wiki at:

http://plan9.bell-labs.com/wiki/plan9/Configuring_a_standalone_CPU_server/index.html

I inserted the bootdir section into the kernel configuration file as
directed; yet when I compile I get an error message (I have attached
the entire compile output at the end of this message):

8c -FVw bootpcauth.c
8l -o bootpcauth.out bootpcauth.8 ../boot/libboot.a8 print.8
../port/mkroot bootpcauth boot
bootpcauth.c:8 name not declared: configfactotum
bootpcauth.c:8 name not declared: connectfactotum
bootpcauth.c:8 name not declared: factotum
bootpcauth.c:9 name not declared: config
bootpcauth.c:9 name not declared: bin
bootpcauth.c:9 name not declared: disk
bootpcauth.c:9 name not declared: kfs
bootpcauth.c:9 name not declared: connect
bootpcauth.c:9 name not declared: bin
bootpcauth.c:9 name not declared: disk
bootpcauth.c:9 name not declared: kfs
too many errors
mk: ../boot/mkboot pcauth > ...  : exit status=rc 583: 8c 595: error
term% ls -l 9pcauth
ls: 9pcauth: '9pcauth' directory entry not found
term%

I looked in our archives and I found a previous message that might
have been someone complaining about the same issue:

https://lists.cse.psu.edu/archives/9fans/2003-February/022826.html

I tried the bootdir entries that people responded with in that thread,
and they gave similar errors.

I looked at that mkboot script which seems to make the bootpcauth.c
file, and if I understood what it was trying to do maybe I could just
write the bootpcauth.c file myself or fix the script.  I read the wiki
entries on compiling the kernel and bootdir.

I can compile a kernel if I simply omit the entire bootdir section
from the pcauth configuration file.  However, when it reboots it
requires me to tell it what kernel to boot from as well as the usual
[il,local] and user login, and I have other problems in later steps (
the "auth/changeuser bootes" step gives "changeuser: can't create user
bootes: access permission denied" ).

Is this bootdir stuff really necessary, and if so, where should I
start reading to make it work ?  Or has making a kernel without the
bootdir section succeeded, and I should focus on those error messages
?

Thanks in advance !

--Rob


[-- Attachment #2.1: Type: text/plain, Size: 266 bytes --]

The following attachment had content that we can't
prove to be harmless.  To avoid possible automatic
execution, we changed the content headers.
The original header was:

	Content-Type: application/octet-stream
	Content-Disposition: attachment; filename=mk.log

[-- Attachment #2.2: mk.log.suspect --]
[-- Type: application/octet-stream, Size: 4568 bytes --]

term% pwd
/sys/src/9/pc
term% mk 'CONF=pcauth'
../boot/libboot.a8 doesn't exist: assuming it will be an archive
rc ../port/mkdevc pcauth > pcauth.c
8a $AFLAGS l.s
8a $AFLAGS plan9l.s
8c -FVw cga.c
8c -FVw i8253.c
8c -FVw i8259.c
8c -FVw kbd.c
8a initcode.s
8l -l -R4 -o init.out initcode.8
{echo 'uchar initcode[]={'
 xd -1x init.out |
	sed -e 's/^[0-9a-f]+ //' -e 's/ ([0-9a-f][0-9a-f])/0x\1,/g'
 echo '};'} > init.h
8c -FVw memory.c
8c -FVw mmu.c
8c -FVw random.c
8c -FVw -I. ../port/rdb.c
8c -FVw trap.c
8c -FVw vga.c
8c -FVw ether82557.c
8c -FVw uarti8250.c
8c -FVw sdata.c
8c -FVw -I. ../port/devmnt.c
8c -FVw -I. ../ip/iproute.c
8c -FVw -I. ../port/devtls.c
8c -FVw -I. ../port/devdup.c
8c -FVw -I. ../port/devenv.c
8c -FVw -I. ../ip/tcp.c
8c -FVw apm.c
8c -FVw -I. ../port/devsd.c
8c -FVw vgax.c
8c -FVw devarch.c
8c -FVw -I. ../ip/ipifc.c
8c -FVw devether.c
8c -FVw -I. ../ip/chandial.c
8c -FVw -I. ../port/devsrv.c
8c -FVw -I. ../ip/icmp.c
8c -FVw -I. ../ip/ethermedium.c
8c -FVw -I. ../port/devcap.c
8c -FVw -I. ../port/devproc.c
8c -FVw dma.c
8c -FVw -I. ../port/devmouse.c
8c -FVw devrtc.c
8c -FVw devfloppy.c
8c -FVw -I. ../ip/ip.c
8c -FVw -I. ../ip/udp.c
8c -FVw -I. ../ip/ipv6.c
8c -FVw -I. ../port/devcons.c
8c -FVw -I. ../port/devpnp.c
8c -FVw -I. ../ip/il.c
8c -FVw -I. ../port/devuart.c
8c -FVw -I. ../ip/arp.c
8c -FVw uartpci.c
cp /386/bin/disk/kfs kfs.out
../port/mkroot kfs kfs
mkroot kfs kfs
mkroot kfs kfs done
8c -FVw screen.c
8c -FVw -I. ../ip/devip.c
8a $AFLAGS ptclbsum386.s
8c -FVw -I. ../port/devkprof.c
8c -FVw -I. ../ip/pktmedium.c
8c -FVw vgamach64xx.c
cp /386/bin/ip/ipconfig ipconfig.out
../port/mkroot ipconfig ipconfig
mkroot ipconfig ipconfig
mkroot ipconfig ipconfig done
8c -FVw -I. ../ip/ipaux.c
8c -FVw -I. ../port/devpipe.c
8a $AFLAGS apmjump.s
8c -FVw sdscsi.c
8c -FVw -I. ../ip/inferno.c
8c -FVw -I. ../port/devroot.c
cp /386/bin/auth/factotum factotum.out
../port/mkroot factotum factotum
mkroot factotum factotum
mkroot factotum factotum done
8c -FVw -I. ../ip/netlog.c
8c -FVw devvga.c
8c -FVw mouse.c
8c -FVw -I. ../port/devdraw.c
8c -FVw -I. ../port/devssl.c
8c -FVw -I. ../ip/nullmedium.c
8c -FVw -I. ../port/netif.c
8c -FVw pci.c
8c -FVw -I. ../ip/icmp6.c
8c -FVw -I. ../ip/netdevmedium.c
8c -FVw -I. ../port/alarm.c
8c -FVw -I. ../port/alloc.c
8c -FVw -I. ../port/allocb.c
8c -FVw -I. ../port/auth.c
8c -FVw -I. ../port/cache.c
8c -FVw -I. ../port/chan.c
8c -FVw -I. ../port/dev.c
8c -FVw -I. ../port/fault.c
8c -FVw -I. ../port/latin1.c
8c -FVw -I. ../port/nulledf.c
8c -FVw -I. ../port/page.c
8c -FVw -I. ../port/parse.c
8c -FVw -I. ../port/pgrp.c
8c -FVw -I. ../port/portclock.c
8c -FVw -I. ../port/print.c
8c -FVw -I. ../port/proc.c
8c -FVw -I. ../port/qio.c
8c -FVw -I. ../port/qlock.c
8c -FVw -I. ../port/rebootcmd.c
8c -FVw -I. ../port/segment.c
8c -FVw -I. ../port/swap.c
8c -FVw -I. ../port/sysfile.c
8c -FVw -I. ../port/sysproc.c
8c -FVw -I. ../port/taslock.c
8c -FVw -I. ../port/tod.c
8c -FVw -I. ../port/xalloc.c
8c -I../boot -FVw ../boot/bootauth.c
8c -I../boot -FVw ../boot/aux.c
8c -I../boot -FVw ../boot/boot.c
8c -I../boot -FVw ../boot/bootcache.c
8c -I../boot -FVw ../boot/bootip.c
8c -I../boot -FVw ../boot/local.c
8c -I../boot -FVw ../boot/embed.c
8c -I../boot -FVw ../boot/settime.c
8c -I../boot -FVw ../boot/sac.c
8c -I../boot -FVw ../boot/paq.c
8c -FVw main.c
8a $AFLAGS kfs.root.s
8a $AFLAGS ipconfig.root.s
8a $AFLAGS factotum.root.s
names=`{membername $newprereq}
ar vu ../boot/libboot.a8 $names
rm $names
ar: creating ../boot/libboot.a8
a - bootauth.8
a - aux.8
a - boot.8
a - bootcache.8
a - bootip.8
a - local.8
a - embed.8
a - settime.8
a - sac.8
a - paq.8
../boot/mkboot pcauth > bootpcauth.c
8c -FVw bootpcauth.c
8l -o bootpcauth.out bootpcauth.8 ../boot/libboot.a8 print.8
../port/mkroot bootpcauth boot
bootpcauth.c:8 name not declared: configfactotum
bootpcauth.c:8 name not declared: connectfactotum
bootpcauth.c:8 name not declared: factotum
bootpcauth.c:9 name not declared: config
bootpcauth.c:9 name not declared: bin
bootpcauth.c:9 name not declared: disk
bootpcauth.c:9 name not declared: kfs
bootpcauth.c:9 name not declared: connect
bootpcauth.c:9 name not declared: bin
bootpcauth.c:9 name not declared: disk
bootpcauth.c:9 name not declared: kfs
too many errors
mk: ../boot/mkboot pcauth > ...  : exit status=rc 583: 8c 595: error
term% ls -l 9pcauth
ls: 9pcauth: '9pcauth' directory entry not found
term%

Re: [9fans] compiling a pcauth kernel

[andrey mirtchovski]

this works for me (pcauth kernel):

bootdir
	bootpcauth.out boot
	/386/bin/ip/ipconfig
	/386/bin/auth/factotum
	/386/bin/disk/kfs

never really dug into it though. I was afraid to change the wiki since I
wasn't sure whether I'm not doing something wrong...

Re: [9fans] compiling a pcauth kernel

[andrey mirtchovski]

need to mention this too -- the kernels able to boot out of a fossil
partition have a much more elaborate 'bootdir' section. it may be worthy
looking at 'pcfl' (i think) to glean some more insight into what goes there
and why...

andrey

Re: [9fans] compiling a pcauth kernel

[David Presotto]

I just did

	cd /sys/src/9/pc
	mk 'CONF=pcauth'

on sources and it compiled without said errors.

Re: [9fans] compiling a pcauth kernel

[andrey mirtchovski]

he followed these instructions from the wiki
(http://plan9.bell-labs.com/wiki/plan9/Configuring_a_standalone_CPU_server/index.html):

--- paste ---
Standalone implies the server will boot from it's own kfs, hence kfs is
needed in the 'bootdir' section of kernel configuration. Also required in
this section is the factotum for Authentication.


bootdir
	factotum.hack factotum
	/386/bin/disk/kfs
--- /paste ---

I haven't had the guts to remove them from the Wiki, though I've known this
to be a bug...

andrey

On Mon, 30 Jun 2003, David Presotto wrote:

> I just did
>
> 	cd /sys/src/9/pc
> 	mk 'CONF=pcauth'
>
> on sources and it compiled without said errors.
>

Re: [9fans] compiling a pcauth kernel

[boyd, rounin]

> cd /sys/src/9/pc
> mk 'CONF=pcauth'

worked for me 'straight out of the box'.

Re: [9fans] compiling a pcauth kernel

[boyd, rounin]

now this is probably a silly question, but is there any reason i shouldn't
be about to have a pcauth server with a DHCP served address on its
ADSL interface?  i want to build an internal network on the other side.

just don't talk to me about RIPE nor my isp's interesting ideas about
network building and the dns etc ...

Re: [9fans] compiling a pcauth kernel

[okamoto]

> now this is probably a silly question, but is there any reason i shouldn't
> be about to have a pcauth server with a DHCP served address on its
> ADSL interface?  i want to build an internal network on the other side.

Because none replies this.
You mean, of course, only once at the first time to build Plan 9 system
behind ADSL?  ☺

Kenji

[9fans] Re: compiling a pcauth kernel

[Rob Ristroph]

I did a replica/pull and there is a different pcauth file, which has a
bootdir section.  I was able to compile a kernel just fine.  The
problem I reported may be gone, or may just not be exercised by the
new kernel configuration file.

--Rob

P.S.  I am now having a different problem, but I have to investigate
further before I can post a useful message.