From: Matt S. <ma...@ma...> - 2002-09-05 03:47:50
|
Using the latest boot floppy, when attempting to get most of the packages over the network, I get: gunzip: Invalid gzip magic And the package doesn't load. It works for some packages on the mirrors, but only a couple. I saw a post about this back in March, but the suggested correction didn't help here. Any ideas? --Matt |
From: Timothy B. <tb...@ar...> - 2002-09-05 14:52:26
|
It is possible that the cause may be elsewhere. If your trinux system runs out of ramdisk, I believe that it keeps quiet about it. If you are attempting to get packages, and some fail, it could be the large packages that are failing, due to insufficient resources (memory or ramdisk). Trinux is special because it runs in a resource restricted environment. It assumes that the operator knows this. Error checking and the meaningful text messages can sometimes double the size of an executable. Trinux must be kept small, and sometimes this is at the expense of even minimal diagnostics. Your request for help is very short on details. A short list of 3 packages that failed, and 3 that succeed, could help determine the cause. Also, try to include some parameters of your running system. Most importantly, the total amount of installed ram, and the output of the df (disk free) command, would really help. And please ACK the list, when a suggested fix does the deed. It is most frustrating to see several posts of a problem, and never a final "That fixed it!". Thanks! On Wed, 4 Sep 2002, Matt Smith wrote: > Using the latest boot floppy, when attempting to get most of the packages > over the network, I get: > > gunzip: Invalid gzip magic > > And the package doesn't load. It works for some packages on the mirrors, > but only a couple. I saw a post about this back in March, but the > suggested correction didn't help here. > > Any ideas? > > > --Matt > > > > > > ------------------------------------------------------- > This sf.net email is sponsored by: OSDN - Tired of that same old > cell phone? Get a new here for FREE! > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 > _______________________________________________ > Trinux-talk mailing list > Tri...@li... > https://lists.sourceforge.net/lists/listinfo/trinux-talk > -- -------------------- Timothy Burt General Manager Arbor Group LLC Los Angeles, Calif. USA |
From: Matt S. <ma...@ma...> - 2002-09-05 14:59:20
|
Thanks for the reply. I'm not in front of the system (it's at home), but I'll tell you what I know. The machine is a AMD-based older box. 48MB ram. I'm booting from the trinux-0.80rc2-net.img floppy. I didn't get the impression that any of the packages that the bootable floppy attempts to load actually loaded. I can't say any loaded for sure because when it works, it doesn't complain. The only package I successfully loaded manually myself was vi. But then, of course, it wouldn't run due to dependency issues. The network was working properly - as I was able to manually pull down packages with snarf.. just trying to gunzip them failed with the aforementioned error. I'll provide the df output later, and I'll most definitely let you know what works and what doesn't. :) --Matt > > It is possible that the cause may be elsewhere. > > If your trinux system runs out of ramdisk, I believe that it keeps quiet > about it. If you are attempting to get packages, and some fail, it > could be the large packages that are failing, due to insufficient > resources (memory or ramdisk). > > Trinux is special because it runs in a resource restricted environment. > It assumes that the operator knows this. Error checking and the > meaningful text messages can sometimes double the size of an executable. > Trinux must be kept small, and sometimes this is at the expense of > even minimal diagnostics. > > Your request for help is very short on details. A short list of 3 > packages that failed, and 3 that succeed, could help determine the > cause. > > Also, try to include some parameters of your running system. Most > importantly, the total amount of installed ram, and the output of the df > (disk free) command, would really help. > > And please ACK the list, when a suggested fix does the deed. It is most > frustrating to see several posts of a problem, and never a final "That > fixed it!". > > Thanks! > > On Wed, 4 Sep 2002, Matt Smith wrote: > >> Using the latest boot floppy, when attempting to get most of the >> packages over the network, I get: >> >> gunzip: Invalid gzip magic >> >> And the package doesn't load. It works for some packages on the >> mirrors, but only a couple. I saw a post about this back in March, >> but the suggested correction didn't help here. >> >> Any ideas? >> >> >> --Matt >> >> >> >> >> >> ------------------------------------------------------- >> This sf.net email is sponsored by: OSDN - Tired of that same old cell >> phone? Get a new here for FREE! >> https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 >> _______________________________________________ >> Trinux-talk mailing list >> Tri...@li... >> https://lists.sourceforge.net/lists/listinfo/trinux-talk >> > > -- > -------------------- > Timothy Burt > General Manager > Arbor Group LLC > Los Angeles, Calif. USA |
From: Matthew F. <mf...@ci...> - 2002-09-05 15:31:47
|
It could be the memory question or the package might not exist on the server # free should tell you if your ramdisks are full. # cat /etc/tux/config/server will tell you where the packages are being loaded from Or it probably does this if the package doesn't exist # snarf http://trinux.sf.net/pkg/pkgname.tgz if this fails, then the package doesn't exist or has been renamed - mdf > It is possible that the cause may be elsewhere. > > If your trinux system runs out of ramdisk, I believe that it keeps quiet > about it. If you are attempting to get packages, and some fail, it could > be the large packages that are failing, due to insufficient resources > (memory or ramdisk). > > Trinux is special because it runs in a resource restricted environment. > It assumes that the operator knows this. Error checking and the > meaningful text messages can sometimes double the size of an executable. > Trinux must be kept small, and sometimes this is at the expense of > even minimal diagnostics. > > Your request for help is very short on details. A short list of 3 > packages that failed, and 3 that succeed, could help determine the cause. > > Also, try to include some parameters of your running system. Most > importantly, the total amount of installed ram, and the output of the df > (disk free) command, would really help. > > And please ACK the list, when a suggested fix does the deed. It is most > frustrating to see several posts of a problem, and never a final "That > fixed it!". > > Thanks! > > On Wed, 4 Sep 2002, Matt Smith wrote: > > > Using the latest boot floppy, when attempting to get most of the packages > > over the network, I get: > > > > gunzip: Invalid gzip magic > > > > And the package doesn't load. It works for some packages on the mirrors, > > but only a couple. I saw a post about this back in March, but the > > suggested correction didn't help here. > > > > Any ideas? |
From: Matt S. <ma...@ma...> - 2002-09-06 01:53:02
|
These are immediately after booting from the floppy... output from df command: Filesystem 1k-blocks Used Available Use% Mounted on /dev/ram0 6076 1811 4265 30% / /dev/null 16000 48 15952 0% /usr /dev/null 1000 0 1000 0% /home output from free command: total used free shared buffers mem: 46584 10512 36072 0 6160 swap: 0 0 0 Total: 46584 10512 36072 I don't have any extra memory handy to see if that helps, but I'm working on another machine to try it on. I'll let you know if I have any success. --Matt > > It is possible that the cause may be elsewhere. > > If your trinux system runs out of ramdisk, I believe that it keeps quiet > about it. If you are attempting to get packages, and some fail, it > could be the large packages that are failing, due to insufficient > resources (memory or ramdisk). > > Trinux is special because it runs in a resource restricted environment. > It assumes that the operator knows this. Error checking and the > meaningful text messages can sometimes double the size of an executable. > Trinux must be kept small, and sometimes this is at the expense of > even minimal diagnostics. > > Your request for help is very short on details. A short list of 3 > packages that failed, and 3 that succeed, could help determine the > cause. > > Also, try to include some parameters of your running system. Most > importantly, the total amount of installed ram, and the output of the df > (disk free) command, would really help. > > And please ACK the list, when a suggested fix does the deed. It is most > frustrating to see several posts of a problem, and never a final "That > fixed it!". > > Thanks! > > On Wed, 4 Sep 2002, Matt Smith wrote: > >> Using the latest boot floppy, when attempting to get most of the >> packages over the network, I get: >> >> gunzip: Invalid gzip magic >> >> And the package doesn't load. It works for some packages on the >> mirrors, but only a couple. I saw a post about this back in March, >> but the suggested correction didn't help here. >> >> Any ideas? >> >> >> --Matt >> >> >> >> >> >> ------------------------------------------------------- >> This sf.net email is sponsored by: OSDN - Tired of that same old cell >> phone? Get a new here for FREE! >> https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 >> _______________________________________________ >> Trinux-talk mailing list >> Tri...@li... >> https://lists.sourceforge.net/lists/listinfo/trinux-talk >> > > -- > -------------------- > Timothy Burt > General Manager > Arbor Group LLC > Los Angeles, Calif. USA |
From: <HHu...@t-...> - 2002-09-06 05:49:57
|
Hallo, Matt, Du meintest am 05.09.02 zum Thema Re: [Trinux-talk] Invalid gzip magic: > These are immediately after booting from the floppy... > output from df command: > Filesystem 1k-blocks Used Available Use% > Mounted on > /dev/ram0 6076 1811 4265 30% / > /dev/null 16000 48 15952 0% /usr > /dev/null 1000 0 1000 0% /home Really "/dev/null"? That's no good device ... Viele Gruesse! Helmut |
From: Matthew F. <mf...@ci...> - 2002-09-06 15:50:23
|
I'm not sure why I'm adding the /dev/null but it works. Maybe because glibc2.1 doesn't have /dev/shm ??? mount -n -t tmpfs -o size=640000 /dev/null /usr Anyway, tmpfs is much better than ramdisks. - mdf [/usr/src/linu/Documentation/filesystems/tmpfs.txt] Tmpfs is a file system which keeps all files in virtual memory. Everything in tmpfs is temporary in the sense that no files will be created on your hard drive. If you unmount a tmpfs instance, everything stored therein is lost. tmpfs puts everything into the kernel internal caches and grows and shrinks to accommodate the files it contains and is able to swap unneeded pages out to swap space. It has maximum size limits which can be adjusted on the fly via 'mount -o remount ...' If you compare it to ramfs (which was the template to create tmpfs) you gain swapping and limit checking. Another similar thing is the RAM disk (/dev/ram*), which simulates a fixed size hard disk in physical RAM, where you have to create an ordinary filesystem on top. Ramdisks cannot swap and you do not have the possibility to resize them. Since tmpfs lives completely in the page cache and on swap, all tmpfs pages currently in memory will show up as cached. It will not show up as shared or something like that. Further on you can check the actual RAM+swap use of a tmpfs instance with df(1) and du(1). tmpfs has the following uses: 1) There is always a kernel internal mount which you will not see at all. This is used for shared anonymous mappings and SYSV shared memory. This mount does not depend on CONFIG_TMPFS. If CONFIG_TMPFS is not set, the user visible part of tmpfs is not build. But the internal mechanisms are always present. 2) glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for POSIX shared memory (shm_open, shm_unlink). Adding the following line to /etc/fstab should take care of this: tmpfs /dev/shm tmpfs defaults 0 0 Remember to create the directory that you intend to mount tmpfs on if necessary (/dev/shm is automagically created if you use devfs). This mount is _not_ needed for SYSV shared memory. The internal mount is used for that. (In the 2.3 kernel versions it was necessary to mount the predecessor of tmpfs (shm fs) to use SYSV shared memory) 3) Some people (including me) find it very convenient to mount it e.g. on /tmp and /var/tmp and have a big swap partition. But be aware: loop mounts of tmpfs files do not work due to the internal design. So mkinitrd shipped by most distributions will fail with a tmpfs /tmp. 4) And probably a lot more I do not know about :-) tmpfs has a couple of mount options: size: The limit of allocated bytes for this tmpfs instance. The default is half of your physical RAM without swap. If you oversize your tmpfs instances the machine will deadlock since the OOM handler will not be able to free that memory. nr_blocks: The same as size, but in blocks of PAGECACHE_SIZE. nr_inodes: The maximum number of inodes for this instance. The default is half of the number of your physical RAM pages. These parameters accept a suffix k, m or g for kilo, mega and giga and can be changed on remount. To specify the initial root directory you can use the following mount options: mode: The permissions as an octal number uid: The user id gid: The group id These options do not have any effect on remount. You can change these parameters with chmod(1), chown(1) and chgrp(1) on a mounted filesystem. So 'mount -t tmpfs -o size=10G,nr_inodes=10k,mode=700 tmpfs /mytmpfs' will give you tmpfs instance on /mytmpfs which can allocate 10GB RAM/SWAP in 10240 inodes and it is only accessible by root. > > Filesystem 1k-blocks Used Available Use% > > Mounted on > > /dev/ram0 6076 1811 4265 30% / > > /dev/null 16000 48 15952 0% /usr > > /dev/null 1000 0 1000 0% /home > > > Really "/dev/null"? > That's no good device ... > > Viele Gruesse! > Helmut > > |
From: Matt S. <ma...@ma...> - 2002-09-06 03:02:38
|
Okay.. I guess there's something screwy with the packages at http://www.trinux.org/pkg/ I removed that url from the /tux/config/server file on the floppy and just left the io.com one and rebooted and it's working fine now. --Matt > > It is possible that the cause may be elsewhere. > > If your trinux system runs out of ramdisk, I believe that it keeps quiet > about it. If you are attempting to get packages, and some fail, it > could be the large packages that are failing, due to insufficient > resources (memory or ramdisk). > > Trinux is special because it runs in a resource restricted environment. > It assumes that the operator knows this. Error checking and the > meaningful text messages can sometimes double the size of an executable. > Trinux must be kept small, and sometimes this is at the expense of > even minimal diagnostics. > > Your request for help is very short on details. A short list of 3 > packages that failed, and 3 that succeed, could help determine the > cause. > > Also, try to include some parameters of your running system. Most > importantly, the total amount of installed ram, and the output of the df > (disk free) command, would really help. > > And please ACK the list, when a suggested fix does the deed. It is most > frustrating to see several posts of a problem, and never a final "That > fixed it!". > > Thanks! > > On Wed, 4 Sep 2002, Matt Smith wrote: > >> Using the latest boot floppy, when attempting to get most of the >> packages over the network, I get: >> >> gunzip: Invalid gzip magic >> >> And the package doesn't load. It works for some packages on the >> mirrors, but only a couple. I saw a post about this back in March, >> but the suggested correction didn't help here. >> >> Any ideas? >> >> >> --Matt >> >> >> >> >> >> ------------------------------------------------------- >> This sf.net email is sponsored by: OSDN - Tired of that same old cell >> phone? Get a new here for FREE! >> https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 >> _______________________________________________ >> Trinux-talk mailing list >> Tri...@li... >> https://lists.sourceforge.net/lists/listinfo/trinux-talk >> > > -- > -------------------- > Timothy Burt > General Manager > Arbor Group LLC > Los Angeles, Calif. USA |
From: Matt S. <ma...@ma...> - 2002-09-06 03:14:18
|
Well, It's not the memory... Intel machine, 128MB ram, same thing... Failed packages during boot: term baselib nmap system netconf (others that scrolled off the screen) All failed saying gunzip: Invalid gzip magic.... Pretty much all that worked was what was on the floppy. (dhcpcd and dnslibs) When I got the vi package to work one time before, I changed the server from the trinux one to one of the mirrors, but others from that mirror failed too.... --Matt > > It is possible that the cause may be elsewhere. > > If your trinux system runs out of ramdisk, I believe that it keeps quiet > about it. If you are attempting to get packages, and some fail, it > could be the large packages that are failing, due to insufficient > resources (memory or ramdisk). > > Trinux is special because it runs in a resource restricted environment. > It assumes that the operator knows this. Error checking and the > meaningful text messages can sometimes double the size of an executable. > Trinux must be kept small, and sometimes this is at the expense of > even minimal diagnostics. > > Your request for help is very short on details. A short list of 3 > packages that failed, and 3 that succeed, could help determine the > cause. > > Also, try to include some parameters of your running system. Most > importantly, the total amount of installed ram, and the output of the df > (disk free) command, would really help. > > And please ACK the list, when a suggested fix does the deed. It is most > frustrating to see several posts of a problem, and never a final "That > fixed it!". > > Thanks! > > On Wed, 4 Sep 2002, Matt Smith wrote: > >> Using the latest boot floppy, when attempting to get most of the >> packages over the network, I get: >> >> gunzip: Invalid gzip magic >> >> And the package doesn't load. It works for some packages on the >> mirrors, but only a couple. I saw a post about this back in March, >> but the suggested correction didn't help here. >> >> Any ideas? >> >> >> --Matt >> >> >> >> >> >> ------------------------------------------------------- >> This sf.net email is sponsored by: OSDN - Tired of that same old cell >> phone? Get a new here for FREE! >> https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 >> _______________________________________________ >> Trinux-talk mailing list >> Tri...@li... >> https://lists.sourceforge.net/lists/listinfo/trinux-talk >> > > -- > -------------------- > Timothy Burt > General Manager > Arbor Group LLC > Los Angeles, Calif. USA |