is here :
http://www.dedoimedo.com/computers/grub.html
Friday, August 1, 2008
Wednesday, July 30, 2008
How to setup a DNS server in Linux
Check these out :
http://www.freeos.com/articles/3956/
and
http://www.tldp.org/HOWTO/DNS-HOWTO.html
http://www.freeos.com/articles/3956/
and
http://www.tldp.org/HOWTO/DNS-HOWTO.html
Tuesday, June 24, 2008
Booting the kernel with desired #CPUs ...
.. can be done by adding the parameter 'maxcpus=#' on the boot line which specifies the kernel to boot (the line that starts with 'kernel'). This can be done either at the boot stage or by editing your own grub.conf file. Of course, editing grub.conf will make the system boot with the specified number of CPUs always.
Thursday, June 12, 2008
Saturday, April 5, 2008
Thursday, April 3, 2008
How does the open source community earn bread and butter ?
I always wonder, why the heck in this world do open source developers make their mehnat available to everyone. Microsoft might well be taking their ideas and selling on their own. Ya dude, but there's an honor code in the name of GNU public licence. Microsoft ... really ?
Sunday, March 30, 2008
Installing WiFi drivers for Broadcom 43xx in Ubuntu
A real pain let me tell you. I tried a 100 things before I stumbled upon a great tut. Involves fractionally more bit of work in terms of ndiswrapper installation etc but what the heck, it makes your system work. I tried this on my new HP dv6700t notebook and worked without any complications. So here we go :
https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx/Feisty_No-Fluff
You might ask what the heck is Ndiswrapper. To answer you, many wireless cards do not carry Linux drivers. To get around the problem, Ndiswrapper works by implementing Windows kernel and NDIS APIs and then dynamically linking the driver to its implementation. This enables the use of wireless drivers for Windows, on Unix like operating systems. Isn't it .... sweet.
People also propose using the firmware cutter (such as bcm4xx-fwcutter) because there might be cases where the device is recognized (because of the driver) but does not work because necessary firmware has not been installed. So this cutter uses Windows drivers to create firmware for ubuntu.
All this pain only if your card is a Broadcom and hence not supported by the Madwifi community. Else you can go for madwifi installation.
Cheers
https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx/Feisty_No-Fluff
You might ask what the heck is Ndiswrapper. To answer you, many wireless cards do not carry Linux drivers. To get around the problem, Ndiswrapper works by implementing Windows kernel and NDIS APIs and then dynamically linking the driver to its implementation. This enables the use of wireless drivers for Windows, on Unix like operating systems. Isn't it .... sweet.
People also propose using the firmware cutter (such as bcm4xx-fwcutter) because there might be cases where the device is recognized (because of the driver) but does not work because necessary firmware has not been installed. So this cutter uses Windows drivers to create firmware for ubuntu.
All this pain only if your card is a Broadcom and hence not supported by the Madwifi community. Else you can go for madwifi installation.
Cheers
Subscribe to:
Posts (Atom)