Search results

Do the files exist in the Angstrom /home? /home/esn should be the _exact same_ on both Angstrom and Debian... so use them for comparison shots rather than directly inside the overlay as it won't match up. And again, the log states that it has bound up correctly. :( Seeing as you seem to be...

It does, but it does it via an aufs bind so you get your NAND /home as well as the overlay file. All writes into /home will then go into the overlay rather than your NAND, but you can access them both from the same point.. which is one of the funky benefits of using overlays in general...

Yea ignore Debian's mount.. it's bollocks ;) it's my fault, and I might fix it, but probably not as it doesn't affect anything. From your main Angstrom mount spew though, it does seem to have linked up successfully: /dev/loop2 on /var/volatile/tmp/1gb.overlay type ext2 (rw,errors=continue)...

Well there's another bug, extendutils isn't unmounting cleanly.. but that won't cause your issue. From what I can see, everything is working as it should do :\ Let me see what the output of "mount" is from Angstrom, when everything is bound up.

I've been using a FAT32 card to test this all with, so that's not the problem. To be honest, I have no idea what the problem is :( Especially as it looks like your home folder is bound out as /home/esn in the screenshot there, and since it's an rbind mount, it should be exactly what you see in...

Normal to a Linux system.. I keep forgetting that in general, people with Pandoras will be using SD cards formatted for non-Linux systems.. so in this case, a Linux filesystem, not FAT or NTFS. Did it work though? Yep, going to fix that.. they're the same thing with a different extension is...

You probably weren't far from it.. it's just a tad fiddly still. I'm trying to figure out how people use the system ( whoever still does! ) so I can code up "wizards" to help run through it. As well as tidy it up and get rid of confusing stuff like Extends vs Overlays, and preMount instead of...

If you look over in the Extend Utils topic, I'm writing up guides and stuff on using a Debian chroot to dev in, so there's another option for you. Personally, I do prefer just creating a bootable SD card with everything I need on it - be that booting Angstrom ( with _careful_ use of opkg ) or...

Oops, there's a bug... anyway, don't use "mount" in the Debian Dev Extend as it doesn't know what your base system is currently mounted. That spam is from my testing it with the Old Extend Utils, which erroneously copied my mtab in, so it thinks your mount stuff is what I had mounted at the time...

Check mount to ensure that it's put the home overlay on properly, and post up the script file it spat out. ( or post up both if you're not sure what you're looking for in the mount spam. ) I would also manually check /home to see if the files you places on the overlay are there as well - as...

That sounds about right.. though once you have the mount script, you can just call it manually from a terminal without having to jump back into Extend Utils. They are just bash scripts. And it is linked on the Wiki under OS Extends as it's a full Debian chroot plus dev tools :) Actually, I...

The Debian Extend doesn't export anything into Angstrom.. so that Debian Extend Terminal that it calls up is the _only_ place that you can run your dev tools in. This is to stop libraries getting mangled and other things from going awry. And by "use mount" I mean literally run "mount" from an...

You can use your Home Extend without issue.. bind the Home Extend first ( and if you're still using the older Extend Utils, use "mount" to make sure it actually _is_ bound as I had issues when I was testing with it and it didn't always take, ) then run the Debian Extend so that when it binds to...

That's why I cheated and created a Debian-based extend instead ;) It won't be dependent upon opkg and underlying Angstrom bits and pieces this time so shouldn't break apart into a horrific mess as we get new hot fixes. Least, that's the theory... time will tell!

Ahh.. well I had called it preMount as generally the scripts do a lot of weird stuff before it finally throws you into the final mount, so I thought the term would be appropriate. No idea why I didn't just call it extendMount like you suggest - much more obvious! ;) Think the next version (...

From the errors, and following through the code, it looks like your X window management is iffy. Here's the X window code that I use in GLESGAE without much issue: X11RenderWindow::X11RenderWindow() : mDisplay(XOpenDisplay(0)) // Display* , mWindow(0) // Window , mDeleteMessage() // Atom {...

Right *rolls up sleeves* All the old Extend Utils stuff has now been deprecated, and I've removed it from my server. The current stuff still lives, but in a different place ( no longer in the misleadingly named "SimpleDev" folder. ) The old ( old old really old ) dev.extend stuff linked on the...

Debian Dev Extend I've quickly (well, it's taken me all day, but still... ) put together a Debian-based development environment. It's based off Lenny and is therefore pretty much library compatible with our Angstrom. I'm going to guide you through setting up and using it now. Files: 125mb -...

Afternoon. Seems there's been a hellova mess with Extend Utils usage, which I'm going to attempt to fix some of it today... or failing that, towards the end of July when I find some free time. Effectively, there are two versions of Extend Utils being used... the "OldExtendUtils" package, and...

And the shader based transform stuff has now been finished. http://pandorawiki.org/GLESGAE:Shader_Based_Transformations Beware the headaches that the cameras can cause ;) I *highly* suggest you read through all three parts in order... so you can get a good understanding to what OpenGL actually...