Debian/zaurus Faqs (plan)

[ZDevil]

Now there is a draft version of the installation guide to installing debian on the Zaurus. Perhaps it's also a good time to think about its sequel.

This is just a rough plan. If you have already gone through the process and have the experience/skills, come join us!
The idea is we first throw out the bits, then when the list begins to grow, we will have another pinned thread.
It may not be a good thing to start out right away with a pinned thread to avoid too many discussions and debates in it. The ultimate pinned thread is supposed to be for reference. And this thread may serve as a kinda buffer or filter for the pinned thread.

Part II FAQs
No rules to follow, but just one basic principle of KISS (keep it short and simple)

Rough outline:
1. After installation (anything missing from in installation guide)
2. Network connection (configurations, supported card models, etc)
3. Basic package management commands (apt-get)
4. Binding mouse buttons to keyboard
5. Brightness adjustment
6. Bluetooth
7. X-windows (including WMs)
8. Sound issues
9. Compilation: onboard and cross
10. Other known issues

I suggest replying this way may make the discussion cleaner:

2. Network connection
-- Wifi CF card supported: Symbol Spectrum 24
5. Brightness adjustment
-- Use the setfl script ...blahblah

It is just my little suggestion. What do you folks  think?

[cortez]

What about the swiffle on the back. It has been sitting there useless for quite some time  

[ZDevil]

"swiffle on the back" =     ?

Yeah, quite a bit of info is already out there, but the bits are scattering all over the threads. Wouldn't it be nice to have a one-stop thread for this, just like the installation guide?

[koan]

The ultimate pinned thread is supposed to be for reference. And this thread may serve as a kinda buffer or filter for the pinned thread.

Why not put it on the Wiki ?

The problem with pinned threads is that they are no good for reference: you have to scan through several pages to find the up to date info. Working backwards from the last post also takes time because the last post usually assumes you read all the previous posts.

Some of us are working through the current wiki, trying to bring it up to date. A lot of information e.g. window managers/X is surely going to overlap ?

[ZDevil]

Thanks. The main reason why I haven't put the guide to the wiki yet is because the content is complicated and needs a while for testing/correction/verification.
As I put in the beginning of the pinned thread on installation methods, the next version will be on the wiki once the content becomes more or less stable.

IMHO the negative side of posting in the wiki right away in this case is things may not have been verified. Changes are allowed in the wiki, but too frequent/many changes will defeat the purpose.

Don't forget that many (or most) of us here have only started playing with the many different Debianization for a week or so.  

So that's why I am thinking of using the threads (just) as a filter. In the end all the gems will be shelved on the wiki.  

[jpmatrix]

Thanks. The main reason why I haven't put the guide to the wiki yet is because the content is complicated and needs a while for testing/correction/verification.

that's the aim of a wiki no ? so that many user can read & write at the same time...
or you can also use my wiki as a temporary storage ?

[ZDevil]

Hmm... After thinking for a while, i begin to agree with you guys.

Then again, perhaps at least a planned hierarchy (e.g. networking > wifi cf card > supported models) will be nice, at least better than a long list of unorganized questions filling up the pages. Clearing them up and relocating them may waste more time than planning beforehand... or not?

[2or0]

ZDevil, I wrote a simple manuscript and uploaded some packages in following link. In order to write this and to ckeck the packages, I reinstalled everything from scratch. I hope that this will help you write the installation guide.

http://yonggun.tistory.com/54

[ZDevil]

Bravo!  
It's definitely more convenient to use your repackaged armel .deb than my provisional zaurus-hardware-eabi tarball (although they work similarly).
I will update the guide as soon as I can spare time for that, and will do so tomorrow night the latest.

Shall we also start a custom armel package repositiory to host your packages and also those to be (re)compiled?

[ZDevil]

BTW i have a question about your 2.6.23.1 kernel: I see the name has hda1. Does it also work for SD and also on C1000?

[2or0]

Bravo!  
It's definitely more convenient to use your repackaged armel .deb than my provisional zaurus-hardware-eabi tarball (although they work similarly).
I will update the guide as soon as I can spare time for that, and will do so tomorrow night the latest.

Shall we also start a custom armel package repositiory to host your packages and also those to be (re)compiled?

I wanted to make a feed for these packages but I don't have a space. If someone share his space, it would be very good. Also these packages are mostly from angstrom stuff. I never compiled them but I have many packages already compiled such as zbedic, justreader, and so on.

BTW i have a question about your 2.6.23.1 kernel: I see the name has hda1. Does it also work for SD and also on C1000?

I think it is possible. Thanks to uboot, we can install it on sd.

[ZDevil]

jpmatrix, do you still have space for the packages?

I will also begin to compile some soon: Portabase, NoteCase, TuxCards, glHack, Sangband, emacs23, ...

[jpmatrix]

jpmatrix, do you still have space for the packages?

no problemo! i'm a little busy these days but from thursday i'll be "available"
so i'll open my ftp for you to upload and i'll put them on my web site!

[scottlfa]

Awesome, love the link working on sound atm.  usb-gadget-mode deb seems to have some issues, did not setup for me and was hell of hard to remove.

[2or0]

Awesome, love the link working on sound atm.  usb-gadget-mode deb seems to have some issues, did not setup for me and was hell of hard to remove.

The script is something wrong. I cannot figure it out so I remove the script in a package. In order to remove it, first remove start-up scripts: update-rc.d -f usb-gadget remove ; delete the information files: rm /var/lib/dpkg/info/usb-gadget-mod*; then reinstall the package in my blog which is repackaged. If you want to remove it, now you can do it.