Ok, thanks for clearing that up, and thanks for the link. Sorry for being off topic.

Hmm… Ok, I’ll look into doing that, but my concern is “How am I running Debian all of a sudden?”

I’m the only one with the credentials for this server. I built it. It has only been, and should only be, touched by me. These are not reused credentials. I created them specifically for this and use them only on this server.

I was running Ubuntu Server 10.04. I don’t know if there is a GUI option for US, but it was strictly command line. I see you pointed out that Ubuntu is a derivative of Debian. Does that mean a Debian desktop UI comes with an Ubuntu Server install and I just never knew?

I just find it weird that I’ve been booting into the command line US environment, and now all of a sudden it boots to a GUI Debian environment. If that is a normal option, I didn’t do it explicitely, and nobody else should be able to log into this server.

I checked the command history and I only see the commands I explicitly entered recently.

I’m a Windows helpdesk support guy. I have minimal knowledge of Linux. I’ve played with Debian. I’ve played with Ubuntu and Ubuntu Server.

Through trial and error, I’ve set up FOG on Ubuntu Server 10.04 and have been happily building my image collection and capturing/deploying images for the last ~month. I usually shut it down after the task I need it for is finished, but last night I left it running.

This morning I went to ssh in and the connection was refused. I checked the web interface and the page wasn’t found. Weird. I plugged in directly and got no video output so I did a hard reboot.

It brought me to a Debian login screen with my FOG users listed. I logged in. My fog file structure is there. Everything works now. …but how is Debian all of a sudden installed? Does Debian come with an Ubuntu Server install and some kind of dual boot config? Did a boot option somehow get switched? This seems really strange to me, and I was recently thinking about my limited knowledge of linux security, so even though I’m inside a pretty secure network and not really connected to anything, I’m freaking out a little.

What happened?

EDIT: I don’t even have Debian install media, at the moment.

Hey, thanks for the reply!

I want TRK to be an option in my main menu. When I choose TRK, it will load TRK and put me in the TRK menu, just like booting TRK.

I played with the ISO option in that specific guide for a few days this week. Like I said, I can boot WinPE, but I have a different issue with TRK.

When I boot TRK as an ISO, I get the TRK menu, except the background is missing and choosing any options has no affect, except when choosing the first option, default, the Autoboot timer resets. Do you have any ideas about that? Like I said, I’d prefer being able to boot the TRK kernel from the FOG menu, but I would be happy being able to boot the ISO properly.

I’m pretty new to Linux. Not sure if I said that right.

So as far as my first issue: Can you see anything wrong with my code for the menu option? vesamenu.c32 IS the correct kernel?

Hi all. Cross posting this from the TRK forums, since it could be a FOG problem as well.

I just discovered FOG and TRK last week and I think they’re great!

I want to use TRK as our network bootable recovery disk. I point DHCP option 67 to TRK’s pxelinux.0 and that works fine. But I want to incorporate TRK into my existing FOG setup. That’s where the problem comes in.

When I choose TRK from the FOG menu, the TRK menu comes up, but the background isn’t loaded. Choosing the first option just restarts the Autoboot timer, any other option does nothing.

default tftp folder is /srv/tftp

[CODE]My folders:
/srv
-/tftp
-FOG’s pxelinux.0
-/FOG’s pxelinux.cfg
-/trkfiles
-TRK’s pxelinux.cfg and everything else for TRK

FOG’s pxelinux.cfg entry for TRK:

LABEL Trinity
MENU LABEL Trinity
MENU PASSWORD ******
KERNEL vesamenu.c32
APPEND trkfiles/pxelinux.cfg/default

TRK’s pxelinux.cfg/default is unedited[/CODE]

TRK 3.4 build 372
Windows DHCP
FOG server is a Debian 6 VM in WMWare
Target computers are another VM and a physical client workstation. This happens on both targets.

Like I said, I can pxe boot TRK fine by itself. I can also boot a WinPE iso through FOG. I tried booting a TRK iso through FOG and had a different issue. I feel like I’m really close, but I’ve been hammering at this particular issue for 2 days and I’m stuck. I’d like help instead of wasting too much more time being stubborn. Any ideas? Any more info I can provide?

Thanks for your time!