Posts made by need2

Yeah I had that too… didn’t think much of it though since I usually prefer more of the control freak method of doing the updates via console anyways.

Partclone is the new method. Partimage is the old one. No research to back this up but it appears that partclone handles compression more efficiently. You should only have Partimage selected for legacy images from 0.32, and ideally you should replace those eventually with new images from 0.33 .

I also don’t want to step on any toes but this type of oddness is another reason I avoid distros like Ubuntu for servers now.

I about caved my keyboard in with my face yesterday when I made the jump to 0.33 and couldn’t get TFTP transactions to work either. I checked everything, and even did a sudo clean install, but to no avail. Finally I double checked my DHCP settings, and I swear some documentation somewhere told me to use undionly.pxe, when it should be undionly.kpxe . Once I fixed that Option 67 on my DHCP, magically everything worked.

I blame reading the wrong thing somewhere but I know it was likely my own internal processing error.

I have never had an issue with that page, but I tend to use Tom’s kernels because they work on damn near everything. Here’s another question. How did you modify the PXE menu? Directly, or did you use the built in method in FOG Settings?

How did you update the kernel? Did you follow [URL=‘http://fogproject.org/wiki/index.php/FAQ’]these intructions[/URL] ?

Are you sure the user data isn’t just in a deprecated user folder? Such as C:\Users\gobbledegook

I would definitely test that drive. Do you have another drive to try in its place?

Are you using Fog 0.32 or Fog 0.33? Which kernel did you grab?

I follow. So you would either have to do some odd multiple boot/reboot thing to set a task from the host or set tasks from the server which could then do its musical kernel dance. That’s a bit more than I have the time or knowledge for right now, but its good to know the support is out there.

I see, so it is included in the FOG 0.33 kernels. I’ll get back to poking about then.

So… that UEFI kernel… where might one find that lovely build of yours?

What manufacturer is this? I have seen Dell do odd things with the mini partitions. Worst case scenario you may have to boot a repair disc and mark the OS partition as the boot partition and fix the MBR.

I am curious what ports you require for the Mining features for those of us with paranoid firewalls. I may take a box that is on its way out and let it spend its last working hours making you money XD .

EDIT: Is there something I can do to force the machine to stay in this mining mode? If not I could always keep it redoing a task lol.

Funny to read this now. This is the reason I switched from using a Ubuntu server install to a plain Debian install. Overall I’ve still been happier with Debian, but good to know this was nothing I broke.

I was wondering when I would be able to pull this out again:

[URL=‘http://www.albinoblacksheep.com/flash/posting’]An Educational Video on Forum Posting[/URL]

But searching past the first page of a thread is hard and stuff and things.

Yay updates!

Now sadly, many users will be affected by this long term, due to OpenSSL being embedded in various network appliances and other long-life systems that companies have to pay license fees just to update. My organization narrowly missed this bug due to our equipment being in the golden age right before the versions vulnerable to Heartbleed.

I think within the next month, most major and responsible organizations will have patched themselves against Heartbleed. But due to the wide ranging impact of an OpenSSL exploit, Heartbleed could still be leaking data for the next five years.

I’ll admit, FOG not playing well with my NAS boxes actually did me a favor. I started digging deep enough in the boxes to find out that their linux kernel that lived on the board was insecure, and there was no good way to go about patching it, let alone ever get it to support the security features that I required. I ended up wiping the drives and giving them away. Had I not attempted to attach them to FOG, I may have never realized how insecure they were.

I’ll admit I am drooling a bit for some UEFI love as well. I have started to accept having to strike UEFI support from our department’s three year plan though. FOG alone will solve so many issues for us, that UEFI would be a willing sacrifice.