|
|
|
|
| Author |
Message |
David Reichelt
Guest
|
 Posted: Fri Jun 01, 2007 4:04 pm Post subject: diskless sun3 client/ how to set up? |
 |
|
Hi everybody,
i want to run my sun3zoo without any harddisks, so i followed
http://sites.inka.de/pcde/help/sunos_network_boot.html to set up a boot
server.
this is how far the client comes:
| Quote: | b le()
Boot: le(0,0,0) |
Using IP Address 192.168.1.253 = C0A801FD
Booting from tftp server at 192.168.1.254 = C0A801FE
Downloaded 101800 bytes from tftp server.
Using IP Address 192.168.1.253 = C0A801FD
hostname: sun350
Boot: null domain name returned by bootparam server
server name '192.168.1.254'
root pathname '/export/root/sun350'
root on 192.168.1.254:/export/root/sun350 fstype nfs
Boot: vmunix
Size: 507912+123920+79144 bytes
SunOS Release 4.1.1 (MUNIX) #1: Sat Oct 13 08:59:27 PDT 1990
Copyright (c) 1983-1990, Sun Microsystems, Inc.
mem = 4096K (0x400000)
avail mem = 3260416
Ethernet address = 8:0:20:0:5f:9e
si0 at obio 0x140000 pri 2
st0 at si0 slave 32
st1 at si0 slave 40
st2 at si0 slave 24
st3 at si0 slave 16
sr0 at si0 slave 48
sd0 at si0 slave 0
sd1 at si0 slave 1
sd2 at si0 slave 8
sd3 at si0 slave 9
sd4 at si0 slave 16
sd6 at si0 slave 24
zs0 at obio 0x20000 pri 3
zs1 at obio 0x0 pri 3
le0 at obio 0x120000 pri 3
bwtwo0 at obmem 0x100000 pri 4
bwtwo0: resolution 1152 x 900
Initialize ram disk from device ( st%d[a-h] sr%d[a-h] sd%d[a-h] ):
where is the problem?
best regards,
David |
|
| Back to top |
|
 |
