All - I just yesterday upgraded my laptop installation to 8.2 from the DVD, all seems to have worked, but the NFS server behavior and dhcp server behavior have changed. Under 8.1/kernel 2.4.19 I was able to Jumpstart Solaris clients from the laptop, using either bootp or dhcp. Now, I can't even "net boot" a Solaris client, and NFS seems to be at the heart of it. Under 8.1, I could check the RPC info and see that NFS was being served both udp and tcp, and both version 2 and 3, e.g. hogwarts:/home/markea 1> rpcinfo -p localhost program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 32768 status 100024 1 tcp 32768 status 100003 2 udp 2049 nfs <---------- Vers 2/udp 100003 3 udp 2049 nfs <---------- Vers 3/udp 100003 2 tcp 2049 nfs <---------- Vers 2/tcp 100003 3 tcp 2049 nfs <---------- Vers 3/tcp 100021 1 udp 32771 nlockmgr 100021 3 udp 32771 nlockmgr 100021 4 udp 32771 nlockmgr 100021 1 tcp 32769 nlockmgr 100021 3 tcp 32769 nlockmgr 100021 4 tcp 32769 nlockmgr 100005 1 udp 32772 mountd 100005 1 tcp 32770 mountd 100005 2 udp 32772 mountd 100005 2 tcp 32770 mountd 100005 3 udp 32772 mountd 100005 3 tcp 32770 mountd hogwarts:/home/markea 2> uname -a Linux hogwarts 2.4.19-4GB #1 Wed Nov 27 00:56:53 UTC 2002 i686 unknown hogwarts:/home/markea 3> rpm -qa | grep ^k_ k_deflt-2.4.19-274 Now on the 8.2 system/kernel 2.4.20, the behavior seems to be that only udp NFS is served by default hogwarts:/home/markea 1> rpcinfo -p localhost program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 32768 status 100024 1 tcp 32768 status 100005 1 udp 32771 mountd 100005 1 tcp 32769 mountd 100005 2 udp 32771 mountd 100005 2 tcp 32769 mountd 100005 3 udp 32771 mountd 100005 3 tcp 32769 mountd 100003 2 udp 2049 nfs <--------------- Vers 2/udp 100003 3 udp 2049 nfs <--------------- Vers 3/udp 100021 1 udp 32772 nlockmgr 100021 3 udp 32772 nlockmgr 100021 4 udp 32772 nlockmgr hogwarts:/home/markea 2> uname -a Linux hogwarts 2.4.20-4GB #1 Mon Mar 17 17:54:44 UTC 2003 i686 unknown unknown GNU/Linux hogwarts:/home/markea 3> rpm -qa | grep ^k_ k_deflt-2.4.20-39 So, it appears that the loss of the Version 3/tcp protocols has broken Jumpstart, and I can't find how to bring it back. Also, the earlier version of dhcpd seemed to work just fine with a setup I put together based on some samples I found on the 'net, but the new version gets errors at startup on the same file: Setup that worked: hogwarts:/home/markea 5> rpm -qa | grep dhcp dhcpcd-1.3.22pl1-128 dhcp-tools-1.2-212 dhcp-base-3.0.1rc9-59 dhcp-server-3.0.1rc9-59 New setup that fails: hogwarts:/home/markea 5> rpm -qa | grep dhcp dhcp-tools-1.2-274 dhcp-client-3.0.1rc10-32 dhcpcd-1.3.22pl4-27 dhcp-base-3.0.1rc10-32 dhcp-server-3.0.1rc10-32 Here is the config entries which cause the error: option space SUNW; # option SUNW.root-mount-options code 1 = text; option SUNW.rootopt code 1 = text; option SUNW.root-server-ip-address code 2 = ip-address; option SUNW.root-server-hostname code 3 = text; option SUNW.root-path-name code 4 = text; option SUNW.swap-server-ip-address code 5 = ip-address; option SUNW.swap-file-path code 6 = text; option SUNW.boot-file-path code 7 = text; option SUNW.posix-timezone-string code 8 = text; option SUNW.boot-read-size code 9 = unsigned integer 16; option SUNW.install-server-ip-address code 10 = ip-address; option SUNW.install-server-hostname code 11 = text; option SUNW.install-path code 12 = text; option SUNW.sysid-config-file-server code 13 = text; option SUNW.JumpStart-server code 14 = text; option SUNW.terminal-name code 15 = text; # # Sample setup to Jumpstart SPARCstation5 - Solaris 8 02/02 # class "SUNW.SPARCstation-5" { match if option vendor-class-identifier = "SUNW.SPARCstation-5"; option vendor-class-identifier = "SUNW.SPARCstation-5"; vendor-option-space; option SUNW.rootopt "vers=2"; option SUNW.root-server-hostname "gryffindor"; option SUNW.root-server-ip-address 192.168.1.21; option SUNW.root-path-name \ "/jumpstart/OS/Solaris_8_02-02/Solaris_8/Tools/Boot"; option SUNW.install-server-hostname "gryffindor"; option SUNW.install-server-ip-address 192.168.1.21; option SUNW.install-path "/jumpstart/OS/Solaris_8_02-02"; option SUNW.JumpStart-server "gryffindor:/jumpstart"; option SUNW.sysid-config-file-server \ "gryffindor:/jumpstart/Sysidcfg/Solaris_8"; option SUNW.terminal-name "vt100"; } Any ideas? HW is a Sony VAIO PCG-GRX580, P4M 1.8GHz, 512MB RAM, 30GB HD, Sony DVD/CD-RW, ATI Radeon 7500 LW @1600X1200 24bpp, now running SuSE Pro 8.2 (I like the KDE 3.1 stuff!). Mark Almeida
On Wed May 7 2003 5:20 pm, The Wizard wrote:
All - I just yesterday upgraded my laptop installation to 8.2 from the DVD, all seems to have worked, but the NFS server behavior and dhcp server behavior have changed. Under 8.1/kernel 2.4.19 I was able to Jumpstart Solaris clients from the laptop, using either bootp or dhcp. Now, I can't even "net boot" a Solaris client, and NFS seems to be at the heart of it.
snip<
Any ideas?
HW is a Sony VAIO PCG-GRX580, P4M 1.8GHz, 512MB RAM, 30GB HD, Sony DVD/CD-RW, ATI Radeon 7500 LW @1600X1200 24bpp, now running SuSE Pro 8.2 (I like the KDE 3.1 stuff!).
Mark Almeida
Would the section of the release notes for SuSE 8.2 about NFS and ACLs apply? ---- Changes in NFS: Access Control Lists SuSE Linux 8.2 also supports POSIX Access Control Lists over NFS. In order for that to work, both the client and server must be running SuSE Linux 8.2. The NFS ACL support uses the same protocol that is also used by Solaris. Therefore, ACLs also work between Linux and Solaris systems. Since the ACL protocol extensions cause some additional overhead in the NFS protocol, which also causes moderate additional network traffic, these protocol extensions can be deactivated by mounting NFS file systems with the `-o noacl' mount option. When this option is used, the client assumes that the mounted file system contains no ACLs, and also does not use the ACCESS remote procedure call, which is otherwise needed. Therefore, file systems mounted with `-o noacl' should not contain any ACLs at all. ---- Just a thought, Stan
On Thursday 08 May 2003 00:20, The Wizard wrote:
So, it appears that the loss of the Version 3/tcp protocols has broken Jumpstart, and I can't find how to bring it back.
Recompile the kernel, and change "provide NFS server over TCP support" to "y", it's under File systems->Network file systems
On Thursday 08 May 2003 06:40, Anders Johansson wrote:
On Thursday 08 May 2003 00:20, The Wizard wrote:
So, it appears that the loss of the Version 3/tcp protocols has broken Jumpstart, and I can't find how to bring it back.
Recompile the kernel, and change "provide NFS server over TCP support" to "y", it's under File systems->Network file systems
Anders - Should I try the latest kernel source from ftp:///ftp.suse.com/pub/people/mantel/next/RPM/ (2.4.20-62) or just start with the source on the 8.2 CDs? I haven't installed the source yet, as normally with 8.1 I was always able to use the pre-built kernel rpms. Mark Almeida
On Thursday 08 May 2003 20:51, The Wizard wrote:
Should I try the latest kernel source from
ftp:///ftp.suse.com/pub/people/mantel/next/RPM/ (2.4.20-62)
or just start with the source on the 8.2 CDs? I haven't installed the source yet, as normally with 8.1 I was always able to use the pre-built kernel rpms.
That's up to you. Just be advised that the people/mantel/next kernels are experimental and unsupported, so if you're running a production environment you're probably safer running the sources off the CD
participants (3)
-
Anders Johansson -
Stan Glasoe -
The Wizard