This website is a sort of personal project, rather than a proper blog – the reason I make this distinction is because I usually don’t have anything interesting to say; at least, nothing that would be of any interest to anyone who doesn’t know me.
Tag: linksys
Hardcore HTML
I’ve never really had any cause to write large posts using WordPress, except for my NSLU2 guides – and even then the built-in WYSIWYG editor was good enough, albeit a little clunky and requiring gentle persuasion every so often.
But after changing blog themes the other day, I realised the NSLU2 pages were actually quite dependent on the underlying CSS – and for some themes, this means that they looked rubbish.
Another new look
One of the features of WordPress is the ability to change the theme of a blog with the click of a button; and that’s exactly what I did when the K2 theme, although quite powerful in its own right, was found lacking again.
With this theme, my NSLU2 guides currently look like they were formatted by a 4-year-old, so I might get round to fixing them, eventually. They’re by far the most popular pages on this site!
Linksys NSLU2: print server with CUPS
Installing and configuring CUPS with an HP PhotoSmart 8150 was ridiculously easy, since CUPS comes complete with HPIJS (the HP linux print drivers). The printer is attached via a USB hub on port 1.
Installing CUPS
To start, install CUPS and its documentation package. Strangely enough, the docs include a lot of the files required to run the CUPS web interface.
ipkg install cups
ipkg install cups-doc
Linksys NSLU2: time server with NTP
If you’re running an email server on your Slug, where accurate server time is vital, or you simply want the Slug’s system time to be accurate, you need to make a few changes.
When it comes out of the factory the Slug has an inherrent bug which causes the internal clock to lose time; apparently Linksys tried to fix this problem by adjusting the time regularly (using cron) but it seems the time is adjusted in the wrong direction – thus, the error is doubled. This problem is fixed in Unslung 2.6 and higher anyway (Unslung 2.10 is the latest release as at Jan 2009), so we can remove the relevant crontab entry.
