Re: [leaf-devel] Help needed: new chapters in Bering doc
Hi Jaques: We would welcome proofreading, comments and suggestions before release. 1 chapter in the Bering installation guide: http://leaf.sf.net/devel/jnilo/bisystem.html 2 chapters in the Bering user's guide: http://leaf.sf.net/devel/jnilo/butime.html http://leaf.sf.net/devel/jnilo/bumail.html I'll give them a look, but remember I'm not english native. Regards. -- Jaime Nebrera Herrera [EMAIL PROTECTED] --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] LINCE Project
Hej Jaime! We are doing quite the same but still have trouble finding the right hardware! I hope you might answer me the following question which is a knockout criteria for us: Does your CF have a physical write protection? We thought about using www.openbrick.org but didn't find the right hardware features until now! Do you have a better idea? Thanks a lot, Boris Andratzek At 23:50 08.10.2002 +0200, you wrote: Hi all, We are developing a Bering evolution focused in Compact Flash or DOM systems. Yes, Bering is great, but sticking to the floppie paradigma poses some limitations to its functionallity. Yes, you can do this adding more floppies into the equation but its not a practicall solution. Either way, we want to stay as close as posibble to the official release. That way, we could share code and lrp packages. Mostly the idea is just to pack enough lrp packages to have a lot more functionality and still use around 10MB. The other 6MB (of a 16MB CF card) will be left free for custom additions of each user. At this moment we have just created the official web page (http://www.eneotecnologia.com/proyectos_lince.html). Sorry at this moment only in spanish :( Also we have made an iso image that installs the standard Bering into the Hard Disk. Slowly we plan to add more packages to the core distro. In our priorities are HTB QoS and IPSeC. For the first we made a while ago a lrp package that used htb.init and worked great (but needed bash). I guess we will just include it. For IPSeC we will use standard lrp packages. Also dnscache will surelly be included. We dont plan to include a lot of hardware support into the base distro. This is an embedded project not a general distro. Most people will need to customize the iso image for their hardware. The typicall ethernet adapters will be included as this eases software installation. Also all lrp packages will be included into the iso image but wont be installed by default. Well, please post your comments and suggestions. Also, we dont have many hosting space, will be possible to use some of LEAF facilities (ftp). We could host the webpage but the iso is bigger than the space we have left in our hosting plan and dont want to buy a bigger one. Thanks in advance. Regards. -- Jaime Nebrera Herrera [EMAIL PROTECTED] --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] LINCE Project
Hej Jaime! At 11:08 09.10.2002 +0200, you wrote: Hi Boris, We are doing quite the same but still have trouble finding the right hardware! Have you solved the software side? Do you have already a ~10MB Bering distribution? It would be great to share efforts. No, we still work with older versions! Does your CF have a physical write protection? I have seen this thread in the list. I have no idea. We expect to receive the first unit at the end of the month. Please let me know if the physical write protector exists! Actually we dont consider that feature a must as we like the idea of updating remote systems easily. From our point of view this does not really conflict. Think of a red button at the front of the hardware and of someone to be advised to turn it to green while doing the service, later back to red. For us, the physical write protection is a neccessary requirement! regards, Boris --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] LINCE Project
Hi Vladimir, You may want to look into using CramFS like WISP-Dist does. You will save RAM on this. Yes indeed, WISP is much closer to what we want to achieve than standard Bering. Its already a Compact Flash oriented system. The problem is we have no experience with it, and we dont know what will be easier, going upwards with Bering (that we are used to) or trying to get a hand into WISP (that we are novels). But yes, I think this is a good point, we will play a bit with WISP too :)) Thanks for the advice. -- Jaime Nebrera Herrera [EMAIL PROTECTED] --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
RE: [leaf-devel] LINCE Project
I like the idea of a 'service' mode versus an 'operation' mode. That could be extremely useful. And how hard would that be to wire in. I'd like to contribute on a project like this, but my biggest problem is funding. I am trying to convince my boss to buy me some play hardware that could be used as a prototype. While we are on the subject, has any more progress been made on a web based config tool? Joey Officer Martin Apparatus, Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jaime Nebrera Herrera Sent: Wednesday, October 09, 2002 8:29 AM To: [EMAIL PROTECTED] Subject: Re: [leaf-devel] LINCE Project Hi again, Please let me know if the physical write protector exists! I will but dont think so. Actually we dont consider that feature a must as we like the idea of updating remote systems easily. From our point of view this does not really conflict. Think of a red button at the front of the hardware and of someone to be advised to turn it to green while doing the service, later back to red. For us, the physical write protection is a neccessary requirement! Yes indeed, but what happens when you are the only guy with the key to the rack enclosure? What happens if you have found some great piece of hardware but doesnt come with such a buttom? I'm not saying this is a bad idea. Probably it gives you the best security, but well, wont be a requisite in our development effort. Regards. -- Jaime Nebrera Herrera [EMAIL PROTECTED] --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] LINCE Project WP flash disk
Hi Boris I know that Mike Noyes was working on the write protectd flash disk. Actually there is such a beast, but it is hard to come by in small quantities. I was lucky to get a sample from SST http://www.sst.com and I am about to analyse the standard set up. If it is the way I believe it is then installing a write protect switch should be a piece of cake. HTH Erich At 14:34 09.10.2002, B. wrote: Hej Jaime! At 11:08 09.10.2002 +0200, you wrote: Does your CF have a physical write protection? I have seen this thread in the list. I have no idea. We expect to receive the first unit at the end of the month. Please let me know if the physical write protector exists! THINK Püntenstrasse 39 8143 Stallikon mailto:[EMAIL PROTECTED] PGP Fingerprint: BC9A 25BC 3954 3BC8 C024 8D8A B7D4 FF9D 05B8 0A16 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Help needed: new chapters in Bering doc
On Wed, Oct 09, 2002 at 07:59:07AM +0200, Jacques Nilo wrote: We have three new pieces for the Bering documentation that will be released with rc4 coming out shortly. We would welcome proofreading, comments and suggestions before release. Great stuff! I like the page about time in particular. That's something I always wanted... ;) I'll try to stay out of the content, more or less... So this is mostly just proofreading. Comments inline: 1 chapter in the Bering installation guide: http://leaf.sf.net/devel/jnilo/bisystem.html Proofreading: 10.3: If you want to add an hard-disk... - If you want to add a hard-disk... 10.9: PLease refer to... - Please refer... Suggestion: 10.8: Maybe mention ssh along with smtp/nntp towards the end? 2 chapters in the Bering user's guide: http://leaf.sf.net/devel/jnilo/butime.html 13.1: ...Jeff Newmiller from which... - ...from whom... 13.9: Miscellaneous g) maybe add some reason? Or just elaborate slightly more...? h) Does backing up etc.lrp save stuff if one chooses to go with ntpdate.lrp? (I guess not, but it ought to be a little clearer imho) i) great ;) http://leaf.sf.net/devel/jnilo/bumail.html 14.1: ... a help... 14.2: ! If you want to send mail...: ACCEPT fw net 25 tcp ...well, I might want to send it to an *internal* host ...(?) 14.3: After changing the cronjob is updated automatically. Maybe it's just me, but some punctuation might be good: After changing, the cronjob is updated automatically. -or even a small mention of *how* cron sees that something's changed (that the timestamp on the directory is updated) You can edit the multicron file as above or (probably a better idea) insert a new file with the syntax as before for each additional purpose. Might be better phrased as something like: To add jobs to be run, you can edit the multicron file. A better idea might be to put them in (a) separate file(s) in /etc/cron.d/ (keeping the syntax) ...or something Also this might be a good place to mention /var/spool/cron/crontabs/ -in case somebody would like to run a userland cronjob. And if that gets added, then a note on the fact that userland crontabs don't have the user -field. I know this is not supposed to be a new manpage, but having been through a bunch of cron-related stuff recently, I think it would be great to 'spell it out' just a *little* more. MHO, HTH, TIA a.s.o. ;) Jon Clausen --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Help needed: new chapters in Bering doc
Have you checked that ntpdate will run after serial modem is working, I have seen ntpclnt try to run before it can reach the internet! It might work fine for other connections but not a pppd demand dialing. Larry Platzek [EMAIL PROTECTED] On Wed, 9 Oct 2002, Jacques Nilo wrote: Date: Wed, 9 Oct 2002 07:59:07 +0200 From: Jacques Nilo [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: [leaf-devel] Help needed: new chapters in Bering doc We have three new pieces for the Bering documentation that will be released with rc4 coming out shortly. We would welcome proofreading, comments and suggestions before release. 1 chapter in the Bering installation guide: http://leaf.sf.net/devel/jnilo/bisystem.html 2 chapters in the Bering user's guide: http://leaf.sf.net/devel/jnilo/butime.html http://leaf.sf.net/devel/jnilo/bumail.html There are still some unresolved hyperlinks. Jacques Eric --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Help needed: new chapters in Bering doc
On Wed, 9 Oct 2002, Jacques Nilo wrote: We have three new pieces for the Bering documentation that will be released with rc4 coming out shortly. We would welcome proofreading, comments and suggestions before release. 1 chapter in the Bering installation guide: http://leaf.sf.net/devel/jnilo/bisystem.html 2 chapters in the Bering user's guide: http://leaf.sf.net/devel/jnilo/butime.html 13.3.2 : preformat example commands 13.3.3 : preformat example commands 13.3.3 : activate link to arachnoid 13.3.3 : I am pretty sure the second Shorewall rule should be ACCEPT fw loc udp 37 13.5 : See Bering Installation Guide ... perhaps should be a link to ___, except that I don't see a section on /etc/lrp.conf to link to. Omit? Note: 13.5, 13.6, and 13.7 and 13.8 are all (effectively) mutually exclusive approaches to the optional setup of automatic time maintenance, and should be presented as part of the same section 13.5... perhaps 13.5.1, 13.5.2, 13.5.3, and 13.5.4. 13.6 : b/ ... timsersever should be timeserver 13.7 : not having done this, I wonder whether svi ntpsimpl restart is needed. 13.9 : Spelling: Miscellaneous --- Jeff NewmillerThe . . Go Live... DCN:[EMAIL PROTECTED]Basics: ##.#. ##.#. Live Go... Live: OO#.. Dead: OO#.. Playing Research Engineer (Solar/BatteriesO.O#. #.O#. with /Software/Embedded Controllers) .OO#. .OO#. rocks...2k --- --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Help needed: new chapters in Bering doc
Am Mittwoch, 9. Oktober 2002 07:59 schrieb Jacques Nilo: We have three new pieces for the Bering documentation that will be released with rc4 coming out shortly. We would welcome proofreading, comments and suggestions before release. 1 chapter in the Bering installation guide: http://leaf.sf.net/devel/jnilo/bisystem.html -- snip --- # SPACECHECK, will check the space available on the root device. # If the remaining free space is = MINKB or = MINPER, each level # of file mask(s) will be wiped, until the minimum available space # is met or level 5 is reached. Files are individually null'ed # to 0 size. They are not rm'ed. (syslogd will not be interrupted) # When the level set in MAIL_LEVEL, is reached or exceeded, an # alert will be sent to ADMIN. (If set) lrp_SPACECHECK=NO # YES or NO lrp_SC_MINKB=-1 # = -1 to disable. lrp_SC_MINPER=2 # = 101 to disable. Default 2%. lrp_SC_MAIL_LEVEL=2 # = 6 to disable. lrp_SC_MNT=L lrp_SC_MOUNT=/var/log I guess the above comments are self explanatory :-) snip This isn't self explanatory. What are lrp_SC_MNT=L lrp_SC_MOUNT=/var/log ? I guess the spacecheck will happen on lrp_SC_MOUNT and not on the root device. No idea what lrp_SC_MNT stands for... kp --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] snort and nmap
Howdy Folks, I am looking for the most recent versions of nmap.lrp and snort.lrp. I checked the CVS packages repository and the only thing I found was an older version of nmap and no snort. Your guidance is appreciated... Eric --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Help needed: new chapters in Bering doc
Hello K-P you are right, there is even a small error in the abbreviated version, At the bottom I included a part of the original xml documentation. hope this makes it more clear. Am Mittwoch, 9. Oktober 2002 07:59 schrieb Jacques Nilo: We have three new pieces for the Bering documentation that will be released with rc4 coming out shortly. We would welcome proofreading, comments and suggestions before release. 1 chapter in the Bering installation guide: http://leaf.sf.net/devel/jnilo/bisystem.html -- snip --- # SPACECHECK, will check the space available on the root device. # If the remaining free space is = MINKB or = MINPER, each level # of file mask(s) will be wiped, until the minimum available space # is met or level 5 is reached. Files are individually null'ed # to 0 size. They are not rm'ed. (syslogd will not be interrupted) # When the level set in MAIL_LEVEL, is reached or exceeded, an # alert will be sent to ADMIN. (If set) lrp_SPACECHECK=NO # YES or NO lrp_SC_MINKB=-1 # = -1 to disable. lrp_SC_MINPER=2 # = 101 to disable. Default 2%. lrp_SC_MAIL_LEVEL=2 # = 6 to disable. lrp_SC_MNT=L lrp_SC_MOUNT=/var/log I guess the above comments are self explanatory :-) snip This isn't self explanatory. What are lrp_SC_MNT=L lrp_SC_MOUNT=/var/log ? I guess the spacecheck will happen on lrp_SC_MOUNT and not on the root device. No idea what lrp_SC_MNT stands for... I hope this part of the original documentation will makes things more clear. screen lrp_SPACECHECK=YES# YES or NO/screen paraYou can find this variable in the systemconfiguration. The default is NO. /para para This will check how much space there is left on a device you specify. If the space is less than the limit you set than a choosen action will be performed. For example delete files and mail an alert /para paraIn contrast to the original Dachstein and LRP version which tested the root device the Bering image tests the /var/log device as this is on a separate partition. /para para The configuration may seem a little complicated at first. The lrp_SC_MNT= sets the abbreviation for the different partitions/directory that should be tested example lrp_SC_MNT=L T /example Corresponding there should be a variable set with the name of the partition / directory example lrp_SC_MOUNT_L=/var/log lrp_SC_MOUNT_T=/tmp /example Now you can specify a treshold for the memory to take an action. You can specify this as KB (lrp_SC_MINKB) or percent of the partition.(lrp_SC_MINPER) example lrp_SC_MINKB_L=200 lrp_SC_MINPER_T=30 /example in this case there will be an action as soon as the free memory on /var/log is less than 200 KB on the /tmp partition there will be an action as soon as the amount of free space is less than 30% /para paraAs soon as one of the treshold for a certain partition is reached the following action is taken. look if there is a variable specifying the level and nullify the files in this variable. Now the space is checked again to see if the space is still under the treshold level if yes then the next level files is nullified. This continues untill level 5 is reached. example lrp_SC_L1=/var/log/*.4.gz lrp_SC_L2=/var/log/daemon.log /example in level 2 /var/log/daemon.log will be set to 0. /para Regards Eric Wolzak member of the Bering Crew --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] Re: [leaf-user] Best way to control ppp-on-demand ?
From: Elmar Gerwalin [EMAIL PROTECTED] To: Larry Platzek [EMAIL PROTECTED] Subject:Re: [leaf-user] Best way to control ppp-on- demand ? Copies to: leaflist [EMAIL PROTECTED] Date sent: Wed, 9 Oct 2002 18:13:02 +0200 Hello, On Wednesday 09 October 2002 18:03, Larry Platzek wrote: Why not use pppd to do demand dialing? I already have that, but it starts even when I don't want it E.g. Windows wants to get online without a user action and I want to stop it. What are you trying to prevent by having todo pon and poff by ssh? If you are just trying to limit what time of day pppd is online then you can use a cron job for turning ppp on and off (two events in cron table). Time limit is set to a few minutes, but that has some disadvantages: - when I want to stay offline , my system sometimes doesn't (see above) - when I'm thinking too long in front of my system, pppd goes offline Maybe this helps understanding my problem. Bye Elmar Hello Elmar, I used on a safe private network for exactly this situation the routerst.lrp this is a very small webserver (1-2 Kb) that must be run as root, and that can execute commands on the webserver. on calling a certain page ifdown ppp0 was executed, on an calling another ifup ppp0 was called. unfortunately the link http://www.digitech.org/~tjunkie/routerst is dead If you are interested, mail me , I have a version somewhere around. Regards grüsse nach Kaiserslautern Eric Wolzak member of the bering crew. --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Help needed: new chapters in Bering doc
Jon, Jeff, KPK and Larry: Thanks everyone for the useful feedback. I'll include most of your comments/remarks. Here is the updated version of butime.html: http://leaf.sf.net/devel/jnilo/butime1.html I still have to fix the rest: Jacques --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] LINCE Project WP flash disk
On Wed, 09 Oct 2002 19:24:49 +0200 Erich Titl [EMAIL PROTECTED] wrote Hi Boris I know that Mike Noyes was working on the write protectd flash disk. Actually there is such a beast, but it is hard to come by in small quantities. I was lucky to get a sample from SST http://www.sst.com and I am about to analyse the standard set up. If it is the way I believe it is then installing a write protect switch should be a piece of cake. What is considered an order, or what's to small of an order? What I'm getting at, can we pool together and make an order? Course, this is if it works ;) --- Homer Parker http://www.homershut.net telnet://bbs.homershut.net msg05729/pgp0.pgp Description: PGP signature
[leaf-devel] [ leaf-Bugs-621031 ] partial backup bug
Bugs item #621031, was opened at 2002-10-09 16:50 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=113751aid=621031group_id=13751 Category: Release/Branch: Bering Group: None Status: Open Resolution: None Priority: 5 Submitted By: Brad Fritz (bradfritz) Assigned to: Jacques Nilo (jnilo) Summary: partial backup bug Initial Comment: Line 172 of lrcfg.back.script currently clobbers the $EXCLUDE file generated by mk_inc_part(). Eric Wolzak suggested a fix in http://www.mail-archive.com/leaf-user%40lists.sourceforge.net/msg10133.html --Brad [EMAIL PROTECTED] -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=113751aid=621031group_id=13751 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
RE: [leaf-devel] LINCE Project
Joey Joey Officer wrote the following at 18:51 09.10.2002: I like the idea of a 'service' mode versus an 'operation' mode. That could be extremely useful. And how hard would that be to wire in. I'd like to contribute on a project like this, but my biggest problem is funding. I am trying to convince my boss to buy me some play hardware that could be used as a prototype. While we are on the subject, has any more progress been made on a web based config tool? I am toying with it, trying to get the skeleton right. Should dedicate more time but then who is paying the rent Erich THINK Püntenstrasse 39 8143 Stallikon mailto:[EMAIL PROTECTED] PGP Fingerprint: BC9A 25BC 3954 3BC8 C024 8D8A B7D4 FF9D 05B8 0A16 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] UML Questions
Hi All, I am working with bering1.0-rc3 and using it in a UML environment. I wanting to be able to boot up multiple bering file systems and be able to modify them and save the changes. In the UML documentation it says that if you use the same copy of a file system to do this then you will corrupt it. What I am trying to figure out is how to this without one uml load writing over another one. Here is my script: #! /bin/sh ./linuxuml-2.4.18-21\ ubd0=bering_fs \ initrd=initrd.lrp \ root=/dev/ram0 \ init=/linuxrc \ boot=/dev/ubd0:minix\ PKGPATH=/dev/ubd0 \ devfs=nomount \ LRP=root,etc,local,log,modules If I use this script multiple times then won't I have multiple copies of bering_fs using ubd0 and ram0? I modified the script so that ubd0 became ubd9 and ram0 became ram9 but I was unable to get through the boot sequence. Should this have worked? Any help is appreciated. Please let me know if there is more information needed that I have overlooked. Regards, Eric --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] UML Questions
Hello Eric, On Wed, 09 Oct 2002 20:03:47 -0400 Eric Kiser wrote: Hi All, I am working with bering1.0-rc3 and using it in a UML environment. I wanting to be able to boot up multiple bering file systems and be able to modify them and save the changes. In the UML documentation it says that if you use the same copy of a file system to do this then you will corrupt it. What I am trying to figure out is how to this without one uml load writing over another one. Here is my script: #! /bin/sh ./linuxuml-2.4.18-21\ ubd0=bering_fs \ initrd=initrd.lrp \ root=/dev/ram0 \ init=/linuxrc \ boot=/dev/ubd0:minix\ PKGPATH=/dev/ubd0 \ devfs=nomount \ LRP=root,etc,local,log,modules If I use this script multiple times then won't I have multiple copies of bering_fs using ubd0 and ram0? I modified the script so that ubd0 became ubd9 and ram0 became ram9 but I was unable to get through the boot sequence. Should this have worked? I am at the edge of (and possibly beyond) my understanding of UML here, but I believe ubd0 and ram0 are devices internal to each UML environment. If I am correct, you should be able to run multiple UML instances all using ubd0 and ram0. Any help is appreciated. Please let me know if there is more information needed that I have overlooked. I was able to get two copies of UML to boot simultaneously using the UML Copy-On-Write layer[1]. Here is a diff of my two start scripts: ./linuxuml-2.4.18-45 ubd0=cow0,bering_fs \ --- ./linuxuml-2.4.18-45 ubd0=cow1,bering_fs \ (Notice the first argument to the ubd0 parameter in each.) Aside from the different ubd0 parameters, my start scripts are nearly identical to yours. Here's one for reference: #!/bin/sh ./linuxuml-2.4.18-45 ubd0=cow0,bering_fs \ initrd=initrd.lrp \ root=/dev/ram0 \ init=/linuxrc \ boot=/dev/ubd0:minix \ PKGPATH=/dev/ubd0 devfs=nomount \ LRP=`cat packages.minimal` I haven't done any testing beyond booting the two instances, so I am not 100% positive I didn't screw something up that would come back to haunt me later. In other words, don't blame me if the above advice causes your computer to start smoking or blow up. ;) If I am reading the howto correctly, it looks like you can also merge the COW file with its backing file into a new file system image. Good luck! --Brad [1] http://user-mode-linux.sourceforge.net/UserModeLinux-HOWTO-7.html --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] snort and nmap
On Wed, Oct 09, 2002 at 02:05:49PM -0400, Eric B Kiser wrote: I am looking for the most recent versions of nmap.lrp and snort.lrp. I checked the CVS packages repository and the only thing I found was an older version of nmap and no snort. I'm the one who's probably responsible for those packages - and responsible for them being so old. I've not kept up development as I ought. However, I'm planning to get back into the game. I recently configured a Pentium with Red Hat 6.x and Oxygen dual boot; we'll see how it goes. Also, the Oxygen/LEAF Resource CDROM contains all binaries and sources and probably also the compile-time options in a patch and so forth. These days, I've been working towards putting all source code into a sort of ports tree like FreeBSD and Gentoo Linux; it becomes very flexible. I'll see if I can compile nmap and/or snort in coming days. --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
