The error is a line not found in cygwin1.dll, so it is entirely possible that I have messed up cygwin along the way somewhere.

The flash-kernel thing is strange. To get the ftp client to send it, I first need to telnet to the empeg and rw. Then send the file. Then ro. Then sometimes when I reboot I have the new kernel, sometimes not. It used to work 90% of the time, now about 20%.

Most of my boxes are unix or linux, and I can easily hook one up to talk to the empeg, but I still don't understand the format of the .disk file which is gziped into upg_pumphda5. What do I use to create that file?

Copy cygwin1.dll into the same directory as the upgrader. That should eliminate any problems with it not being able to find the DLL.

As about the flash_kernel thing. Try using /proc/kernel_flash instead.

To create the image you need to mount a file using the loopback device with ext2 format.

Cheers! I'll give all 3 of those a try this evening...

The flash-kernel thing is strange. To get the ftp client to send it, I first need to telnet to the empeg and rw. Then send the file. Then ro. Then sometimes when I reboot I have the new kernel, sometimes not. It used to work 90% of the time, now about 20%.

Time for you to find a real FTP client, not to bash/trash Hijack's FTP services!

There is ZERO (absolutely NO) need to set the drive(s) RW just to upload a new kernel to the Empeg.

-ml

That's what I thought, originally. I use leechftp, which is generally pretty good.

Wasn't in any way getting at any of hijack's functionality - I am a confirmed next-hijack-version addict - I normally assume I have just configured something incorrectly or corrupted something

I know most of the problems on my network are down to Microsoft - some fixable, some just MS. All my *nix boxen just work. They way they always have.

>All my *nix boxen just work. They way they always have.

Mine would too, if I'd just leave them alone

Actually, my internet server is *still* running a (mostly) 1998 distro. I keep making motions to update it to the 2000's, but just never seem to want to disturb it since it works almost perfectly all the time.

Cheers

Tried cygwin1.dll in the same directory, and I get the same error when I try to run upgrader (same error with v6, v4 and an earlier one):

The procedure entry point__getreent could not be located in the dynamic link library cygwin1.dll

Unfortunately I have no idea how to troubleshoot an error like that on a Windoze box.

Any ideas?

get the latest cygwin? also, you're gonna need ncftput. even after that, you wouldn't be able to run it from command prompt, because a couple of the ncftput's commands require /dev/null. easiest way is to run it from cygwin's bash shell.

Hmmm - I reckon I might just use the Linux upgrader from linux then, as I can't find anywhere where I can get the full cygwin without connecting to the internet during setup (ie I just want to download the entire thing onto one ofthe machines outside my network and burn it onto CD to install inside my perimeter)

Anyhow, it might all be irrelevant as I can't figure out how to make a copy of my empegs current hda5 to compress into the upgrade file anyway. I have gone through all the disk image and loopback howtos I can find but all seem to require a loopback device to exist on the empeg.

Has anyone managed this, and how did you do it?

Hi Mark,

After trying various things, I eventually gave up and recreated the flash_kernel device from scratch, now it all works perfectly.

So I guess I corrupted it somewhere along the line.

Cheers

How the heck do you corrupt the device file?!? Anyway... You could just use /proc/kernel_flash instead. It's part of the proc filesystem so it's automagically created.

That is a good question, and one I have no answer to

I tried to use /proc/kernel_flash and it doesn't work for me. I can write the new kernel to it, if I first delete the old one and occasionally it will upgrade. Sometimes it won't. It is too unreliable for me to use. The timestamp on the file shows it has the right one, but I have no idea why it doesn't use it.

Anyway, now I have rebuilt the /dev/flash_kernel it works every time, which is nice.

Delete the old one?

I've even used the useless commandline FTP client that comes with Windows and it works... I just do bin, hash, put zImage /proc/kernel_flash, quit

i thought it was /proc/empeg_kernel. maybe there are more than one aliases.

Umm. Yeah I was do it from memroy and getting confused with the one he'd created in /dev/

Yup - delete the old one. Very strange - that's why I've been puzzled, as I have had to telnet in to do it, and I'm sure that's just not right. And I couldn't remember whether it was empeg_kernel, kernel_flash or flash_kernel either