From owner-freebsd-small Mon Jul 16 4:13:15 2001 Delivered-To: freebsd-small@freebsd.org Received: from kalaid.f2f.com.ua (kalaid.f2f.com.ua [62.149.0.33]) by hub.freebsd.org (Postfix) with ESMTP id 0CCA037B401; Mon, 16 Jul 2001 04:13:07 -0700 (PDT) (envelope-from sobomax@FreeBSD.org) Received: from Mail-In.Net (borey.f2f.com.ua [62.149.0.24]) by kalaid.f2f.com.ua (8.11.4/8.11.4) with ESMTP id f6GBFHj72554; Mon, 16 Jul 2001 14:15:18 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Received: from vega.vega.com (root@[212.35.189.160]) by Mail-In.Net (8.11.3/8.H.Z) with ESMTP id f6GBE4u20273; Mon, 16 Jul 2001 14:14:04 +0300 (EEST) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.11.4/8.11.3) with ESMTP id f6GBBxD47572; Mon, 16 Jul 2001 14:11:59 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <3B52CC08.1B08210F@FreeBSD.org> Date: Mon, 16 Jul 2001 14:12:17 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en,uk,ru MIME-Version: 1.0 To: small@FreeBSD.org Cc: arch@FreeBSD.org Subject: Extending md(4) to allow it use pre-compressed disk image Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi folks, I extended md(4) driver to allow it use pre-compressed disk image. In contrast with the current implementation, when loader(8) on loading decompresses compressed image and holds it uncompressed in the memory, with new feature loader(8) places compressed image into a memory, while md(4) decompresses sectors when they are read. This could be useful to decrease minimal memory requrements on FreeBSD install or in another cases when memory is scarce. Performance is quite good - even P133 reads data from such device at 2-2.5MB/s. Since standard gzip format is not really suitable for the task I created an utility that splits original image into clusters (cluster size could vary), compresses each cluster using zlib and writes compressed clusters along with information about offset of each cluster into resulting image. After that compressed image could be put into the floppy or other media, loaded using loader(8) and accessed through md(4) as usually. The only difference is that it is impossible to write into resulting disk. I would like to know if there is enough interest in integrating this feature into base system, please let me know what do you think about it. -Maxim P.S. Please keep me on the CC list. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Mon Jul 16 8:40:50 2001 Delivered-To: freebsd-small@freebsd.org Received: from granger.mail.mindspring.net (granger.mail.mindspring.net [207.69.200.148]) by hub.freebsd.org (Postfix) with ESMTP id AF8F937B40A; Mon, 16 Jul 2001 08:40:31 -0700 (PDT) (envelope-from bill@mindspring.com) Received: from ah-soo.mindspring.com (pool0550.cvx7-bradley.dialup.earthlink.net [209.178.166.40]) by granger.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id LAA18617; Mon, 16 Jul 2001 11:40:29 -0400 (EDT) From: bill@mindspring.com Received: from localhost (bill@localhost) by ah-soo.mindspring.com (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id IAA22248; Mon, 16 Jul 2001 08:39:53 -0700 X-Authentication-Warning: ah-soo.mindspring.com: bill owned process doing -bs Date: Mon, 16 Jul 2001 08:39:53 -0700 (PDT) Reply-To: Bill Cassady To: Maxim Sobolev Cc: small@FreeBSD.org Subject: Re: Extending md(4) to allow it use pre-compressed disk image In-Reply-To: <3B52CC08.1B08210F@FreeBSD.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 16 Jul 2001, Maxim Sobolev wrote: >...After that compressed image could be put > into the floppy or other media, loaded using loader(8) and accessed > through md(4) as usually. The only difference is that it is impossible > to write into resulting disk. > > I would like to know if there is enough interest in integrating this > feature into base system, please let me know what do you think about > it. A voice from Pico user, whose interest is in a shirt-pocket operating system capable of dial-in and plugging into a network, asks that as far as Pico is concerned what difference would it make? As far as I have discovered, all bytes on the Pico disk are permanent except for the ppp configuration. Although Pico will mount msdos and ext2fs floppy disks, it constantly complains when reading dos disks that it can't write to them because they are write protected. (!) If I mount an ext2 disk Pico page-faults as soon as I do an ls... So, to clarify my question, assuming funtionality to be first consideration and speed/memory secondary, and assuming also that the mount problem would be fixed, within the size limitations of a floppy, wouldn't this limitation of your feature have no big negative effect for Pico? I certainly appreciate all the work that has gone into the Pico project, and only dip into it from time-to-time. And I am very glad to see that things are moving forward. -Bill Cassady To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Mon Jul 16 9:20:44 2001 Delivered-To: freebsd-small@freebsd.org Received: from kalaid.f2f.com.ua (kalaid.f2f.com.ua [62.149.0.33]) by hub.freebsd.org (Postfix) with ESMTP id D440937B401 for ; Mon, 16 Jul 2001 09:20:35 -0700 (PDT) (envelope-from sobomax@FreeBSD.org) Received: from Mail-In.Net (borey.f2f.com.ua [62.149.0.24]) by kalaid.f2f.com.ua (8.11.4/8.11.4) with ESMTP id f6GGMhj85960; Mon, 16 Jul 2001 19:22:43 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Received: from vega.vega.com (root@[212.35.189.174]) by Mail-In.Net (8.11.3/8.H.Z) with ESMTP id f6GGLHI03556; Mon, 16 Jul 2001 19:21:18 +0300 (EEST) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.11.4/8.11.3) with ESMTP id f6GGK3D51021; Mon, 16 Jul 2001 19:20:03 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <3B531443.56C3D67@FreeBSD.org> Date: Mon, 16 Jul 2001 19:20:19 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en,uk,ru MIME-Version: 1.0 To: Bill Cassady Cc: small@FreeBSD.org Subject: Re: Extending md(4) to allow it use pre-compressed disk image References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG bill@mindspring.com wrote: > On Mon, 16 Jul 2001, Maxim Sobolev wrote: > > >...After that compressed image could be put > > into the floppy or other media, loaded using loader(8) and accessed > > through md(4) as usually. The only difference is that it is impossible > > to write into resulting disk. > > > > I would like to know if there is enough interest in integrating this > > feature into base system, please let me know what do you think about > > it. > > A voice from Pico user, whose interest is in a shirt-pocket operating > system capable of dial-in and plugging into a network, asks > that as far as Pico is concerned what difference would it make? > > As far as I have discovered, all bytes on the Pico disk are permanent > except for the ppp configuration. > > Although Pico will mount msdos and ext2fs floppy disks, it constantly > complains when reading dos disks that it can't write to them because > they are write protected. (!) If I mount an ext2 disk Pico page-faults > as soon as I do an ls... > > So, to clarify my question, assuming funtionality to be first > consideration and speed/memory secondary, and assuming also that > the mount problem would be fixed, within the size limitations of a > floppy, wouldn't this limitation of your feature have no big negative > effect for Pico? No negative affect actually. The proposed new feature doesn't remove any existing ones, so PicoBSD or any other FreeBSD sub-project could use it as it sees fit. > I certainly appreciate all the work that has gone into the Pico project, > and only dip into it from time-to-time. And I am very glad to see that > things are moving forward. Nice to hear. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Mon Jul 16 15:44:34 2001 Delivered-To: freebsd-small@freebsd.org Received: from fw1.tamsa.com (fw1.tamsa.com [12.18.88.225]) by hub.freebsd.org (Postfix) with ESMTP id 7226D37B403 for ; Mon, 16 Jul 2001 15:44:25 -0700 (PDT) (envelope-from rpaez@tamsa.com) Received: from compaq202 ([192.168.2.202]) by fw1.tamsa.com (8.9.3/8.9.3) with SMTP id RAA66535 for ; Mon, 16 Jul 2001 17:27:01 -0500 (CDT) (envelope-from rpaez@tamsa.com) MIME-Version: 1.0 Message-Id: <3B536BA7.000011.95275@compaq202.tamsa.com> Date: Mon, 16 Jul 2001 17:33:11 -0500 (Central Daylight Time) Content-Type: Multipart/Alternative; boundary="------------Boundary-00=_BZ7LIA11VA4000000000" X-Mailer: IncrediMail 2001 (1500284) From: "Rolando Paez" X-Priority: 3 X-FID: FLAVOR00-NONE-0000-0000-000000000000 To: Subject: Hello and problems changing the configuration Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --------------Boundary-00=_BZ7LIA11VA4000000000 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello to all, I have a problem changing the configuration of a picobsd router floppy, it booted ok but the network interface is (of course) not configured, I searched all the fs for a text editor like vi without luck, and then tried to mount the floppy, it mounted and I could see all the configuration files but when I tried to do the same in another full versi= on FBSD box :=0D =0D # mount /dev/fd0 /mnt=0D =0D it replied with:=0D mount: device not configured=0D =0D I've tried with different names fd0, fd0a, fd0.1440 without luck, can any= one hwlp me?=0D =0D The kernel has support for the floppy.=0D =0D Thanks=0D =0D -RP --------------Boundary-00=_BZ7LIA11VA4000000000 Content-Type: Text/HTML; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello to all, I have a problem changing the configuration of a= =20 picobsd router floppy, it booted ok but the network interface is (o= f=20 course) not configured, I searched all the fs for a text editor lik= e vi=20 without luck, and then tried to mount the floppy, it mounted and I = could=20 see all the configuration files but when I tried to do the same in = another=20 full version FBSD box :
 
