Re: What do we know about Diablo (Maemo 4.1) ?
 

I'm not uploading a 147MB tar package straight. When I reboot into windows, I'll see if I can make a split rar file and upload to mediafire. Someone else can download and mirror of there if they wish.

Rar files shouldn't matter in this case as debs are just debs, no permissions needed. If someone doesn't like rars, tough.

If you symlink your archives directory to the memory card, you can directly extract the debs in there and run the apt-get command. I'll see, I'm super tired right now and my upload speed is kinda crap (hence the split rars).

Also, field test display works better with the diablo kernel (you get new /proc entries). I'm waiting for the GIMP to compile so I can carry on with the initfs.

Re: What do we know about Diablo (Maemo 4.1) ?
 

Torrent could work, too. I'd be willing to host it (500 MB free University web space), but I don't need a run-in with OIT if Nokia contacts them. Too many fuzzy rules to make me want attention.

Re: What do we know about Diablo (Maemo 4.1) ?
 

That is true. Some files in there are copyrighted (bt-firmware & wlan-firmware etc afaik). I don't have the time, patience or the money to fight against what may happen if I did upload those packages.

Re: What do we know about Diablo (Maemo 4.1) ?
 

Ok, I can't seem to make a proper initfs image so here are the ipv6 modules from the diablo image:

http://www.mediafire.com/?hxmpmb39wwy

Extract somwhere and point the ipv6 script to the new place.

Extracted by qwerty12 :cool:

Re: What do we know about Diablo (Maemo 4.1) ?
 

I am not a lawyer, and this is not legal advice.

Maemo is a community project, and Nokia depends on the goodwill of open source developers for the success of the N8x0 and future devices.

I highly doubt if they'd be stupid enough to threaten to sue a maemo customer for tinkering with the platform.

Regardless, if -anyone- else has the files, and uses Tor (www.torproject.org) to anonymously upload them somewhere - many of us would be very appreciative.

Chris

Re: What do we know about Diablo (Maemo 4.1) ?
 

Well, I, at least, am not concerned about an actual lawsuit; I can see them requesting it be taken down though, and I don't like the idea of them contacting the OIT about it, and requesting they be pulled down, and then I get unwanted scrutiny from OIT for anything else I do that might be a gray area. So I don't want it such request-bait on my webspace.

But I'd happily seed a torrent...

Re: What do we know about Diablo (Maemo 4.1) ?
 

I was thinking torrent also and I wasn't demanding any particular format. I don't consider 147Mb to be that unreasonably huge, but if you're willing to share it on whatever terms you consider reasonable that would be generous of you.

PM me or one of us if you decide to let one of us have them and I'm sure we can find a way to "seed" them....

In any case someone PM me if you have them and want to share. :)

Thanks

Re: What do we know about Diablo (Maemo 4.1) ?
 

Oh well, I read this too late.
Would have been nice to check the new Diablo earlier, but well.. if they don't want to, then I will respect their wish and won't try it out.
After all, we'll just have to wait one or two months, I hope..

Keep letting us know about any new discovery you'll make with Diablo as we're more than willing to read them! ;)

Re: What do we know about Diablo (Maemo 4.1) ?
 

A note: it should be possible, for us Chinook users, to at least update the flash player, right ?
What do you think querty12 ?

Re: What do we know about Diablo (Maemo 4.1) ?
 

It could be done theorecically (spelling). The original flash player package in chinook is replaced with one of a new name. I would guess that you would need Navi's SVN build of MicroB installed too.

My torrent upload speed is really crap. 147MB isn't huge but when you have a upload speed like mine. It took me 15 mins to upload the kernel source for lardman.

Tor sounds interesting but it kinda defeats the point if I say I will upload. So I might (and I really do mean might) upload. Sorry for being a prick but you know.