Re: Modifying /etc/rc?
On Thu, Jan 30, 2003 at 02:49:07PM +0700, Roger Merritt said: Now, it seems to me that modifying the vncserver script is not elegant. I don't think it's a good idea for me to make *any* modifications to something that somebody else wrote, even when the code is as clear and easy to understand as in this case. Besides, what if I upgrade and forget to check if that file has changed? I could change the PATH variable to add /usr/X11R6/bin in my rc.d script. This sounds like a better idea to me. /etc/rc is also something that somebody else wrote. How about making a change to /etc/rc? Is this a Bad Idea (tm)? I'm sure there's a reason /usr/X11R6/bin isn't in the path set in that script. So far I haven't made an /etc/rc.local and I don't want to. The obvious argument against modifying /etc/rc is that it will add another merging operation to mergemaster whenever I upgrade. Is this kind of modification suitable for putting in /etc/rc.conf? unless I'm wrong, /etc/rc.local exists specifically so you don't have to modify /etc/rc. /etc/rc refers to rc.local as traditional (but rather obsolete), but nowhere in my FreeBSD travels over the past four years have I found any suggestion of what else you're supposed to use. I may not be understanding the problem you're trying to solve. HTH, Chris --- Chris Doherty chris [at] randomcamel.net I think, said Christopher Robin, that we ought to eat all our provisions now, so we won't have so much to carry. -- A. A. Milne --- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: IPFW, blocking IM servers
On Tue, Jan 21, 2003 at 06:20:09PM -0600, Kirk Strauser said: I'm doing that now, however, I know the Yahoo client will use any open port it can find and tunnel through that. I hadn't been aware of that. Seems like rather un-neighborly behaviour. heh. not that they originated the idea, but the first I heard about every application using HTTP was maybe five years ago when it turned out that if you blocked AIM's normal ports, it would just start using HTTP over port 80. :-) c --- Chris Doherty chris [at] randomcamel.net I think, said Christopher Robin, that we ought to eat all our provisions now, so we won't have so much to carry. -- A. A. Milne --- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: make in ports versus pkg_add
On Fri, Jan 17, 2003 at 05:58:40PM +1100, paul van den bergen said: Hi all, dumb q warning it seems to me that doing an install from /usr/ports/... is fine and all, but how do you do an uninstall? ok, with pkg_remove or pkg_delete, this is not a problem... but how does pkg know??? the pkg_* tools get that information from the directories in /var/db/pkg, which contain files with dependencies and packing lists. I prefer to use pkg_deinstall, which has support for wildcards and dependency recursion (if I delete a package I can tell pkg_deinstall to delete everything depending on that package, so I don't end up with packages broken because I deleted something they need). also note that pkg_* take specific package names, and not port names: i.e. I have to use zip-2.3_1 and not just zip. if the port version has not changed (e.g. the version of zip in /usr/ports/archivers/zip is still 2.3), you can cd to the ports directory and type make deinstall. it's always worth a shot: if the port version has changed it will just say Port is not installed, with no harm done. HTH, Chris --- Chris Doherty chris [at] randomcamel.net I think, said Christopher Robin, that we ought to eat all our provisions now, so we won't have so much to carry. -- A. A. Milne --- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Running portupgrade in the background?
On Fri, Jan 10, 2003 at 05:54:17PM -0500, Martin Gignac said: Hi, I'm often use portupgrade in combination with sudo from an SSH session and up till now I've never been able to put the portupgrade process in the background so that it can finish its job and I can safely exit the SSH session. when a process dies, in general all of its child processes die with it. in this case the portupgrade process is a child of the ssh session and dies when you log out. the solution is nohup(1): % nohup portupgrade $options which should leave the process running after you log out, and will dump the output to the file nohup.out unless you redirect it elsewhere. HTH, chris --- Chris Doherty chris [at] randomcamel.net I think, said Christopher Robin, that we ought to eat all our provisions now, so we won't have so much to carry. -- A. A. Milne --- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Renaming files with spaces in the name to files without spaces..
On Wed, Jan 08, 2003 at 06:01:50PM +0200, BigBrother (BigB3) said: -BEGIN PGP SIGNED MESSAGE- Sorry for this OT but I am trying for some hours to achieve a massive rename of files using a simple script and I have not success yet. I want to rename files like there is already a general utility for this: /usr/src/contrib/perl5/eg/rename . leviathan:/home/chris:1168 /usr/src/contrib/perl5/eg/rename Usage: rename perlexpr [filenames] not only already written and tested, but you get to use perl regexen. :-) HTH, Chris --- Chris Doherty chris [at] randomcamel.net I think, said Christopher Robin, that we ought to eat all our provisions now, so we won't have so much to carry. -- A. A. Milne --- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: bgcc, an idea
On Sun, Jan 05, 2003 at 03:15:41AM -0800, Brett Glass said: After the thread on GPL'd parts of FreeBSD, specially the compiler, I've decided to contribute my bit to the FreeBSD community. I'm proud to preset bgcc, 'The Brett Glass compiler collection', released under the BSD license, of course. As a lot of you know, I'm a professional programmer who does mostly embedded systems work, and the need for a truly free (free as in Richard Stallman blows dead goats) has arised many times. before anyone gets all excited, the real Brett Glass appears to be Brett Glass [EMAIL PROTECTED] and the given URL is a 404. probably the same bitter, unemployed tech worker with too much free time (I do sympathize there) who's been doing poor impersonations of Matt Dillon. I'm also pretty sure the real Brett Glass wouldn't say arised. please don't feed the troll. c not that anyone gung-ho on a flame war is going to read farther into the thread than the original post, and the irony of writing an email to stop emails doesn't escape me... --- Chris Doherty chris [at] randomcamel.net I think, said Christopher Robin, that we ought to eat all our provisions now, so we won't have so much to carry. -- A. A. Milne --- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: FreeBSD Stability
On Thu, Jan 02, 2003 at 06:09:11PM -0600, Dave Uhring said: You do realize, I hope, that Linux and Solaris roll over their uptimes at something like 492 days. from http://uptime.netcraft.com/up/accuracy.html#whichos -- Additionally HP-UX, Linux, Solaris and recent releases of FreeBSD cycle back to zero after 497 days, exactly as if the machine had been rebooted at that precise point. Thus it is not possible to see a HP-UX, Linux or Solaris system with an uptime measurement above 497 days. -- wacky. how/why is this the case? chris --- Chris Doherty chris [at] randomcamel.net I think, said Christopher Robin, that we ought to eat all our provisions now, so we won't have so much to carry. -- A. A. Milne --- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
