> Why do you need vsftpd? I'm not saying you don't, but I'm curious what > your use case is.
I don't exactly build a "daily personal use" system, though it is that. I build something I can throw at any (compatible) box for whatever purpose I can imagine I'd want to do, and have it "stick". So far that's been true. I do have a dedicated server box, and use both scp and FTP. The LAN is encrypted or wired, so why pay the price of encrypting & decrypting in the server and client? The benefit everybody attributes to SSH/SCP is more of a penalty. As a matter of fact all of my boxes can be server boxes with just a reboot! I've setup runlevel 4 to start the servers. I do have to restart my firewall though. > > Of course it is your system to do as you please. But sometimes newer But I need, want, and/or appreciate (B)LFS being an *open* development system. It doesn't get into cloud or even container stuff, barely mentions virtualization, but that's OK. > things are better than the old ways. Of course, some newer things are > worse (*cough* systemd *cough*). Not so often better, more often worse, IMO. I'd throw the major distros in that boat too. I learned the term "creeping featuritis" long, long ago. I *like* the *NIX philosophy of simple programs that do one thing very well. KISS. I have a P3 on this table running a couple versions of my "POD", but also W98 & W95 partitions because I have occasional need of PaintShop Pro. I know how to get work done in it, and *don't* need GIMP or Inkscape loaded up with features that make it way too complicated to learn to do a simple job! I tried! That's why the P3 is here. > > One of the things I like to teach at school are what applications or > programs are still around, but of questionable value. Questionable by whom? Maybe you don't have a use case... Sure, some of the things I see flying by that people are doing with Linux boggle my mind, but they apparently need to do whatever. (I admit to having wondered "what the #### is *THAT* option good for" a time or three.) > want to teach every program in coreutils. Some have been around since > RAM was measured in K and floppies or punch cards were the main mass I was cleaning out my "junk room" late last week because I need to put some rhododendros seedling under lights in there and came across a 256K S-100 DRAM board. Yes, we had S-100 systems that supported that much RAM; hard drives too! I come from an IBM mainframe environment, very familiar with punch cards. Got a box of 10" reels of 1/2" mag tape (24MB/reel!) I need to toss, would if they would be recycled. > > The book does not recommend building BLFS as root. Those of us who Yeah, heard that. Made no sense. Everybody makes mistakes, so you prepare for them! Why do I need sudo? Protect me from myself? Like I don't know the root password? > > More to the point, ISTR make fails *quickly*. It does for root, but this SSL thing is buried *deep*, in stuff it downloads. Not sure what I'm going to do. So I hung a garage side door today--amazingly everythhing fitted spot on! > as a user, but I think that was to do with trying to catch dump > files when tests segfaulted. "C 0" I'm not young enough to use a core dump on somebody else's code! One of the things "life's too short" for. Sounding like an old curmudgeon, I am! -- Paul Rogers [email protected] Rogers' Second Law: "Everything you do communicates." (I do not personally endorse any additions after this line. TANSTAAFL :-) -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
