Woody change affecting openvt
It appears that something has changed in Woody which affects the behavior of
openvt. When rcS_fai calls task_setup() from /usr/share/fai/subroutines,
openvt is invoked as "openvt -c2; openvt -c3". On a system booted from the
nfsroot I built this morning (from a Debian mirror updated late last week),
I get this error for each openvt invocation:
> Usage: openvt [-c vtnumber] [-l] [-u] [-s] [-v] [-w] -- command_line
Replacing the openvt invocation with this seems to work as expected:
"openvt -c2 bash; openvt -c3 bash"
However, this does not appear to be the real issue. Reading the openvt
manpage, I find that it defaults to using the command named by the
environment variable "SHELL". However, it appears that SHELL is set but
*not* exported when FAI is running:
> sh-2.05a# echo $SHELL
> /bin/bash
> sh-2.05a# export -p | grep -i shell
> sh-2.05a# export -p | head -3
> export AUTOBOOT="YES"
> export BOOTFILE="/boot/fai/test01"
> export BOOT_IMAGE="FAI-BOOTP"
> sh-2.05a# openvt -c6
> Usage: openvt [-c vtnumber] [-l] [-u] [-s] [-v] [-w] -- command_line
> sh-2.05a# export SHELL
> sh-2.05a# openvt -c6
[this final invocation of openvt succeeds]
I might imagine this is due to some change in /sbin/init, but I don't quite
have time to chase it all down on my own.
Can anyone verify that the FAI install-time shells have SHELL not only set,
but exported? ("export -p | grep -i shell") If so, what version of init is
being used by your nfsroot? My nfsroot is using version "2.84-1".
Re: FAI for woody or potato WAS Re: Problems with bootp andself-compiled kernels
On Mon, 17 Dec 2001, Thomas Lange wrote: > > On Mon, 17 Dec 2001 16:42:14 +0100 (CET), Phil <[EMAIL PROTECTED]> said: > > > On Mon, 17 Dec 2001, Thomas Lange wrote: > >> FAI 2.2.3 is for potato, where the tar command needs -I, in > >> woody a new tar version needs -j. So it seems you using a mix > >> of potato and woody packages. > > > FAI 2.2.3 is the version distributed for woody and sid. > > FAI was first released after the potato was the stable release, so it > could not go into potato, but is always in the tree of unstable and > testing. But I wanted to support the stable Debian version. It is also > mentioned in the README, that the default templates and configurations > are for potato (See also NEWS file). > > Maybe the next version of FAI will be the "woody default" version and potato > support will be dropped. But I'm not sure when to drop potato support. There are for me 3 versions that can be used : - the server distrib - the nfsroot distrib - the installed distrib Why do we want them to be the same ? I don't see any reason. What I'd expect is that the fai package which is in the (where is in [potato,woody,sid]) repository work on a machine with distrib x. That mean that only scripts that are run on the server have to work for distrib . What about releasing different packages for each distrib version we want to install (we will suppose that nfsroot distrib=installed distrib) ? There could be a fai-common package with scripts that run on the intallation server, then fai-potato, a fai-woody and a fai-sid packages that contains scripts that will run on the installed machine. -- Philippe BiondiCartel Informatique Security Consultant/R&D http://www.cartel-info.fr Phone: +33 1 44 06 97 94Fax: +33 1 44 06 97 99 PGP KeyID:3D9A43E2 FingerPrint:C40A772533730E39330DC0985EE8FF5F3D9A43E2
FAI for woody or potato WAS Re: Problems with bootp and self-compiled kernels
> On Mon, 17 Dec 2001 16:42:14 +0100 (CET), Phil <[EMAIL PROTECTED]> said: > On Mon, 17 Dec 2001, Thomas Lange wrote: >> FAI 2.2.3 is for potato, where the tar command needs -I, in >> woody a new tar version needs -j. So it seems you using a mix >> of potato and woody packages. > FAI 2.2.3 is the version distributed for woody and sid. FAI was first released after the potato was the stable release, so it could not go into potato, but is always in the tree of unstable and testing. But I wanted to support the stable Debian version. It is also mentioned in the README, that the default templates and configurations are for potato (See also NEWS file). Maybe the next version of FAI will be the "woody default" version and potato support will be dropped. But I'm not sure when to drop potato support. -- Gruss Thomas
Re: Problems with bootp and self-compiled kernels
On Mon, 17 Dec 2001, Thomas Lange wrote: > > Btw, I tried to apt-get source fai-kernel. > > > the I option is used in tar and it should be -j : > > FAI 2.2.3 is for potato, where the tar command needs -I, in woody a > new tar version needs -j. So it seems you using a mix of potato and > woody packages. FAI 2.2.3 is the version distributed for woody and sid. -- Philippe BiondiCartel Informatique Security Consultant/R&D http://www.cartel-info.fr Phone: +33 1 44 06 97 94Fax: +33 1 44 06 97 99 PGP KeyID:3D9A43E2 FingerPrint:C40A772533730E39330DC0985EE8FF5F3D9A43E2
Re: Problems with bootp and self-compiled kernels
> On Fri, 14 Dec 2001 10:35:59 +0100 (CET), Phil <[EMAIL PROTECTED]> said: > Hi all! I wanted to add aic7xxx support in the boot kernel (I > don't know if it should have been loaded automatically as a > module, but it did not do so) but I was not able to boot because > the kernel did not send any bootp requests. So first try to solve your bootp problem before compiling a new kernel. Any logs available ? -- Gruss Thomas
Re: Problems with bootp and self-compiled kernels
> Btw, I tried to apt-get source fai-kernel. > the I option is used in tar and it should be -j : FAI 2.2.3 is for potato, where the tar command needs -I, in woody a new tar version needs -j. So it seems you using a mix of potato and woody packages. -- Gruss Thomas
Problems creating a woody nfsroot
Hi, It seems that fai-setup has some hardcoded potato-related pathes : # fai-setup Adding system user fai... Adding new user fai (103) with group nogroup. Creating home directory /home/fai. Generating public/private rsa1 key pair. Your identification has been saved in /home/fai/.ssh/identity. Your public key has been saved in /home/fai/.ssh/identity.pub. The key fingerprint is: d6:38:7f:d2:18:9d:14:f8:c5:ba:02:d1:32:2e:8d:5b fai@ /home/fai/.ssh/authorized_keys created. User account fai set up. Creating FAI nfsroot can take a long time and will need more than 130MB disk space in /usr/lib/fai/nfsroot. [...] (installing nfsroot with debootstrap) cp: cannot create regular file `usr/lib/perl5/Debian/Fai.pm': No such file or directory Moreover, I'm not sure of my fai.conf : -8<- FAI_ARCH=`dpkg --print-installation-architecture` ftpserver=ftp.uk.debian.org debdist=woody # distribution: potato, woody, sid FAI_DEBOOTSTRAP="$debdist http://$ftpserver/debian"; FAI_SOURCES_LIST="deb http://$ftpserver/debian $debdist main contrib non-free deb http://$ftpserver/debian $debdist/non-US main contrib non-free" NFSROOT_PACKAGES="ssh expect portmap libdetect0 discover reiserfsprogs dpkg-dev" FAI_ROOTPW="56hNVqht51tzc" SSH_IDENTITY=/home/pbi/.ssh/id_dsa.pub UTC=yes KERNELPACKAGE=/usr/lib/fai/kernel/kernel-image-2.2.19_BOOTP1_i386.deb KERNELVERSION=2.2.19 LOGUSER=fai FAI_REMOTESH=ssh FAI_REMOTECP=scp NFSROOT=/usr/lib/fai/nfsroot FAI_CONFIGDIR=/usr/share/fai -8<- Btw, the default value for FAI_CONFIGDIR is /usr/local/share/fai. Doesn't that sound weird for a package ? -- Philippe BiondiCartel Informatique Security Consultant/R&D http://www.cartel-info.fr Phone: +33 1 44 06 97 94Fax: +33 1 44 06 97 99 PGP KeyID:3D9A43E2 FingerPrint:C40A772533730E39330DC0985EE8FF5F3D9A43E2
