Okay, I have updated Hijack with the two lines of changes for beta13. The new version v282 of Hijack is now available, along with a full kernel source tree for v2.00-beta13.

Cheers

Two lines of changes? You remember the post counter is gone, right?

Two lines of changes? You remember the post counter is gone, right?

v283 is already out

Mark - can you find out how to change the content-type that your pre-built binaries are sent with? Currently, they're provided as text/plain, which is eventually going to cause transfer corruption.

Greetings!

Also, would it be possible to put the unmodified kernel binary for b13 up on the site as well? Right now, it is only b11. Thanks!

I would like to ask this too!

Thanks guys!

You can get it here until Mark gets around to updating his page.

- Trevor

Piece-O-Cake for the content-type, but .. what content-type should I use for them?

Thanks

>You remember the post counter is gone, right?

Yup, that's why my posts are rather brief these days.

Cheers

I'll put up a stock v2b13 kernel shortly.

cheers

Greetings!

Thanks! I always keep a copy of it, hijack, LogoEdit, debian, etc. in an install directory in music-space. This way, I have it if I ever need to reload or move it around. It comes in handy...

The most appropriate existing content-type to describe kernel images is application/octet-stream. It basically means, "unidentified binary content - do not attempt to interpret".

You could invent a type like application/x-empeg-kernel (the "x-" is important), and anything that doesn't understand that should treat it the same as application/octet-stream. That would enable somebody to install a "player" for that type that uploaded it direct to the player. But that's probably OTT.

(Except to MS Internet Explorer of course, which seems to ignore content types in favour of "guess based on contents". But there's nothing you can do about that, and I doubt its heuristics would get it wrong in this case. It is a nuisance for those with HTML tutorials that have links to view the source as text/plain - and the browser "corrects" it to text/html. )

Okay, octet stream it is.. let me know if it still comes up with text.

Cheers

Oh shoot.. I forgot.. these are served from sourceforge now, as a mirror of my local site.

This'll take a few more minutes..

Well, no problem with my local Apache server, but sourceforge still serves them as text. Take a look at the html for the index.html page and feel free to suggest anything.

Cheers

Looking at the HTML isn't likely to help - most servers (as you know from using Apache) base their types on the filenames. You can give hints in HTML to tell the browser what type to expect, but the HTTP headers are the last word.

SourceForge appears to use Apache as its Web server; did you try adding a .htaccess file? Something like the following should do:

AddType application/octet-stream .zImage

(in the same directory as the files).

Okay, bingo. works now, thanks.

Cheers