Re: cannot find the Kernelimage aft compiling
robert_wilhelm_land wrote: > > Andrei Pelinescu - Onciul wrote: > [...] > > A small example of what you call "masochistic": > > > > cd /usr/src/linux-2.2.18pre18 > > make config|menuconfig|xconfig > > make-kpkg --revision 9:blabla kernel_image > > dpkg -i ../kernel-image-2.2.18pre18_blabla*.deb > > If you keep up to debian - no problem, Andrei. In a few years we might > have 10 linux distributers and 10 diffrent kernel build routines - big > fun! There will always be the classical method so no problem. It is much easier to use make-kpkg especially if you want to use the same kernel on more machines. You will have only to copy the new .deb and dpkg -i. [...] > > You can use the classic kernel build process if you want (make clean dep > > bzImage modules modules_install). The kernel image will be in > > arch/i386/boot. > > > > [...] > > > > Andrei > > Oh sure - how many times did I report it didn't? I'll do it all over > again. > Did you control it the last time you made one? Yes, it works: kernel-source-2.2.17 (from Debian), 2.2.18pre18 (ftp.kernel.org+pre-patch-2.2.18-18), 2.4.0-test9 make clean make oldconfig dep bzImage and bzImage is in arch/i386/boot/bzImage. How exactly did you try to build your kernel? Did you get any error message? The kernel build process has nothing to do with Debian or any other distribution. It just needs make, gcc etc. Andrei
Re: cannot find the Kernelimage aft compiling
robert_wilhelm_land wrote: > [...] > As far as I'm concerned most distributions and README's recommend to > create a linux/ dir as a sub of src/ and I did so. > In the end this makes up: > /usr/src/linux/kernel-source-2.2.17/arch/i386/boot > - after x-tar'ing the kernet-sourcexx.tar.gz. Usually you find a > kernel image file in the above mentioned ..arch/i386/boot (not the > /boot!) and exactly there is none. > The impression I get now is - after reading your explaination - step > 2a/b would not work without step b/c (dpkg -i ../some-kernel-package > needs a *.deb file) which I would rather discribe as masochistic > because I have to learn another new kernel-build process which relies > only on Debian and cannot be used on other distributions. A small example of what you call "masochistic": cd /usr/src/linux-2.2.18pre18 make config|menuconfig|xconfig make-kpkg --revision 9:blabla kernel_image dpkg -i ../kernel-image-2.2.18pre18_blabla*.deb > Likewise, my > previous kernel-build process can be put into /dev/null because no > one knows what exactly happens using dpkg and make-kpkg and is not > able to tell where to find my kernel image file! Now that not what I > would expect which I would discribe as the "linux spirit". You can use the classic kernel build process if you want (make clean dep bzImage modules modules_install). The kernel image will be in arch/i386/boot. [...] Andrei
Re: sed question
Jesse Goerz wrote: > > I'm trying to write a script and as part of it I need to change the "/" in a > variable to a "." and then put it right back into another variable. I've > tried > using sed but can't seem to grip these regular expressions 8-(. Here's what I > got so far: > > echo $variable_before | sed s///./ variable_after Try: variable_after=`echo $variable_before | sed 's/\//./' ` (you must escape the "/") If you want to replace all the occurences of "/" add an 'g' : variable_after=`echo $variable_before | sed 's/\//./g' ` You can do this also only with bash: variable_after=${variable_before/\//.} and for multiple occurences: variable_after=${variable_before//\//.} Andrei
Re: Debian, PCMCIA and DHCP
Martin Fluch wrote: [...] > I forgot to say, that I use a PCMCIA card to connect to the internet... > [...] > > And thats the problem I have: I have no experience with that, I never > > played around with it and now I should get it working till Thuesday :-) > > Has somebody experience with this, perhaps even on an Debian 2.2 or Debian > > Unstable/Woody system (I use the later, but they shouldn't be that too > > different). Edit /etc/pcmcia/network.opts and set DHCP="y" or DHCPCLIENT="y" or PUMP="y", depending on the dhcp client you want to use. Also set IPADDR="". Now you only have to do a cardctl eject; cardctl insert (or change the scheme) and your network interface should get an ip address from the dhcp server. [...] > > Which packages do I need beside dhcp, dhcp-client? You need only one of them. There are 3 packages for dhcp clients: dhcp, dhcp-client and pump. I use pump. Andrei