From pocket-linux@ufo.chicago.il.us Fri Jul 4 04:49:11 2003 From: pocket-linux@ufo.chicago.il.us (pocket-linux@ufo.chicago.il.us) Date: Thu, 3 Jul 2003 23:49:11 EDT Subject: [pocket-linux] Trouble with proc_fs in Section 5.4.2 Message-ID: --part1_a7.33b368c6.2c365337_boundary Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit PocketLinux Community: I was constructing PocketLinux according to Version 1.2 and all was going as advertised until Section 5.4.2. When I ran the script proc_fs the following message kept appearing on the monitor: Out of Memory: Killed Process 1(sh). I have checked the script for typos several times, but haven't found any. As much as a remedy I would like an explanation, since the real purpose of PocketLinux is knowledge. Also a question. In Section 5.3.6 one creates a symlink between /etc/mtab and /proc/mount. It appears that proc/mount isn't a permanent file. That is, there is no ~/staging/proc/mount at stage 5.3.8. Is it created "on-the-fly" when one mounts proc? Regards, Rick --part1_a7.33b368c6.2c365337_boundary Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable PocketLinux Community:

I was constructing PocketLinux according to Version 1.2 and all was going as= advertised until Section 5.4.2. When I ran the script proc_fs the following= message kept appearing on the monitor: Out of Memory: Killed Process 1(sh).= I have checked the script for typos several times, but haven't found any. <= BR>
As much as a remedy I would like an explanation, since the real purpose of P= ocketLinux is knowledge.

Also a question. In Section 5.3.6 one creates a symlink between /etc/mtab an= d /proc/mount. It appears that proc/mount isn't a permanent file. That is, t= here is no ~/staging/proc/mount at stage 5.3.8. Is it created "on-the-= fly" when one mounts proc?

