Fog registration with NUC
-
I typically use symbolic links.
[code]cd /tftpboot
mv undionly.kpxe undionly.kpxe.ORIGINAL
ln -s undionly.kkpxe undionly.kpxe[/code] -
This is what I get
mv: cannot stat ‘undionly.kpxe’: No Such File or directoryI must be missing a step someplace.
-
Well… can you access /tftpboot? [#cd /tftpboot]
What do you see when you type [#ls -alh]? Can you see severall files, including undionly.kpxe and undionly.kkpxe?
Copy commands from what Elliot typed, one by one, and paste them in Linux shell… -
I see files, but not undionly.kpxe - here is what I see:
root@FOG:~# cd /tftpboot
root@FOG:/tftpboot# ls -alh
total 220K
drwxr-xr-x 5 fog root 4.0K Apr 1 14:44 .
drwxr-xr-x 26 root root 4.0K Apr 2 08:46 …
-rw-r–r-- 1 fog root 828 Apr 2 08:46 boot.txt
drwxr-xr-x 5 fog root 4.0K Apr 1 14:44 fog
-rw-r–r-- 1 fog root 25K Apr 2 08:46 memdisk
-rw-r–r-- 1 fog root 17K Apr 2 08:46 pxelinux.0
drwxr-xr-x 2 fog root 4.0K Jun 26 14:43 pxelinux.cfg
drwxr-xr-x 2 fog root 4.0K Apr 1 14:44 tftpboot
-rw-r–r-- 1 fog root 145K Apr 2 08:46 vesamenu.c32
root@FOG:/tftpboot# -
I found this, so let me try its steps and see if I can complete to make the files.
[url]http://www.fogproject.org/wiki/index.php/Building_undionly.kpxe[/url] -
what version of fog are you running?
-
What version of fog are you running?
I should’ve asked this first but…
-
Running FOG 0.32
-
fog 0.32 doesn’t use undionly.kpxe
you need pxelinux.0 -
There’s your problem man.
FOG 0.32 is not the same as 1.x.x, which I’d highly recommend upgrading to.
Anyway, what problems are you having. You seem to have taken over this thread and I believe Jjared had 1.x.x.
-
Jared and I work together, same FOG machine. I have read some posts on upgrading from 0.x to 1.x will cause loss of data, is this still a risk with 1.1.2?
-
Loss of data?
What do you mean?
-
[FONT=sans-serif][COLOR=#000000][B]NOTE: 1.0.0 is a, nearly, complete rewrite from previous versions of FOG. There may be issues when upgrading from past revisions of FOG so please backup you installation before upgrading![/B][/COLOR][/FONT]
[FONT=sans-serif][COLOR=#000000]Migration for 0.32 to version 1.x.x will cause you to loose the operation system information that was associated with your hosts. This information has been moved to the image item now, so you will need to update all your images to set the appropriate operating system! Please see the Migration Instructions section below for more information.[/COLOR][/FONT]
[FONT=sans-serif][COLOR=#000000]All commands are assumed to be run as root. If you don’t have access to root, prepend the installation with sudo (ex.[/COLOR][/FONT]
[FONT=sans-serif][COLOR=#000000] [/COLOR][/FONT]
[FONT=sans-serif][COLOR=#000000]from [url]http://fogproject.org/wiki/index.php?title=Upgrade_to_1.0.0[/url][/COLOR][/FONT] -
what that’s talking about is not a “risk.” It’s a change in operating procedure. Before, OS was associated with hosts. but the actual operating system resides in the image. so, that’s where that info has been put now.
you should, of course, be prepared for a catastrophic failure, as you should be at all times, and especially when performing a major upgrade. We recommend that you do a fresh install instead of an upgrade, and migrate your data over to the new server. that is because you’re much less likely to have issues that way. upgrading is, however, supported. -
Update: I have built a new UBUNTU desktop 14.04lts and have installed FOG 1.1.2 and I am to this point from the instructions on Building UNDIONLY.KPXE file (see link above) and I do not understand the “[B][FONT=sans-serif][COLOR=#000000]Remove the {}'s and only apply the file you wish to build if you want only a specific file.” from this part.[/COLOR][/FONT][/B]
[FONT=sans-serif][COLOR=#000000]Build the undionly/ipxe files.[/COLOR][/FONT]
[FONT=sans-serif][COLOR=#000000][B]I USE THE FOLLOWING COMMAND TO BUILD ALL FILES AT ONCE.[/B] [B]Remove the {}'s and only apply the file you wish to build if you want only a specific file.[/B][/COLOR][/FONT]
[COLOR=#000000][FONT=monospace]make bin/{undionly,ipxe}.{,k,kk}pxe EMBED=ipxescript[/FONT][/COLOR]
[SIZE=5][B][FONT=sans-serif][SIZE=19px][COLOR=#000000]Copy and/or Use your files[/COLOR][/SIZE][/FONT][/B][/SIZE][FONT=sans-serif][COLOR=#000000][B]I USE THE FOLLOWING COMMAND TO COPY ALL FILES AT ONCE. Remove the {}'s and only copy the file you wish to use if you want only a specific file.[/B][/COLOR][/FONT]
[COLOR=#000000][FONT=monospace]cp bin/{undionly,ipxe}.{,k,kk}pxe /tftpboot/ [/FONT][/COLOR]
[COLOR=#000000][FONT=monospace]I ran the full command - make bin/{undionly,ipxe}.{,k,kk}pxe EMBED=ipxescript then realized it said to REMOVE the brackets should it be re-run but as[/FONT][/COLOR]
[FONT=monospace]make bin/undionly,ipxe.,k,kk pxe EMBED=ipxescript[/FONT]
[COLOR=#000000][FONT=monospace][/FONT][/COLOR]
[COLOR=#000000][FONT=monospace][/FONT][/COLOR] -
why are you building unidonly.kpxe? one is included with fog, that has fog-specific embedded scripting
-
because when I went to do this, it said it did not exist.
[FONT=Consolas]cd /tftpboot
mv undionly.kpxe undionly.kpxe.ORIGINAL
ln -s undionly.kkpxe undionly.kpxe[/FONT] -
So you’re still running 0.32?
-
if you installed FOG 1.1.2, you should no longer have the problem where the undionly.kpxe, or undionly.kkpxe do NOT exist.
-
even if the files were for some reason missing, you could just download them from the sourceforge page
