Re: Problem with package removal...
Henning Sprang wrote: On 2/16/07, Carl J. Van Arsdall [EMAIL PROTECTED] wrote: Is there a way I can tell fai to only remove the packages I explicitly tell it to? Are you sure that the things you want to do work correctly, depency-wise? Well, they had for a long time anyhow. Ant is a java package, and I install java, I just don't know gnu java, I use sun java (which can't live in the main apt repositories cause of the software license). I imagine that at one point in time, Ant wasn't dependent on gcj, but perhaps they added it. Sounds quite reasonable that ant depends on some java base package, and therefore is removed when you throw java base packages away. FAI doesn't circumvent dependencies normally, it uses normal apt and aptitude calls. I am not sure if there is something to force doing things against dependencies. Alright, its not too much of a pain. gcj will install things into my path, I just need to unlink them and put links to the sun java. Nothing a script can't do, sometimes I just wish things wouldn't get fixed. Thanks, -carl
Problem with package removal...
Hey, I have an issue where a package I am choosing to install is being removed, indirectly when removing a package I don't know. The system didn't used to do this one, but maybe someone fixed the package dependencies or something. So here's my conf file: PACKAGES aptitude AMD64 memtest86+ udev openssh-server rsync cvs cvs2cl mkisofs sudo ntp ntpdate bzip2 vim linux32 ncurses-dev ant ibm-j2sdk1.4 ant-optional libxerces-java libxml-commons-resolver1.1-java python pyro linux-image-2.6.20-fai-client ibm-j2sdk1.4 lm-sensors libsensors3 rpm makedev make ia32-libs PACKAGES aptitude DHCPC dhcp3-client PACKAGES aptitude GRUB grub lilo- PACKAGES aptitude LILO lilo grub- PACKAGES remove gcj-4.1-base libgcj-common libgcj7-0 libgcj7-jar java-gcj-compat Basically, there are several java packages I install for the class AMD64. I dunno exactly what happens, but in the process of all this stuff, gcj-base gets pulled down (or it happens somewhere else). I don't want this package, so I remove it, but this seems to take ant, ant-optional, and a couple other java related packages with it. Is there a way I can tell fai to only remove the packages I explicitly tell it to? -carl -- Carl J. Van Arsdall [EMAIL PROTECTED] Build and Release MontaVista Software
Re: Docu update
Oliver Osburg wrote: Hi Carl, thanks for interest! Best would be to put these things in the wiki. If you do not have an account (I did not check) mail to: [EMAIL PROTECTED] regards, oliver Alright, I summarized the ideas a bit and added them to the wiki page. Please feel free to build on those and hopefully we can get some more information in the docs. -carl -- Carl J. Van Arsdall [EMAIL PROTECTED] Build and Release MontaVista Software
Re: Docu update
Oliver Osburg wrote: Hi, I plan to do the messy work to update the documentation. My first step was to work through the wish- and buglist on http://faiwiki.informatik.uni-koeln.de/index.php/Etch-doc-todo Basic plan is first to fix all of the bugs in it (wrong paths in descriptions, etc, etc) and then exend the guide _a little_ according to the wishlist. Basic comments, suggestions? I don't know if I missed this in the manual or if its just not there, but I thought it would have been useful to have a Scripting for FAI type of guide. This guide would define various internal variables like $target, the appropriate way to exit a bash script for FAI (like a description of the method used in the examples) things like that. Perhaps even a simple and a complex script demonstrating the capabilities and the documentation to support things that are unique (or necessary) to FAI. That might go beyond a little, I'd be willing to help/edit too, but I don't know enough of what's going on to write that document myself. There's also a howto on the wiki about configuring/compiling extra kernels, I think that would be a useful addition to the manual how to make a kernel that covers necessary or recommended options for install and client kernels, and adding them to your local apt repository using a command like reprepro. (again, all stuff someone could figure out, but that would have helped me when i was most clueless, especially if all of that information had been in a single place instead of scattered). That's another one I can help with (or update the wiki page, and put a link to it in the manual, i don't know how you guys like to approach docs). A third thing on my wishlist: supporting heterogeneous computing farms (having one fai server doing both i386/amd64 and the special steps to take in order to set that up). Maybe an entry in an FAQ? And the last thing, a high-level scripts and defaults put into fai. This might be one i missed in the manual too (i feel like i read it a million times, but something always eludes me and it has been a while, I don't remember all of what is in there). What i'm talking about here is how by default nodes will get the class: FAIBASE. Following that, the scripts in /srv/fai/config/scripts/FAIBASE are executed and may alter settings that a user cares about.Again, I know you could just go and read the scripts, but it would be cool to know how the system would work right out of the box and what scripts you may want to edit before really digging into each script. Ah, sorry for so much, I guess I really like documentation. I'm also happy to help where I can. -carl -- Carl J. Van Arsdall [EMAIL PROTECTED] Build and Release MontaVista Software
Re: Strange error w/ fai-mirror
Michael Tautschnig wrote: [snip] Hmm, for the fix: It probably suffices to choose different mirror directories rather than different machines, but that's up to you. Well, its funny you mention that. I do have two different mirror directories. I have a /srv/fai/mirror and a /srv/fai/mirror64. I'm honestly not sure how /srv/fai/mirror ended up containing both arches in it. Before when i had done things, I had noticed that various fai scripts would detect my architecture and download accordingly. For example, I can't make an nfsroot for a 32bit machine on the 64 bit machine, at least I don't know how. What I had tried this time was to fake it out using debian's linux32 package and running the command: #linux32 fai-mirror /srv/fai/mirror Where /srv/fai/mirror is a completely empty directory (i run an rm -rf /srv/fai/mirror/* before hand). Granted my package_config/DEFAULT contains packages for both i386 and amd64, I assumed (or hoped) that it would detect the architecture and build the appropriate mirror. It appears to have attempted to build mirrors for both archs and then failed right at the end, but I haven't read into the script enough to really understand what's going on, which would be my next step. To really fix it please file a bug with the Debian BTS to get this issue solved as soon as possible, it probably doesn't even take too much effort. For this bug I would report that fai-mirror fails when detecting two archs in a mirror? That seems like one bug (i.e. better error message). I also think I'm going to read into this a little more (when i have time) to see if I can figure out why fai-mirror is populating /srv/fai/mirror with more than one arch or would that type of investigation be generally discouraged? (I'm a bit new to open source and contributing to projects, but would like to help more if i could) Thanks for your help, Carl -- Carl J. Van Arsdall [EMAIL PROTECTED] Build and Release MontaVista Software
Strange error w/ fai-mirror
I'm running 3.1.6. After running the command and some downloading the script produces an error... [apt doing stuff.] Calling apt-move /usr/bin/fai-mirror: line 319: $pfile: ambiguous redirect overlord:/srv/fai/config/package_config# Is this something I've done wrong or a problem with the script? -carl -- Carl J. Van Arsdall [EMAIL PROTECTED] Build and Release MontaVista Software
Re: Strange error w/ fai-mirror
Michael Tautschnig wrote: I'm running 3.1.6. After running the command and some downloading the script produces an error... [apt doing stuff.] Calling apt-move /usr/bin/fai-mirror: line 319: $pfile: ambiguous redirect overlord:/srv/fai/config/package_config# Is this something I've done wrong or a problem with the script? Definitely a problem of the script as it should deal with such situations properly, but in essence it means that pfile=$(find $mirrordir/dists -name Packages) returns more than one match (or none?) Could you try this find command manually after the script has failed? $mirrordir is the directory you are using for creating a mirror. Thanks, Michael Sure enough, it was finding two dists. /srv/fai/mirror/dists/etch/main/binary-i386/Packages /srv/fai/mirror/dists/etch/main/binary-amd64/Packages I use this machine to do fai installations for both 32bit and 64bit machines. Originally I set things up on original machines and copied them over. I was hoping to make things work on a single machine without having to set things up on two different machines. For a workaround i'll continue to do things on separate machines (a 32bit and a 64bit) and copy the results over to my server unless anyone has a better suggestion? Thanks, Carl p.s. Thanks to everyone that works on fai, its incredibly useful. -- Carl J. Van Arsdall [EMAIL PROTECTED] Build and Release MontaVista Software
Extra partition being created
It would appear to me as though somehow an extra partition is being created during the disk setup. Here is my partition setup file, the partition.sda from the logs, is there a script somewhere adding an extra partition? #disk_config/FAIBASE # generic disk configuration for one small disk # disk size from 500Mb up to what you can buy today # # type mountpoint size in mb [mount options] [;extra options] disk_config disk1 primary / 3000- rw,errors=remount-ro ; -c -j ext3 logical swap 1000 rw # logical /homepreserve9 rw,nosuid; -m 1 -j ext3 #logs/partition.sda glue:/var/log/fai/node-27/last# cat partition.sda # partition table of device: /dev/sda unit: sectors /dev/sda1 : start=63, size= 33784632, Id= 83, bootable /dev/sda2 : start= 33784695, size= 2056320, Id= 5 /dev/sda3 : start= 0, size= 0, Id= 0 /dev/sda4 : start= 0, size= 0, Id= 0 /dev/sda5 : start= 33784758, size= 2056257, Id= 82 The partition on /dev/sda2 is extra and not something I defined. I just want one big partition and a 1 gig swap, is my configuration wrong? Furthermore, I looked at the partition table via fdisk, these partitions are assigned to the same starting point? Command (m for help): p Disk /dev/sda: 18.3 GB, 18351967232 bytes 255 heads, 63 sectors/track, 2231 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1210316892316 83 Linux /dev/sda221042231 10281605 Extended /dev/sda521042231 1028128+ 82 Linux swap / Solaris Thanks, -carl -- Carl J. Van Arsdall [EMAIL PROTECTED] Build and Release MontaVista Software
Re: Extra partition being created
Michael Tautschnig wrote: It would appear to me as though somehow an extra partition is being created during the disk setup. Here is my partition setup file, the partition.sda from the logs, is there a script somewhere adding an extra partition? #disk_config/FAIBASE # generic disk configuration for one small disk # disk size from 500Mb up to what you can buy today # # type mountpoint size in mb [mount options] [;extra options] disk_config disk1 primary / 3000- rw,errors=remount-ro ; -c -j ext3 logical swap 1000 rw # logical /homepreserve9 rw,nosuid; -m 1 -j ext3 #logs/partition.sda glue:/var/log/fai/node-27/last# cat partition.sda # partition table of device: /dev/sda unit: sectors /dev/sda1 : start=63, size= 33784632, Id= 83, bootable /dev/sda2 : start= 33784695, size= 2056320, Id= 5 /dev/sda3 : start= 0, size= 0, Id= 0 /dev/sda4 : start= 0, size= 0, Id= 0 /dev/sda5 : start= 33784758, size= 2056257, Id= 82 The partition on /dev/sda2 is extra and not something I defined. I just want one big partition and a 1 gig swap, is my configuration wrong? Furthermore, I looked at the partition table via fdisk, these partitions are assigned to the same starting point? /dev/sda2 is what you implictly requested - an extended partition (you said the swap partition should be a logical one, so setup_harddisks inferred an extend partition must be created). Oh, I see, because I said it was a logical disk so an extended partition had to be created to house the logical disk. Its been a while since I've done some of this stuff, but is that more or less correct? -carl -- Carl J. Van Arsdall [EMAIL PROTECTED] Build and Release MontaVista Software
And a question about writing scripts
Hey, thanks for everyone's patience with me on this list, I've had a lot of questions and you've all been very helpful. I'm just about done with my FAI setup, but i'm having an issue with the scripts. I have a series of bash scripts I wish to run. From what I understood, I could label them 10-script.sh 11-script.sh 12-script.sh and so on and so forth. And as I understand it, this is done per class, so DEFAULT would execute 10-13 FAIBASE would execute 10-13 I386 would execute 10-13 Or whatever the numbers were (i'm just trying to illustrate my understanding, please correct me if i'm wrong). Now to my problem. I use a couple classes for scripts, DEFAULT, FAIBASE, I386. In two of my directories not all scripts are being executed. In the default directory it executes 10, 11 and 20, but not 12. In my I386 directory it executes 22 but not 23. Below are the contents of these directories, can anyone tell me what I'm doing wrong? Is there more to this step than just a numbering scheme? DEFAULT: 10-grab_ssh_host_keys.sh 11-openssh_setup.sh 12-enable_sudo.sh 20-install_chroot_environments.sh I386: 22-install_node_chroot.sh 23-setup_ssh.sh -- Carl J. Van Arsdall [EMAIL PROTECTED] Build and Release MontaVista Software
Re: And a question about writing scripts
Michael Tautschnig wrote: [...] Now to my problem. I use a couple classes for scripts, DEFAULT, FAIBASE, I386. In two of my directories not all scripts are being executed. In the default directory it executes 10, 11 and 20, but not 12. In my I386 directory it executes 22 but not 23. Below are the contents of these directories, can anyone tell me what I'm doing wrong? Is there more to this step than just a numbering scheme? [...] Have you checked that all of the scripts have proper permissions, i.e., are they readable and executable? I sure have. Everything looks pretty good from the outside. Here's my listing: -rwxr-xr-x 1 root root 822 2006-11-13 16:39 03-add_nfs_mounts.sh -rwxr-xr-x 1 root root 260 2006-11-13 16:41 04-add_user_build.sh -rwxr-xr-x 1 root root 110 2006-11-13 16:41 10-grab_ssh_host_keys.sh -rwxr-xr-x 1 root root 1809 2006-11-16 11:14 11-openssh_setup.sh -rwxr-xr-x 1 root root 140 2006-11-13 16:45 12-enable_sudo.sh -rwxr-xr-x 1 root root 1291 2006-11-16 09:21 20-install_chroot_environments.sh -rwxr-xr-x 1 root root 389 2006-11-14 11:18 21-install_newstyle_chroot.sh Is there a way to get a more verbose output from fai-do-scripts to help trouble shoot the error? -- Carl J. Van Arsdall [EMAIL PROTECTED] Build and Release MontaVista Software
Re: And a question about writing scripts
Michael Tautschnig wrote: Michael Tautschnig wrote: [...] (looks good) Could you provide an ls -lR scripts/ ? Just to have another quick look at all your scripts. Are you using NFS to access the config space? Sure thing, I've sent it as an attachment. I am using nfs (it was default). Is there a way to get a more verbose output from fai-do-scripts to help trouble shoot the error? I guess doing an export debug=1 somewhere, e.g., in class/DEFAULT.var should give you quite a lot of debug information. Alright, i'll give that a shot too and see if I can generate more information. I'll also be logged into the channel as glue. Thanks! -carl -- Carl J. Van Arsdall [EMAIL PROTECTED] Build and Release MontaVista Software
Re: And a question about writing scripts
Michael Tautschnig wrote: And here's the attachment I just forgot to send containing `ls -lR scripts/` -- Carl J. Van Arsdall [EMAIL PROTECTED] Build and Release MontaVista Software ÿþd r w x r - x r - x 2 r o o t r o o t 4 0 9 6 2 0 0 6 - 1 0 - 0 2 0 9 : 5 8 A M D 6 4 d r w x r - x r - x 2 r o o t r o o t 4 0 9 6 2 0 0 6 - 1 1 - 1 6 1 1 : 1 4 D E F A U L T d r w x r - x r - x 2 r o o t r o o t 4 0 9 6 2 0 0 6 - 1 0 - 0 2 0 9 : 5 8 D E M O d r w x r - x r - x 2 r o o t r o o t 4 0 9 6 2 0 0 6 - 1 1 - 1 3 1 6 : 5 0 F A I B A S E d r w x r - x r - x 2 r o o t r o o t 4 0 9 6 2 0 0 6 - 1 0 - 0 2 0 9 : 5 8 F A I S E R V E R d r w x r - x r - x 2 r o o t r o o t 4 0 9 6 2 0 0 6 - 1 0 - 0 2 0 9 : 5 8 G R U B d r w x r - x r - x 2 r o o t r o o t 4 0 9 6 2 0 0 6 - 1 1 - 1 6 1 2 : 5 0 I 3 8 6 d r w x r - x r - x 2 r o o t r o o t 4 0 9 6 2 0 0 6 - 1 1 - 1 3 1 6 : 4 0 L A S T d r w x r - x r - x 2 r o o t r o o t 4 0 9 6 2 0 0 6 - 1 0 - 0 2 0 9 : 5 8 L I L O s c r i p t s / A M D 6 4 : t o t a l 4 - r w x r - x r - x 1 r o o t r o o t 2 4 9 2 0 0 6 - 0 8 - 0 1 0 8 : 3 9 9 9 - d i s c o v e r - b u g s c r i p t s / D E F A U L T : t o t a l 2 8 - r w x r - x r - x 1 r o o t r o o t 8 2 2 2 0 0 6 - 1 1 - 1 3 1 6 : 3 9 0 3 - a d d _ n f s _ m o u n t s . s h - r w x r - x r - x 1 r o o t r o o t 2 6 0 2 0 0 6 - 1 1 - 1 3 1 6 : 4 1 0 4 - a d d _ u s e r _ b u i l d . s h - r w x r - x r - x 1 r o o t r o o t 1 1 0 2 0 0 6 - 1 1 - 1 3 1 6 : 4 1 1 0 - g r a b _ s s h _ h o s t _ k e y s . s h - r w x r - x r - x 1 r o o t r o o t 1 8 0 9 2 0 0 6 - 1 1 - 1 6 1 1 : 1 4 1 1 - o p e n s s h _ s e t u p . s h - r w x r - x r - x 1 r o o t r o o t 1 4 0 2 0 0 6 - 1 1 - 1 3 1 6 : 4 5 1 2 - e n a b l e _ s u d o . s h - r w x r - x r - x 1 r o o t r o o t 1 2 9 1 2 0 0 6 - 1 1 - 1 6 0 9 : 2 1 2 0 - i n s t a l l _ c h r o o t _ e n v i r o n m e n t s . s h - r w x r - x r - x 1 r o o t r o o t 3 8 9 2 0 0 6 - 1 1 - 1 4 1 1 : 1 8 2 1 - i n s t a l l _ n e w s t y l e _ c h r o o t . s h s c r i p t s / D E M O : t o t a l 8 - r w x r - x r - x 1 r o o t r o o t 4 4 3 2 0 0 6 - 0 9 - 1 9 0 7 : 4 7 1 0 - m i s c - r w x r - x r - x 1 r o o t r o o t 4 0 8 2 0 0 6 - 0 8 - 0 1 0 8 : 3 8 3 0 - d e m o s c r i p t s / F A I B A S E : t o t a l 1 2 - r w x r - x r - x 1 r o o t r o o t 1 1 5 7 2 0 0 6 - 0 9 - 0 5 0 6 : 4 2 1 0 - m i s c - r w x r - x r - x 1 r o o t r o o t 8 1 5 2 0 0 5 - 1 2 - 0 5 1 5 : 1 0 3 0 - i n t e r f a c e - r w x r - x r - x 1 r o o t r o o t 5 5 4 2 0 0 6 - 0 9 - 2 1 0 6 : 4 7 4 0 - m i s c s c r i p t s / F A I S E R V E R : t o t a l 8 - r w x r - x r - x 1 r o o t r o o t 4 8 3 2 0 0 6 - 0 7 - 2 2 1 6 : 2 8 1 0 - c o n f f i l e s - r w x r - x r - x 1 r o o t r o o t 3 8 1 2 0 0 6 - 0 9 - 2 6 0 2 : 3 9 2 0 - c o p y - m i r r o r s c r i p t s / G R U B : t o t a l 4 - r w x r - x r - x 1 r o o t r o o t 9 8 2 0 0 5 - 1 1 - 2 3 1 3 : 5 9 1 0 - s e t u p s c r i p t s / I 3 8 6 : t o t a l 8 - r w x r - x r - x 1 r o o t r o o t 8 0 2 2 0 0 6 - 1 1 - 1 3 1 6 : 5 6 2 2 - i n s t a l l _ n o d e _ c h r o o t . s h - r w x r - x r - x 1 r o o t r o o t 2 5 0 2 0 0 6 - 1 1 - 1 3 1 6 : 5 8 2 3 - s e t u p _ s s h . s h s c r i p t s / L A S T : t o t a l 4 - r w x r - x r - x 1 r o o t r o o t 9 6 2 2 0 0 6 - 1 1 - 1 3 1 6 : 4 0 5 0 - m i s c s c r i p t s / L I L O : t o t a l 4 - r w x r - x r - x 1 r o o t r o o t 1 5 3 8 2 0 0 5 - 1 0 - 0 8 1 3 : 3 0 2 0 - c r e a t e - l i l o c o n f
Need help understanding the partition/mountdisks tasks
I need to write some scripts that will modify the file system on the disk. I'm lookin in the manual for partition mountdisks and it says that my local disk should be mounted according to /tmp/fai/fstab relative to $FAI_ROOT, but I don't quite understand how things are being mounted. How is /tmp/fai/fstab generated? Is this the same as the fstab in my logs directory? If I had a single / partition, where would this be mounted to during the install? Thanks for your help! -carl -- Carl J. Van Arsdall [EMAIL PROTECTED] Build and Release MontaVista Software
Re: Using fai-chboot
Thomas Lange wrote: On Mon, 23 Oct 2006 11:31:03 -0700, Carl J. Van Arsdall [EMAIL PROTECTED] said: Is it possible to set the fai action as well as specify the nfs root on the same command line? Yes. fai-chboot -Iv vmlinuz-install /srv/fai/nfsroot_i386 node-30 Try: fai-chboot -v -k root=/dev/nfs vmlinuz-install /srv/fai/nfsroot_i386 node-30 Alright, i'm having some trouble. The use of fai-chboot -I host does quite a bit of stuff. I looked in the man pages, the -i option says its the same as -k ip=dhcp vmlinuz-install /dev/nfs, but this doesn't work. Is this man page old? its nothing like the example you provided. So I'm trying this command to set the parameters for booting, installing, while maintaining my custom nfsroot name glue:/srv/fai/config/scripts# fai-chboot -v -f install -k ip=dhcp root=/dev/nfs vmlinux-install /srv/fai/nfsroot_i386,v3,tcp,rsize=32768,wsize=32768 node-30 append parameters: ip=dhcp FAI_FLAGS=install Booting kernel root=/dev/nfs rootfs is vmlinux-install Kernel parameters: ip=dhcp fai-chboot: unknown host: /srv/fai/nfsroot_i386,v3,tcp,rsize=32768,wsize=32768 How do I use this command to do absolutely everything that fai-chboot -I does while allowing me to specify a custom nfsroot? -carl Is this isn't already done, has anyone considering changing fai-chboot to take nfsroot and kernel using options? But the best thing is to create a template for it, for e.g myinst.tmpl. This can be copied using fai-chboot -vc myinst.tmpl hostname If there are no objections, I'd be happy to work on a patch for this kind of functionality, it could be useful (at least it seems to be in my case). Thoughts? Ideas? Patches are always welcome, but maybe the template works for you. -- Carl J. Van Arsdall [EMAIL PROTECTED] Build and Release MontaVista Software
Re: Installing kernel's for local boot
Thomas Lange wrote: On Mon, 09 Oct 2006 15:14:35 -0700, Carl J. Van Arsdall [EMAIL PROTECTED] said: I've been playing with getting FAI setup for a couple weeks now. I've Which version are you using? Things have changed with FAI 3.0. I have 3.0, i've been doing my best to figure it all out with the old documentation and piecing together what looks different. I'm getting there custom kernels. The thing is, the howto is pretty dated. It comments putting files in files/packages which was deprecated in 2.54 from what I FAI Guide version 2.5.4, 20 april 2006 for FAI package version 2.10.1 . Yea, you are right, I had thought that the guide had the same version as fai. Sorry about the confusion . `files/packages/' THE USE OF THIS DIRECTORY IS NOW OBSOLETE. Maybe you are using an older version of the fai guide. But you are right we have to update the fai guide. Well, I was also using a howto that I found via the howtos from the fai wiki. I was desperate for information so I went there, the link to it is: http://faiwiki.informatik.uni-koeln.de/index.php/Using_customized_kernels_with_FAI So it seems to me that kernel's are specified in two places: 1. /etc/fai/make-fai-nfsroot.conf 2. specify a kernel for PXE that lives /srv/tftp/fai/ (or whereever your tftp stuff is housed I guess). yep. So, my question, the boot kernel is always going to be vmlinuz install or whatever you point to using fai-chboot right? In FAI 3.0, make-fai-nfsroot has now the option -V to specify the kernel name. See man make-fai-nfsroot for more info. You can also specify the kernel name with fai-chboot. From the comments in the conf file, the kernel from make-fai-nfsroot.conf is the kernel that will boot via nfs. Correct. I'm a bit confused as to how this works. This is the normal way how diskless clients boots. Have a look at nfsroot.txt in the kernel sources documentation. Anyhow, following that stuff.. what's the best way to configure fai to install a specific kernel for class? Build your own kernel using make-kpkg. This will make a Debian package out of this kernel. The create a local Debian package repository, add a line to the soures.lsit file and add the name of your kernel package to the class in package_config. Alright, so I'd make a local repository on my fai server, place that debian package inside of it, and add it to package_config. Does this handle updating menu.lst and the modules for me? (sorry if that's a noob question, previously I just wrote scripts to manipulate these files for me) -- Carl J. Van Arsdall [EMAIL PROTECTED] Build and Release MontaVista Software
Installing kernel's for local boot
Hey everyone, I've been playing with getting FAI setup for a couple weeks now. I've spent a lot of time with the manual as well as the howto for installing custom kernels. The thing is, the howto is pretty dated. It comments putting files in files/packages which was deprecated in 2.54 from what I can tell. So there are a number of things confusing me, but I've done my best to try and figure them out. So it seems to me that kernel's are specified in two places: 1. /etc/fai/make-fai-nfsroot.conf 2. specify a kernel for PXE that lives /srv/tftp/fai/ (or whereever your tftp stuff is housed I guess). So, my question, the boot kernel is always going to be vmlinuz install or whatever you point to using fai-chboot right? From the comments in the conf file, the kernel from make-fai-nfsroot.conf is the kernel that will boot via nfs. I'm a bit confused as to how this works. Anyhow, following that stuff.. what's the best way to configure fai to install a specific kernel for class? Since the howto talks about seriously deprecated things, I'm assuming a better was has been put in place. If there's no fancy way, does anyone do a brute force approach where the kernel is copied by a script to /boot along with all the other necessary things (menu.lst, modules, etc).? -- Carl J. Van Arsdall [EMAIL PROTECTED] Build and Release MontaVista Software
