hijack update

Today I updated my players's Hijack kernel via FTP als described here.

Everything went OK, the kernel got uploaded, but there's something that bugs me.
I've used FlashFXP to upload the kernel. First I renamed the kernel file to "empeg_kernel" as the FAQ states, and then I upload the file to the /proc directory.
Funny thing is, though everything works, I can't see the file in the /proc directory! Is this normal ? I mean, I've looked before I uploaded the file too, and then also I couldn't find a empeg_kernel file.

Why is this ? I'm sorry is this is a stupid question, bug I'm not that big into networking.

I'm pretty sure it because that's just the place you upload the kernel file to in order to have hajack intercept it and start the upgrade. There's no actual need to have the upgrade file stored on the empeg.

On a related note, I've recently started using jEmplode to update my hijack kernel. It's oh-so-easy. Like click a menu item and an ok button kind of easy. Highly recomended to any who updates there hijack kernal even semi-frequently.

John

Yeah, I've tried that using JEmplode first, but the connection timed out.
Hmmm, maybe because of my router, I don't know. But instead of fiddling around with it , I decided to do it manually. I remembered something in the FAQ about doing it via FTP, so that's what I've tried next.

Funny thing is, though everything works, I can't see the file in the /proc directory! Is this normal ? I mean, I've looked before I uploaded the file too, and then also I couldn't find a empeg_kernel file.

Why is this ? I'm sorry is this is a stupid question, bug I'm not that big into networking.

Not really a networking thing, but a Unix thing...

Is it listed at all or is just the size off? Do you see the other files in /proc? My ftp client (Leech ftp) lists the "files" (see below) in /proc without problems (see attachment).

Here's the interesting thing: the stuff listed under /proc doesn't really exist... It's created by the kernel at run-time and offers interfaces to various functions and information - so it's not real files, though they should look like it.

What happens when you upload the empeg_kernel file is that the kernel senses the upload to that file and automatically diverts it to the flash memory instead. If you read from the file, the kernel senses that to, and reads from the flash memory and passes that out to the reader.

/Michael

Is it listed at all or is just the size off? Do you see the other files in /proc? My ftp client (Leech ftp) lists the "files" (see below) in /proc without problems (see attachment).


I've taken a screenshot of my ftp client and attached it to this post. All the files I can see are listed (there are some directories too, but did not include those), empeg_kernel is not one of them.

But by reading your explanation I now know why.

Thanks for the info!

Still doesn't make much sense that you don't have the file listed at all, considering that you have the other files (that are essentially the same thing, but interfaces other things...).

Any kernel gurus awake?

/Michael

Still appears to be in the Hijack source...

Can you see it if you browse to it over http?

Can you see it if you browse to it over http?

I wish I could check that, but I haven't been able to connect to my empeg through http. See other thread, "how to stream mp's using winamp/http ?"
Any help there would be appreciated.

I see that you now can http to the empeg. Any update on whether you can see /proc/empeg_kernel ?

Just a sec, checking....

Ah! There it is, naughty little bugger!

Yep, no problems in viewing it with http.
Mmmm. Maybe the problem lies with FlashFXP?
If I have the time tomorrow, I'll install CuteFTP and see what that gives...

I'm pretty sure it's hijack not reporting that the file exists. When I upgraded to 267 I did it manually over ftp and the file didn't show up, but if you take it on blind faith that it's there, all goes according to plan. I don't think chaning ftp clients is goign to change anything...

Matthew

You may be right - I've never looked for it in an ftp session

Yeah, I've seen(or not seen) a few directories/files I know are on the player, like /drive0, that didn't show up in the FTP directory listing. I don't know if it was intended to be like that, but I can still cd into them just fine.
Why would you want to read/download /proc/empeg_kernel anyway? I thought that was a "virtual" file used for uploading only?

What command the client sends will affect what is returned by the FTP server. This is how it's supposed to work...

[edit] If you compare the two lists below then you'll notice that any block or character devices aren't included in one of the lists. In this case empeg_kernel and empeg_bootlogos

- Trevor

