One of the reasons that I love/hate Linux so much is that it makes a lot more interesting things possible, but it also makes a lot of pretty straightforward things a pain in the ass.
I’m not sure which category this one falls into. Information wants to be free, I’m told, but the other side of that is that sometimes information dies in the wild, of age, starvation or neglect. Most of the information I can find about this little project is either crippled or gone, and it’s frustrating.
- “Werewindle”, a Dell Inspiron 3800 running a religiously-updated Debian Sid.
- “Shiv”, A Cassiopeia E-100 PDA running a deeply-annoying WinCE 2.11
- To get IR working properly on the Dell
- To get an IR connection between the laptop and the PDA.
- To be able to futz around in the Shiv’s filesystem over IR with smbclient, so that I can put some kind of Linux on it, in the hopes getting something that’s less wildly irritating running on this otherwise-respectable widget.
I’m having problems with the connection; I’ve got IRDA set up on the laptop; I can, after I’ve booted the machine up, see irda0 in ifconfig, and
cat /proc/net/irda/discovery/ tells me that the laptop can see the pda.
I’ve got pppd set up as described here, including their perl script near the end, but that’s not giving me much love. Before I even get close to the Samba bit, I run into two problems.
- Werewindle doesn’t like ipchains, and I don’t know enough about either
iptables or ipchains to rewrite that script.
- After bootup, I can put Shiv next to Werewindle and the “cat /proc…” bit works as advertised. If I start screwing around with the pppd scripts, then irda discovery stops working, ifconfig stops showing irda0, and I’m basically cured of all symptoms of success.
- Under no circumstances have I been able to get Shiv to recognize that
it is connected.
If you, intrepid reader, have any idea how I should attack this, I would be very much indebted.