# mount /dev/fd0 /mnt
 
it replied with:
mount: device not configured
 
I've tried with different names fd0, fd0a, fd0.1440 without lu= ck, can=20 anyone hwlp me?
 
The kernel has support for the floppy.
 
Thanks
 
-RP
=09 =09 =09 =09 =09 =09 =09
_________________________________________________
IncrediMail - Email has finally= =20 evolved - Click=20 Here --------------Boundary-00=_BZ7LIA11VA4000000000-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Jul 17 7:46:42 2001 Delivered-To: freebsd-small@freebsd.org Received: from fw1.tamsa.com (fw1.tamsa.com [12.18.88.225]) by hub.freebsd.org (Postfix) with ESMTP id 9A11837B408 for ; Tue, 17 Jul 2001 07:46:36 -0700 (PDT) (envelope-from rpaez@tamsa.com) Received: from compaq202 ([192.168.2.202]) by fw1.tamsa.com (8.9.3/8.9.3) with SMTP id JAA69333 for ; Tue, 17 Jul 2001 09:29:07 -0500 (CDT) (envelope-from rpaez@tamsa.com) MIME-Version: 1.0 Message-Id: <3B544D2A.000008.95357@compaq202.tamsa.com> Date: Tue, 17 Jul 2001 09:35:22 -0500 (Central Daylight Time) Content-Type: Text/Plain X-Mailer: IncrediMail 2001 (1500284) From: "Rolando Paez" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-FID: FLAVOR00-NONE-0000-0000-000000000000 To: Subject: Fw: Hello and problems changing the configuration Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Sorry about the last message in html... -RP -------Original Message------- From: Rolando Paez Date: Monday, July 16, 2001 17:33:11 To: freebsd-small@freebsd.org Subject: Hello and problems changing the configuration Hello to all, I have a problem changing the configuration of a picobsd router floppy, it booted ok but the network interface is (of course) not configured, I searched all the fs for a text editor like vi without luck, and then tried to mount the floppy, it mounted and I could see all the configuration files but when I tried to do the same in another full version FBSD box : # mount /dev/fd0 /mnt it replied with: mount: device not configured I've tried with different names fd0, fd0a, fd0.1440 without luck, can anyone hwlp me? The kernel has support for the floppy. Thanks -RP To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Jul 17 10:48:20 2001 Delivered-To: freebsd-small@freebsd.org Received: from kawoserv.kawo2.rwth-aachen.de (kawoserv.kawo2.RWTH-Aachen.DE [134.130.180.1]) by hub.freebsd.org (Postfix) with ESMTP id CF60937B405; Tue, 17 Jul 2001 10:48:14 -0700 (PDT) (envelope-from alex@big.endian.de) Received: from zerogravity.kawo2.rwth-aachen.de (zerogravity.kawo2.rwth-aachen.de [134.130.181.28]) by kawoserv.kawo2.rwth-aachen.de (8.9.3/8.9.3) with ESMTP id TAA18649; Tue, 17 Jul 2001 19:48:14 +0200 Received: by zerogravity.kawo2.rwth-aachen.de (Postfix, from userid 1001) id 8703114AF5; Tue, 17 Jul 2001 19:48:13 +0200 (CEST) Date: Tue, 17 Jul 2001 19:48:12 +0200 From: Alexander Langer To: Maxim Sobolev Cc: small@FreeBSD.ORG, arch@FreeBSD.ORG Subject: Re: Extending md(4) to allow it use pre-compressed disk image Message-ID: <20010717194812.A804@zerogravity.kawo2.rwth-aachen.d> References: <3B52CC08.1B08210F@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B52CC08.1B08210F@FreeBSD.org>; from sobomax@FreeBSD.ORG on Mon, Jul 16, 2001 at 02:12:17PM +0300 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake Maxim Sobolev (sobomax@FreeBSD.ORG): > size could vary), compresses each cluster using zlib and writes > compressed clusters along with information about offset of each > cluster into resulting image. After that compressed image could be put You sure that you don't produce that much overhead with all the additional gzip headers that it doesn't worse the compression? > I would like to know if there is enough interest in integrating this > feature into base system, please let me know what do you think about > it. Can you tell loader to load a mfs-compressed.gz? (I hope so) Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Jul 17 17: 1:48 2001 Delivered-To: freebsd-small@freebsd.org Received: from kalaid.f2f.com.ua (kalaid.f2f.com.ua [62.149.0.33]) by hub.freebsd.org (Postfix) with ESMTP id 7F5B537B405; Tue, 17 Jul 2001 17:01:37 -0700 (PDT) (envelope-from sobomax@FreeBSD.org) Received: from mail.uic-in.net (root@[212.35.189.4]) by kalaid.f2f.com.ua (8.11.4/8.11.4) with ESMTP id f6I02lB02793; Wed, 18 Jul 2001 03:02:51 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Received: from notebook.vega.com (das0-l102.uic-in.net [212.35.189.229]) by mail.uic-in.net (8.11.4/8.11.4) with ESMTP id f6I00pk01057; Wed, 18 Jul 2001 03:00:53 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Date: Wed, 18 Jul 2001 03:00:53 +0300 (EEST) Message-Id: <200107180000.f6I00pk01057@mail.uic-in.net> To: alex@big.endian.de Cc: small@FreeBSD.org, arch@FreeBSD.org From: Maxim Sobolev Subject: Re: Extending md(4) to allow it use pre-compressed disk image X-Mailer: Pygmy (v0.5.10) In-Reply-To: <20010717194812.A804@zerogravity.kawo2.rwth-aachen.d> Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 17 Jul 2001 19:48:12 +0200, Alexander Langer wrote: > Thus spake Maxim Sobolev (sobomax@FreeBSD.ORG): > > > size could vary), compresses each cluster using zlib and writes > > compressed clusters along with information about offset of each > > cluster into resulting image. After that compressed image could be put > > You sure that you don't produce that much overhead with all the > additional gzip headers that it doesn't worse the compression? That depends on how big your "much" is ;). It certainly produces some overhead compared to the plain gzip'ed file due to following reasons: additional index with offset of each compressed cluster (4 bytes per cluster) and clustering, which means that pieces of input treated by zlib as a fully independend data, that obviously limits the compression ratio. The former is rather small, as you can easily calculate with 16KB per cluster there will be only 1280 clusters for a 20MB image, which occupes only 5KB of data, while the latter is much bigger and it significantly depends on the size of cluster used. The following table compares results of compressing 10MB test image, which contains /bin and /etc subdirs from my workstation using different block sizes: Original size of the image: 10485760 bytes Size of the image when compressed with gzip -9: 3855949 bytes Cluster Size of Compressed Overhead Compared Amount ofRAM Size Image to gzip'ed Image Saved ------- ------------------ ----------------- ------------ 512 5,932,330 54% 4,553,430 1024 5,246,779 36% 5,238,981 2048 4,792,210 24% 5,693,550 4096 4,482,894 16% 6,002,866 8192 4,258,122 10% 6,227,638 16384 4,111,334 7% 6,374,426 32768 4,004,817 4% 6,480,943 65536 3,939,527 2% 6,546,233 Both the driver and compression utility support different block sizes, so it is really up to user whether he preffers performance over compression ratio or compression ratio over performance. Obviously that with the larger block sizes the driver will do more and more redundant work because to read some, arbitrary small portion of the cluster the driver has to decompress the whole cluster. However, provided simple MRU cahe effectively masks this effect by holding dozen of the most recently used clusters in decomressed form, so that from the performance standpoint difference between the cluster size of 512 bytes and cluster size of 16KB is ralatively small. > > I would like to know if there is enough interest in integrating this > > feature into base system, please let me know what do you think about > > it. > > Can you tell loader to load a mfs-compressed.gz? (I hope so) Yes, obviously you can, but unfortunately compression ratios achieved by compressing already compressed `mfs-compressed' images are rather low (typically less than 1%), so you wouldn't gain too much this way. :(( Please feel free to contact me with any other questions you might have. I think that among other things this new feature could be very useful to lower down minimal memory requirements during installation process, which could be a concern if we will move away from the plain old sysinstall(8) to a some GUI-based tool. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Jul 17 17:17:14 2001 Delivered-To: freebsd-small@freebsd.org Received: from wombat.bytecraft.au.com (wombat.bytecraft.au.com [203.39.118.3]) by hub.freebsd.org (Postfix) with ESMTP id 4CAF037B401 for ; Tue, 17 Jul 2001 17:17:09 -0700 (PDT) (envelope-from taylorm@bytecraft.au.com) Received: from pc99101401.bytecraft.au.com (unknown [203.39.118.42]) by wombat.bytecraft.au.com (Postfix) with SMTP id 6C75B3E9F; Wed, 18 Jul 2001 10:17:06 +1000 (EST) Message-ID: <00a201c10f1f$3251a9a0$2a7627cb@pc99101401.bytecraft.au.com> Reply-To: "Murray Taylor" From: "Murray Taylor" To: "Rolando Paez" , Cc: Subject: Re: Hello and problems changing the configuration Date: Wed, 18 Jul 2001 10:18:40 +1000 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MIMEOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG v mount /dev/fd0c /mnt works on my FreeBSD 4.3 box when ^ mounting my pico router disk (note the c. this tells the system to mount the disk using the 'c slice' ie the whole disk) Setting up initial configurations can be done like this: Creat and edit the file /usr/src/release/picobsd/mfs_tree/etc/oinit.rc putting in the required statements like ifconfig if0 10.1.2.3 netmask 255.255.255.0 and then re-compiling the pico router causes them to be put intothe crunched image and autorunning upon pico boot. I also create a file of ipfw rules (firewall.rules) and add a line to the oinit.rc file ipfw /etc/firewall.rules and this sets ipfw up correctly on boot also HTH cheers Murray Taylor Project Manager Bytecraft Systems Pty Ltd ph: +61 3 9587 2555 Fax: +61 3 9587 1614 Email: taylorm@bytecraftsystems.com -----Original Message----- From: Rolando Paez To: freebsd-small@freebsd.org Date: Wednesday, 18 July 2001 00:46 Subject: Fw: Hello and problems changing the configuration Sorry about the last message in html... -RP -------Original Message------- From: Rolando Paez Date: Monday, July 16, 2001 17:33:11 To: freebsd-small@freebsd.org Subject: Hello and problems changing the configuration Hello to all, I have a problem changing the configuration of a picobsd router floppy, it booted ok but the network interface is (of course) not configured, I searched all the fs for a text editor like vi without luck, and then tried to mount the floppy, it mounted and I could see all the configuration files but when I tried to do the same in another full version FBSD box : # mount /dev/fd0 /mnt it replied with: mount: device not configured I've tried with different names fd0, fd0a, fd0.1440 without luck, can anyone hwlp me? The kernel has support for the floppy. Thanks -RP To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Jul 17 17:45:45 2001 Delivered-To: freebsd-small@freebsd.org Received: from kwanon.research.canon.com.au (kwanon.research.canon.com.au [203.12.172.254]) by hub.freebsd.org (Postfix) with ESMTP id 6B6C537B405; Tue, 17 Jul 2001 17:45:37 -0700 (PDT) (envelope-from iain@research.canon.com.au) Received: from bellmann.research.canon.com.au (bellmann.research.canon.com.au [10.5.0.3]) by kwanon.research.canon.com.au (Postfix) with ESMTP id 2E9C4C2BB0; Wed, 18 Jul 2001 00:52:38 +0000 (UTC) Received: from blow.research.canon.com.au (blow.research.canon.com.au [10.8.1.4]) by bellmann.research.canon.com.au (Postfix) with ESMTP id 51AB28B10; Wed, 18 Jul 2001 10:30:28 +1000 (EST) Received: by blow.research.canon.com.au (Postfix, from userid 683) id E7921328FD; Wed, 18 Jul 2001 10:45:35 +1000 (EST) Received: from localhost (localhost [127.0.0.1]) by blow.research.canon.com.au (Postfix) with ESMTP id C5556328F5; Wed, 18 Jul 2001 10:45:35 +1000 (EST) Date: Wed, 18 Jul 2001 10:45:35 +1000 (EST) From: Iain Templeton To: small@FreeBSD.org Cc: arch@freebsd.org Subject: Re: Extending md(4) to allow it use pre-compressed disk image In-Reply-To: <200107180000.f6I00pk01057@mail.uic-in.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 18 Jul 2001, Maxim Sobolev wrote: > Original size of the image: 10485760 bytes > Size of the image when compressed with gzip -9: 3855949 bytes > > Cluster Size of Compressed Overhead Compared Amount ofRAM > Size Image to gzip'ed Image Saved > ------- ------------------ ----------------- ------------ > 512 5,932,330 54% 4,553,430 > 1024 5,246,779 36% 5,238,981 > 2048 4,792,210 24% 5,693,550 > 4096 4,482,894 16% 6,002,866 > 8192 4,258,122 10% 6,227,638 > 16384 4,111,334 7% 6,374,426 > 32768 4,004,817 4% 6,480,943 > 65536 3,939,52x 2% 6,546,233 > > Both the driver and compression utility support different block > sizes, so it is really up to user whether he preffers performance > over compression ratio or compression ratio over performance. > Obviously that with the larger block sizes the driver will do > more and more redundant work because to read some, arbitrary small > portion of the cluster the driver has to decompress the whole > cluster. However, provided simple MRU cahe effectively masks this > effect by holding dozen of the most recently used clusters in > decomressed form, so that from the performance standpoint difference > between the cluster size of 512 bytes and cluster size of 16KB is > ralatively small. > I know that the cramfs of linux used 4k blocks, but that was probably because they happened to be the page size of the machine we were using. This way when they needed to load a page, only one decompress was needed, and it was the entire resulting page. Would this provide any advantage to say the VM system? Our fs image was about 650k using initrd, and 900k using cramfs, but considering that it seemed to save about 1.5 MB of system memory, that wasn't a problem. It seemed that the initrd was in memory, but being loaded into memory again when the files were used... I guess it would be useful for us to be able to run a compressed filesystem out of flash memory, so only the used bits were in memory at a time. Actually, the bigger problem is that FreeBSD doesn't run on the MPC855/860, but that may change soon. Iain My 0.022c To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Jul 19 4:27:56 2001 Delivered-To: freebsd-small@freebsd.org Received: from mail002.syd.optusnet.com.au (mail002.syd.optusnet.com.au [203.2.75.245]) by hub.freebsd.org (Postfix) with ESMTP id B7A6D37B40C; Thu, 19 Jul 2001 04:27:39 -0700 (PDT) (envelope-from andrew.hannam@bigfoot.com) Received: from w95 (wdcax13-060.dialup.optusnet.com.au [198.142.220.60]) by mail002.syd.optusnet.com.au (8.11.1/8.11.1) with SMTP id f6JBRaC22124; Thu, 19 Jul 2001 21:27:37 +1000 Message-ID: <009901c11045$d0536a40$0104010a@famzon.com.au> Reply-To: "Andrew Hannam" From: "Andrew Hannam" To: "Maxim Sobolev" , References: <3B52CC08.1B08210F@FreeBSD.org> Subject: Re: Extending md(4) to allow it use pre-compressed disk image Date: Thu, 19 Jul 2001 21:27:24 +1000 Organization: FamZon Systems MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Does this include the necessary utilities to enable it to be written into the kernel so that the (bloated) loader is not needed in a Pico situation ? I would imagine that something like the "write_mfs_in_kernel" utility. You may also need some pre-compression utility so that you know how much space to allocate into the kernel image when building the kernel. ----- Original Message ----- From: "Maxim Sobolev" To: Cc: Sent: Monday, July 16, 2001 9:12 PM Subject: Extending md(4) to allow it use pre-compressed disk image > Hi folks, > > I extended md(4) driver to allow it use pre-compressed disk image. In > contrast with the current implementation, when loader(8) on loading > decompresses compressed image and holds it uncompressed in the memory, > with new feature loader(8) places compressed image into a memory, > while md(4) decompresses sectors when they are read. This could be > useful to decrease minimal memory requrements on FreeBSD install or in > another cases when memory is scarce. Performance is quite good - even > P133 reads data from such device at 2-2.5MB/s. > > Since standard gzip format is not really suitable for the task I > created an utility that splits original image into clusters (cluster > size could vary), compresses each cluster using zlib and writes > compressed clusters along with information about offset of each > cluster into resulting image. After that compressed image could be put > into the floppy or other media, loaded using loader(8) and accessed > through md(4) as usually. The only difference is that it is impossible > to write into resulting disk. > > I would like to know if there is enough interest in integrating this > feature into base system, please let me know what do you think about > it. > > -Maxim > P.S. Please keep me on the CC list. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-small" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Jul 19 14:51:45 2001 Delivered-To: freebsd-small@freebsd.org Received: from nwlynx.network-lynx.net (nwlynx.network-lynx.net [63.122.185.99]) by hub.freebsd.org (Postfix) with ESMTP id 2101337B403 for ; Thu, 19 Jul 2001 14:51:43 -0700 (PDT) (envelope-from Don@Silver-Lynx.com) Received: from Silver-Lynx.com (fly.network-lynx.net [63.122.185.98]) by nwlynx.network-lynx.net (8.11.1/8.9.3/Who.Cares) with ESMTP id f6JLpwO06500 for ; Thu, 19 Jul 2001 15:51:58 -0600 (MDT) (envelope-from Don@Silver-Lynx.com) Message-ID: <3B5755F1.14AF8D72@Silver-Lynx.com> Date: Thu, 19 Jul 2001 15:49:37 -0600 From: Don Wilde Reply-To: Don@Network-Lynx.net Organization: Network Lynx X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.3-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-small@freebsd.org Subject: status? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I just cvsup'd to 4-stable, and now my pico won't compile. The function that fails build is 'status', and the failure messages refer to a lack of identifiers named 'ieee80211_status' and 'set80211*'. Can someone point me to what's wrong? The buildworld/installworld and main kernel build went flawlessly. -- Don Wilde, President Network Lynx 866-272-5586 Email: Don@Network-Lynx.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Jul 19 14:56:50 2001 Delivered-To: freebsd-small@freebsd.org Received: from nwlynx.network-lynx.net (nwlynx.network-lynx.net [63.122.185.99]) by hub.freebsd.org (Postfix) with ESMTP id B160B37B401 for ; Thu, 19 Jul 2001 14:56:48 -0700 (PDT) (envelope-from Don@Silver-Lynx.com) Received: from Silver-Lynx.com (fly.network-lynx.net [63.122.185.98]) by nwlynx.network-lynx.net (8.11.1/8.9.3/Who.Cares) with ESMTP id f6JLvAO07240; Thu, 19 Jul 2001 15:57:10 -0600 (MDT) (envelope-from Don@Silver-Lynx.com) Message-ID: <3B575728.A5AA54CB@Silver-Lynx.com> Date: Thu, 19 Jul 2001 15:54:48 -0600 From: Don Wilde Reply-To: Don@Network-Lynx.net Organization: Network Lynx X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.3-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Don@Network-Lynx.net Cc: freebsd-small@freebsd.org Subject: Re: status? References: <3B5755F1.14AF8D72@Silver-Lynx.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Don Wilde wrote: > > I just cvsup'd to 4-stable, and now my pico won't compile. > > The function that fails build is 'status', and the failure messages > refer to a lack of identifiers named 'ieee80211_status' and 'set80211*'. > Can someone point me to what's wrong? The buildworld/installworld and > main kernel build went flawlessly. Sorry, that should have been: function 'status' in _ifconfig_. -- Don Wilde, President Network Lynx 866-272-5586 Email: Don@Network-Lynx.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Jul 19 15:11:31 2001 Delivered-To: freebsd-small@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 70CFE37B405 for ; Thu, 19 Jul 2001 15:11:23 -0700 (PDT) (envelope-from brdavis@odin.ac.hmc.edu) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f6JMBBj10477; Thu, 19 Jul 2001 15:11:11 -0700 Date: Thu, 19 Jul 2001 15:11:11 -0700 From: Brooks Davis To: Don@Network-Lynx.net Cc: freebsd-small@FreeBSD.ORG Subject: Re: status? Message-ID: <20010719151111.A8727@Odin.AC.HMC.Edu> References: <3B5755F1.14AF8D72@Silver-Lynx.com> <3B575728.A5AA54CB@Silver-Lynx.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="T4sUOijqQbZv57TR" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B575728.A5AA54CB@Silver-Lynx.com>; from Don@Silver-Lynx.com on Thu, Jul 19, 2001 at 03:54:48PM -0600 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --T4sUOijqQbZv57TR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jul 19, 2001 at 03:54:48PM -0600, Don Wilde wrote: > Don Wilde wrote: > >=20 > > I just cvsup'd to 4-stable, and now my pico won't compile. > >=20 > > The function that fails build is 'status', and the failure messages > > refer to a lack of identifiers named 'ieee80211_status' and 'set80211*'. > > Can someone point me to what's wrong? The buildworld/installworld and > > main kernel build went flawlessly. >=20 > Sorry, that should have been: function 'status' in _ifconfig_. If this is a compile error, you've probably got an out of date ifconfig.h. If it's a link error, then the process isn't including ifieee80211.c for some reason. Beyond that, I can't say since I don't have any idea how the picobsd build process works. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --T4sUOijqQbZv57TR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7V1r+XY6L6fI4GtQRAt1eAKDl6gWmTQ+ynURx3/ItC6ow3ZI8WQCguhGJ OkEP8xgrIGGQeFRNC49NQpw= =pkE+ -----END PGP SIGNATURE----- --T4sUOijqQbZv57TR-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Jul 19 16:30:53 2001 Delivered-To: freebsd-small@freebsd.org Received: from blount.mail.mindspring.net (blount.mail.mindspring.net [207.69.200.226]) by hub.freebsd.org (Postfix) with ESMTP id C38FC37B401 for ; Thu, 19 Jul 2001 16:30:51 -0700 (PDT) (envelope-from bill@mindspring.com) Received: from ah-soo.mindspring.com (pool0910.cvx19-bradley.dialup.earthlink.net [209.179.247.145]) by blount.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id TAA05797; Thu, 19 Jul 2001 19:30:49 -0400 (EDT) From: bill@mindspring.com Received: from localhost (bill@localhost) by ah-soo.mindspring.com (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id QAA03086; Thu, 19 Jul 2001 16:30:59 -0700 X-Authentication-Warning: ah-soo.mindspring.com: bill owned process doing -bs Date: Thu, 19 Jul 2001 16:30:59 -0700 (PDT) Reply-To: Bill Cassady To: Brooks Davis Cc: Don@Network-Lynx.net, freebsd-small@FreeBSD.ORG Subject: Off Topic::Re: status? In-Reply-To: <20010719151111.A8727@Odin.AC.HMC.Edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 19 Jul 2001, Brooks Davis wrote: > Any statement of the form "X is the one, true Y" is FALSE. Does that include or exclude the above statement? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Fri Jul 20 1: 5: 5 2001 Delivered-To: freebsd-small@freebsd.org Received: from kalaid.f2f.com.ua (kalaid.f2f.com.ua [62.149.0.33]) by hub.freebsd.org (Postfix) with ESMTP id 25B8737B405 for ; Fri, 20 Jul 2001 01:04:59 -0700 (PDT) (envelope-from sobomax@FreeBSD.org) Received: from mail.uic-in.net (root@[212.35.189.4]) by kalaid.f2f.com.ua (8.11.4/8.11.4) with ESMTP id f6K86fO34824; Fri, 20 Jul 2001 11:06:41 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Received: from vega.vega.com (das0-l93.uic-in.net [212.35.189.220]) by mail.uic-in.net (8.11.4/8.11.4) with ESMTP id f6K84Yk27565; Fri, 20 Jul 2001 11:04:42 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.11.4/8.11.3) with ESMTP id f6K84RD77977; Fri, 20 Jul 2001 11:04:27 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <3B57E622.5EA768C4@FreeBSD.org> Date: Fri, 20 Jul 2001 11:04:50 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en,uk,ru MIME-Version: 1.0 To: Andrew Hannam Cc: small@FreeBSD.org Subject: Re: Extending md(4) to allow it use pre-compressed disk image References: <3B52CC08.1B08210F@FreeBSD.org> <009901c11045$d0536a40$0104010a@famzon.com.au> Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Andrew Hannam wrote: > Does this include the necessary utilities to enable it to be written into > the kernel so that the (bloated) loader is not needed in a Pico situation ? I suppose that it could be written into the kernel like any other md(4) image. The only problem in this sutuation is the fact that we need to tell md(4) driver somehow that the image is in fact compressed one, not just plain md(4) image. It is easier with loader(8), because it allows specifying type of the image (i.e. md_image vs md_image_compressed). > I would imagine that something like the "write_mfs_in_kernel" utility. You > may also need some pre-compression utility so that you know how much space > to allocate into the kernel image when building the kernel. The write_mfs_in_kernel utility should work w/o problems with compressed image, however it is necessary to create an image before compiling the kernel to estimate size that needs to be allocated. -Maxim > ----- Original Message ----- > From: "Maxim Sobolev" > To: > Cc: > Sent: Monday, July 16, 2001 9:12 PM > Subject: Extending md(4) to allow it use pre-compressed disk image > > > Hi folks, > > > > I extended md(4) driver to allow it use pre-compressed disk image. In > > contrast with the current implementation, when loader(8) on loading > > decompresses compressed image and holds it uncompressed in the memory, > > with new feature loader(8) places compressed image into a memory, > > while md(4) decompresses sectors when they are read. This could be > > useful to decrease minimal memory requrements on FreeBSD install or in > > another cases when memory is scarce. Performance is quite good - even > > P133 reads data from such device at 2-2.5MB/s. > > > > Since standard gzip format is not really suitable for the task I > > created an utility that splits original image into clusters (cluster > > size could vary), compresses each cluster using zlib and writes > > compressed clusters along with information about offset of each > > cluster into resulting image. After that compressed image could be put > > into the floppy or other media, loaded using loader(8) and accessed > > through md(4) as usually. The only difference is that it is impossible > > to write into resulting disk. > > > > I would like to know if there is enough interest in integrating this > > feature into base system, please let me know what do you think about > > it. > > > > -Maxim > > P.S. Please keep me on the CC list. > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-small" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Sat Jul 21 14: 3:31 2001 Delivered-To: freebsd-small@freebsd.org Received: from blount.mail.mindspring.net (blount.mail.mindspring.net [207.69.200.226]) by hub.freebsd.org (Postfix) with ESMTP id 7498737B403 for ; Sat, 21 Jul 2001 14:03:28 -0700 (PDT) (envelope-from bill@mindspring.com) Received: from ah-soo.mindspring.com (pool0416.cvx19-bradley.dialup.earthlink.net [209.179.245.161]) by blount.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id RAA09202; Sat, 21 Jul 2001 17:03:20 -0400 (EDT) From: bill@mindspring.com Received: from localhost (bill@localhost) by ah-soo.mindspring.com (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id OAA07937; Sat, 21 Jul 2001 14:03:25 -0700 X-Authentication-Warning: ah-soo.mindspring.com: bill owned process doing -bs Date: Sat, 21 Jul 2001 14:03:25 -0700 (PDT) Reply-To: Bill Cassady To: Murray Taylor Cc: Rolando Paez , freebsd-small@freebsd.org, brucem@mail.cruzio.com Subject: Re: Hello and problems changing the configuration In-Reply-To: <00a201c10f1f$3251a9a0$2a7627cb@pc99101401.bytecraft.au.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 18 Jul 2001, Murray Taylor wrote: > Date: Wed, 18 Jul 2001 10:18:40 +1000 > From: Murray Taylor > Reply-To: Murray Taylor > To: Rolando Paez , freebsd-small@freebsd.org > Cc: brucem@mail.cruzio.com > Subject: Re: Hello and problems changing the configuration > > v > mount /dev/fd0c /mnt works on my FreeBSD 4.3 box when > mounting my pico router disk (note the c. this tells the > system to mount the disk using the 'c slice' ie the whole disk) I have not had success with this on the dial-in disk. pico complains of page fault, panics and reboots. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message