Upgrading old RH4 system to Debian 1.3.0
I thought it might be a good idea (which is usually the bad idea(tm)) to upgrade old RedHat4 system to Debian 1.3.0. So, this is a production machine, so I thought complete install is out of question and preferred method would be libc-upgrade and then proc-by-proc installation to make sure machine is usable all the time. Happily compiled statically linked dpkg and copied needed files to RH system. Ok, everything seems to be working (as always), but dpkg-deb fails with following error: gzip: stdout: Broken pipe dpkg-deb: subprocess gzip -dc returned error exit status 1 So, compiled statically linked gzip (just in case libc-5.4.33 isn't working ok with old RH4 binaries), tar and cpio. Still getting same errors. Has anyone solution for this (except doing complete install, which isn't really an option here)? -- Sami Laine To reply via mail, remove 'no.spam.' from my address. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
NIS maps for shadow passwords?
What is easiest way to enable NIS shadow map lookups for Debian 1.3.0? -- Sami Laine -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Ypbind problem
I have a small problem with ypbind. Master NIS server is running at 192.168.1.100 (network 192.168.96/255.255.255.224) and client machine is at 192.168.1.37 (network 192.168.1.32/255.255.255.224). When I start ypbind it tries to find out master server by broadcasts, even if I specify domain and server with 'ypbind -S office,192.168.1.100'. I have also placed following info into /etc/yp.conf: domain office nisserver 192.168.1.100 But I assume /etc/yp.conf doesn't do anything because Debian 1.3.0 doesn't have NIS support compiled into C-library. I found syntax of /etc/nsswitch.conf a bit confusing too, but I assume following entries enable NIS lookups for passwd and group: passwd: files db group: files db I other systems I've seen 'db' replaced with 'nis', but this should do same thing? Maybe someone has solved my problem and has been able to use NIS server from another subnetwork? -- Sami Laine -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
