From: Bruce S. <bw...@ar...> - 2003-07-20 01:26:06
|
> >> o Errors from postfix/postfix-script: > > > > I've never used postfix, so I can't help you with that one, sorry. > > Hopefully one of the other developers can look into that. > > Well, I've gotten all but two of the problems fixed (see my other email). I > can't do much about the missing cmp command, and I still haven't figured out > yet why the aliases.db file isn't being created (but at least I have a > workaround - I simply created and copied an aliases.db to /etc). Missing "cmp" command? It's on my DL box: root@Devil:~ # whereis cmp cmp: /usr/bin/cmp /usr/share/man/man1/cmp.1.gz root@Devil:~ # cat /cdrom/VERSION 0.6Beta1-2003-07-18 root@Devil:~ # > > > o SOMEBODY MOVED GREP! Grep used to be in /usr/bin and is now in /bin - > > > this killed my firewall script. > > > > I suspect grep should be in /bin. That's where it is on my Redhat 9 PC. > > Sorry if that caused you problems. > > I have no thoughts on its "proper" place, but I don't remember seeing a > warning that its location had been moved. Something should be put into the > release notes. I did a little looking around (grep'ing scripts :) and I don't see where we copy it to CD in any of our scripts. That leads me to believe it gets copied to CD as part of the package's "make install" command. (if I had a clue what package it is part of, I could check to be sure) If so, then I can blame the fact it moved on the authors of grep, and we had no idea it moved when we upgraded to the latest version. Truthfully, I think you're making too big of a deal out of this. Don't specify the entire path name of the commands in your scripts, let $PATH do it's job instead. Or check for the location of the command(s) in your scripts and set a variable to use. > > > o Shutdown failed! (shutdown -r now). ... > > > > Yes, I tried it on my Devil Linux box and got the same thing. That's > > definitely a problem. Thanks for letting us know, we'll check it out. > > It also fails with a normal "shutdown -h now" the same way. Not surprised. > When a fix is determined, can you please announce it? That way, I can edit > my config files rather than having to burn another CD. Sure, I'll do my best to remember to announce it. > Also, now that I am thinking about it, there was some discussion that now > that everything will be symb. linked onto the CD that Devil-linux could > remove the requirement to "install" a lot of options (that they could simply > be there). I would point out that a strong security feature of Devil-Linux > is that there is NOTHING there that you don't ask for. I would have to have > somebody be able to exploit a hole in IPTRAF (as an example) simply because > it was now automatically installed (and now available). Not having all the commands loaded is a false sense of security. You don't have to start any more services than you need, so you're just as safe from outside attack. If you get compromised, then someone has root access to your system (since root is the only user), and if root needs a command that's not loaded, all they have to do is untar the package from the CDROM. Or then can untar one of the FTP clients and transfer anything they want. - BS |