Quick update and summary


It for sure uses the Letux kernel, although aTc has to enable a few extras like AUFS for the DBP system to work and such. I believe hns has his own LetuxOS, but this is different than PyraOS as aTc manages that. Although It just boils down to being just some flavo(u)r of Debian.
Oh, okay, didn't realise there was a difference, so thanks
 
Yeah, I was a little mystified as the exact difference. I recall hns's Letux OS project targetting open phones and the Pandora going forward, but kind of assumed we'd be running debian's ARM port of the kernel since we were running debian on the Pyra. But if all the work to support the tiler and now SGX acceleration are going on on the letux kernel then I guess pulling that in makes sense.
 
Hmm, an accidental Internet search turns up that Letux is a place in Spain (picture, pictures). It is not very big, and appears to be fairly remote. So who will get a picture of themselves holding a device running Letux in front of a village roadsign?
 
DBPs are the new version of the Pandora's old PND files; they're archives that you download to install any pyra-specific software, such as that found on the repo. You need some sort of union mount to mount them with the appdata folder, and our chosen solution while waiting for something genuinely better is aufs.
 
Last edited:
Are these Prototyphs Transparent ? If the new Cases Arive, it would be quite Awesome, if you post some Footages of a running Pyra in a Case whit Mass Produktion Material, and mybe to show the diverence to the Transparent Case..

But this is only möglich when you have time..

Some Every Time Footage would also be cool: Take the Pyra at Morning from the Charging Cable, the Play some Musik, Text Editing whit the Build in Keyboard, Text Editing whit a Hocket on Mouse and Keyboard, Print something, divid something whit zero ( 1/0 = error) play a Youtube Video on the Pyra in which you showed the Pandora..
And put in in you Pocket
 
Thanks TrashyMG and levi.
That's a long thread and I haven't read it yet -- maybe my answers are there. It starts off with the assumptions that 1) the reader is familiar with the Pandora and .PND files (sadly, I missed out on the Pandora which makes the discussion a bit harder to follow -- I'll keep slogging away at it!); and 2) that a system similar to the one used on the Pandora is a desirable thing for the Pyra.
DBPs are the new version of the Pandora's old PND files; they're archives that you download to install any pyra-specific software, such as that found on the repo.
Why not use .deb files for packages in the Pyra repository and install them with the Debian package system?

Also, on that Pyra DBP repo site (https://pyra-handheld.com/repo), there doesn't seem to be a field in the metadata for the licence of the software and there is no link to the source code?
 
Last edited:
Why not use .deb files for packages in the Pyra repository and install them with the Debian package system?
You can sure, but there is only 32GB of storage on the internal storage, some games and things like codeblocks have peaked over 2GB in size, so there is a finite space and .deb doesn't easily if not make impossible to install applications outside of default locations.

DBP and prior PND is designed to work well with removable storage, allowing the application and user data to be managed even when ejecting the media.

licenses show up in the links box, I have the link to the license and sources on one of the games I uploaded.

https://pyra-handheld.com/repo/apps/2
 
32 gb Internal Storage, whow , everything on the Pyra sounds like a Mirracle if you came from the CC Pandora

Whit the Pyra, there are mostly the same Peaple like on the Pandora, so if somewhone can Port a good DS Emulator on a Device like the Pandora, which wasnt that fast, then i suspect there should be great thinks on the Pyra to looking forward..
 
licenses show up in the links box, I have the link to the license and sources on one of the games I uploaded.

https://pyra-handheld.com/repo/apps/2
Hmm... that seems to be the only package in the repository with a "License" link, though.

(Seems to me it would be better if it were a mandatory part of the metadata, since it is (arguably) the most important piece of information about something one is about to make a copy of by downloading.)

Also that "License" link seems to be broken (at least when used from my computer) -- it takes me not a licence statement but rather to a page on SourceForge advertising all the packages there which have a zlib licence.
 
Hmm... that seems to be the only package in the repository with a "licence" link, though.
Yeah it still requires the maintainer of the package to provide the links.


(Seems to me it would be better if it were a mandatory part of the metadata, since it is (arguably) the most important piece of information about something one is about to make a copy of by downloading.)
I'd bring this up in @slaeshjag's thread, it's a still in development system.


Also that "licence" link seems to be broken (at least when used from my computer) -- it takes me not a licence statement but rather to a page on SourceForge advertising all the packages there which have a zlib licence.
Well It used to go to a license link two years ago when I pushed it up. Fairly easy to fix, just did in a few seconds.
 
Got the lids assembled (had to wait for the new lid magnets here) and will continue this weekend.

Please, please make a push to get those out. It has been a long time on preorders and it would be nice to get measurable progress and get progress going on the OS/final testing.

Also what is the word on the molds and the new case company? They were doing mold tests, can they start producing?
 
You can sure, but there is only 32GB of storage on the internal storage, some games and things like codeblocks have peaked over 2GB in size, so there is a finite space and .deb doesn't easily if not make impossible to install applications outside of default locations.

On the eMMC, yes. Until unless the internal microSDXC port becomes fully activated anyway.

Theoretically, once the internal microSDXC capabilities come to life, we -should- be able to do all of this to the internal microSDXC for those who's debian repository software footprint exceeds the 32GB eMMC. The current capacity of that internal microSDXC should be 512GB - but the user would have to purchase their own microSDXC card. I plan to drop a 400GB card in there just as soon as the internal microSDXC port is working. Then I'll boot from microSDXC and save the eMMC installed 'basic OS with utilities' as a troubleshooting and recovery OS. The 400GB card is sitting in my desk drawer - waiting...
 
It for sure uses the Letux kernel, although aTc has to enable a few extras like AUFS for the DBP system to work and such. I believe hns has his own LetuxOS, but this is different than PyraOS as aTc manages that. Although It just boils down to being just some flavo(u)r of Debian.
PyraOS uses the LetuxOS kernel tree but adds some quirks and config changes for optimization.
To me it seems as if AUFS can be completely replaced by OverlayFS wich is maintained in mainline kernels for a long time. It is available in LetuxOS kernels.
[doublepost=1550249647,1550249518][/doublepost]
When I see "Letux" my brain's first read is, "Lettuce", and I think of salad.
Well, the name was coined from french "Le Tux" (the Tux penguin) by a french coworker long ago and should be spoken "Let us". But your are free (as in free speech) to pronounce it as you like :)
And salad isn't a bad association. It is good and mixed...
 
To me it seems as if AUFS can be completely replaced by OverlayFS wich is maintained in mainline kernels for a long time. It is available in LetuxOS kernels.
I believe from what I thought I heard from slaeshjag, There was some features of AUFS that can't be done with OverlayFS, I just know it's something that fundamentally breaks how the DBP system works.
 
Back
Top