ports have made me lazy
I need to install zlib (not zlibc), and AFACT it is not included in ports. When I look at the zlib web site, I see that there are several (not a lot, but several) dependencies for the installation -- and I think, OH NO, NOT DEPENDENCIES! Or something like that. I blame it on ports. They have made me lazy. I am a victim. ;-) Anyway, and more to the point, am I missing something? Is zlib really not included in ports? If not, is there an automated/semi-automated means of installing it -- or am I back to the old days of installing dependencies manually? (I have had two servers go toes up in three days, so if I've missed the obvious here, well, it wouldn't surprise me. Just administer clue in the standard manner, and I'll get with the program.) __ Vince Sabio vi...@vjs.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ports have made me lazy
** At 13:30 -0400 on 10/03/2009, ill...@gmail.com wrote: 2009/10/3 Glen Barber glen.j.bar...@gmail.com: On Sat, Oct 3, 2009 at 10:04 AM, Vince Sabio vi...@vjs.org wrote: I need to install zlib (not zlibc), and AFACT it is not included in ports. When I look at the zlib web site, I see that there are several (not a lot, but several) dependencies for the installation -- and I think, OH NO, NOT DEPENDENCIES! Or something like that. I blame it on ports. They have made me lazy. I am a victim. ;-) They should have meetings once a week or something... :-) If they had them, I'd be a candidate. Anyway, and more to the point, am I missing something? Is zlib really not included in ports? If not, is there an automated/semi-automated means of installing it -- or am I back to the old days of installing dependencies manually? I'll assume you mean the zlib compression library. Yes, that's probably what it is. I found a few with: cd /usr/ports; make search key=zlib Worked for me. Muchas gracias. Based on what I read at http://www.zlib.net/ The latest version (1.2.3) is in base: http://www.freebsd.org/cgi/man.cgi?query=zlibapropos=0sektion=0manpath=FreeBSD+7.2-RELEASEformat=html http://tinyurl.com/yksxt9p I don't know if I had a screwy install (I wouldn't put it past the stoopit sysadmin) (oh wait, that's me) or what -- but while I had the man page for zlib, I apparently it wasn't actually installed. Someone is trying to install some web-site-management kit on the machine, and it complained that zlib wasn't installed. Seems to be installed now; I guess, at some point, I'll find out if the web kit installer is happy now. Many thanks for the assistance on this. __ Vince Sabio vi...@vjs.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: what character is a physical newline
** At 22:30 -0400 on 06/28/2009, Glen Barber wrote: On Sun, Jun 28, 2009 at 10:27 PM, Aryeh M. Friedman wrote: What do you mean exactly? What language(s)? If I understand your question correctly, the C / C++ / Java / PHP (and I think Perl) 'newline' character is '\n' I meant what ascii character does \n actual correspond to (I assume CR but just making sure) No, CR is a carriage return, which is a \r in C, and is an ASCII 13 (hex 0D). Newline is a line feed (LF), which is a \n in C, and is an ASCII 10 (hex 0A) Oh. IIRC, CR is the DOS way, and LR is the POSIX way. Not exactly; CRLF is the DOS way, CR is the Macintosh way, and LF is Unix/Posix. HTH. __ Vince Sabio vi...@vjs.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: MIME attachments in mbox files
** At 00:56 -0700 on 05/30/2009, George Davidovich wrote:
On Fri, May 29, 2009 at 11:40:52PM -0400, Vince Sabio wrote:
I have a need (well, I have lots of needs, but I'll try to stay
focused here)
Given the nature of most messages in the last few days, I'd suggest
you're trying too hard. ;-)
Yeah, I was considering leading with an apology for the on-topic post. g
to be able to take a Windows zip file that is stored as a MIME
attachment to an e-mail message in an Mbox-format spool file, and
unzip the attachment. I actually need to script the process. In case
it helps, I can dedicate a mailbox to the task.
Anyone know of any FreeBSD utility(ies) that do(es) this?
Generally, when you're talking about processing an mbox and doing
something with message bodies, you're looking at formail plus procmail
in combination with a tool that can interpret the mime structure and
process the components (mimedefang, demine, stripmime, mimedecode,
reformime, renattach, etc.). That's a roundabout way of saying, no,
there are no FreeBSD utilities to do what you want, but there's lots to
be found in ports.
Sorry, I misspoke: sed 's/utilities/ports/g'
I'd start with a quick read through of some of those manpages, but at
first glance, ripmime alone might do the trick:
http://www.freebsd.org/cgi/man.cgi?query=ripmimeapropos=0sektion=0manpath=FreeBSD+7.2-RELEASE+and+Portsformat=ascii
This, and Ian's munpack suggestion, will both do what I need -- but
with one [very minor] exception: There is no way to override the file
name specified in the MIME header (if present, which, in my case, it
typically will be) and force it to use a specific output file name.
Or just send the output to stdout, so I can redirect it to a file
name of my choice (or to unzip). Not a show stopper by any means,
just requires a workaround. I suspect that the authors of these
utilities (there I go again) expected they would be invoked
interactively.
If necessary, I can write my own parser to strip out the attachment,
in which case I'd need only a widget that can take in a MIME (base64)
encoded zip file, convert it to binary, and unzip it.
In that case, and assuming you're using Perl, MIME::base64 and
IO::Uncompress::Unzip (or /usr/ports/archivers/unzip) is what you want.
Bonus points for writing a one-liner.
Using C, but shelling out where necessary to get stuff done.
It looks like {ripmime, munpack} and unzip will do the trick. Many
thanks for the pointers. I now return you to your regularly scheduled
META discussion(s)... :-)
__
Vince Sabio vi...@vjs.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
MIME attachments in mbox files
I have a need (well, I have lots of needs, but I'll try to stay focused here) to be able to take a Windows zip file that is stored as a MIME attachment to an e-mail message in an Mbox-format spool file, and unzip the attachment. I actually need to script the process. In case it helps, I can dedicate a mailbox to the task. If necessary, I can write my own parser to strip out the attachment, in which case I'd need only a widget that can take in a MIME (base64) encoded zip file, convert it to binary, and unzip it. Anyone know of any FreeBSD utility(ies) that do(es) this? __ Vince Sabio vi...@vjs.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Issue With 7.0-Rel - 7.1-Rel Update
Anyone have any ideas on this? Or should I make a couple of backups (test them to confirm they're viable) and install v7.1 from scratch? Hmmm. There's actually a certain appeal to installing v7.1 from scratch. RHEL has the option of creating SoftRAID mirrors at install time (and later, of course). Does the FreeBSD installer have that capability, as well? If so, then I'll probably go that route even if there's a simple solution to the dilemma below; disk space has become so incredibly cheap that it's almost a mistake *not* to configure mirrors at this point. Either way, all pointers appreciated Thanks, Vince ** At 14:24 -0500 on 02/22/2009, Vince Sabio wrote: Hi folks, I am updating an AMD-based machine from v7.0-RELEASE to v7.1-RELEASE. Here's what I get: BEGIN: ares-root# freebsd-update upgrade -r 7.1-RELEASE Looking up update.FreeBSD.org mirrors... 2 mirrors found. Fetching metadata signature for 7.0-RELEASE from update2.FreeBSD.org... done. Fetching metadata index... done. Inspecting system... done. The following components of FreeBSD seem to be installed: kernel/generic src/base src/bin src/contrib src/crypto src/etc src/games src/gnu src/include src/krb5 src/lib src/libexec src/release src/sbin src/secure src/share src/sys src/ubin src/usbin world/base world/dict world/doc world/games world/info world/manpages world/proflibs The following components of FreeBSD do not seem to be installed: src/cddl src/compat src/rescue src/tools world/catpages Does this look reasonable (y/n)? y Fetching metadata signature for 7.1-RELEASE from update2.FreeBSD.org... done. Fetching metadata index... done. Fetching 1 metadata patches. done. Applying metadata patches... done. Fetching 1 metadata files... done. Inspecting system... done. Fetching files from 7.0-RELEASE for merging... done. Preparing to download files... done. Fetching 14771 patches.[snip snip snip]... done. Applying patches... done. Fetching 21632 files... gunzip: (stdin): unexpected end of file 21ca797afb693c5ee108f0c9a617760501cb749b9592603dc16e089acf2be70f has incorrect hash. ares-root# END Weird. But hey, I'm an optimist (and it was 2:00 a.m.), so I figured WTF, I'll try it again BEGIN: ares-root# freebsd-update upgrade -r 7.1-RELEASE Looking up update.FreeBSD.org mirrors... 2 mirrors found. Fetching metadata signature for 7.0-RELEASE from update2.FreeBSD.org... done. Fetching metadata index... done. Fetching 1 metadata patches. done. Applying metadata patches... done. Fetching 1 metadata files... done. Inspecting system... done. The following components of FreeBSD seem to be installed: kernel/generic src/base src/bin src/contrib src/crypto src/etc src/games src/gnu src/include src/krb5 src/lib src/libexec src/release src/sbin src/secure src/share src/sys src/ubin src/usbin world/base world/dict world/doc world/games world/info world/manpages world/proflibs The following components of FreeBSD do not seem to be installed: src/cddl src/compat src/rescue src/tools world/catpages Does this look reasonable (y/n)? y Fetching metadata signature for 7.1-RELEASE from update2.FreeBSD.org... done. Fetching metadata index... done. Fetching 1 metadata patches. done. Applying metadata patches... done. Fetching 1 metadata files... done. Inspecting system... done. Fetching files from 7.0-RELEASE for merging... done. Preparing to download files... done. Fetching 10796 patches.102030. done. Applying patches... done. Fetching 18821 files... done. Attempting to automatically merge changes in files... done. The following file could not be merged automatically: /etc/amd.map Press Enter to edit this file in vi and resolve the conflicts manually... END Okay, I reach that point and press Enter, and I am presented with a diff-style file in vi (which is fine; I'm a vi user) that clearly highlights the differences between the current file and v7.1-R file. I'm good to go with the v7.1-R version, so I edit out the 'current' section, remove the 'diff' markers, ZZ, and that file is done. The updater then presents me with another file whose changes could not be merged automatically. So I go through the identical process. Wash, rinse, repeat, FOR [more than] FORTY MINUTES' worth of files. Each time, I kept thinking, Okay, this has to be the last one.., but it wasn't. Even after 40 minutes, the process was not completed -- I just threw in the towel. For all I know, this process could have continued for all 21632 files -- version 11.5-RELEASE could have been out by the time I finished that process. So, first of all, what did I do wrong? Second, when I start the upgrade over again, what should I do differently? And, if all else fails: In each case of editing the files, the v7.1 version was fine. Is there any way to tell it, I have good backups, and want to live dangerously, so Just Do It, and don't ask me if I want to edit anything...? Muchas
Issue With 7.0-Rel - 7.1-Rel Update
Hi folks, I am updating an AMD-based machine from v7.0-RELEASE to v7.1-RELEASE. Here's what I get: BEGIN: ares-root# freebsd-update upgrade -r 7.1-RELEASE Looking up update.FreeBSD.org mirrors... 2 mirrors found. Fetching metadata signature for 7.0-RELEASE from update2.FreeBSD.org... done. Fetching metadata index... done. Inspecting system... done. The following components of FreeBSD seem to be installed: kernel/generic src/base src/bin src/contrib src/crypto src/etc src/games src/gnu src/include src/krb5 src/lib src/libexec src/release src/sbin src/secure src/share src/sys src/ubin src/usbin world/base world/dict world/doc world/games world/info world/manpages world/proflibs The following components of FreeBSD do not seem to be installed: src/cddl src/compat src/rescue src/tools world/catpages Does this look reasonable (y/n)? y Fetching metadata signature for 7.1-RELEASE from update2.FreeBSD.org... done. Fetching metadata index... done. Fetching 1 metadata patches. done. Applying metadata patches... done. Fetching 1 metadata files... done. Inspecting system... done. Fetching files from 7.0-RELEASE for merging... done. Preparing to download files... done. Fetching 14771 patches.[snip snip snip]... done. Applying patches... done. Fetching 21632 files... gunzip: (stdin): unexpected end of file 21ca797afb693c5ee108f0c9a617760501cb749b9592603dc16e089acf2be70f has incorrect hash. ares-root# END Weird. But hey, I'm an optimist (and it was 2:00 a.m.), so I figured WTF, I'll try it again BEGIN: ares-root# freebsd-update upgrade -r 7.1-RELEASE Looking up update.FreeBSD.org mirrors... 2 mirrors found. Fetching metadata signature for 7.0-RELEASE from update2.FreeBSD.org... done. Fetching metadata index... done. Fetching 1 metadata patches. done. Applying metadata patches... done. Fetching 1 metadata files... done. Inspecting system... done. The following components of FreeBSD seem to be installed: kernel/generic src/base src/bin src/contrib src/crypto src/etc src/games src/gnu src/include src/krb5 src/lib src/libexec src/release src/sbin src/secure src/share src/sys src/ubin src/usbin world/base world/dict world/doc world/games world/info world/manpages world/proflibs The following components of FreeBSD do not seem to be installed: src/cddl src/compat src/rescue src/tools world/catpages Does this look reasonable (y/n)? y Fetching metadata signature for 7.1-RELEASE from update2.FreeBSD.org... done. Fetching metadata index... done. Fetching 1 metadata patches. done. Applying metadata patches... done. Fetching 1 metadata files... done. Inspecting system... done. Fetching files from 7.0-RELEASE for merging... done. Preparing to download files... done. Fetching 10796 patches.102030. done. Applying patches... done. Fetching 18821 files... done. Attempting to automatically merge changes in files... done. The following file could not be merged automatically: /etc/amd.map Press Enter to edit this file in vi and resolve the conflicts manually... END Okay, I reach that point and press Enter, and I am presented with a diff-style file in vi (which is fine; I'm a vi user) that clearly highlights the differences between the current file and v7.1-R file. I'm good to go with the v7.1-R version, so I edit out the 'current' section, remove the 'diff' markers, ZZ, and that file is done. The updater then presents me with another file whose changes could not be merged automatically. So I go through the identical process. Wash, rinse, repeat, FOR [more than] FORTY MINUTES' worth of files. Each time, I kept thinking, Okay, this has to be the last one.., but it wasn't. Even after 40 minutes, the process was not completed -- I just threw in the towel. For all I know, this process could have continued for all 21632 files -- version 11.5-RELEASE could have been out by the time I finished that process. So, first of all, what did I do wrong? Second, when I start the upgrade over again, what should I do differently? And, if all else fails: In each case of editing the files, the v7.1 version was fine. Is there any way to tell it, I have good backups, and want to live dangerously, so Just Do It, and don't ask me if I want to edit anything...? Muchas gracias __ Vince Sabio vi...@vjs.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
WRITE errors
I recently installed 7.0-RELEASE, and have recently started seeing these in my kernel log: g_vfs_done():ad2s1a[WRITE(offset=19671924736, length=131072)]error = 5 ad2: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=71976351 ad2: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=36619199 ad2: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=36638271 ad2: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=36638271 ad2: FAILURE - WRITE_DMA status=51READY,DSC,ERROR error=84ICRC,ABORTED LBA=36638271 g_vfs_done():ad2s1a[WRITE(offset=1578893312, length=131072)]error = 5 I suspect that the errors are not associated with the upgrade (i.e., coincidence). Are they serious, or just something that is being reported in v7 that wasn't being reported in v5.1? __ Vince Sabio [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrade v5.x to v7.0
** At 12:14 -0400 on 08/11/2008, Robert Huff wrote: Vince Sabio writes: I am currently running FreeBSD v5.1 (yes, I am a Bad Person(tm)), Why? Why am I a Bad Person(tm), or why am I still running v5.1? and need to update it to v7.0. Questions: 1. Can I go straight from v5.1 to v7.0? Or do I need to make a stop at v6.x? It is probably technically possible. However: when jumping major versions, my advice is always If possible, install from clean disk. I assume you mean install from a clean CD -- I did that, and it worked like a charm. And, for anyone else running v5.x who is considering upgrading to v7.0, this seems to be a very good way to do it. I downloaded and burned a bootonly.iso, and then ran the upgrade via [passive] FTP. Ten or fifteen minutes later, I was booting into v7.0. In either case: remember to save critical config files (rc.conf, the kernel config, sshd_config, the named directory, etc.) elsewhere. The fact that the upgrade worked proves that my backups are in good shape -- if they weren't, then the upgrade would have overwritten the system disk and then failed. ;-) __ Vince Sabio [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Upgrade v5.x to v7.0
I am currently running FreeBSD v5.1 (yes, I am a Bad Person(tm)), and need to update it to v7.0. Questions: 1. Can I go straight from v5.1 to v7.0? Or do I need to make a stop at v6.x? 2. I'm Unix shell literate with a reasonable level of Solaris sysadmin experience, but have no experience (yet) with FreeBSD updates. Is there a site with step-by-step instructions for the uninitiated, to help minimize Pr(failure)? 3. Anything else I should know? Muchas gracias __ Vince Sabio [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrade v5.x to v7.0
** At 00:25 +0200 on 08/12/2008, Ivan Voras wrote: Vince Sabio wrote: I am currently running FreeBSD v5.1 (yes, I am a Bad Person(tm)), and need to update it to v7.0. Questions: 1. Can I go straight from v5.1 to v7.0? Or do I need to make a stop at v6.x? Theoretically it might be possible but definitely not recommended. 5.1 is very old (it's not even labeled STABLE Neither am I -- so my FreeBSD box and I are even. - are you sure FreeBSD updates track such old releases?) I don't think they do. and there might be unexpected problems. 2. I'm Unix shell literate with a reasonable level of Solaris sysadmin experience, but have no experience (yet) with FreeBSD updates. Is there a site with step-by-step instructions for the uninitiated, to help minimize Pr(failure)? 3. Anything else I should know? You probably don't want to do it with binary upgrades, for many reasons, including unexpected problems (i.e. possibility of ending up with a system so messed up nobody could help you restore it). Do a source upgrade to 6.0 then to 7.0 - it's not hard. For best effects, you need to also recompile all additional ports installed on the server (actually, you *can* run ports compiled for 5.x on 7.x but as soon as you need to upgrade one of them, you'll probably need to upgrade all or most of them because of cross-dependencies). Got it. There are sites that go through the 6.x to 7.0 upgrade, but I've foud nothing that explains how to get from 5. to 6.x. Any ideas here? __ Vince Sabio [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [SSHd] Increasing wait time?
** At 07:33 +0200 on 05/08/2008, Peter Boosten wrote: Vince Sabio wrote: Note if you choose to do this: scp'ing files becomes a four-step process (i.e., scp file(s) to intermediate server, log in to intermediate server, scp to destination server, delete file(s) from intermediate server). Still worth it, though. Never thought of port forwarding? Sure, but that would still leave my machines vulnerable to script kiddies. Since I rarely move files between my laptop and my server, the four-step process is not a big deal. If I did it more often, I'd probably cron up a script on the intermediate machine to move (and delete) the files for me. __ Vince Sabio [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [SSHd] Increasing wait time?
** At 09:59 -0800 on 05/06/2008, Beech Rintoul wrote: On Tuesday 06 May 2008, David Kelly said: On Tuesday 06 May 2008, Gilles said: Is there a way to configure SSHd, so that the wait time between login attempts increases after X failed tries? Depending on how you use ssh from external systems you could add firewall rules to disallow all but known sources. I was doing that in the past, but I found it to be inflexable and sometimes a pain to deal with. I sometimes need to access a server from a new location and that kind of hard lockdown just isn't practical. I had the same problem (i.e., needing to access the server from a new location). In my case, one of the allowed sites is the server of a friend who has provided a shell account for me. When I'm on the road, I just ssh to his machine, and from there I can ssh into any of my machines. His machine effectively does all of the script-kiddie filtering for my site. ;-) Note if you choose to do this: scp'ing files becomes a four-step process (i.e., scp file(s) to intermediate server, log in to intermediate server, scp to destination server, delete file(s) from intermediate server). Still worth it, though. Remember the wave theory of script kiddies (WARNING: Gross oversimplification ahead): Quantum mechanics says that if you throw yourself against a wall several quintillion times, you'll eventually wave through it without leaving a mark on yourself or the wall.* Similarly, a sufficiently large number of break-in attempts by script kiddies will result in one of them waving straight past all of the security without leaving a scratch. FWIW, I agree with cpghost -- it's strange that an addition as obvious and useful as this isn't already supported. __ Vince Sabio [EMAIL PROTECTED] * As if the first few billion tries didn't already leave some rather noticeable marks on both you AND the wall. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Javascript in Lynx
I'm running 5.1-RELEASE, and need to use Lynx via an ssh session to access my firewall's administrative interface. Logging into the firewall requires javascript. My FreeBSD machine has a stock installation of Lynx Version 2.8.4rel.1. I've gone through the [O]ptions in Lynx to find some means of enabling javascript, but haven't been able to locate it. The on-line docs don't seem to mention anything about it. Does Lynx even support javascript? If so, how do I enable it? -- __ Vince Sabio [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
math.h doesn't include pow?
My C library documentation states that the pow (power) function is included in math.h. However, when I go to link (compiling and linking with gcc), I get the following: In function `[function name]': [path/]datetime.c:668: undefined reference to `pow' Yes, I'm including math.h. If I compile the exact same code under Darwin (BSD on PowerPC), it compiles fine. It also compiles in CodeWarrior. Is anyone else familiar with this problem? Could I have a path set up incorrectly, and be using the wrong libraries? Running FreeBSD v5.1, installed from CD, including the developer tools. Single-boot system; there is no Microsoft software anywhere on the machine, so it's not their fault (for a change). ;-) -- __ Vince Sabio [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: math.h doesn't include pow?
** Sometime around 13:03 -0600 11/08/2004, Peter Seebach sent everyone: In message [EMAIL PROTECTED], Vince Sabio writes: In function `[function name]': [path/]datetime.c:668: undefined reference to `pow' Yes, I'm including math.h. If I compile the exact same code under Darwin (BSD on PowerPC), it compiles fine. It also compiles in CodeWarrior. Is anyone else familiar with this problem? Could I have a path set up incorrectly, and be using the wrong libraries? FAQ. Very FAQ. I thought it must have been, so I searched my list archives -- which, admittedly, go back only to January of this year -- but didn't find anything on this problem. If there's a formal FreeBSD FAQ, I'd be happy to be clue-batted with it FFR. Headers and libraries are distinct. Headers provide prototypes; libraries provide definitions. Yes, my bad; sorry about that: % sed 's/libraries/headers/' You want -lm. Ah! Yes, that did the trick. Muchas gracias, or however those wacky Irish spell it -- __ Vince Sabio [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
termcap problem
I have a relatively new installation of FreeBSD v5.1, and the machine has just been staged at my co-lo site. So far, everything works well, except for a minor vi problem: I cannot navigate using the arrow keys. I can navigate using control keys, but not via the arrow keys. I'm now accessing the server over ssh via a terminal window on a Mac laptop running OS X (a new distant relative of FreeBSD, FWIW). I access lots of machines this way, including a Solaris machine, a couple of Linux boxen, and at least one other FreeBSD machine (not mine), and I don't have this problem on any of them. I assume it's a termcap problem, but I don't know how to fix it. Any ideas? Note: As nice as some of the other editors are, I'm really rather attached to vi, and have been so ever since I got my first abacus. ;-) -- __ Vince Sabio [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: termcap problem
** Sometime around 03:51 + 02/09/2004, Jez Hancock said: On Sun, Feb 08, 2004 at 10:35:59PM -0500, Vince Sabio wrote: I have a relatively new installation of FreeBSD v5.1, and the machine has just been staged at my co-lo site. So far, everything works well, except for a minor vi problem: I cannot navigate using the arrow keys. I can navigate using control keys, but not via the arrow keys. I'm now accessing the server over ssh via a terminal window on a Mac laptop running OS X (a new distant relative of FreeBSD, FWIW). I access lots of machines this way, including a Solaris machine, a couple of Linux boxen, and at least one other FreeBSD machine (not mine), and I don't have this problem on any of them. I assume it's a termcap problem, but I don't know how to fix it. Any ideas? Have you tried setting the TERM env variable to 'xterm' or 'xterm-color' in your .cshrc file (or the rc file for the shell you use)? That did it -- thanks! (TERM=xterm-color; export TERM) in ~/.profile. -- __ Vince Sabio [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Cannot Add User
I just installed a v5.1 single-boot system from CD. So far, the only changes I've made from the initial installation were to configure sshd, set the system security level to moderate (from high), and set the system clock; other than that, it's a clean installation. I'm now trying to install Postfix, and the problem I'm running into is that I cannot create new user accounts. I created several user accounts during installation, and they seem to be fine. But when I [manually] create entries in /etc/passwd, master.passwd, and group, the entries are 'ignored' -- e.g., a chown [newuser] [filename] command fails, attempts to su from root into the user account fail, etc. When I try to create the user via adduser (using the standard defaults), the account creation step fails with the following error: pw: user '[newuser]' disappeared during update Again, attempts to 'access' the user (i.e., chmod, etc.) will fail. Interestingly, though, if I try to re-create the user, adduser tells me that the user already exists -- and a check of the relevant files confirms that the entries are there. I've looked around for a solution to this problem, but haven't found one, so here I am. FYI, the system security level was set to high during installation, and was then reset to moderate after installation, as this system is intended to be used as a server (and high was too restrictive; I couldn't even [find a way to] set the system time correctly). Appreciate the assistance -- __ Vince Sabio [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cannot Add User
** Sometime around 09:21 -0500 02/04/2004, Lowell Gilbert sent everyone: Vince Sabio [EMAIL PROTECTED] writes: [...] I'm now trying to install Postfix, and the problem I'm running into is that I cannot create new user accounts. I created several user accounts during installation, and they seem to be fine. But when I [manually] create entries in /etc/passwd, master.passwd, and group, the entries are 'ignored' -- e.g., a chown [newuser] [filename] command fails, attempts to su from root into the user account fail, etc. When I try to create the user via adduser (using the standard defaults), the account creation step fails with the following error: pw: user '[newuser]' disappeared during update It sounds like you've messed up your user database. Try running pwd_mkdb(8) by hand to get it straightened out. In future, remember not to edit passwd and so forth by hand; stick with adduser(8) and/or vipw(8) to avoid shooting yourself in the foot like this. I have to wonder if this is unique to the BSDs; I've been using Solaris for nearly a decade now, and the _only_ way I've ever created user accounts is manually -- by editing /etc/passwd, shadow, and group files, creating user directories, etc. I've never had a problem with it before. (I'm pretty sure I've done the same under Linux, too.) Running adduser is fine for simple user accounts -- but there are few user accounts on a typical server. The problem with adduser is that it isn't well suited to things like accounts with no home directories or login shells, disabled passwords (not the same as a locked account), etc. Either way, I tried running pwd_mkdb -C /etc/passwd, and it reported a format error on line 3 -- which happens to be the root account, and is the first real data line in the file. Moreover, it's a line that I didn't modify. It reported no errors on /etc/master.passwd, so I copied and modified it into a passwd file -- and pwd_mkdb then reported no errors on the new passwd file. However, that action also prevented any new logins, and running passwd didn't fix the problem. So, after mucking around with pwd_mkdb for a while, I opted to simply reinstall the OS -- it was still a rather new installation, and I wanted to increase the /usr partition, anyway. After completing the new FreeBSD installation, the first thing I did upon logging in was run pwd_mkdb on /etc/passwd, and it still reported a format error on line 3. I then manually added the necessary users, and this time the postfix installation ran to completion. While it's possible that I messed up the format on the original try, it's unlikely -- I checked it over a dozen times before going in search of a FreeBSD list on which to ask the question. I'm thinking that there might have been something else in the mix. But either way, the clean install fixed it (though admittedly it was a rather Draconian fix). -- __ Vince Sabio [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
