On Wed, 6 Feb 2002, David Douthitt wrote: > I've been working on setting up ports a little bit. I've finally > gotten to installing OpenBSD (this time on intel instead of mac68k) > and it uses ports like the other BSDs. > > Ports are really nice - basically you can download the entire ports > tree, or just one. Then, you change directory into > /usr/ports/net/wget (for example) and do a make - then a make install. > > The system automatically gets the original file, patches it and > configures it, and builds it for your system. In the case of OpenBSD, > it even creates the package and installs THAT when you do a make > install. > > Considering what this could mean for LEAF, consider this: a > NFS-enabled LEAF system, with / from a full system mounted somewhere. > Changing directories to /usr/src/ports/net/wget, do a make (pulls the > file in, patches, builds, compiles) - and a make install. > > After the make install is done, the LEAF system now has /tmp/wget.lrp > and an installed wget binary. > > Another possibility: using that full Linux system again, doing the > same thing - except this time a make install uses scp and a private > key to copy the file over to the LEAF system, then uses ssh and a > private key to install the package on the LEAF system. > > Thoughts? > -- > David Douthitt > UNIX Systems Administrator > HP-UX, Unixware, Linux > [EMAIL PROTECTED] >
I've always been attracted by this, even to the point of installed an OpenBSD 2.9 system to futz with. The BSD->Linux conversion is not something I like though -- I'm sure that there are workarounds and options for all the things that bug me, but I'm not willing to spend the time figuring it out. RPM has got to go. It's handy for point-by-point upgrades, but when the system gets out-of-date there's really no good way to upgrade the whole thing - you have to get a new distribution CD and do an upgrade, and in my experience it usually doesn't go smoothly, so you have to backup and whack the whole system. So the choices I'm looking at for my next Linux install (now that my Mandrake 8 boxen are getting out of date) are: LFS: appealing idea, but doesn't fix upgrading issues. Gentoo: leading the pack because they've brought ports to Linux. Sorcerer: very nifty, but showing a lot of rough edges. You'll note all three of these compile on your box instead of installing binaries. But now, you're discussing doing something like this for LEAF. I do not like the idea of LEAF having its own development environment at all. As it stands currently, most default LEAF installs could be hooked up to the Internet with telnet wide open and no root password without causing a lot of damage -- the only really hazardous tool in there is ping, and the SSH packages don't include scp. There's no lrzsz or uuencode or nc, so uploading all those evil packages you've made is very difficult, and there's no compiler or headers so uploading source and compiling it is impossible. All that changes if the bad guy can merely cd /usr/src/ports/net/ettercap. For a server appliance it makes more sense than for a router. But I'm really starting to lean away from the idea of using LEAF in its current form as an appliance. Doing so makes sense with special-purpose hardware designed not to have a hard disk, and LEAF compares nicely with Midori for this purpose. But on a PC or server, running an application from RAMdisk doesn't make sense to me. -- Jack Coates Monkeynoodle: A Scientific Venture... _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
