Author Topic: my feedback on "Daniela". (Read 7164 times)

maslovsky · « **Reply #15 on:** March 10, 2004, 01:03:08 pm »

Quote

I\'m not against colouring of ls, I am against it corrupting the output with control codes at inappropriate times (e.g. if you are using a remote terminal). I would like to choose colours when I need them and suppress them when I\'m using things like \"expect\".

Changing ls means changing busybox, which also means breaking compatibility with lots of utils. We cannot afford that, we\'re not Sharp
If yuu want you can build your self a better version of busybox and replace it.

Quote

Regarding adding a sleep into /etc/pcmcia/blootooth, I added it to the line after \"echo \"Done.\" when stopping the card but it did not seem to make any difference. Should I redownload the latest BlueZ ipks? Does it help diagnose the fault if I say the bluetooth card\'s green light goes on and stays on? Ahh well, out with the battery....

Try to add it just inside the \"stop\" case, before any other actions like rmmod, etc are done.

Grimwiz · « **Reply #16 on:** March 10, 2004, 01:36:26 pm »

I\'ve got the development package installed and running - compiling angband as I type.

Direct link is http://www.zaurususergroup.com/modules.php...q=getit&lid=207

I dont really want to go near busybox but I will compile a standalone \"ls\"

bluetooth update - I moved the sleep 1 so it was between \"stop_uarts\" and \"rmmod rfcomm\" but it still halts as before.

tumnus · « **Reply #17 on:** March 10, 2004, 02:08:13 pm »

Quote

bluetooth update - I moved the sleep 1 so it was between \"stop_uarts\" and \"rmmod rfcomm\" but it still halts as before.

Sounds like you\'re editing the wrong file. I\'m pretty sure I said /etc/pcmcia/bluetooth, which is what I mean. In that script in the latest BlueZ ipks I put a sleep command. It\'s probable the sleep time just needs increasing.

See the BlueZ Howto for the latest packages

zbones · « **Reply #18 on:** March 10, 2004, 03:03:40 pm »

Quote

* eject my Bluemonkey Bluetooth card through software - the user interface locks up but plugging and unplugging the USB cable causes \"boing\" noises in Windows so I guess something must still be running. Just ripping the card out without stopping it does not always lock up the zaurus.

I have the same card and the same problem.

Just install \"bluez-zaurus_2.3-2.4.18d_arm.ipk\" (thanks again tumnus) and your problem will go away.

no need to edit or remove anything, just whack it straight on over the top of the exiting stuff.

***** EDIT ******
Erm, actually, don\'t do this.

It *was* all working fine until I rebooted it, and now it\'s not working at all.

At least it doesn\'t crash when you eject the card anymore
Peter

zbones · « **Reply #19 on:** March 10, 2004, 05:38:22 pm »

OK, reflashed and started again.

Here is what I have discovered. if you issue

Code: [Select]

hciconfig hci0 down before doing an eject, it works.

tumnus,
your /etc/pcmcia/bluetooth and the one in this rom are *totally* different.

This is much much bigger.

I will continue to experiment.

Peter

zbones · « **Reply #20 on:** March 10, 2004, 06:01:20 pm »

ok,
I seem to have it working now.
for the 5/3/04 qtrom do this as root :-

Code: [Select]

 vi /etc/pcmcia/bluetooth

:56                    (to jump to line 56)

o                       (to insert a line after "echo -n $"Shutting down $prog... ")

{tab key}hciconfig hci0 down

{cancel x key}   (to escape from insert mode in vi)

:wq                   (to save and exit)

works for me, how about you?

Peter

Grimwiz · « **Reply #21 on:** March 11, 2004, 05:40:02 am »

Adding the hciconfig line fixes the problem for me too. My line numbers match with yours, Zbones.

Grimwiz · « **Reply #22 on:** March 11, 2004, 05:41:51 am »

For those who were following the angband saga - it works fine if I shut down the gui and use the raw console but sadly doesnt work inside Qconsole.

maslovsky · « **Reply #23 on:** March 11, 2004, 07:36:25 am »

Quote

tumnus,
your /etc/pcmcia/bluetooth and the one in this rom are *totally* different.

This is much much bigger.

Basicaly that\'s because new ROM initializes bluetooth only upon card insertion, while original tumnus packages start bluetooth upon zaurus boot. The bluetooth script in /etc/pcmcia is basicaly the one that used to be in /etc/rc.d/init.d directory.

ScottYelich · « **Reply #24 on:** March 11, 2004, 12:24:38 pm »

look, as far as the ls... just compile gnu ls and put it in your path before the busybox ls, etc. you can then
set LS_COLORS=none or whatever. that way, you configure YOUR machine for YOUR taste, etc.

me, I hate ls color, and whenever I have had it, I was able to disable it with a setting, if you can\'t do that
with busybox, then put another bin in your path before... if that doesn\'t work, break the link to busybox, etc.

It\'s your machine -- configure it as you wish.

Scott

Grimwiz · « **Reply #25 on:** March 12, 2004, 07:10:27 am »

:-) ScottYelich. that makes two of us that dont like colours so far, but you missed my point - blindly adding control characters is in my view a bug, nothing to do with preferences. One reason why linux has improved so much so fast is because people roll back bugfixes into the distributed code so that we dont all have to reproduce the same fixes to progress. I would concur that this forum is the wrong place to discuss busybox bugs though. Consider the matter closed, I will not discuss \"ls\" further.

ScottYelich · « **Reply #26 on:** March 12, 2004, 10:27:50 am »

I agree... in the past I have hard coded vt control codes into some programs ...
good luck to anyone not on a VT compatible, eh?

so, same goes with colors, etc. :-]

Scott
ps: ever come across a rabid mirc user in irc?

Grimwiz · « **Reply #27 on:** March 18, 2004, 03:38:30 am »

Installed Xqt, looks like running angband in an xterm works perfectly.

News:

Author Topic: my feedback on "Daniela". (Read 7164 times)