Fix your Windows Problems - FAST.
FREE Safe Scan Registry Check. Locate & Fix Errors in Minutes!
|
|
Barry Keeney
Guest
|
| Posted: Fri Jun 01, 2007 6:28 pm Post subject: Re: diskless sun3 client/ how to set up? |
|
|
David Reichelt <Freud-Schiller@gmx.net> wrote:
: Hi everybody,
: i want to run my sun3zoo without any harddisks, so i followed
: http://sites.inka.de/pcde/help/sunos_network_boot.html to set up a boot
: server.
I used to have 3-4 Sun 3/50's and 3/60's running this way, Let's
see if I can remember enough to be of some help.
What kind of system are you using for your boot server, Sun sparc,
BSD, linux, etc - OS/Version?
Looks like it good the kernel down, but not finding the rest
of the OS or the Swap file.
Did you create the swapfile and the OS shares/exports?
What about the device files for the client system, did you
create them as well?
Can you post the contents of the bootparams and nfs exports/shares?
--
Barry Keeney
Chaos Consulting
email barryk@chaoscon.com
"Rap is Square Dancing gone terribly, terribly Wrong...." |
|
| Back to top |
|
|
Dennis Grevenstein
Guest
|
| Posted: Fri Jun 01, 2007 11:19 pm Post subject: Re: diskless sun3 client/ how to set up? |
|
|
David Reichelt <Freud-Schiller@gmx.net> wrote:
| Quote: |
i want to run my sun3zoo without any harddisks, so i followed
http://sites.inka.de/pcde/help/sunos_network_boot.html to set up a boot
server.
this is how far the client comes:
Boot: vmunix
Size: 507912+123920+79144 bytes
SunOS Release 4.1.1 (MUNIX) #1: Sat Oct 13 08:59:27 PDT 1990
^^^^^ |
okay, now I have something. MUNIX is the install kernel which
works without swap space, but you should use the regular kernel.
gruss,
Dennis
--
Don't suffer from insanity...
Enjoy every minute of it. |
|
| Back to top |
|
|
David Reichelt
Guest
|
| Posted: Sat Jun 02, 2007 12:33 am Post subject: Re: diskless sun3 client/ how to set up? |
|
|
Dennis Grevenstein schrieb:
| Quote: | David Reichelt <Freud-Schiller@gmx.net> wrote:
i want to run my sun3zoo without any harddisks, so i followed
http://sites.inka.de/pcde/help/sunos_network_boot.html to set up a boot
server.
this is how far the client comes:
Boot: vmunix
Size: 507912+123920+79144 bytes
SunOS Release 4.1.1 (MUNIX) #1: Sat Oct 13 08:59:27 PDT 1990
^^^^^
okay, now I have something. MUNIX is the install kernel which
works without swap space, but you should use the regular kernel.
gruss,
Dennis
u were right again, |
now i get:
Boot: le(0,0,0)
Using IP Address 192.168.1.253 = C0A801FD
Booting from tftp server at 192.168.1.254 = C0A801FE
Downloaded 101800 bytes from tftp server.
Using IP Address 192.168.1.253 = C0A801FD
hostname: sun350
Boot: null domain name returned by bootparam server
server name '192.168.1.254'
root pathname '/export/root/sun350'
root on 192.168.1.254:/export/root/sun350 fstype nfs
Boot: vmunix
Size: 893160+189568+202104 bytes
SunOS Release 4.1.1 (GENERIC) #1: Sat Oct 13 06:05:48 PDT 1990
Copyright (c) 1983-1990, Sun Microsystems, Inc.
mem = 4096K (0x400000)
avail mem = 2621440
Ethernet address = 8:0:20:0:5f:9e
si0 at obio 0x140000 pri 2
st0 at si0 slave 32
st1 at si0 slave 40
st2 at si0 slave 24
st3 at si0 slave 16
sr0 at si0 slave 48
sd0 at si0 slave 0
sd1 at si0 slave 1
sd2 at si0 slave 8
sd3 at si0 slave 9
sd4 at si0 slave 16
sd6 at si0 slave 24
zs0 at obio 0x20000 pri 3
zs1 at obio 0x0 pri 3
le0 at obio 0x120000 pri 3
bwtwo0 at obmem 0x100000 pri 4
bwtwo0: resolution 1152 x 900
hostname: sun350
whoami: no domain name
root on 192.168.1.254:/export/root/sun350 fstype nfs
swap on 192.168.1.254:/export/swap/sun350 fstype nfs size 24576K
dump on 192.168.1.254:/export/swap/sun350 fstype nfs size 24552K
NFS server 192.168.1.254 not responding still trying
Information(for Barry)
the server is a u60 with stock solaris 9
etc/dfs/dfstab looks like this:
share -F nfs -o rw=sun350 /export/root/sun350
share -F nfs -o rw=sun350 /export/swap/
share -F nfs -o rw=sun350 /var/spool/mail
share -F nfs -o rw=sun350 /export/home
share -F nfs /export/exec
etc/bootparams looks like this:
Sun350 root=192.168.1.254:/export/root/sun350
swap=192.168.1.254:/export/swap/sun350 gateway=192.168.1.1:0xffffff00
and a tcpdump looks like this: (when the erorr comes up)
21:17:01.717188 IP SunUltra60 > sun350: udp
21:17:15.477896 IP sun350.536371469 > SunUltra60.nfs: 116 read [|nfs]
21:17:15.478489 IP SunUltra60.nfs > sun350.536371469: reply ok 1472 read
[|nfs]
21:17:15.478513 IP SunUltra60 > sun350: udp
21:17:15.478534 IP SunUltra60 > sun350: udp
21:17:15.478554 IP SunUltra60 > sun350: udp
21:17:15.478575 IP SunUltra60 > sun350: udp
21:17:15.478593 IP SunUltra60 > sun350: udp
21:17:35.477636 IP sun350.536371469 > SunUltra60.nfs: 116 read [|nfs]
21:17:35.478241 IP SunUltra60.nfs > sun350.536371469: reply ok 1472 read
[|nfs]
/dev/ of the client is fine
how /export/swap looks like
-bash-3.1# pwd
/export/swap
-bash-3.1# ls -l
Gesamt 49200
-rw------- 1 root other 25165824 Mai 28 17:27 sun350
-bash-3.1#
so that is it.
and thx everybody so far! i have a good feeling now |
|
| Back to top |
|
|
Dennis Grevenstein
Guest
|
| Posted: Sat Jun 02, 2007 12:50 am Post subject: Re: diskless sun3 client/ how to set up? |
|
|
David Reichelt <Freud-Schiller@gmx.net> wrote:
| Quote: |
the server is a u60 with stock solaris 9
etc/dfs/dfstab looks like this:
share -F nfs -o rw=sun350 /export/root/sun350
share -F nfs -o rw=sun350 /export/swap/
share -F nfs -o rw=sun350 /var/spool/mail
share -F nfs -o rw=sun350 /export/home
share -F nfs /export/exec
|
You will probably have to enable root access to some of these
NFS shares.
gruss,
Dennis
--
Don't suffer from insanity...
Enjoy every minute of it. |
|
| Back to top |
|
|
|
|
David Reichelt
Guest
|
| Posted: Sat Jun 02, 2007 2:56 pm Post subject: Re: diskless sun3 client/ how to set up? |
|
|
Dennis Grevenstein schrieb:
| Quote: | David Reichelt <Freud-Schiller@gmx.net> wrote:
the server is a u60 with stock solaris 9
etc/dfs/dfstab looks like this:
share -F nfs -o rw=sun350 /export/root/sun350
share -F nfs -o rw=sun350 /export/swap/
share -F nfs -o rw=sun350 /var/spool/mail
share -F nfs -o rw=sun350 /export/home
share -F nfs /export/exec
You will probably have to enable root access to some of these
NFS shares.
gruss,
Dennis
and again a step forward: |
| Quote: | b le()
Boot: le(0,0,0) |
Using IP Address 192.168.1.253 = C0A801FD
Booting from tftp server at 192.168.1.254 = C0A801FE
Downloaded 101800 bytes from tftp server.
Using IP Address 192.168.1.253 = C0A801FD
hostname: sun350
Boot: null domain name returned by bootparam server
server name '192.168.1.254'
root pathname '/export/root/sun350'
root on 192.168.1.254:/export/root/sun350 fstype nfs
Boot: vmunix
Size: 893160+189568+202104 bytes
SunOS Release 4.1.1 (GENERIC) #1: Sat Oct 13 06:05:48 PDT 1990
Copyright (c) 1983-1990, Sun Microsystems, Inc.
mem = 4096K (0x400000)
avail mem = 2621440
Ethernet address = 8:0:20:0:5f:9e
si0 at obio 0x140000 pri 2
st0 at si0 slave 32
st1 at si0 slave 40
st2 at si0 slave 24
st3 at si0 slave 16
sr0 at si0 slave 48
sd0 at si0 slave 0
sd1 at si0 slave 1
sd2 at si0 slave 8
sd3 at si0 slave 9
sd4 at si0 slave 16
sd6 at si0 slave 24
zs0 at obio 0x20000 pri 3
zs1 at obio 0x0 pri 3
le0 at obio 0x120000 pri 3
bwtwo0 at obmem 0x100000 pri 4
bwtwo0: resolution 1152 x 900
hostname: sun350
whoami: no domain name
root on 192.168.1.254:/export/root/sun350 fstype nfs
swap on 192.168.1.254:/export/swap/sun350 fstype nfs size 24576K
dump on 192.168.1.254:/export/swap/sun350 fstype nfs size 24552K
ifconfig: auto-revarp: bad address
mount: /usr: No such file or directory
checking filesystems
fsck: No such file or directory
Unknown error in reboot fsck.
WARNING - file systems have NOT been remounted read-write.
Use fsck to fix any file system problems, rebooting the
system if any problems are found with a mounted file system.
After file systems have fsck'ed cleanly, you can remount file
systems and finish single-user setup using "/etc/rc.single".
NFS write error 13 on host 192.168.1.254 fh 800008 2 a0000 4d1ba
3bdf910e a0000
4d132 53765edd
but after creating /export/root/sun350/usr to have a mountpoint it goes to
this
| Quote: | b le()
Boot: le(0,0,0) |
Using IP Address 192.168.1.253 = C0A801FD
Booting from tftp server at 192.168.1.254 = C0A801FE
Downloaded 101800 bytes from tftp server.
Using IP Address 192.168.1.253 = C0A801FD
hostname: sun350
Boot: null domain name returned by bootparam server
server name '192.168.1.254'
root pathname '/export/root/sun350'
root on 192.168.1.254:/export/root/sun350 fstype nfs
Boot: vmunix
Size: 893160+189568+202104 bytes
SunOS Release 4.1.1 (GENERIC) #1: Sat Oct 13 06:05:48 PDT 1990
Copyright (c) 1983-1990, Sun Microsystems, Inc.
mem = 4096K (0x400000)
avail mem = 2621440
Ethernet address = 8:0:20:0:5f:9e
si0 at obio 0x140000 pri 2
st0 at si0 slave 32
st1 at si0 slave 40
st2 at si0 slave 24
st3 at si0 slave 16
sr0 at si0 slave 48
sd0 at si0 slave 0
sd1 at si0 slave 1
sd2 at si0 slave 8
sd3 at si0 slave 9
sd4 at si0 slave 16
sd6 at si0 slave 24
zs0 at obio 0x20000 pri 3
zs1 at obio 0x0 pri 3
le0 at obio 0x120000 pri 3
bwtwo0 at obmem 0x100000 pri 4
bwtwo0: resolution 1152 x 900
hostname: sun350
whoami: no domain name
root on 192.168.1.254:/export/root/sun350 fstype nfs
swap on 192.168.1.254:/export/swap/sun350 fstype nfs size 24576K
dump on 192.168.1.254:/export/swap/sun350 fstype nfs size 24552K
ifconfig: auto-revarp: bad address
checking filesystems
but i disabled the filesystem checking in the fstab by putting "0 0"
behind every entry
after 4h of "checking filesystems" i aborted the boot process :-(
whats wrong here?
while working on the sun3 system i´m now testing sun4c to see if this is
an sun3 topic... |
|
| Back to top |
|
|
David Reichelt
Guest
|
| Posted: Sat Jun 02, 2007 10:48 pm Post subject: Re: diskless sun3 client/ how to set up? |
|
|
David Reichelt schrieb:
| Quote: | Dennis Grevenstein schrieb:
David Reichelt <Freud-Schiller@gmx.net> wrote:
the server is a u60 with stock solaris 9
etc/dfs/dfstab looks like this:
share -F nfs -o rw=sun350 /export/root/sun350
share -F nfs -o rw=sun350 /export/swap/
share -F nfs -o rw=sun350 /var/spool/mail
share -F nfs -o rw=sun350 /export/home
share -F nfs /export/exec
You will probably have to enable root access to some of these
NFS shares.
gruss,
Dennis
and again a step forward:
b le()
Boot: le(0,0,0)
Using IP Address 192.168.1.253 = C0A801FD
Booting from tftp server at 192.168.1.254 = C0A801FE
Downloaded 101800 bytes from tftp server.
Using IP Address 192.168.1.253 = C0A801FD
hostname: sun350
Boot: null domain name returned by bootparam server
server name '192.168.1.254'
root pathname '/export/root/sun350'
root on 192.168.1.254:/export/root/sun350 fstype nfs
Boot: vmunix
Size: 893160+189568+202104 bytes
SunOS Release 4.1.1 (GENERIC) #1: Sat Oct 13 06:05:48 PDT 1990
Copyright (c) 1983-1990, Sun Microsystems, Inc.
mem = 4096K (0x400000)
avail mem = 2621440
Ethernet address = 8:0:20:0:5f:9e
si0 at obio 0x140000 pri 2
st0 at si0 slave 32
st1 at si0 slave 40
st2 at si0 slave 24
st3 at si0 slave 16
sr0 at si0 slave 48
sd0 at si0 slave 0
sd1 at si0 slave 1
sd2 at si0 slave 8
sd3 at si0 slave 9
sd4 at si0 slave 16
sd6 at si0 slave 24
zs0 at obio 0x20000 pri 3
zs1 at obio 0x0 pri 3
le0 at obio 0x120000 pri 3
bwtwo0 at obmem 0x100000 pri 4
bwtwo0: resolution 1152 x 900
hostname: sun350
whoami: no domain name
root on 192.168.1.254:/export/root/sun350 fstype nfs
swap on 192.168.1.254:/export/swap/sun350 fstype nfs size 24576K
dump on 192.168.1.254:/export/swap/sun350 fstype nfs size 24552K
ifconfig: auto-revarp: bad address
mount: /usr: No such file or directory
checking filesystems
fsck: No such file or directory
Unknown error in reboot fsck.
WARNING - file systems have NOT been remounted read-write.
Use fsck to fix any file system problems, rebooting the
system if any problems are found with a mounted file system.
After file systems have fsck'ed cleanly, you can remount file
systems and finish single-user setup using "/etc/rc.single".
NFS write error 13 on host 192.168.1.254 fh 800008 2 a0000 4d1ba
3bdf910e a0000
4d132 53765edd
but after creating /export/root/sun350/usr to have a mountpoint it goes to
this
b le()
Boot: le(0,0,0)
Using IP Address 192.168.1.253 = C0A801FD
Booting from tftp server at 192.168.1.254 = C0A801FE
Downloaded 101800 bytes from tftp server.
Using IP Address 192.168.1.253 = C0A801FD
hostname: sun350
Boot: null domain name returned by bootparam server
server name '192.168.1.254'
root pathname '/export/root/sun350'
root on 192.168.1.254:/export/root/sun350 fstype nfs
Boot: vmunix
Size: 893160+189568+202104 bytes
SunOS Release 4.1.1 (GENERIC) #1: Sat Oct 13 06:05:48 PDT 1990
Copyright (c) 1983-1990, Sun Microsystems, Inc.
mem = 4096K (0x400000)
avail mem = 2621440
Ethernet address = 8:0:20:0:5f:9e
si0 at obio 0x140000 pri 2
st0 at si0 slave 32
st1 at si0 slave 40
st2 at si0 slave 24
st3 at si0 slave 16
sr0 at si0 slave 48
sd0 at si0 slave 0
sd1 at si0 slave 1
sd2 at si0 slave 8
sd3 at si0 slave 9
sd4 at si0 slave 16
sd6 at si0 slave 24
zs0 at obio 0x20000 pri 3
zs1 at obio 0x0 pri 3
le0 at obio 0x120000 pri 3
bwtwo0 at obmem 0x100000 pri 4
bwtwo0: resolution 1152 x 900
hostname: sun350
whoami: no domain name
root on 192.168.1.254:/export/root/sun350 fstype nfs
swap on 192.168.1.254:/export/swap/sun350 fstype nfs size 24576K
dump on 192.168.1.254:/export/swap/sun350 fstype nfs size 24552K
ifconfig: auto-revarp: bad address
checking filesystems
but i disabled the filesystem checking in the fstab by putting "0 0"
behind every entry
after 4h of "checking filesystems" i aborted the boot process :-(
whats wrong here?
while working on the sun3 system i´m now testing sun4c to see if this is
an sun3 topic...
|
same topic on the sun4c arch
a tcpdump on the server shows this:
19:16:48.242455 IP 192.168.1.153.netbios-dgm >
192.168.1.255.netbios-dgm: NBT UDP PACKET(138)
19:16:49.253865 arp who-has 192.168.1.1 (Broadcast) tell SunUltra60
19:16:49.254424 arp reply 192.168.1.1 is-at 00:04:e2:90:6b:83 (oui Unknown)
19:17:20.240623 IP SunUltra60.nfs > SunIPX-PU.1163765439: reply ok 96
getattr [|nfs]
19:17:20.264284 IP SunIPX-PU.1163765440 > SunUltra60.nfs: 108 getattr [|nfs]
19:17:20.264375 IP SunUltra60.nfs > SunIPX-PU.1163765440: reply ok 96
getattr [|nfs]
19:17:49.961090 IP SunUltra60.32841 > res1.netcologne.de.domain:
37807+[|domain]
19:18:25.982158 IP SunUltra60.32842 > res1.netcologne.de.domain:
24493+[|domain]
19:18:35.254365 IP SunIPX-PU.1163765441 > SunUltra60.nfs: 108 getattr [|nfs]
19:18:35.254793 IP SunUltra60.nfs > SunIPX-PU.1163765441: reply ok 96
getattr [|nfs]
19:18:40.265309 IP SunIPX-PU.1163765442 > SunUltra60.nfs: 108 getattr [|nfs]
19:18:40.265679 IP SunUltra60.nfs > SunIPX-PU.1163765442: reply ok 96
getattr [|nfs]
19:19:55.258294 IP SunIPX-PU.1163765443 > SunUltra60.nfs: 108 getattr [|nfs]
19:19:55.258712 IP SunUltra60.nfs > SunIPX-PU.1163765443: reply ok 96
getattr [|nfs]
19:19:55.264803 IP SunIPX-PU.1163765444 > SunUltra60.nfs: 108 getattr [|nfs]
19:19:55.264891 IP SunUltra60.nfs > SunIPX-PU.1163765444: reply ok 96
getattr [|nfs]
19:21:10.262624 IP SunIPX-PU.1163765445 > SunUltra60.nfs: 108 getattr [|nfs]
19:21:10.263051 IP SunUltra60.nfs > SunIPX-PU.1163765445: reply ok 96
getattr [|nfs]
19:21:20.273369 IP SunIPX-PU.1163765446 > SunUltra60.nfs: 108 getattr [|nfs]
19:21:20.273792 IP SunUltra60.nfs > SunIPX-PU.1163765446: reply ok 96
getattr [|nfs]
19:21:26.001641 IP SunUltra60.32844 > res1.netcologne.de.domain:
42183+[|domain]
19:22:35.266183 IP SunIPX-PU.1163765447 > SunUltra60.nfs: 108 getattr [|nfs]
19:22:35.266595 IP SunUltra60.nfs > SunIPX-PU.1163765447: reply ok 96
getattr [|nfs]
19:22:35.272686 IP SunIPX-PU.1163765448 > SunUltra60.nfs: 108 getattr [|nfs]
19:22:35.272769 IP SunUltra60.nfs > SunIPX-PU.1163765448: reply ok 96
getattr [|nfs]
19:23:50.270516 IP SunIPX-PU.1163765449 > SunUltra60.nfs: 108 getattr [|nfs]
19:23:50.270953 IP SunUltra60.nfs > SunIPX-PU.1163765449: reply ok 96
getattr [|nfs]
19:24:10.280534 IP SunIPX-PU.1163765450 > SunUltra60.nfs: 108 getattr [|nfs]
19:24:10.280966 IP SunUltra60.nfs > SunIPX-PU.1163765450: reply ok 96
getattr [|nfs]
19:25:25.273319 IP SunIPX-PU.1163765451 > SunUltra60.nfs: 108 getattr [|nfs]
19:25:25.273751 IP SunUltra60.nfs > SunIPX-PU.1163765451: reply ok 96
getattr [|nfs]
19:25:25.279841 IP SunIPX-PU.1163765452 > SunUltra60.nfs: 108 getattr [|nfs]
19:25:25.279927 IP SunUltra60.nfs > SunIPX-PU.1163765452: reply ok 96
getattr [|nfs]
19:26:40.277642 IP SunIPX-PU.1163765453 > SunUltra60.nfs: 108 getattr [|nfs]
19:26:40.278068 IP SunUltra60.nfs > SunIPX-PU.1163765453: reply ok 96
getattr [|nfs]
19:27:20.289476 IP SunIPX-PU.1163765454 > SunUltra60.nfs: 108 getattr [|nfs]
19:27:20.289904 IP SunUltra60.nfs > SunIPX-PU.1163765454: reply ok 96
getattr [|nfs]
19:28:35.288955 IP SunIPX-PU.1163765455 > SunUltra60.nfs: 108 getattr [|nfs]
19:28:35.289378 IP SunUltra60.nfs > SunIPX-PU.1163765455: reply ok 96
getattr [|nfs]
19:28:35.295466 IP SunIPX-PU.1163765456 > SunUltra60.nfs: 108 getattr [|nfs]
19:28:35.295551 IP SunUltra60.nfs > SunIPX-PU.1163765456: reply ok 96
getattr [|nfs]
19:29:50.293263 IP SunIPX-PU.1163765457 > SunUltra60.nfs: 108 getattr [|nfs]
19:29:50.293691 IP SunUltra60.nfs > SunIPX-PU.1163765457: reply ok 96
getattr [|nfs]
19:31:10.297217 IP SunIPX-PU.1163765458 > SunUltra60.nfs: 108 getattr [|nfs]
19:31:10.297642 IP SunUltra60.nfs > SunIPX-PU.1163765458: reply ok 96
getattr [|nfs]
19:31:10.303686 IP SunIPX-PU.1163765459 > SunUltra60.nfs: 108 getattr [|nfs]
19:31:10.303774 IP SunUltra60.nfs > SunIPX-PU.1163765459: reply ok 96
getattr [|nfs]
19:32:25.301553 IP SunIPX-PU.1163765460 > SunUltra60.nfs: 108 getattr [|nfs]
19:32:25.302056 arp who-has SunIPX-PU (Broadcast) tell SunUltra60
19:32:25.302736 arp reply SunIPX-PU is-at sunipx-pu
19:32:25.302758 IP SunUltra60.nfs > SunIPX-PU.1163765460: reply ok 96
getattr [|nfs]
19:32:25.308841 IP SunIPX-PU.1163765461 > SunUltra60.nfs: 108 getattr [|nfs]
19:32:25.308931 IP SunUltra60.nfs > SunIPX-PU.1163765461: reply ok 96
getattr [|nfs]
19:33:40.305881 IP SunIPX-PU.1163765462 > SunUltra60.nfs: 108 getattr [|nfs]
19:33:40.306313 IP SunUltra60.nfs > SunIPX-PU.1163765462: reply ok 96
getattr [|nfs]
19:35:29.749544 IP 192.168.1.153.netbios-dgm >
192.168.1.255.netbios-dgm: NBT UDP PACKET(138)
19:35:40.306819 IP SunIPX-PU.1163765463 > SunUltra60.nfs: 108 getattr [|nfs]
19:35:40.307249 IP SunUltra60.nfs > SunIPX-PU.1163765463: reply ok 96
getattr [|nfs]
19:35:40.313262 IP SunIPX-PU.1163765464 > SunUltra60.nfs: 108 getattr [|nfs]
19:35:40.313347 IP SunUltra60.nfs > SunIPX-PU.1163765464: reply ok 96
getattr [|nfs]
19:36:15.313967 IP SunIPX-PU.629 > 192.168.4.230.sunrpc: UDP, length 56
19:36:16.338013 arp reply SunUltra60 is-at 08:00:20:c5:00:92 (oui Unknown)
19:36:55.311150 IP SunIPX-PU.1163765465 > SunUltra60.nfs: 108 getattr [|nfs]
19:36:55.311562 IP SunUltra60.nfs > SunIPX-PU.1163765465: reply ok 96
getattr [|nfs]
19:36:55.317645 IP SunIPX-PU.1163765466 > SunUltra60.nfs: 108 getattr [|nfs]
19:36:55.317731 IP SunUltra60.nfs > SunIPX-PU.1163765466: reply ok 96
getattr [|nfs]
19:38:10.315472 IP SunIPX-PU.1163765467 > SunUltra60.nfs: 108 getattr [|nfs]
19:38:10.315900 IP SunUltra60.nfs > SunIPX-PU.1163765467: reply ok 96
getattr [|nfs]
this comes on fot hours and hours :-( |
|
| Back to top |
|
|
Dennis Grevenstein
Guest
|
| Posted: Sun Jun 03, 2007 10:06 pm Post subject: Re: diskless sun3 client/ how to set up? |
|
|
David Reichelt <Freud-Schiller@gmx.net> wrote:
| Quote: | getattr [|nfs]
19:38:10.315472 IP SunIPX-PU.1163765467 > SunUltra60.nfs: 108 getattr [|nfs]
19:38:10.315900 IP SunUltra60.nfs > SunIPX-PU.1163765467: reply ok 96
getattr [|nfs]
this comes on fot hours and hours :-(
|
You might want to try a different server, i.e. something
other than Solaris.
gruss,
Dennis
--
Don't suffer from insanity...
Enjoy every minute of it. |
|
| Back to top |
|
|
David Reichelt
Guest
|
| Posted: Mon Jun 04, 2007 12:31 pm Post subject: Re: diskless sun3 client/ how to set up? |
|
|
Dennis Grevenstein schrieb:
| Quote: | David Reichelt <Freud-Schiller@gmx.net> wrote:
getattr [|nfs]
19:38:10.315472 IP SunIPX-PU.1163765467 > SunUltra60.nfs: 108 getattr [|nfs]
19:38:10.315900 IP SunUltra60.nfs > SunIPX-PU.1163765467: reply ok 96
getattr [|nfs]
this comes on fot hours and hours :-(
You might want to try a different server, i.e. something
other than Solaris.
gruss,
Dennis
i used gentoo linux 2006.1(2.4.32) and everything works fine!!! |
i can´t believe it
THX a lot Dennis !!! |
|
| Back to top |
|
|
|
  |
Index
-> SUN |
All times are GMT
|
| Page 1 of 1 |
|
| |
Watched Topics
Search
Register
Log in to check your private messages
Profile
Log in
Memberlist
Usergroups