Re: [Debian] iso9660 in 2.0.34 ?
Hi, Hmm. I think I shall put a note at the bottom of the man page pointing to the /usr/doc/kernel-package area. I have gotten too used to looking at /usr/doc, apparently. I have tried to put a fairly complete tutorial about kernel compilation in /usr/doc/kernel-package/README.gz Maybe I should create HTML docs and send it to the www.debian web master. What about putting a Readme.debian in the /usr/src/linux dir of the debian kernel-source package, in which you tell people about compiling kernels the debian way? I think that would be really helpful to new debian users. It seems that the questions that need the answer `use make-kpkg' are among the most frequently asked on this list. Eric -- E.L. Meijer ([EMAIL PROTECTED]) | tel. office +31 40 2472189 Eindhoven Univ. of Technology | tel. lab. +31 40 2475032 Lab. for Catalysis and Inorg. Chem. (TAK) | tel. fax+31 40 2455054 -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: [Debian] iso9660 in 2.0.34 ?
Hi, E == E L Meijer \(Eric\) E.L. writes: E What about putting a Readme.debian in the /usr/src/linux dir of the E debian kernel-source package, in which you tell people about compiling E kernels the debian way? I think that would be really helpful to new E debian users. It seems that the questions that need the answer `use E make-kpkg' are among the most frequently asked on this list. That has been done already in newer version of kernel-package (don't the latest kernel-source-* have a README.debian in there?) manoj -- He had occasional flashes of silence that made his conversation perfectly delightful. -- Sydney Smith Manoj Srivastava [EMAIL PROTECTED] http://www.datasync.com/%7Esrivasta/ Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: [Debian] iso9660 in 2.0.34 ?
On 16 Jul 1998, Manoj Srivastava wrote: : Hi, : E == E L Meijer \(Eric\) E.L. writes: : : E What about putting a Readme.debian in the /usr/src/linux dir of the : E debian kernel-source package, in which you tell people about compiling : E kernels the debian way? I think that would be really helpful to new : E debian users. It seems that the questions that need the answer `use : E make-kpkg' are among the most frequently asked on this list. : : That has been done already in newer version of kernel-package : (don't the latest kernel-source-* have a README.debian in there?) pavlov:~ $ dpkg -l kernel-package Desired=Unknown/Install/Remove/Purge | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ NameVersionDescription +++-===-==- ii kernel-package 4.11 Debian Linux kernel package build scripts. pavlov:~ $ ls -lAF /usr/doc/kernel-package total 33 -rw-r--r-- 1 root root 3004 Mar 27 12:37 Flavours.gz -rw-r--r-- 1 root root 2000 Feb 9 17:30 Multi-Arch.gz -rw-r--r-- 1 root root 2323 Mar 5 16:37 Problems.gz -rw-r--r-- 1 root root 7053 May 11 01:54 README.gz -rw-r--r-- 1 root root 1606 Mar 5 16:42 Rationale.gz -rw-r--r-- 1 root root13240 May 12 13:58 changelog.gz -rw-r--r-- 1 root root 1550 Feb 18 01:09 copyright There's a README.gz - was the logical thing to read when I looked in there. -- Nathan Norman MidcoNet - 410 South Phillips Avenue - Sioux Falls, SD 57104 mailto://[EMAIL PROTECTED] http://www.midco.net finger [EMAIL PROTECTED] for PGP Key: (0xA33B86E9) -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: [Debian] iso9660 in 2.0.34 ?
Hi, kernel-source-2.0.33_2.0.33-9.deb (found in my hamm mirror) -rw-r--r-- root/root 844 1998-05-01 04:38 usr/src/kernel-source-2.0.33/README.Debian That points to stuff in /usr/doc/kernel-source-2.0.33/, which has more docs. I mean, I am running out of places to put pointers in ;-) manoj -- UNIX Shell is the Best Fourth Generation Programming Language It is the UNIX shell that makes it possible to do applications in a small fraction of the code and time it takes in third generation languages. In the shell you process whole files at a time, instead of only a line at a time. And, a line of code in the UNIX shell is one or more programs, which do more than pages of instructions in a 3GL. Applications can be developed in hours and days, rather than months and years with traditional systems. Most of the other 4GLs available today look more like COBOL or RPG, the most tedious of the third generation languages. _UNIX Relational Database Management: Application Development in the UNIX Environment_ by Rod Manis, Evan Schaffer, and Robert Jorgensen. Prentice Hall Software Series. Brian Kernighan, Advisor. 1988. Manoj Srivastava [EMAIL PROTECTED] http://www.datasync.com/%7Esrivasta/ Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: [Debian] iso9660 in 2.0.34 ?
Hi, Jay == Jay Barbee [EMAIL PROTECTED] writes: Jay ...I believe I am confused... I do not mind a little Jay automation, but currently in my lilo.conf I have 3 linux kernels Jay that I use. Jay This kernel-package util seems as if it takes this functionality Jay away from you and simply uses default (/vmlinuz) and that is it. Rubbish. Please do not spread FUD. I have, at times, a round dozen kernel images on my machine, all compiled with kernel-package. I even have 2-3 2.0.34 images *ON AT THE SAME TIME*. Look at my lilo.conf, 5 (count it, five) different options. kernel-package is about flexibility and ease of use, not for putting peole in a straight jacket. Please investigate before making assumptions about things. __ boot = /dev/hda delay = 50# optional, for systems that boot very quickly compact vga=normal# force sane state root = current# use current setting message = /etc/lilo.message verbose = 3 prompt timeout = 300 image = /vmlinuz label = 2 root = /dev/hda2 append = mem=95M read-only image = /vmlinuz.old label = 3 root = /dev/hda2 append = mem=95M read-only image = /vmlinuz.stable label = 4 root = /dev/hda2 append = mem=95M read-only image = /vmlinuz.reallystable label = 5 root = /dev/hda2 append = mem=95M read-only other = /dev/hda1 table = /dev/hda label = 1 __ Jay Perhaps I simply don't understand what you are telling me to do Jay with this kernel-package when I go to install or test a new Jay kernel. Yup. manoj == Advantages of using make-kpkg -- -- - - I have been asked several times about the advantages of using the kernel-package package over the traditional Linux way of hand compiling kernels, and I have come up with this list. This is off the top of my head, I'm sure to have missed points yet. Any additions welcomed. i) Convenience. I used to compile kernels manually, and it involved a series of steps to be taken in order; kernel-package was written to take all the required steps (it has grown beyond that now, but essentially, that is what it does). This is especially important to novices: make-kpkg takes all the steps required to compile a kernel, and installation of kernels is a snap. ii) It allows you to keep multiple version of kernel images on your machine with no fuss. iii) It has a facility for you to keep multiple flavours of the same kernel version on your machine (you could have a stable 2.0.33 version, and a 2.0.33 version patched with the latest drivers, and not worry about contaminating the modules in /lib/modules) iv) It knows that some architectures do not have vmlinuz (using vmlinux instead), and other use zImage rather than bzImage, and calls the appropriate target, and takes care of moving the correct file into place. v) Several other kernel module packages are hooked into kernel-package, so one can seamlessly compile, say, pcmcia modules at the same time as one compiles a kernel, and be assured that the modules so compiled are compatible. vi) It enables you to use the package management system to keep track of the kernels created. Using make-kpkg creates a .deb file, and dpkg can track it for you. This facilitates the task of other packages that depend on the kernel packages. vii) It keeps track of the configuration file for each kernel image in /boot, which is part of the image package, and hence is the kernel image and the configuration file are always together. viii) It allows to create a package with the headers, or the sources, also as a deb file, and enables the package management system to keep track of those (and there are packages that depend on the package management system being aware of these packages) ix) Since the kernel image package is a full fledged Debian package, it comes with maintainer scripts, which take care of details like offering to make a boot disk, manipulating symbolic links in / so that you can make boot loader scripts static (just refer to the symbolic links, rather than the real image files; the names of the symbolic links do not change, but the kernel image file names change with the version) x) There is support for the multitudinous sub architectures that have blossomed under the umbrella of the m68k
Re: [Debian] iso9660 in 2.0.34 ?
On 14 Jul 1998 18:21:21 -0500, you wrote: Rubbish. Please do not spread FUD. I have, at times, a round dozen kernel images on my machine, all compiled with kernel-package. I even have 2-3 2.0.34 images *ON AT THE SAME TIME*. Look at my lilo.conf, 5 (count it, five) different options. kernel-package is about flexibility and ease of use, not for putting peole in a straight jacket. Please investigate before making assumptions about things. [big snip] Having just installed Debian (coming from a Slackware version out of the back of a book) and being inundated with all the packages I could install (Debian 1.3.1, Version 2 beta cd in the post) I saw this make-kpkg package and, after reading article from people here on the list, thought I'd give it a try. I'm still a fairly novice user, but I manage to blunder my way around. After remembering the name (after trying make-kpg, make-dkpg, make-kdpg, find | grep make- :) Ah ha! found it. man make-kpkg. Humm, thats a bit short. man kernel-package.conf (or what ever it's called, I'm away from my machine at the moment). It appears the only option I want to set is the option to put the compiled kernel image in /boot. So I set this (you must set this option to true it says, but dosn't give an example about how to do it). Does make-kpkg run config for you? It dosn't say. I run make config first, and the run make-kpkg. Off it goes and makes my kernel. I wonder off to make a cup of tea, and do the washing up. Come back and it's finished. It hasn't made or installed the modules, it hasn't put the kernel into /boot. All it seems to have done is compile my kernel for me. All the functionallity you describe sounds really good, I (and many others by the sounds of things) might be missing the point here, but how do we USE this marvelous package? Is there any documentation, because the man pages are really, really poor. If there is no documentation, then this package is fairly usless unless you know how to use it correctly. A little pointer to how to start using the package correctly would be nice. -- Matthew Collins Mitral Systems Ltd arrgh! Sorry, spam filter in place. substitute nospam for matthew to reply by email. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: [Debian] iso9660 in 2.0.34 ?
On Wed, Jul 15, 1998 at 08:46:35AM +, Matthew Collins wrote: On 14 Jul 1998 18:21:21 -0500, you wrote: Does make-kpkg run config for you? It dosn't say. It does not run config...you have to run make [menu,x]config yourself I run make config first, and the run make-kpkg. Off it goes and makes my kernel. I wonder off to make a cup of tea, and do the washing up. Come back and it's finished. It hasn't made or installed the modules, it hasn't put the kernel into /boot. All it seems to have done is compile my kernel for me. right...go up on elevel (usually to /usr/src/) and you should see a .deb file int hat directory... just install that deb as if it were any other deb package just dpkg -i ... it will install the kernel and the modules. Then save that deb for laterhave to re-install the system?? want an identical kenrel somewhere else... there it is how do we USE this marvelous package? Is there any documentation, /usr/doc/kernel-package -Steve -- /* -- Stephen Carpenter [EMAIL PROTECTED] -- */ A favorite quote from a source I forget: Only Microsoft can take an algorithim that has been under years of public scrutiny and weaken it to the point where the entire key space can be searched in 3 days -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: [Debian] iso9660 in 2.0.34 ?
On Wed, 15 Jul 1998, Matthew Collins wrote: [ snip ] : All the functionallity you describe sounds really good, I (and many : others by the sounds of things) might be missing the point here, but : how do we USE this marvelous package? Is there any documentation, : because the man pages are really, really poor. If there is no : documentation, then this package is fairly usless unless you know how : to use it correctly. : : A little pointer to how to start using the package correctly would be : nice. RTFM kernel-package docs. All Debian documentation is in /usr/doc/packagename ... at the very least, there will be a copyright file there :) However, since Manoj is a very diligent maintainer, there's a wealth of information in /usr/doc/kernel-package . For starters, take a peek at the README.gz ... on the second page you would have found this: For the Brave and the impatient: 1% cd kernel source tree 2% make config # or make menuconfig or make xconfig and configure 3% make-kpkg clean 4% make-kpkg --rootcmd fakeroot --revision=custom.1.0 kernel_image 5% dpkg -i ../kernel-image-X.XXX_1.0_arch.deb 6% shutdown -r now # If and only if LILO worked or you have a means of # booting the new kernel. YOU HAVE BEEN WARNED!! With this example you'll also need the `fakeroot' package, or you can run line 4 with sudo (or su to root). You need root privileges to create a deb package. kernel-package is the coolest thing ever. It has a ton of options, works with Debian kernel source, non-Debian kernel source, stable kernels, unstable kernels ... -- Nathan Norman MidcoNet - 410 South Phillips Avenue - Sioux Falls, SD 57104 mailto://[EMAIL PROTECTED] http://www.midco.net finger [EMAIL PROTECTED] for PGP Key: (0xA33B86E9) -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: [Debian] iso9660 in 2.0.34 ?
On Wed, 15 Jul 1998 09:04:42 -0500 (CDT), you wrote: RTFM kernel-package docs. All Debian documentation is in /usr/doc/packagename ... at the very least, there will be a copyright file there :) [snip] kernel-package is the coolest thing ever. It has a ton of options, works with Debian kernel source, non-Debian kernel source, stable kernels, unstable kernels ... -- Nathan Norman MidcoNet - 410 South Phillips Avenue - Sioux Falls, SD 57104 mailto://[EMAIL PROTECTED] http://www.midco.net finger [EMAIL PROTECTED] for PGP Key: (0xA33B86E9) Ahh! Now I know where the docs are, I'll certainly RTFM. One problem (not really a problem, but hey) is that there is so many new things when you install a new Debian system that you don't know where to start looking. I've always typed man whatever and see what I get. I guess I should look in usr/docs first. I have a hard enough time remembering the name of things I've installed. :) Thanks for the pointers. -- Matthew Collins Mitral Systems Ltd arrgh! Sorry, spam filter in place. substitute nospam for matthew to reply by email. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: [Debian] iso9660 in 2.0.34 ?
Hi, Hmm. I think I shall put a note at the bottom of the man page pointing to the /usr/doc/kernel-package area. I have gotten too used to looking at /usr/doc, apparently. I have tried to put a fairly complete tutorial about kernel compilation in /usr/doc/kernel-package/README.gz Maybe I should create HTML docs and send it to the www.debian web master. manoj -- Better late than before anybody has invited you. Ambrose Bierce Manoj Srivastava [EMAIL PROTECTED] http://www.datasync.com/%7Esrivasta/ Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: [Debian] iso9660 in 2.0.34 ?
On Tue, Jul 14, 1998 at 09:21:28AM +0200, Nico De Ranter wrote: Hi, can anybody tell me how to enable iso9660 support in a 2.0.34 kernel. There doesn't seem to be an option when I do 'make menuconfig'. In menu filesystems set on Native language support (Unicode, codepages) you get iso and fat options. Mirek -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: [Debian] iso9660 in 2.0.34 ?
On Tue, Jul 14, 1998 at 09:21:28AM +0200, Nico De Ranter wrote: Hi, can anybody tell me how to enable iso9660 support in a 2.0.34 kernel. There doesn't seem to be an option when I do 'make menuconfig'. In menu filesystems set on Native language support (Unicode, codepages) you get iso and fat options. Ah, I didn't know iso and fat where languages :-) Thanks Nico Mirek -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- -- Nico De Ranter Sony Service Center (PSDC-B/DNSE-B) Sint Stevens Woluwestraat 55 (Rue de Woluwe-Saint-Etienne) 1130 Brussel (Bruxelles), Belgium, Europe, Earth Telephone: +32 2 724 86 41 Telefax: +32 2 726 26 86 e-mail: [EMAIL PROTECTED] -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: [Debian] iso9660 in 2.0.34 ?
On Tue, Jul 14, 1998 at 09:53:11AM +0200, Nico De Ranter wrote: Ah, I didn't know iso and fat where languages :-) Changed in 2.0.35 anyway, just out. Hamish -- Hamish Moffatt, [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Latest Debian packages at ftp://ftp.rising.com.au/pub/hamish. PGP#EFA6B9D5 CCs of replies from mailing lists are welcome. http://hamish.home.ml.org -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: [Debian] iso9660 in 2.0.34 ?
*-Nico De Ranter (14 Jul) | On Tue, Jul 14, 1998 at 09:21:28AM +0200, Nico De Ranter wrote: | | Hi, | | can anybody tell me how to enable iso9660 support in a 2.0.34 | kernel. There doesn't seem to be an option when I do 'make menuconfig'. | | In menu filesystems set on Native language support (Unicode, codepages) | you get iso and fat options. | | Ah, I didn't know iso and fat where languages :-) | Their not, but they need to understand different characters sets for different languages(i.e. native language support). -- Brian -- Mechanical Engineering [EMAIL PROTECTED] Purdue University http://www.ecn.purdue.edu/~servis -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: [Debian] iso9660 in 2.0.34 ?
Nico, During your 'make menuconfig', enable the NLS support and you will get the option for ISO9660, FAT, VFAT, etc... Steve Mayer [EMAIL PROTECTED] Nico De Ranter wrote: Hi, can anybody tell me how to enable iso9660 support in a 2.0.34 kernel. There doesn't seem to be an option when I do 'make menuconfig'. Nico -- -- Nico De Ranter Sony Service Center (PSDC-B/DNSE-B) Sint Stevens Woluwestraat 55 (Rue de Woluwe-Saint-Etienne) 1130 Brussel (Bruxelles), Belgium, Europe, Earth Telephone: +32 2 724 86 41 Telefax: +32 2 726 26 86 e-mail: [EMAIL PROTECTED] -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: [Debian] iso9660 in 2.0.34 ?
Nico, During your 'make menuconfig', enable the NLS support and you will get the option for ISO9660, FAT, VFAT, etc... I recompiled mine and I still cannot get the ISO, FAT or VFAT to mount. I also cannot load this module manually? I have not looked into this too hard, but I have been reading this thread on the list. What I have done (I am not sure if this is bad or not) is copy the .config from the old kernel to the new one? I was going to can this and start from scratch. Could this be the source of so many peoples (including mine) problems? --Jay Barbee -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: [Debian] iso9660 in 2.0.34 ?
Ya know, The 'kernel-package' package automates all of this for you. I had troubles getting modules to work even though I thought I did all the steps (make dep ; make clean ; make bzImage ; make modules ; make modules_install ; depmod -a. Then symlinking the new kernel and running lilo. The kernel booted and all built in support worked perfect but modules didn't. Leaving my config file unchanged I used kernel-package and everything worked.). If you use the kernel-package package you don't need to worry about copying or editing or symlinking and files, it's all done for you and it works PERFECTLY. At least for me. In the modules support section of the configuration make sure to enable the third option that lets you use kerneld for autoloading of modules. Chris Jay Barbee wrote: Nico, During your 'make menuconfig', enable the NLS support and you will get the option for ISO9660, FAT, VFAT, etc... I recompiled mine and I still cannot get the ISO, FAT or VFAT to mount. I also cannot load this module manually? I have not looked into this too hard, but I have been reading this thread on the list. What I have done (I am not sure if this is bad or not) is copy the .config from the old kernel to the new one? I was going to can this and start from scratch. Could this be the source of so many peoples (including mine) problems? --Jay Barbee -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: [Debian] iso9660 in 2.0.34 ?
...I believe I am confused... I do not mind a little automation, but currently in my lilo.conf I have 3 linux kernels that I use. Linux [default] Old [Previous Image] Experment [Pointing to /usr/src/linux/arch/i386/boot/zImage] This kernel-package util seems as if it takes this functionality away from you and simply uses default (/vmlinuz) and that is it. I am not sure this is a fair trade off for correcting whatever problem I am having with FS modules. I am not saying it is a viable option, but if I cannot 'insmod isofs.o', somthing is pretty wrong with how I compiled the kernel. Perhaps I simply don't understand what you are telling me to do with this kernel-package when I go to install or test a new kernel. --Jay Barbee Ya know, The 'kernel-package' package automates all of this for you. I had troubles getting modules to work even though I thought I did all the steps (make dep ; make clean ; make bzImage ; make modules ; make modules_install ; depmod -a. Then symlinking the new kernel and running lilo. The kernel booted and all built in support worked perfect but modules didn't. Leaving my config file unchanged I used kernel-package and everything worked.). If you use the kernel-package package you don't need to worry about copying or editing or symlinking and files, it's all done for you and it works PERFECTLY. At least for me. In the modules support section of the configuration make sure to enable the third option that lets you use kerneld for autoloading of modules. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
