I gave a thought of providing a description directly but then it was getting too messy, If you can suggest an alternate approach i am ready to try it out.
The tree controls just get in the way. There is not so much content here that it justifies needing to click 5 or 10 times just to see it all. When I first visited the page with NoScript, the tree was actually easier to see because it defaulted to fully open.
I'd also consider just inlining the "details" too with a simple "dirname - details" scheme; maybe color them a little differently (I wouldn't even go nuts, just a dark grey vs. black will be fine, not bright red or anything). Unfortunately, you've gone through a lot of work to make the content on this page quite difficult to use :(
I don't think an upvote is enough to show that I agree with you. Especially the last sentence. The info is very interesting, but I gave up after I opened the first tree.
Another problem jerf's design fixes is that you have no way of telling which line has a tooltip and which doesn't, and coupled with the fact the tooltips take a fraction of a second to appear waste my time.
let's spin it the other way: what advantages would following the LSB have? there is little need for standard linux utilities to be easily ported to android, the standard utils are not included, and package management is dealt with in an android-specific way
The problem isn't getting ssh access (Cyanogen ships with the dropbear ssh server), but getting decent userland tools and possibly some form of package management. This is hard precisely because Android doesn't obey the LSB and assumes that mostly everything will be done in Java.
It would be very nice to have an OS designed for phones which would be a standard Linux with additional stuff on top. Sadly, Android is more of a Linux kernel without standard tools but with a bulky alien Java-based stuff to do everything.
It would be very nice to have an OS designed for phones which would be a standard Linux with additional stuff on top. Sadly, Android is more of a Linux kernel without standard tools but with a bulky alien Java-based stuff to do everything.
Maemo/Meego is/was exactly that: Debian Linux complete with apt, with a tablet and phone UI.
Has anyone tried creating a Debian/Android distribution (like Debian/kFreeBSD)? Mozilla's B2G (Boot To Gecko) OS uses the Android kernel without the Dalvik VM or frameworks. I don't know what B2G's userland looks like.
A Debian/kAndroid distro could be what Maemo/Meego wanted to be, but benefit from Debian's popular userland and Android device support provided by Google and device manufacturers.
Whatever the reasons for not following standards, no matter what company is doing it, I think they should be weighed against the advantages _to the computing community as a whole_ of following standards. Each user might ask themselves, "Is it more worth it for me to learn some nonstandard stuff that will only apply to one company's products, or to learn some standard stuff that applies to many companies' products."
I see clear advantages to everyone who has ever learned UNIX (and everyone who learns it going forward) of UNIX-like systems having a standard set of UNIX utilities and keeping things in their expected locations. Namely, there's less to learn and potentially wider applicability across a range of products.
Cool, but why can't I see this hierarchy when I plug my HTC Droid into my Mac? I certainly don't see a /data/data directory, even with ls -a. Do I have to root the thing?
You are likely seeing the SD card or 'external storage' contents. The filesystem isn't exposed without extra work. Rooting of course, gives you access to write (and read some areas)
If you want to look at the full hierarchy, get the android developer tools and use adb. If you just plug it into your mac, you'll see the SD card instead.
