Linked by Thom Holwerda on Thu 10th Jun 2010 12:53 UTC
Linux This is a problem I've been dealing with for a while now. I have a Lexmark printer which I've bought without checking for compatibility with Linux (I bought it when I was still using Windows), and as it turns out, this printer is not supported in Linux. I switched to Linux on my main desktop full-time late last year, so instead of to my desktop, I hooked this printer up to my bedroom Windows 7 media server/HTPC, and whenever I need to print, I just drop the file in question on this machine, and print form there. I need a better solution. Update: As it turns out, Lexmark has recently started releasing Linux drivers (good stuff). Still, the problem at hand stands, as there might still be other printers that suffer from the same problem.
Permalink for comment 429587
To read all comments associated with this story, please click here.
Nice dimming effect
by xiaokj on Thu 10th Jun 2010 23:24 UTC
Member since:

Note comment title.

Is this new? When I saw the title I was expecting the all powerful solution to the printing problem.

I used to use a pathetic machine to be my print server using simply a Windows 98 SE share, but eventually the machine simply just died. The hardware was going, and I couldn't even switch it on. No floppy, no cd drive, no image, nothing. I wanted to make it a network share, but even the CD drive could not make it.

When the print server went down, I simply couldn't take it any longer (the Canon print craplet deserved the cannon) and I literally walked my father to the shops to get a supported Brother. Now I can even scan from linux.

Not to say that the Brother drivers are any less crappy, but at least the printer is moderately cheap and still functional. The immediate improvement in scanning and printing facilities made my father thank me for making him spend, though.

(The lesson to take from this is: STUDY BEFORE BUYING and just buy the right one from the start and you can save the frustrating expenditure later!)

EDIT: Anyone figured out how to allow virtual machine guests to access certain hardware? I mean, I can understand why cpus and graphics, keyboard and mice must be virtualised, first because they execute code and anything that executes code is potential danger, and second because you need to share keyboard and mice between the different guest instances and host. But why are printers and other rubbish not selectively allowed to interact with the guests? If we are allowed, then I can wean my parents completely off Windows by running the required drivers in a VM guest in Windows and letting the slave no access to the net and just as a bloated behemoth print server do its job in the sandbox.

Ideally, someone in power (or with loads of $$$) can just legalise braindeadness -- like no more x86 family, no more EFI/bios and mandate coreboot+openbios/firmware, mandate PCL/PS, mandate usb multifunction printers to appear and simply a usb hub connected to a separated scanner and printer so as to be completely handled as two separate machines to the OS...

(I realise the root cause of all those above is highly linked with Windows, just like how, in the Unix Haters' Handbook, sensible system structure gave way to coredumps under Unix. It is all just the problem with monocultures. And it is all due to the consumers taking all these nonsense. And it is all due to education, just like from the above. What is happening in schools these days?)

Edited 2010-06-10 23:37 UTC

Reply Score: 1