Chief Fox,
The kernel tarball is well behaved. When you untar it it makes itself a new directory. I like to build kernels in my /home/<usrername>/ directory because I don't need to be root to do it. Move (mv) or copy (cp) the kernel tarball to your home. If you got it from kernel.org, it may already be there. Code:
mv /path/to/kernel ~ untar the kernel. Code:
tar xjf <kernel_tarball> Code:
ls If your distro provides a file /proc/config.gz zcat it to your new kernel. This is the configuration file of the running kernel. Code:
zcat /proc/config.gz ~/<kernel_dir_name>/.config Once you have a ~/<kernel_dir_name>/.config, change into the kernel dir and you must run make oldconfig to convert your old .config into a legal .config for the new kernel. Code:
cd ~/<kernel_dir_name> When that completes you have a valid kernel config file. run Code:
make The next steps must be run as root. Code:
make modules_install |
Hi, Chief, sorry for sounding fragmented, let me put the steps together sequentially.
Many linux commands are similar to Dos/win, like dir, cp, cd but GNU/Linux has much more. The directories are referenced from / if you cd to boot/grub/ (without the /), it will look from where you are, for boot/grub. Which may not exist. But if you cd /boot/grub it will look from / to find the dir. for example... Code:
door@MusicBox:~$ cd boot/grub (03-07 11:18) Firstly, when you up-zipped/tarred the kernel to the old folder Quote:
This is where the link to /usr/src/linux comes in, you can have many sources available, but only need to change the link to compile or build any of them (within reason) So go back, you can delete that "/usr/src/linux-source-2.6.28" directory later if you need the space. Start here.... move to the directory where the kernel .tar is, then (we need root (admin) access to write to /usr/src/folders, if the your shell terminal is already logged in as root, leave out the preceeding "sudo") sudo tar cjf linux-2.6.30.tar.bz2 /usr/src/linux-2.6.30 change to the root (/) directory, type cd / (enter) Or cd.. enter until you get there. remove any old link... sudo rm -rf /usr/src/linux create a new link to the new kernel sources... sudo ln -s /usr/src/linux-2.6.30 /usr/src/linux now you should be ready to configure the kernel. cd to it to make sure it's there and ls (list the files) ls /usr/src/linux (it should be the same as /usr/src/linux-2.6.30) save a backup copy of /boot/config to /boot/config-old cp /boot/config /boot/config-old, (if you have done it, skip it. ;-)) Before you apply the patches, configure the kernel based on the old one (it works, right?) cd /usr/src/linux make oldconfig (this will apply the old /boot/.config file to the new Makefile) You may get questions about any new stuff in the kernel, it's generally best to follow the defaults, unless you recognise something. You may require the dev packages to do this, but unless you want to customise it further, you can probably skip the config part. (make xconfig, or menuconfig) make all && make modules_install && make install. If all goes well you should be able to boot into the new kernel just by rebooting. If you see errors, and make stops, post those here for us to check. Don't reboot if you get errors, it may break your system! Generally there are warnings, but rarely do they compromise the system, they are just messages. see how you go, regards Glenn |
Configuring flash...<edit>sorry I missed sneddy's post #16, he's not wrong. :-)</edit>
try to install nspluginwrapper (netscape-plugin-wrapper) Where does the flash files live? Code:
locate flash like... ~/.mozilla/../plugins From somewhere @LQ Quote:
Code:
#!/bin/bash I ended up making a script for my system, and I used to use it, but have not for a while. It has clips of text from the install and debug info too. Heaps of redundant/commented text (#) first run... locate libflashplayer.so && locate npflash.so then edit this, changing the addresses to match your system. libflashplayer-linking-script.sh Code:
#! /bin/bash full text, libflashplayer-linking-script.sh, this is for an older system, but you may see what I mean. Code:
#! /bin/bash see how you go. Regards Glenn |
All times are GMT -5. The time now is 04:15 PM. |