I recently got a new printer for my home network. My old Epson Photo 870 printer with a D-Link Ethernet-to-parallel port printer server thing suddenly died one day not too long ago.
I opted for a solution with native Ethernet support that could also work as a copier and scanner so that those (even though rather rarely needed) functions would also be dealt with nicely. (In fact fax too, but I can’t think I’ll ever use that so I haven’t bothered to connect it to the phone system.) I went with the HP C6180 thing, since seemed like a nice setup for a fairly low price. Even though I don’t necessarily plan to print to it from my Linux hosts, I did read some positive reviews about it when used from Linux with CUPS so that was another point talking for this particular model. The printer even has wifi support but I’m using wired Ethernet since it is faster and I have the printer standing next to my wifi router anyway. Also, having scanner supported would mean I can finally put away my 7 year old USB scanner that I’ve been lugging out to use on occasion.
Sometimes (or is it often?) we get to hear that the printer situation on Linux is horrible or at least far from perfect, and while I agree with that I find the situation on Windows horrible – but for entirely different reasons
I followed the printer’s user manual on how to install it on Anja‘s (my wife’s) laptop that runs Windows XP, by inserting the CD and clicking “yes – over Ethernet” etc and it went on and and installed. And wow, did it get installed!
It brought four new icons to the desktop and after the lengthy process was at the end there were at least ten new processes running in the system and for some reason they actually made an impact and the system felt slower! I had to go on a kill frenzy to clear up the worst mess. The amazing part is that even though I killed every single process starting with “HP”, everything still worked exactly like I wanted. And with “msconfig” I could also prevent some of the worst stuff to start again at next reboot… (This kind of behavior is sadly not specific for printers-only on Windows…)
I did have some initial quirks with the printer, until I set it to use a fixed IP address. I’m not sure it really had something to do with it, but I wanted fixed IP anyway and the problems seemed to vanish.
OK, since I already posted about this subject twice I guess I should also post the verdict as of now:
no no no and nej
Although with a very slim margin.
FLOSS weekly just came out with episode 19 containing a fine interview with git‘s maintainer Junio Hamano.
Engadget stops their podcast after 109 episodes.
In general I think there’s a lack of good tech/Linux podcasts.
There’s this saying that a picture is worth more than a thousand words… The picture above is a cropped rip-off linked from the groklaw-article this picture will take you to. It is quite simply the OOXML standard suggestion next to the ODF one.
As Austin Appel posted on the Rockbox mailing list (early this morning, euro time), Rockbox now runs on the SanDisk Sansa e200R models.
In the end, it shows there really isn’t much difference between the two e200 versions. The Rhapsody models have a modified USB stack somehow that makes it hide the second “hidden” partition in which the bootloader and system software (mi4) is stored.
The Rhapsody bootloader doesn’t allow bootloader updates, and it also actually verifies the digital signature in the mi4 files, so in order to allow Rockbox we have to do a rather funny work-around: use e200tool to make it start the plain e200 bootloader and use that bootloaders recovery mode to upload a binary-patched version of the Rhapsody bootloader. The patched version puts back the old flawed signature check from the vanilla e200 series.
When the old broken BL signature check is in place, we can “upgrade” the target using the normal means and just put a Rockbox bootloader mi4 and the Sansa will then nicely load and run that.
The Free Software Conference Scandinavia will be held at ITUniversitetet in Gothenburg, 7-8 December 2007.
I’m invited to do a talk there and so I plan. The fscons site that’s supposed to cover this event seems to remain inaccessible though…
The subject? curl – but I haven’t yet written the description for it so I’ll present that later on.
Given the recent e250R i2c rom dump, MrH brought an analysis of what the rom actually contains and it is indeed the pre-bootloader code that loads the bootloader from the NAND flash and starts it. The perhaps most interesting part is that the e250R’s i2c rom dump is identical to the vanilla e280 one we have… meaning that they both load the bootloader the same way!
So here’s MrH’s suggested steps (keyed in on the wiki page by me) to convert your R model Sansa to make it capable of loading and starting the Rockbox bootloader.
I have a fairly new phone, the Sony Ericsson w580i and I think it is a neat little thing.
I’ve been using it as a usb-storage device at home under Linux without any problems, and I’ve pretty much filled my extra 4GB M2 card with music from my collection.
Today I decided to try to get a picture from my phone to my work PC (which is running… eh, Windows XP) and guess if I’m up to a shock: it doesn’t talk to the phone. It claims it can’t find any drivers for it and for some reason it doesn’t just go for usb-storage (even though we know now that it is OHCI compatible – at least).
Crap. On the Sony Ericsson site they offer the Sony Ericsson PC Suite 2.10.38 (for Windows Vista/XP) which is a whopping 44.8 megabytes! And all I want is to access my phone as UMS. Grrrr.
Once installed, I can access the phone fine but now I get that bonus popup annoyance windows that repeatedly asks me if I want to reboot the computer so that the new stuff can take effect…
Yes, I got to see the character problem several times more (on bus 178 and 670) after my previous LED display post, and I also got it confirmed by friends who saw it on other buses. It hadn’t been fixed, but clearly the displays in some buses show the correct letters.
I contacted some friends I know have some connections on the bus company, and according to “BL” all systems are supposed to be fixed and should display the letters correctly… He did say that he has forwarded my question onwards so hopefully we’ll get some further updates on this soon.
I got a nice quote forwarded from BL about this and it says that this is a failed installation by the techies that installed the sign on these buses. He (the person who wrote what BL forwarded) also said that if there appears “single buses” with this failure still present he wants to know the bus number to be able to fix…
So, if you read this and get to see the dreaded Ã¼-letter on a bus, take a note on the bus number and time (and I believe the “vagnnummer” – the unique vehicle number printed on the outside of the bus) and report it. You can just post a comment to this entry if you can’t find a better place to post it.
(BTW, the photo is taken with my w580i phone and darn is it hard to take photos in the bus. When the bus finally stops at this particular stop, the sign switches text to the end station name so I could only take photos of the sign while driving…)
kerneltrap writes an interesting piece about how some Linux kernel developers wants to remove the BSD parts of the dual-license that appears in several files (and thus keep only the GPL-part) that are kind of co-developed with parts of the BSD community. Complete with lots of Theo de Raadt quotes. Spoiler: no, they’re not allowed to do so.
This was covered on slashdot.