Skip to main content

Wrapping your 54G Wi-Fi card for Linux Desktop

Ok so situation is something like this.(you can translate it to your situation to validate and justify your reasons to go wireless on a linux machine, I'll leave that to you). Your wife and kids want XP windows but you were made for Linux or vice versa. You just install a wireless network at home or if your employer/organization is considering experimenting to have dual boot workstations/laptops for employees , so they can boot on the operating system of their choice or are required to boot to a typical operating system.(linux i.e) as a thin client(say) in order to work on a payroll program for which all they need is a rolled out (customized OS) with linux on it(cos it's cheaper and there is no need to buy a XP machine with 1G ram just because the end user thinks it's his "birth right"! or the heavy classical windows application which is doing all calculations on the client PC ).

Well like I said what ever the reason, it's a compelling choice to go for a linux desktop, only to be left with a pukito problemas(little problem), how to do it?

Click here to download the article in PDF

and tell me that it really worked for you :-)

PS: I had to fry it in a PDF format because the blog was stretching real wide ;-).

Comments

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus

OS Virtualization comparison: Parallels' Virtuozzo vs the rest

Virtuozzo's main differentiators versus hypervisors center on overhead, virtualization flexibility, administration and cost. Virtuozzo requires significantly less overhead than hypervisor solutions, generally in the range of 1% to 5% compared with 7% to 25% for most hypervisors, leaving more of the system available to run user workloads. Customers can also virtualize a wider range of applications using Virtuozzo, including transactional databases, which often suffer from performance problems when used with hypervisors. On the administration side, customers need to manage, maintain and secure just a single OS instance, while the hypervisor model requires customers to manage many OS instances. Of course, the hypervisor vendors have worked hard to automate much of this process, but it still requires more effort to manage and maintain multiple operating systems than a single instance. Finally, OS virtualization with Virtuozzo has a lower list price than the leading hypervisor for comme...