Regards, Rick --part1_a7.33b368c6.2c365337_boundary-- From pocket-linux@ufo.chicago.il.us Fri Jul 4 16:02:13 2003 From: pocket-linux@ufo.chicago.il.us (pocket-linux@ufo.chicago.il.us) Date: Fri, 04 Jul 2003 17:02:13 +0200 (DFT) Subject: [pocket-linux] Trouble with proc_fs in Section 5.4.2 In-Reply-To: References: Message-ID: <1057330933.3f0596f5491f2@webmail.jet2web.at> > PocketLinux Community: >I was constructing PocketLinux according to Version 1.2 and all was >going as advertised until Section 5.4.2. When I ran the script proc_fs the >following message kept appearing on the monitor: Out of Memory: Killed >Process 1(sh). I have checked the script for typos several times, but >haven't found any. I never experienced this problem, is it possible that the ramdisk uses too much of the RAM from your machine? Does this error occur if you mount /proc manually? >Also a question. In Section 5.3.6 one creates a symlink between >/etc/mtab and /proc/mount. It appears that proc/mount isn't a >permanent file. That is, there is no ~/staging/proc/mount at stage 5.3.8. >Is it created "on-the-fly" when one mounts proc? Yes, the proc-fs is only a virtual-filesystem (the files aren't real files on the harddisk) which contains live data from the kernel about devices, memory-usage and much more. So /proc/mount is available as soon as the proc-fs is mounted. But we found out that it isn't the best solution to symlink /etc/mtab on /proc/mount (see the pocket-linux archives June 2003). Greetz Daniel ------------------------------------------- Versendet durch AonWebmail (webmail.aon.at) From pocket-linux@ufo.chicago.il.us Fri Jul 4 18:39:30 2003 From: pocket-linux@ufo.chicago.il.us (pocket-linux@ufo.chicago.il.us) Date: Fri, 4 Jul 2003 13:39:30 EDT Subject: [pocket-linux] Trouble with proc_fs in Section 5.4.2 Message-ID: <76.2f697d87.2c3715d2@aol.com> --part1_76.2f697d87.2c3715d2_boundary Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit PLers: I found the error of my ways, more specifically of my typing. I didn't comment out the line "proc_fs - mount the proc filesystem". It definitely freaked the system. Thanks to Daniel for his reply. When mounting proc "by-hand" worked, I looked again at the proc_fs shell script. Regards, Rick --part1_76.2f697d87.2c3715d2_boundary Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable PLers:

I found the error of my ways, more specifically of my typing. I didn't comme= nt out the line "proc_fs - mount the proc filesystem". It definitely freaked= the system.

Thanks to Daniel for his reply. When mounting proc "by-hand" worked, I looke= d again at the proc_fs shell script.

Regards, Rick --part1_76.2f697d87.2c3715d2_boundary-- From pocket-linux@ufo.chicago.il.us Mon Jul 7 02:29:31 2003 From: pocket-linux@ufo.chicago.il.us (David Horton) Date: Sun, 06 Jul 2003 20:29:31 -0500 Subject: [pocket-linux] Trouble with proc_fs in Section 5.4.2 In-Reply-To: <1057330933.3f0596f5491f2@webmail.jet2web.at> References: <1057330933.3f0596f5491f2@webmail.jet2web.at> Message-ID: <3F08CCFB.60208@megsinet.net> > Yes, the proc-fs is only a virtual-filesystem (the files aren't real > files on the harddisk) which contains live data from the kernel about > devices, memory-usage and much more. So /proc/mount is available as > soon as the proc-fs is mounted. But we found out that it isn't the > best solution to symlink /etc/mtab on /proc/mount (see the > pocket-linux archives June 2003). > Yep, /proc/mounts is definitely not the best way to do things as we discovered the hard way. If you want to try chapter 5 without the /proc/mounts mess, take a look at the preview for version 2.0 at: http://my.core.com/~dhorton/linux/pocket/html/2.0_preview It uses a real file for /etc/mtab that should give better results. There are also other improvements in the other chapters and updated versions of many of the packages used. I'm planning to add an Appendix B with details on how to use busybox and tinylogin packages, but other than that I think it's ready for use. As always any feedback on additions and corrections is appreciated. Dave From pocket-linux@ufo.chicago.il.us Wed Jul 9 00:11:29 2003 From: pocket-linux@ufo.chicago.il.us (pocket-linux@ufo.chicago.il.us) Date: Tue, 8 Jul 2003 19:11:29 EDT Subject: [pocket-linux] GRUB in Pocket Linux Message-ID: <1d2.d702e98.2c3ca9a1@aol.com> --part1_1d2.d702e98.2c3ca9a1_boundary Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit PocketLinuxers: Many distributions use GRUB as the bootloader program instead of LILO, even though GNU hasn't officially released GRUB. Thus, an alternative/optional Chapter 2 of the Pocket Linux Guide using GRUB is appropriate. The required series of commands are listed below, assuming a floppy disk in /dev/fd0 and that GRUB is the bootloader on the host Linux OS. bash# mke2fs -m0 /dev/fd0 bash# mount /dev/fd0 /mnt bash# mkdir /mnt/boot Comment: build the appropriate kernel bash# cp /boot/vmlinuz /mnt/boot/vmlinuz bash# mkdir /mnt/boot/grub bash# cp /boot/grub/stage1 /mnt/boot/grub/stage1 bash# cp /boot/grub/stage2 /mnt/boot/grub/stage2 bash# cp /boot/grub/e2fs_stage1_5 /mnt/boot/grub/e2fs_stage1_5 bash# grub-install --root-directory=/mnt '(fd0)' Comment: grub-install will ask if the device mapping is correct. If the line (fd0) /dev/fd0 is present, all is well for our purposes. bash# cd /mnt/boot/grub Comment: Create the file menu.lst using your favorite editor. menu.lst is the GRUB configuration file. Ours will be very simple. ----------------------------------------------------------------------------- # /boot/grub/menu.lst - GRUB configuration file for Pocket Linux color= light-gray/blue black/light-gray title=bootdisk kernel (fd0)/boot/vmlinuz root=dev/fd0 mount=read-only vga=normal \ init=/bin/sh load_ramdisk=1 prompt_ramdisk=1 # End of configuration file ------------------------------------------------------------------------------ bash# mkdir /mnt/dev bash# cd /mnt/dev bash# mknod fd0 b 2 0 bash# mknod console c 5 1 --part1_1d2.d702e98.2c3ca9a1_boundary Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable PocketLinuxers:

Many distributions use GRUB as the bootloader program instead of LILO,
even though GNU hasn't officially released GRUB. Thus, an alternative/option= al Chapter 2 of the Pocket Linux Guide using GRUB is appropriate. The requir= ed series of commands are listed below, assuming a floppy disk in /dev/fd0 a= nd that GRUB is the bootloader on the host Linux OS.

bash# mke2fs -m0 /dev/fd0

bash# mount /dev/fd0 /mnt

bash# mkdir /mnt/boot

Comment: build the appropriate kernel

bash# cp /boot/vmlinuz /mnt/boot/vmlinuz

bash# mkdir /mnt/boot/grub

bash# cp /boot/grub/stage1 /mnt/boot/grub/stage1

bash# cp /boot/grub/stage2 /mnt/boot/grub/stage2

bash# cp /boot/grub/e2fs_stage1_5 /mnt/boot/grub/e2fs_stage1_5

bash# grub-install --root-directory=3D/mnt '(fd0)'

Comment: grub-install will ask if the device mapping is correct. If the line=
(fd0) /dev/fd0 is present, all is well for our purposes.

bash# cd /mnt/boot/grub

Comment: Create the file menu.lst using your favorite editor. menu.lst is th= e
GRUB configuration file. Ours will be very simple.
----------------------------------------------------------------------------= -
# /boot/grub/menu.lst - GRUB configuration file for Pocket Linux

color=3D light-gray/blue black/light-gray

title=3Dbootdisk
kernel (fd0)/boot/vmlinuz root=3Ddev/fd0 mount=3Dread-only vga=3Dnormal=20= \
init=3D/bin/sh load_ramdisk=3D1 prompt_ramdisk=3D1

# End of configuration file
----------------------------------------------------------------------------= --

bash# mkdir /mnt/dev

bash# cd /mnt/dev

bash# mknod fd0 b 2 0

bash# mknod console c 5 1
--part1_1d2.d702e98.2c3ca9a1_boundary-- From pocket-linux@ufo.chicago.il.us Sat Jul 12 18:55:12 2003 From: pocket-linux@ufo.chicago.il.us (Ciani Israel Jacob) Date: Sat, 12 Jul 2003 13:55:12 -0400 Subject: [pocket-linux] Help with Kernel configuration Message-ID: <000001c3489e$bf7f00b0$6401a8c0@papyrus> This is a multi-part message in MIME format. ------=_NextPart_000_0001_01C3487D.386D60B0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I am fairly new to kernel configuration, I would like to know if there is a template defining a minimum set of drivers needed for my/any kernel to boot properly; such that a foundation can be built for all subsequent kernel builds. In the particular example on the PocketLinux project page I received a kernel panic message asking that parameters be passed to init although the kernel has been told to run the shell directly through the boot loader. Additionally I have configured and compiled kernels successfully, problem is init failures are pervasive. I am left to assume my kernel configuration is invalid. All help is appreciated ------=_NextPart_000_0001_01C3487D.386D60B0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I am fairly new to kernel configuration, I would like to know if there is a template defining a minimum set of = drivers needed for my/any kernel to boot properly; such that a foundation can be = built for all subsequent kernel builds. In the particular example on the PocketLinux project page I received a kernel panic = message asking that parameters be passed to init although the kernel has been = told to run the shell directly through the boot loader. Additionally I have = configured and compiled kernels successfully, problem is = init failures are pervasive. I am left to assume my kernel configuration is = invalid… All help is appreciated

------=_NextPart_000_0001_01C3487D.386D60B0-- From pocket-linux@ufo.chicago.il.us Thu Jul 17 20:44:34 2003 From: pocket-linux@ufo.chicago.il.us (Brandon Carter) Date: Thu, 17 Jul 2003 12:44:34 -0700 (PDT) Subject: [pocket-linux] Building the Kernel Message-ID: <20030717194434.19067.qmail@web9503.mail.yahoo.com> --0-1130905178-1058471074=:18741 Content-Type: text/plain; charset=us-ascii I am running Redhat and I was just about to build the kernel with "make menuconfig" and it didn't work. Make said that there were no instructions to do the requested action. On one computer I was in the /usr/src/linux directory. In the other there was no such directory; only /usr/src/redhat. Does anybody know what I should do? --------------------------------- Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! --0-1130905178-1058471074=:18741 Content-Type: text/html; charset=us-ascii

I am running Redhat and I was just about to build the kernel with "make menuconfig" and it didn't work. Make said that there were no instructions to do the requested action. On one computer I was in the /usr/src/linux directory. In the other there was no such directory; only /usr/src/redhat. Does anybody know what I should do?

Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month! --0-1130905178-1058471074=:18741-- From pocket-linux@ufo.chicago.il.us Fri Jul 18 14:25:38 2003 From: pocket-linux@ufo.chicago.il.us (Dave Henderson) Date: Fri, 18 Jul 2003 06:25:38 -0700 (PDT) Subject: [pocket-linux] Building the Kernel In-Reply-To: <20030717194434.19067.qmail@web9503.mail.yahoo.com> Message-ID: <20030718132538.69429.qmail@web41108.mail.yahoo.com> --0-1341563404-1058534738=:69415 Content-Type: text/plain; charset=us-ascii Brandon, When you do an ls on this directory, do you see directories like "include, init, kernel, lib, fs, drivers" and a file called Makefile. If not, I think you are in the wrong directory. What directories do you have under /usr/src? Dave Henderson Brandon Carter wrote: I am running Redhat and I was just about to build the kernel with "make menuconfig" and it didn't work. Make said that there were no instructions to do the requested action. On one computer I was in the /usr/src/linux directory. In the other there was no such directory; only /usr/src/redhat. Does anybody know what I should do? --------------------------------- Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! --------------------------------- Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! --0-1341563404-1058534738=:69415 Content-Type: text/html; charset=us-ascii

Brandon,

When you do an ls on this directory, do you see directories like "include, init, kernel, lib, fs, drivers" and a file called Makefile. If not, I think you are in the wrong directory. What directories do you have under /usr/src?

Dave Henderson

Brandon Carter <bhcesl@yahoo.com> wrote:

I am running Redhat and I was just about to build the kernel with "make menuconfig" and it didn't work. Make said that there were no instructions to do the requested action. On one computer I was in the /usr/src/linux directory. In the other there was no such directory; only /usr/src/redhat. Does anybody know what I should do?

Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!

Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month! --0-1341563404-1058534738=:69415-- From pocket-linux@ufo.chicago.il.us Fri Jul 18 14:28:24 2003 From: pocket-linux@ufo.chicago.il.us (Dave Henderson) Date: Fri, 18 Jul 2003 06:28:24 -0700 (PDT) Subject: [pocket-linux] Help with Kernel configuration In-Reply-To: <000001c3489e$bf7f00b0$6401a8c0@papyrus> Message-ID: <20030718132824.80738.qmail@web41113.mail.yahoo.com> --0-2091102872-1058534904=:80447 Content-Type: text/plain; charset=us-ascii Ciani, When you compiled the kernel, did you compile the modules for your new kernel after the kernel compile itself? If you have told the "make menuconfig" to use certain options as modules, but you don't compile the modules, then you will have problems because the kernel may be looking for those modules and not find them. Dave Henderson Ciani Israel Jacob wrote: I am fairly new to kernel configuration, I would like to know if there is a template defining a minimum set of drivers needed for my/any kernel to boot properly; such that a foundation can be built for all subsequent kernel builds. In the particular example on the PocketLinux project page I received a kernel panic message asking that parameters be passed to init although the kernel has been told to run the shell directly through the boot loader. Additionally I have configured and compiled kernels successfully, problem is init failures are pervasive. I am left to assume my kernel configuration is invalid� All help is appreciated --------------------------------- Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! --0-2091102872-1058534904=:80447 Content-Type: text/html; charset=us-ascii

Ciani,

When you compiled the kernel, did you compile the modules for your new kernel after the kernel compile itself? If you have told the "make menuconfig" to use certain options as modules, but you don't compile the modules, then you will have problems because the kernel may be looking for those modules and not find them.

Dave Henderson

Ciani Israel Jacob <ciani@tampabay.rr.com> wrote:

I am fairly new to kernel configuration, I would like to know if there is a template defining a minimum set of drivers needed for my/any kernel to boot properly; such that a foundation can be built for all subsequent kernel builds. In the particular example on the PocketLinux project page I received a kernel panic message asking that parameters be passed to init although the kernel has been told to run the shell directly through the boot loader. Additionally I have configured and compiled kernels successfully, problem is init failures are pervasive. I am left to assume my kernel configuration is invalid� All help is appreciated

Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month! --0-2091102872-1058534904=:80447-- From pocket-linux@ufo.chicago.il.us Fri Jul 18 23:28:31 2003 From: pocket-linux@ufo.chicago.il.us (Tibberio) Date: Fri, 18 Jul 2003 22:28:31 +0000 Subject: [pocket-linux] Building the Kernel Message-ID: <3EDF33C70003C325@ims4a.cp.tin.it> Hi Download your favorite kernel (http://www.kernel.org :) ); put the source= in /usr/src/ and open tarredgzipped(or tarredbzipped) file. You must have like some this: ... 4096 Jul 16 19:57 linux-2.4.21/ ... 28533733 Jul 2 06:53 linux-2.4.21.tar.bz2 Now make a symlink: ln -s linux-2.4.21 linux and in linux-2.4.21 play make menuconfig If it don't work, probably you haven't something like ncurses development= lib. good luck ! =20 From pocket-linux@ufo.chicago.il.us Mon Jul 21 07:33:35 2003 From: pocket-linux@ufo.chicago.il.us (Joseph Mpora) Date: Mon, 21 Jul 2003 09:33:35 +0300 Subject: [pocket-linux] Re: Pocket-Linux digest, Vol 1 #31 - 1 msg In-Reply-To: <20030718112901.6479.56397.Mailman@localhost> References: <20030718112901.6479.56397.Mailman@localhost> Message-ID: Brandon, You have to make sure you installed the kernel development package for the source to be included in redhat. The other option is to download the kernel source yourself, decompress to a desired directory and run the 'make menuconfig' in the linux directory within the decompressed source location. Please ensure that you have ncurses before you run 'make menuconfig'. Joseph > Message: 1 > Date: Thu, 17 Jul 2003 12:44:34 -0700 (PDT) > From: Brandon Carter > To: pocket-linux@ufo.chicago.il.us > Subject: [pocket-linux] Building the Kernel > Reply-To: pocket-linux@ufo.chicago.il.us > > --0-1130905178-1058471074=:18741 > Content-Type: text/plain; charset=us-ascii > > I am running Redhat and I was just about to build the kernel with "make > menuconfig" and it didn't work. Make said that there were no > instructions to do the requested action. On one computer I was in the > /usr/src/linux directory. In the other there was no such directory; > only /usr/src/redhat. Does anybody know what I should do? > From pocket-linux@ufo.chicago.il.us Thu Jul 24 04:08:41 2003 From: pocket-linux@ufo.chicago.il.us (Tibberio) Date: Thu, 24 Jul 2003 03:08:41 +0000 Subject: [pocket-linux] Script Message-ID: <3F1C117600003BF8@ims4a.cp.tin.it> Hi I think is usefull try all commands, but after some steps I was boring to mount, copy, gzip ..., so I wrote a little script in bash. It prepares the filesystem on a device, put all programs that you have compiled in it, ... and copies the gzipped root image in a floppy disk (in secure mode, I hope). If anyone is interested, can download it at http://tibberio.freeshell.org= /monta bye From pocket-linux@ufo.chicago.il.us Thu Jul 24 14:41:06 2003 From: pocket-linux@ufo.chicago.il.us (Saurav Gohain) Date: Thu, 24 Jul 2003 19:11:06 +0530 Subject: [pocket-linux] Pocket Linux +Adding Extra Software Message-ID: Hi, I have created a bootable cd disk with a minimal linux system and wants to add RPM utility in the the cdrom. How do I that ? Can anybody guide me a liitle. Regards, Saurav _________________________________________________________________ Attention NRIs. Send money home. http://server1.msn.co.in/msnleads/citibankrca/citibankrca2.asp?type=txt Do it in a jiffy! From dheise at teamtec.de Fri Jul 25 15:05:48 2003 From: dheise at teamtec.de (Daniel Heise) Date: Fri Aug 8 16:17:07 2003 Subject: [pocket-linux] Big problem while booting the root disk (chapter 3) Message-ID: <000001c352a5$15d5cb00$a164fea9@dh> Hello everybody! I'm new to Pocket Linux and Linux itself. I've just startet to build the boot and root disk from the discription in Pocket Linux guide (chapter 3). I've done everything as discribed in the guide but when I try to start the system I get the following error messages after I insert the root disk: ... VFS: Insert root floppy disk to be loaded into RAM disk and press ENTER RAMDISK: Compressed Image found at block 0 VFS: Mounted root (ext2 filesystem) readonly. Freeing unused kernel memory: 60k freed Attempt to access beyond end of device 01:00 rw=0, want 49158, limit=4096 EXT2-fs error (device ramdisk (1,0)): ext2_read_inode: unable to read inode block - inode=12001, block = 49157 Waring unable to open an initial console. attemp to access beyond end of device 01:00 rw=0, want=16390, limit=4096 EXT2-fs error (device RAM disk (1,0)): ext2_read_inode: unable to read inide block - inode = 4001, block = 16389 Kernel panic: No init found. Try passing init= option to kernel. But I insert in the lilo prompt: bootdisk init=/bin/sh Any ideas? Regards Daniel Please forgive me my bad english, I'm from germany. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://tastytronic.net/pipermail/pocket-linux/attachments/20030725/a1bfa9a7/attachment.htm From hendedav at yahoo.com Fri Jul 25 06:49:46 2003 From: hendedav at yahoo.com (Dave Henderson) Date: Fri Aug 8 16:17:08 2003 Subject: [pocket-linux] Pocket Linux +Adding Extra Software In-Reply-To: Message-ID: <20030725124946.20186.qmail@web41113.mail.yahoo.com> Saurav, What distro of Linux are you using? You can simply download the package manager in .tar.gz format and install it that way, or you may be able to find an .rpm for the rpm :). I know Debian has the source for it on their website thats available for download. (http://packages.debian.org/stable/admin/rpm.html). The readme's usually do a pretty good job at telling you how to install it. Dave Henderson Saurav Gohain wrote: Hi, I have created a bootable cd disk with a minimal linux system and wants to add RPM utility in the the cdrom. How do I that ? Can anybody guide me a liitle. Regards, Saurav _________________________________________________________________ Attention NRIs. Send money home. http://server1.msn.co.in/msnleads/citibankrca/citibankrca2.asp?type=txt Do it in a jiffy! _______________________________________________ Pocket-Linux mailing list Pocket-Linux@ufo.chicago.il.us http://ufo.chicago.il.us/cgi-bin/mailman/listinfo/pocket-linux --------------------------------- Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software -------------- next part -------------- An HTML attachment was scrubbed... URL: http://tastytronic.net/pipermail/pocket-linux/attachments/20030725/91426312/attachment.htm