Alex Launi's dashboard

You'll need the recovery media provided by your netbook distributor. If you weren't provided with recovery media, you'll need to contact the manufacturer.

It would be useful for us if you could tell us why jolicloud didn't meet your needs and why you'd like to return to XP.

I'm not sure this is a good idea, this makes it very easy for people to run things as root which they may not actually want to (as well as using up precious bytes on small SSD drives). Making users open a terminal and very explicitly run something with escalated privileges adds a small layer of security, and prevents people from doing stupid things and compromising their netbook.

This use case is also primarily needed for more advanced users. 'Average' users will probably never need to do this as all of the software they need to run should be available in the application directory.

If you'd like to set this up on your own machine, install the nautilus-gksu package, logout, and log back in.

This isn't a sudo su special case; once you've used sudo, it doesn't prompt you the next them you use sudo for that session (within a time period). This is only dangerous if someone has physical access to your machine within (I think) 5 minutes of you doing an operation as root with sudo. If this is the case, you're out of luck anyway because as soon as someone malicious has physical access to your machine, they will have full access to your data.

If we've modified the code, we are obligated to provide source upon request; it is not required to keep the source in a pubically available location at all times. This said, we have not modified very much (I can't think of any userspace application off hand) from upstream ubuntu- therefore it is sufficient to point you upstream for source. If there is an application we've modified that you would like the source for, please shoot us an email and we'll verify that it's a modified application, and provide source. – Alex Launi, on September 01, 2009 21:37

"As long as any changes they're making to GPL code (e.g., the UNR interface) is pushed back into the appropriate source base, they're complying with the GPL."

This is not exactly true, we can forka and maintain our own codebase, it's just that our forked version must also be licensed GPL.

Mono can run most .NET applications, unless they use certain windows only APIs, or make external calls to windows only dlls. You can at least try it, and if it doesn't work try emailing the developers to make it Mono friendly, it shouldn't be much work and the Mono project even has a tool that will assess your .NET code tree and tell you how much work it would be to make it entirely mono compliant.

You can use Alt+left-arrow to go back as a workaround, but I agree there needs to be a better solution.

I assure you that Jolicloud takes licensing issues very seriously. You are correct that we are indeed based upon free software as Jolicloud is a new, friendly, and innovative UI on top of the fantastic ground work the Ubuntu project has done. The source code for the Jolicloud specific bits will be released when we release the software publically. Since it's software that we've developed we reserve the right to license it how we chose, and that includes relicensing it as GPL/MIT/some other free license when we're ready. So please, take this promise that we are fully GPL compliant and that all of the GPL'd software in Jolicloud has source available from the Ubuntu project, or the upstream project.

I assure you that Jolicloud takes licensing issues very seriously. You are correct that we are indeed based upon free software as Jolicloud is a new, friendly, and innovative UI on top of the fantastic ground work the Ubuntu project has done. The source code for the Jolicloud specific bits will be released when we release the software publically. Since it's software that we've developed we reserve the right to license it how we chose, and that includes relicensing it as GPL/MIT/some other free license when we're ready. So please, take this promise that we are fully GPL compliant and that all of the GPL'd software in Jolicloud has source available from the Ubuntu project, or the upstream project.

As for the issue of invitations- at this stage in our development it would be counter productive for us to allow unlimited downloads of our iso. We need to make sure that our systems can handle the load, and flooding them with tens of thousands of users all at once is not a practical way of doing this. By adding 1000 or so users at a time, it allows us to tweak our systems accordingly so that we can provide a very reliable service when we're ready for final release. If we opened the flood gates, and then had an issue, many users would not try again, and we wouldn't be able to make sure we're scaling properly.

I hope I've addressed your concerns. I'm sorry that you haven't received an invite yet, but we're sending them out as fast as we can. Stay patient, it'll come.

I assure you that Jolicloud takes licensing issues very seriously. You are correct that we are indeed based upon free software as Jolicloud is a new, friendly, and innovative UI on top of the fantastic ground work the Ubuntu project has done. The source code for the Jolicloud specific bits will be released when we release the software publically. Since it's software that we've developed we reserve the right to license it how we chose, and that includes relicensing it as GPL/MIT/some other free license when we're ready. So please, take this promise that we are fully GPL compliant and that all of the GPL'd software in Jolicloud has source available from the Ubuntu project, or the upstream project.

As for the issue of invitations- at this stage in our development it would be counter productive for us to allow unlimited downloads of our iso. We need to make sure that our systems can handle the load, and flooding them with tens of thousands of users all at once is not a practical way of doing this. By adding 1000 or so users at a time, it allows us to tweak our systems accordingly so that we can provide a very reliable service when we're ready for final release. If we opened the flood gates, and then had an issue, many users would not try again, and we wouldn't be able to make sure we're scaling properly.

I hope I've addressed your concerns. I'm sorry that you haven't received an invite yet, but we're sending them out as fast as we can. Stay patient, it'll come.

Can you copy and paste the python trace?

This is an awesome idea, there are a lot of people I'd like to get notifications for, but not necessarily on my phone. IM would be perfect for some, but others SMS is needed. I hope this is implemented!!