ftp> dir
200 Okay.
150 Opening data connection.
dr-xr-xr-x 3 0 0 0 May 20 19:46 ide
-r--r--r-- 1 0 0 0 May 20 19:46 empeg_power
-r--r--r-- 1 0 0 0 May 20 19:46 empeg_therm
-r--r--r-- 1 0 0 0 May 20 19:46 empeg_id
-r--r--r-- 1 0 0 0 May 20 19:46 empeg_rds
-r--r--r-- 1 0 0 0 May 20 19:46 empeg_state
-r--r--r-- 1 0 0 0 May 20 19:46 empeg_usb
-r--r--r-- 1 0 0 0 May 20 19:46 empeg_ir
-r--r--r-- 1 0 0 0 May 20 19:46 empeg_cs4231
-r--r--r-- 1 0 0 0 May 20 19:46 audio
brw------- 1 0 0 60, 8 May 20 19:46 empeg_kernel
brw------- 1 0 0 60, 5 May 20 19:46 empeg_bootlogos
-rw-r--r-- 1 0 0 0 May 20 19:46 empeg_notify
-r--r--r-- 1 0 0 1124 May 20 19:46 empeg_screen.png
-r--r--r-- 1 0 0 2048 May 20 19:46 empeg_screen.raw
-r--r--r-- 1 0 0 0 May 20 19:46 misc
dr-xr-xr-x 2 0 0 0 May 20 19:46 bus
dr-xr-xr-x 4 0 0 0 May 20 19:46 tty
-r--r--r-- 1 0 0 0 May 20 19:46 slabinfo
-r--r--r-- 1 0 0 0 May 20 19:46 swaps
-r--r--r-- 1 0 0 0 May 20 19:46 mounts
-r--r--r-- 1 0 0 0 May 20 19:46 locks
-r--r--r-- 1 0 0 0 May 20 19:46 cmdline
-r--r--r-- 1 0 0 0 May 20 19:46 ioports
-r--r--r-- 1 0 0 0 May 20 19:46 dma
dr-xr-xr-x 2 0 0 0 May 20 19:46 fs
-r--r--r-- 1 0 0 0 May 20 19:46 filesystems
-r--r--r-- 1 0 0 0 May 20 19:46 interrupts
-r--r--r-- 1 0 0 0 May 20 19:46 partitions
-r--r--r-- 1 0 0 0 May 20 19:46 devices
-r--r--r-- 1 0 0 0 May 20 19:46 stat
-r--r--r-- 1 0 0 0 May 20 19:46 ksyms
-r--r--r-- 1 0 0 0 May 20 19:46 modules
-r-------- 1 0 0 16781312 May 20 19:46 kcore
dr-xr-xr-x 10 0 0 0 May 20 19:46 sys
dr-xr-xr-x 2 0 0 0 May 20 19:46 scsi
dr-xr-xr-x 4 0 0 0 May 20 19:46 net
lrwxrwxrwx 1 0 0 64 May 20 19:46 self -> 50
-r--r--r-- 1 0 0 0 May 20 19:46 cpuinfo
-r--r--r-- 1 0 0 0 May 20 19:46 version
-r-------- 1 0 0 0 May 20 19:46 kmsg
-r--r--r-- 1 0 0 0 May 20 19:46 meminfo
-r--r--r-- 1 0 0 0 May 20 19:46 uptime
-r--r--r-- 1 0 0 0 May 20 19:46 loadavg
dr-xr-xr-x 3 0 0 0 May 20 19:46 1
dr-xr-xr-x 3 0 0 0 May 20 19:46 2
dr-xr-xr-x 3 0 0 0 May 20 19:46 3
dr-xr-xr-x 3 0 0 0 May 20 19:46 4
dr-xr-xr-x 3 0 0 0 May 20 19:46 5
dr-xr-xr-x 3 0 0 0 May 20 19:46 6
dr-xr-xr-x 3 0 0 0 May 20 19:46 7
dr-xr-xr-x 3 0 0 0 May 20 19:46 12
dr-xr-xr-x 3 0 0 0 May 20 19:46 16
dr-xr-xr-x 3 0 0 0 May 20 19:46 35
dr-xr-xr-x 3 0 0 0 May 20 19:46 36
dr-xr-xr-x 3 0 0 0 May 20 19:46 37
dr-xr-xr-x 3 0 0 0 May 20 19:46 38
dr-xr-xr-x 3 0 0 0 May 20 19:46 39
dr-xr-xr-x 3 0 0 0 May 20 19:46 40
dr-xr-xr-x 3 0 0 0 May 20 19:46 41
dr-xr-xr-x 3 0 0 0 May 20 19:46 43
dr-xr-xr-x 3 0 0 0 May 20 19:46 44
dr-xr-xr-x 3 0 0 0 May 20 19:46 45
dr-xr-xr-x 3 0 0 0 May 20 19:46 46
dr-xr-xr-x 3 0 0 0 May 20 19:46 47
dr-xr-xr-x 3 0 0 0 May 20 19:46 48
dr-xr-xr-x 3 0 0 0 May 20 19:46 49
dr-xr-xr-x 3 0 0 0 May 20 19:46 50
total 0
226 Okay.

ftp> ls
200 Okay.
150 Opening data connection.
empeg_power
empeg_therm
empeg_id
empeg_rds
empeg_state
empeg_usb
empeg_ir
empeg_cs4231
audio
empeg_notify
empeg_screen.png
empeg_screen.raw
misc
slabinfo
swaps
mounts
locks
cmdline
ioports
dma
filesystems
interrupts
partitions
devices
stat
ksyms
modules
kcore
self
cpuinfo
version
kmsg
meminfo
uptime
loadavg
226 Okay.

Very simple: your FTP client is choosing not to show /proc/empeg_kernel to you. But it is there, and Hijack is NOT hiding it.

Try a unix/linux command-line FTP client for proof.

Cheers