Am I Missing A Compat Library?
I just ran pkg_libchk and got this: avahi-app-0.6.29: /usr/local/lib/libavahi-glib.so.1 misses libicui18n.so.46 As I've never seen this before, I'm unclear on what to do to remmediate. Ideas? -- Tim Daneliuk tun...@tundraware.com ___ 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: Am I Missing A Compat Library?
On 7/18/2011 11:23 AM, Roland Smith said this:
On Mon, Jul 18, 2011 at 10:11:28AM -0500, Tim Daneliuk wrote:
I just ran pkg_libchk and got this:
avahi-app-0.6.29: /usr/local/lib/libavahi-glib.so.1 misses libicui18n.so.46
As I've never seen this before, I'm unclear on what to do to remmediate.
Have you updated your ports recently? The ICU port was updated to version 4.8
Yes.
recently, which provides libicui18n.so.48, and replaced libicui18n.so.46. As
noted in /usr/ports/UPDATING, all ports that depend on ICU should be updated.
I did this (and what a joy THAT was ;)
For some unknown reason this dependency was not resolved when you updated your
ports.
Apparently.
Recompile the avahi-app port and it should link with the newer version and
work fine again.
The compilation is blowing out (that might explain the observed problem).
That is, the port does not build properly - apparently there is some
syntax problem in the code:
/usr/include/machine/endian.h:107: syntax error, unexpected '{' in ' return
(__extension__ ({ register __uint32_t __X = (_x); __asm (bswap %0 : +r
(__X)); __X; }));' at '{'
/usr/include/machine/endian.h:107: syntax error, unexpected ';' in ' return
(__extension__ ({ register __uint32_t __X = (_x); __asm (bswap %0 : +r
(__X)); __X; }));' at ';'
/libexec/ld-elf.so.1: Shared object libicui18n.so.46 not found, required by
libavahi-glib.so.1
Command
'['/usr1/ports/net/avahi-app/work/avahi-0.6.29/avahi-gobject/tmp-introspectop_Yoq/Avahi-0.6',
'--introspect-dump=/usr1/ports/net/avahi-app/work/avahi-0.6.29/avahi-gobject/tmp-introspectop_Yoq/types.txt,/usr1/ports/net/avahi-app/work/avahi-0.6.29/avahi-gobject/tmp-introspectop_Yoq/dump.xml']'
returned non-zero exit status 1
gmake[3]: *** [Avahi-0.6.gir] Error 1
gmake[3]: Leaving directory
`/usr1/ports/net/avahi-app/work/avahi-0.6.29/avahi-gobject'
gmake[2]: *** [all] Error 2
gmake[2]: Leaving directory
`/usr1/ports/net/avahi-app/work/avahi-0.6.29/avahi-gobject'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/usr1/ports/net/avahi-app/work/avahi-0.6.29'
gmake: *** [all] Error 2
*** Error code 1
Roland
--
Tim Daneliuk
tun...@tundraware.com
___
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: Am I Missing A Compat Library?
On 7/18/2011 12:43 PM, Roland Smith said this:
But I _don't_ get this linker error. Just a thought, but have a look at glib
and dbus, and check that it is linked to the right libicu? ('ldd
/usr/local/lib/libglib-2.0.so.0' and 'ldd /usr/local/lib/libdbus-glib-1.so.2')
If that is not the case, you'll have to dive into the configure output, I
think.
Roland
A forced deinstallation of avahi-app and then an installation, seems
to have made the problem disappear.
So much for dynamically liked libraries will make systems maintenance
simpler ...
Tim Daneliuk
tun...@tundraware.com
___
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: Am I Missing A Compat Library?
On 7/18/2011 3:15 PM, Roland Smith said this:
On Mon, Jul 18, 2011 at 01:02:53PM -0500, Tim Daneliuk wrote:
On 7/18/2011 12:43 PM, Roland Smith said this:
But I _don't_ get this linker error. Just a thought, but have a look at glib
and dbus, and check that it is linked to the right libicu? ('ldd
/usr/local/lib/libglib-2.0.so.0' and 'ldd
/usr/local/lib/libdbus-glib-1.so.2')
If that is not the case, you'll have to dive into the configure output, I
think.
Roland
A forced deinstallation of avahi-app and then an installation, seems
to have made the problem disappear.
I've seen that problem before. Sometimes an app will link to the previously
installed versions of its libraries rather than the freshly built ones. Do you
by any chance have the environment variable LIBRARY_PATH set to
/usr/local/lib? I've long suspected that or the -L option to gcc to be the
culprit.
Nope.
So much for dynamically linked libraries will make systems maintenance
simpler ...
Static linking does indeed have some advantages. :-) Of course there is still
the option WITHOUT_DYNAMICROOT in /etc/src.conf to build /bin and /sbin
without dynamic linking... Haven't tried it in years, though.
Disk space is cheap. Time wasted fixing silly problems is irreplacable.
--
Tim Daneliuk
tun...@tundraware.com
___
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: Perl Problem After Upgrade to 5.12.4
On 7/8/2011 6:52 AM, Jerry said this: On Fri, 08 Jul 2011 13:00:24 +0200 SoCruel.NU FreeBSD Questions Mailbox articulated: On Wed, 06 Jul 2011 10:01:21 -0500, Tim Daneliuk wrote: Ideas anyone? I am trying to rebuild SpamAssassin after a perl upgrade to 5.12.4 and get this (I DID run perl-after-upgrade prior to this): === p5-Encode-Detect-1.01 depends on file: /usr/local/lib/perl5/site_perl/5.12.4/Module/Build.pm - not found ===Verifying install for /usr/local/lib/perl5/site_perl/5.12.4/Module/Build.pm in /usr/ports/devel/p5-Module-Build === License check disabled, port has not defined LICENSE === Extracting for p5-Module-Build-0.3800_1 = SHA256 Checksum OK for Module-Build-0.3800.tar.gz. === p5-Module-Build-0.3800_1 depends on file: /usr/local/bin/perl5.12.4 - found === Patching for p5-Module-Build-0.3800_1 === p5-Module-Build-0.3800_1 depends on file: /usr/local/bin/perl5.12.4 - found === p5-Module-Build-0.3800_1 depends on package: p5-CPAN-Meta=2.110420 - found === p5-Module-Build-0.3800_1 depends on package: p5-Module-Metadata=1.02 - found === p5-Module-Build-0.3800_1 depends on package: p5-Parse-CPAN-Meta=1.44.01 - found === p5-Module-Build-0.3800_1 depends on package: p5-Perl-OSType=1.000 - found === p5-Module-Build-0.3800_1 depends on package: p5-version=0.87 - found === p5-Module-Build-0.3800_1 depends on file: /usr/local/bin/perl5.12.4 - found === Configuring for p5-Module-Build-0.3800_1 *** BOOTSTRAPPING Perl::OSType *** *** BOOTSTRAPPING version *** *** BOOTSTRAPPING Module::Metadata *** Checking prerequisites... requires: ! CPAN::Meta is not installed build_requires: ! Parse::CPAN::Meta (1.40) is installed, but we need version = 1.4401 ERRORS/WARNINGS FOUND IN PREREQUISITES. You may wish to install the versions of the modules indicated above before proceeding with this installation Could not create MYMETA files Creating new 'Build' script for 'Module-Build' version '0.3800' Copied META.yml to MYMETA.yml for bootstrapping These additional prerequisites must be installed: requires: ! Perl::OSType (we need version 1.00) ! version (we need version 0.87) ! Module::Metadata (we need version 1.02) === Building for p5-Module-Build-0.3800_1 Can't locate Perl/OSType.pm in @INC (@INC contains: t/lib t/bundled lib /usr/local/lib/perl5/5.12.4/BSDPAN /usr/local/lib/perl5/site_perl/5.12.4/mach /usr/local/lib/perl5/site_perl/5.12.4 /usr/local/lib/perl5/5.12.4/mach /usr/local/lib/perl5/5.12.4 .) at lib/Module/Build.pm line 13. BEGIN failed--compilation aborted at lib/Module/Build.pm line 13. Compilation failed in require at Build line 42. BEGIN failed--compilation aborted at Build line 42. *** Error code 2 Stop in /usr1/ports/devel/p5-Module-Build. *** Error code 1 Stop in /usr1/ports/converters/p5-Encode-Detect. *** Error code 1 Stop in /usr1/ports/mail/p5-Mail-SpamAssassin. *** Error code 1 Stop in /usr1/ports/mail/p5-Mail-SpamAssassi Hello Tim, list, I have the same problem on one of my boxes. Cannot upgrade p5-Module-Build-0.3800 port because of this. Has anyone filed a PR against this problem? I was able to work around this by: 1) Uninstalling spamassassin and perl 5.12 2) Upgrading to perl 5.14 3) Running perl-after-upgrade 4) Reinstalling spamassassin I still cannot build remmina. There seems to be some hocus pocus having to do with missing dependent perl XML parser libs. Sigh. I can't wait until the planet either: a) Migrates 100% to python or b) Learns to do batteries included packaging like python. -- Tim Daneliuk tun...@tundraware.com ___ 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: Perl Problem After Upgrade to 5.12.4
On 7/8/2011 8:39 AM, Jerry said this: On Fri, 08 Jul 2011 08:12:16 -0500 Tim Daneliuk articulated: I was able to work around this by: 1) Uninstalling spamassassin and perl 5.12 2) Upgrading to perl 5.14 3) Running perl-after-upgrade 4) Reinstalling spamassassin That is not exactly the method prescribed in UPDATING: You're right, of course - I ordinarily do this when I upgrade perl ... somehow it slipped my tiny and aging mind. Thanks for the reminder :) quote 20110517: AFFECTS: users of lang/perl* AUTHOR: s...@freebsd.org lang/perl5.14 is out. If you want to switch to it from, for example lang/perl5.12, that is: Portupgrade users: 0) Fix pkgdb.db (for safety): pkgdb -Ff 1) Reinstall new version of Perl (5.14): env DISABLE_CONFLICTS=1 portupgrade -o lang/perl5.14 -f perl-5.12.\* 2) Reinstall everything that depends on Perl: portupgrade -fr perl Portmaster users: portmaster -o lang/perl5.14 lang/perl5.12 Conservative: portmaster p5- Comprehensive (but perhaps overkill): portmaster -r perl- Note: If the perl- glob matches more than one port you will need to specify the name of the Perl directory in /var/db/pkg explicitly. /quote I used the portupgrade method without incident. From what I have been told, perl-after-upgrade != env DISABLE_CONFLICTS=1 portupgrade -o lang/perl5.14 -f perl-5.12.\* As always, YMMV! -- Tim Daneliuk tun...@tundraware.com ___ 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
Perl Problem After Upgrade to 5.12.4
Ideas anyone? I am trying to rebuild SpamAssassin after a perl upgrade to 5.12.4 and get this (I DID run perl-after-upgrade prior to this): === p5-Encode-Detect-1.01 depends on file: /usr/local/lib/perl5/site_perl/5.12.4/Module/Build.pm - not found ===Verifying install for /usr/local/lib/perl5/site_perl/5.12.4/Module/Build.pm in /usr/ports/devel/p5-Module-Build === License check disabled, port has not defined LICENSE === Extracting for p5-Module-Build-0.3800_1 = SHA256 Checksum OK for Module-Build-0.3800.tar.gz. === p5-Module-Build-0.3800_1 depends on file: /usr/local/bin/perl5.12.4 - found === Patching for p5-Module-Build-0.3800_1 === p5-Module-Build-0.3800_1 depends on file: /usr/local/bin/perl5.12.4 - found === p5-Module-Build-0.3800_1 depends on package: p5-CPAN-Meta=2.110420 - found === p5-Module-Build-0.3800_1 depends on package: p5-Module-Metadata=1.02 - found === p5-Module-Build-0.3800_1 depends on package: p5-Parse-CPAN-Meta=1.44.01 - found === p5-Module-Build-0.3800_1 depends on package: p5-Perl-OSType=1.000 - found === p5-Module-Build-0.3800_1 depends on package: p5-version=0.87 - found === p5-Module-Build-0.3800_1 depends on file: /usr/local/bin/perl5.12.4 - found === Configuring for p5-Module-Build-0.3800_1 *** BOOTSTRAPPING Perl::OSType *** *** BOOTSTRAPPING version *** *** BOOTSTRAPPING Module::Metadata *** Checking prerequisites... requires: ! CPAN::Meta is not installed build_requires: ! Parse::CPAN::Meta (1.40) is installed, but we need version = 1.4401 ERRORS/WARNINGS FOUND IN PREREQUISITES. You may wish to install the versions of the modules indicated above before proceeding with this installation Could not create MYMETA files Creating new 'Build' script for 'Module-Build' version '0.3800' Copied META.yml to MYMETA.yml for bootstrapping These additional prerequisites must be installed: requires: ! Perl::OSType (we need version 1.00) ! version (we need version 0.87) ! Module::Metadata (we need version 1.02) === Building for p5-Module-Build-0.3800_1 Can't locate Perl/OSType.pm in @INC (@INC contains: t/lib t/bundled lib /usr/local/lib/perl5/5.12.4/BSDPAN /usr/local/lib/perl5/site_perl/5.12.4/mach /usr/local/lib/perl5/site_perl/5.12.4 /usr/local/lib/perl5/5.12.4/mach /usr/local/lib/perl5/5.12.4 .) at lib/Module/Build.pm line 13. BEGIN failed--compilation aborted at lib/Module/Build.pm line 13. Compilation failed in require at Build line 42. BEGIN failed--compilation aborted at Build line 42. *** Error code 2 Stop in /usr1/ports/devel/p5-Module-Build. *** Error code 1 Stop in /usr1/ports/converters/p5-Encode-Detect. *** Error code 1 Stop in /usr1/ports/mail/p5-Mail-SpamAssassin. *** Error code 1 Stop in /usr1/ports/mail/p5-Mail-SpamAssassi -- Tim Daneliuk tun...@tundraware.com ___ 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
Trying To Do A portupgrade On 8-Stable
... and the gstreamer upgrade blows up because of this: /usr/local/bin/g-ir-scanner: not found Ideas? -- Tim Daneliuk tun...@tundraware.com ___ 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: Trying To Do A portupgrade On 8-Stable
On 6/28/2011 2:46 PM, Frank Shute said this: On Tue, Jun 28, 2011 at 01:37:22PM -0500, Tim Daneliuk wrote: ... and the gstreamer upgrade blows up because of this: /usr/local/bin/g-ir-scanner: not found Ideas? On my machine: $ pkg_info -W /usr/local/bin/g-ir-scanner /usr/local/bin/g-ir-scanner was installed by package gobject-introspection-0.9.12_1 So I suggest you do: # portupgrade -fv gobject-introspection Regards, That did it, thanks! -- Tim Daneliuk tun...@tundraware.com ___ 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
Slightly OT: Hardware For FreeNAS
Slightly OT, but since it's based on FreeBSD, I thought I'd start here... Can anyone recommend a good hardware platform (components) around which to build a FreeNAS server? The important non-functional requirements are: 1) Quiet to the point of silent. 2) Reliable/redundant TIA, -- Tim Daneliuk tun...@tundraware.com ___ 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
Emacs Throwing Errors On X
Some time ago, emacs started doing this on startup under X: (emacs:65141): GLib-WARNING **: In call to g_spawn_sync(), exit status of a child process was requested but SIGCHLD action was set to SIG_IGN and ECHILD was received by waitpid(), so exit status can't be returned. This is a bug in the program calling g_spawn_sync(); either don't request the exit status, or don't set the SIGCHLD action. GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Command line `dbus-launch --autolaunch=cd85f2237549bffeda2c670600026934 --binary-syntax --close-stderr' exited with non-zero exit status 2655224: ) (emacs:65141): GLib-WARNING **: In call to g_spawn_sync(), exit status of a child process was requested but SIGCHLD action was set to SIG_IGN and ECHILD was received by waitpid(), so exit status can't be returned. This is a bug in the program calling g_spawn_sync(); either don't request the exit status, or don't set the SIGCHLD action. Other Relevant Info: FBSD 8.2-STABLE (But it happened prior to this release as well) emacs-23.2_4,2 gconf2-2.32.0_2 -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: FreeBSD Decision
On 1/14/2011 12:46 PM, Alessandro Baggi wrote: Hi list, I don't want make a flame post but I would ask an objective opinion, then not a camp opinion, about using FreeBSD or Debian Linux in a production environment for solution as such as cluster of some service, proxy, SAN, performance, smp with an high number of cpu, PDC, Mail Server (qmail), raid software, security support and hardware support. I'm using Slackware Linux but in production environment there are problem with packages and distro update and other support. Then for you, what is the best for those solutions? thanks in advance I work/consult in very large data center environments ( 1000 servers in production is common, and more for dev/test/stage). What you are asking has no simple answer (that why we consultants get paid what we do :) Both Linux and FreeBSD can do the things you ask, but there are larger environmental questions to be answered: 1) What OSs does the hardware vendor formally support? 2) What OSs do the 3rd party commercial applications vendors you use support? 3) Is your networking/HBA hardware supported by the OS? 4) What kind of third party system management and monitoring tools have to be in place? Are they supported on the target OS? 5) Do you need special or emergent capabilities like FCOE and does your target OS support them? 5) Can you get consulting services and/or outside support for your OS? IOW, your selection has less to do with the OS kernel and more to do with the set of tools, applications, and hardware that surround the OS. If all things are equal, I prefer FreeBSD because it has a smaller footprint on the hardware and is easier to install/maintain than Linux. However, whether we like it or not, there is far more commercial and third party support for *some* linux distros (RHEL and SLES). Given what you've told us, if it really does come down to Debian or FreeBSD, it sounds like you don't need much in the way of third party stuff. In that case, I'd use FreeBSD. -- Tim Daneliuk tun...@tundraware.com ___ 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: Simple command to reset / clear all logs?
On 1/13/2011 2:56 PM, Robert Bonomi wrote: Date: Wed, 12 Jan 2011 20:58:04 +0100 From: Polytropon free...@edvax.de Subject: Re: Simple command to reset / clear all logs? On Wed, 12 Jan 2011 20:50:04 +0100, Redd Vinylene reddvinyl...@gmail.com wrote: Will the logs automatically create themselves? Usually not, but it depends on the logging mechanism. If a program continuously re-opens the file (after closing it) in APPEND mode, it should be created if non-existent. But if the program keeps the file open and just writes to it, it can cause trouble. Good programs check the return code of the writing operation and signal an error. Bad programs don't do that, they just keep writing to nowhere. :-) _syslogd_ *explicitly* does -not- _create_ any log files. it is documented in the manpages that it behaves that way. Whether or not this is a good idea is debatable, but it does allow you to suppress some logging w/o having to edit the syslog.conf file and/or re-start syslogd. I mean, I picture I have to manually touch a lotta them in order to avoid cannot find error messages? Syslog does -not- give any such messages, it just doesn't write the message anywere. It's worth noting that if you delete an open file, any programs with open write handles to the file can still write to it and thus chew up disk space. So ... you can't just reach in and delete log files unless you're sure nothing has them open. -- Tim Daneliuk tun...@tundraware.com ___ 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: autoconf and automake
On 12/9/2010 12:54 PM, Steven Friedrich wrote: I'm having trouble with the latest advice in ports/UPDATING: 20101208: AFFECTS: autotools AUTHOR: autoto...@freebsd.org Here's how I did it: 1) Delete all the existing ports manually: pkg_delete -f portname 2) Install the new port manually: cd /usr/ports/devel/portname make install clean When you've done them all, then ... 3) Fix the package database: pkgdb -L pkgdb -Fa Tim Daneliuk tun...@tundraware.com ___ 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: More On Samba And Softupdates
On 11/21/2010 2:16 PM, Adam Vande More wrote: On Sun, Nov 21, 2010 at 10:56 AM, Tim Daneliuk tun...@tundraware.com mailto:tun...@tundraware.com wrote: This drive is being used as a backup drive for all the workstations on this particular network, and reliable is much more important than slightly faster. As someone already said, SU is probably not the culprit here. I've used Samba + SU for a long time with no such problems although I have no current setups to verify. SU substantially increases disk IO, it's not 'slightly faster' it's much faster. The error you see is probably the result of flaky drive or controller as the additional IO provided by SU allows the flakiness to show through. Although from what you describe my choice for the drive would be gjournal + UFS. If you've got a lot of asynchronous IO that's a better solution. It looks like this may have been a loose cable. After reseating the cable and reinitializing the drive, it seems to be fine. I turned on softupdates and all seems well ... Thanks for responding... -- Tim Daneliuk tun...@tundraware.com ___ 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
More On Samba And Softupdates
The other day I mentioned I had a problem with a Samba-shared drive that was just installed blowing up. When I rebuilt it, I forgot to enable softupdates but the drive seems to be working flawlessly. I understand it is possible to do this after-the-fact with tunefs. Some questions: Do I have to unmount the drive to do it? What benefit will I get if I turn on softupdates? This drive is being used as a backup drive for all the workstations on this particular network, and reliable is much more important than slightly faster. -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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
Softupdates And Samba
I installed another SATA drive on a FreeBSD 8.1-STABLE box here last night. After the disk prep, I mounted it and then shared the whole drive via Samba. This morning when I came in, the machine had horked all over itself and I saw this in the log after the reboot: Nov 20 01:06:59 ozzie kernel: ad6: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=34066054 3 Nov 20 01:06:59 ozzie kernel: ad6: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=10 NID_NOT_FOUND LBA=340660543 Nov 20 01:06:59 ozzie kernel: g_vfs_done():ad6s1d[WRITE(offset=174418165760, length=131072)]e rror = 5 Nov 20 02:15:07 ozzie kernel: ad6: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=14580695 35 Nov 20 02:15:07 ozzie kernel: ad6: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=10 NID_NOT_FOUND LBA=1458069535 Nov 20 02:15:07 ozzie kernel: g_vfs_done():ad6s1d[WRITE(offset=746531569664, length=131072)]e rror = 5 I reformatted and remounted the drive and accidentally forgot to enable softupdates. It seems to now be working fine. Is there a known interaction with softupdates and Samba such that I should not use them in this case, or could this just have been a loose cable or something? The drive is pretty new ( 6mo) and it's never been a problem when I used it on an NTFS system previously. TIA, -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: Newer Sambas and PAM
On 11/1/2010 6:34 AM, Andrea Venturoli wrote: Hello. I'd like to have every service on my systems authenticating via Samba (through PAM). With older, now deprecated, 3.0.x version, I did this through security/pam_smb: no problems at all. Since 3.0 was removed, I tried upgrading to 3.4 on one box: since then I am not able to authenticate anything through PAM against it. Is anyone doing this? How? bye Thanks av. ___ 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 Be aware that the samba password directory moved from /usr/local/etc/samba to /usr/local/etc/samba34 -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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
Sendmail Question: Smart Host Round-Robin In Mailertable?
A bit OT, but I'm hoping one of you resident geniuses can point me to an answer I have a situation where I need to set up round-robin across several smart hosts in the sendmail mailertable for all traffic. (For a variety of reasons, the client does not want this done in either the .mc file or directly in the .cf file.) Can some kind soul point me to a resource that explains the syntax for doing this? Thanks, -- Tim Daneliuk tun...@tundraware.com ___ 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: Sendmail Question: Smart Host Round-Robin In Mailertable?
On 10/27/2010 3:26 PM, Giorgos Keramidas wrote: On Wed, 27 Oct 2010 09:51:59 -0500, Tim Daneliuk tun...@tundraware.com wrote: A bit OT, but I'm hoping one of you resident geniuses can point me to an answer I have a situation where I need to set up round-robin across several smart hosts in the sendmail mailertable for all traffic. (For a variety of reasons, the client does not want this done in either the .mc file or directly in the .cf file.) Can some kind soul point me to a resource that explains the syntax for doing this? Maybe a DNS-based round robin solution would suffice? DNS cannot be changed for a variety of reasons... -- Tim Daneliuk tun...@tundraware.com ___ 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: Greybeards (Re: Netbooks BSD)
On 10/20/2010 11:55 AM, Gary Kline wrote: On Wed, Oct 20, 2010 at 12:47:38AM -0700, per...@pluto.rain.com wrote: Matthias Apitz g...@unixarea.de wrote: El d?a Tuesday, October 19, 2010 a las 07:29:46PM -0700, Gary Kline escribi?: PS: I really _was_ current on hardware stuff. Back in the VAX 780 days :-) I booted my first UNIX V7 tape on a PDP-11 around 1982, I think. Gotcha beat :) UNIX V6, PDP-11/34, RK05 disk cartridge, 1975. The whole runtime fit on one RK05. The sources took a second one. I remember the 11/34 fondly. The whole EE department at Cory Hall was running one one; then when I interned at Livermore my job of porting the Portable F77 Compiler was done with vi and the source code that Stu Feldman wrote. I love[d] those bloody old computers, :-) Dunno why. Maybe because they really *were* about computing. Not streaming [[whatever]] or having php running. (Blah^9^9^9) :) Heck, when I started out, they didn't even have zeros and ones yet. We had to settle for os and ls ... -- Tim Daneliuk tun...@tundraware.com ___ 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: Effective FreeBSD installation on several servers
On 8/29/2010 10:21 AM, Mikhail wrote: Hello, I have three servers which I'm going to use for dynamips setup, so I basicly need only computing power of those machines. What would be the most effective way to install/upgrade FreeBSD on servers? I think about PXE booting through the network and mounting /,/home over NFS - is it possible? Has anyone done such thing before? Or maybe there are more effective way for such installation? Be well. I wrote my own backup script to create file-level images which can then be used to populate a new installation. Process described at: http://www.tundraware.com/Software/tbku/Imaging-FreeBSD-With-tbku.html -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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 INDEX file
On 7/22/2010 8:20 PM, Fbsd8 wrote: I have a pristine install of 8.0. There is no /usr/ports directory yet. I am trying to use the portcheckout port and the porteasy port to just populate the ports tree with only the ports I use. Problem is in both cases the above ports require an existing INDEX file to process and since I have none they don't work. How can I just download the ports INDEX file? Portsnap is not a solution. ___ 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 You can use 'csup' to get the ports tree down. You'll find the relevant config file (assuming you installed the source tree) at: /usr/src/share/examples/cvsup -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: Global backup solution for FBSD Ubuntu
On 7/4/2010 4:43 PM, bsd wrote: Hello, I am trying to build a global backup solution for couple of strategic servers (7) based on two operating systems : - FreeBSD (6 - 7 // soon 7 - 8) - Ubuntu 8.04 LTS These servers are hosting some strategic components mainly related to DNS infrastructure and databases. For the moment I am backing up these server using network based backup solution: - A duplicity based solution which backs up key directories in my infrastructure on a remote FTP server provided by my hosting company. - A dump of some key components which I am doing on regular basis for FreeBSD servers. - Duplicity is also used for the Ubuntu servers. - Databases are replicated live on a remote server using slony for the most strategic ones (Postgres DB) and using mysql dump export for MySQL. • I am not a 100% sure these solutions will allow me to restart rapidly from a crash, specially for Ubuntu servers. • I would like to know which solution(s) you have deployed at what cost for what results ? I am actually considering couple of different solutions - SAIT solution and backula. - Disk based solution (maybe also with backula). … I have couple of servers that will reach their end of life that could be recycled as backup solution at a very convenient price… Thanks for you help. Gregober --- PGP ID -- 0x1BA3C2FD bsd @at@ todoo.biz Followup FYI: http://www.mondorescue.org/ -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: Getting kernel trap 12 During Boot Of 8.1-PRERELEASE
On 7/4/2010 10:32 AM, Lowell Gilbert wrote: Tim Daneliuk tun...@tundraware.com writes: I've seen this twice now - once last Sunday, and once again today when I tried to do a build/installworld/kernel with daily sources from the master tree: http://www.mediafire.com/imageview.php?quickkey=qmhizdtnhyothumb=4 That asked me to jump through too many hoops over multiple domains, so I didn't actually see it. I'll assume it's just more information on the error in your subject line. I'm not sure what you mean. It should take you to a screenshot of the problem. What does too many hoops mean in this context? The system boots fine single-user, so I don't suspect the base kernel functionality. Maybe. What you should do is install the kernel *before* the userland. If you already did that, then make sure youtry with a GENERIC kernel. I did exactly that, though I did not try the GENERIC kernel. My conf looks like this: include GENERIC ident MACHINENAME options IPFIREWALL options IPDIVERT options VESA # System console options options SC_DISABLE_REBOOT # disable reboot key sequence options SC_HISTORY_SIZE=200 # number of history buffer lines options SC_PIXEL_MODE # add support for the raster text mode # The following options will change the default colors of syscons. options SC_NORM_ATTR=(FG_GREEN|BG_BLACK) options SC_NORM_REV_ATTR=(FG_YELLOW|BG_GREEN) options SC_KERNEL_CONS_ATTR=(FG_RED|BG_BLACK) options SC_KERNEL_CONS_REV_ATTR=(FG_BLACK|BG_RED) Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: Global backup solution for FBSD Ubuntu
On 07/04/10 16:43, bsd wrote: Hello, I am trying to build a global backup solution for couple of strategic servers (7) based on two operating systems : - FreeBSD (6 - 7 // soon 7 - 8) - Ubuntu 8.04 LTS These servers are hosting some strategic components mainly related to DNS infrastructure and databases. For the moment I am backing up these server using network based backup solution: - A duplicity based solution which backs up key directories in my infrastructure on a remote FTP server provided by my hosting company. - A dump of some key components which I am doing on regular basis for FreeBSD servers. - Duplicity is also used for the Ubuntu servers. - Databases are replicated live on a remote server using slony for the most strategic ones (Postgres DB) and using mysql dump export for MySQL. • I am not a 100% sure these solutions will allow me to restart rapidly from a crash, specially for Ubuntu servers. • I would like to know which solution(s) you have deployed at what cost for what results ? I am actually considering couple of different solutions - SAIT solution and backula. - Disk based solution (maybe also with backula). … I have couple of servers that will reach their end of life that could be recycled as backup solution at a very convenient price… I wrote a simple shell-based solution for this problem some time ago. It (and FreeBSD instructions) can be found: http://www.tundraware.com/Software/tbku/ I am able to recover a production server (DNS, dhcp, http, sendmail, etc...) in under 30 minutes using this technique. ___ 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
'file' Command Giving False Positives
I have a data file with the content: LZasdadqjwjqwjqwjeqwe 'file' (incorrectly) reports this as an MS-DOS executable. Does anyone happen to know the proper changes to 'magic' that would fix this? Thanks, -- Tim Daneliuk tun...@tundraware.com ___ 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: 'file' Command Giving False Positives
On 7/2/2010 10:35 AM, Polytropon wrote: On Fri, 02 Jul 2010 11:25:20 -0400, Lowell Gilbertfreebsd-questions-lo...@be-well.ilk.org wrote: Why is it incorrect? LZ as the first two bytes in a file is (unless my memory is badly mistaken) exactly what the old command.com looked for as the flag of an executable. If I ask *my* memory, it tells me that what you mean is MZ. As far as I remember, those are the initials of a programmer involved with the creation of the DOS binary executable format. :-) Some OSs report both LZ and MZ as being DOS .exe, some only report LZ. Either way, when processing data files, there needs to be a deeper check to avoid the false positive. It may be that 'file' just isn't powerful enough to do this. -- Tim Daneliuk tun...@tundraware.com ___ 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: 'file' Command Giving False Positives
On 7/2/2010 1:42 PM, Polytropon wrote: On Fri, 02 Jul 2010 14:23:24 -0400, Lowell Gilbertfreebsd-questions-lo...@be-well.ilk.org wrote: Apparently, your memory is better than mine, because that was indeed what I was thinking of. Which leads to the question of why magic(5) lists LZ as representing MS-DOS executable (built-in). I'd be hesitant to change that unless we knew for sure it was wrong. As it has been mentioned before, .EXE is *one* of the formats executable in DOS. .COM executables do not have specific headers (as they are loaded directly). Also, .BAT are executable, allthough they are text files, and finally .BTM are also text file executables, specific to NDOS. As far as I also remember, there's .EXE on OS/2, too. One could argue if Windows .PIF are also executables. Of course, VMS also has .COM... but I see I'm making a digression... :-) Even if it _is_ wrong, the problem still remains for MZ at least: Any file starting with those letters is going to be identified as an MS-DOS executable, and there's no clear way to distinguish it from a text file that happens to start with those letters. Well, there's a solution that is not *that* complicated: If the file contains characters that don't match isprint(), i. e. those outside the ASCII set used in real text files, it's likely to be an executable. A scriptable solution might be to difffilename vs. `strings filename`. If they differ, it's not a text, so it might be an executable. I'm not sure if the magic identification string starting with MZ could be enlarged with other specific characters immediately following MZ that are *only* present in executables... The problem is that MZ itself is completely sufficient: % echo MZ foo % file foo foo: MS-DOS executable Of course, that's not correct. All noted (and appreciated). In this case, the client has a situation where none of the above will work: They can take in encrypted files that happen to have an MZ/LZ at the beginning but have binary data thereafter but are NOT executables. They want to properly flag executables but not get false positives. At this point, I'm inclined to believe that 'file' alone is insufficient to do this and, at best - even with more tools - it's going to be a probabilities game - i.e. What percentage of false positives is acceptable? -- Tim Daneliuk tun...@tundraware.com ___ 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
Getting kernel trap 12 During Boot Of 8.1-PRERELEASE
I've seen this twice now - once last Sunday, and once again today when I tried to do a build/installworld/kernel with daily sources from the master tree: http://www.mediafire.com/imageview.php?quickkey=qmhizdtnhyothumb=4 The system boots fine single-user, so I don't suspect the base kernel functionality. Falling back to my 6-18-2010 system image makes everything right again. MOBO is an Intel D946GZIS with a single SATA drive and one additional 3Com 3c905 NIC in addition to the onboard Intel NIC. Anyone else seeing this. Ideas? -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: Followup On Perl Dumping Core
On 6/18/2010 2:45 PM, Tim Daneliuk wrote: On 6/18/2010 2:33 PM, Greg Larkin wrote: Tim Daneliuk wrote: On 6/18/2010 2:09 PM, Matthew Seaman wrote: On 18/06/2010 19:56:26, Tim Daneliuk wrote: I should mention that I don't think it is actually dumping core. It's just reporting the problem in /var/log/messages... You'll only get a core file if the current working directory of the process is writable by the process. Normally. There are various sysctls you can use to affect core-dumping: kern.corefile: process corefile name format string kern.coredump: Enable/Disable coredumps kern.sugid_coredump: Enable coredumping set user/group ID processes See core(5). It is possible to set kern.corefile to an absolute path -- eg /tmp/%N.core -- to always record corefiles in a writable directory. Also, look at setrlimit values for the maximum size core file permitted. Cheers, Matthew Well ... I've figured out what's causing it, but I still don't know why. This is caused when '/usr/local/etc/rc.d/mailscanner restart' is issued from a script I run to reset the mail system. However, it does not happen every time ... go figure. Hi Tim, I apologize if you mentioned this before, but are you using Spamassassin with mailscanner? This message describes a problem that sounds very similar to yours, and there's a solution included: http://old.nabble.com/Re%3A-amavisd---exited-on-signal-11---FreeBSD-8-with-Perl-5.10-p28627858.html Hope that helps, Greg Aha! Der plot thickens. I am indeed running SA. I've just clobbered /root/.spamassassin/* This may well be the issue ... Many thanks. It would seem that this was the problem. Clearing out the old contents of .spamassassin made the perl SEGVs stop... -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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
Followup On Perl Dumping Core
I have rebuilt world to today's 8.1-PRERELEASE sources I have forced a rebuild of every port on the system with: portupgrade -f * I have rebooted. I am still seeing these log messages: (perl5.10.1), uid 0: exited on signal 11 The long running perl processes on this system are associated with MailScanner. MailScanner does periodically restart itself thereby killing these perl processes, but I wouldn't expect this to throw a signal 11... Ideas anyone? -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: Followup On Perl Dumping Core
On 6/18/2010 1:27 PM, Glen Barber wrote: Hi, On 6/18/10 2:24 PM, Tim Daneliuk wrote: I have rebuilt world to today's 8.1-PRERELEASE sources I have forced a rebuild of every port on the system with: portupgrade -f * I have rebooted. I am still seeing these log messages: (perl5.10.1), uid 0: exited on signal 11 The long running perl processes on this system are associated with MailScanner. MailScanner does periodically restart itself thereby killing these perl processes, but I wouldn't expect this to throw a signal 11... Ideas anyone? Have you recently upgraded perl without running perl-after-upgrade afterwards? I did upgrade perl some time ago. I do not recall if I ran perl-after-upgrade. Wouldn't the 'portupgrade -f *' take care of this, or should I go run the script now, just in case? Thanks, -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: Followup On Perl Dumping Core
On 6/18/2010 1:34 PM, Glen Barber wrote: On 6/18/10 2:30 PM, Tim Daneliuk wrote: Have you recently upgraded perl without running perl-after-upgrade afterwards? I did upgrade perl some time ago. I do not recall if I ran perl-after-upgrade. Wouldn't the 'portupgrade -f *' take care of this, or should I go run the script now, just in case? portupgrade does not do this for you. If you don't remember, I'd suggest running it. Regards, Well, I just did, and it reports no changes were necessary... -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: Followup On Perl Dumping Core
On 6/18/2010 1:52 PM, Tim Daneliuk wrote: On 6/18/2010 1:34 PM, Glen Barber wrote: On 6/18/10 2:30 PM, Tim Daneliuk wrote: Have you recently upgraded perl without running perl-after-upgrade afterwards? I did upgrade perl some time ago. I do not recall if I ran perl-after-upgrade. Wouldn't the 'portupgrade -f *' take care of this, or should I go run the script now, just in case? portupgrade does not do this for you. If you don't remember, I'd suggest running it. Regards, Well, I just did, and it reports no changes were necessary... I should mention that I don't think it is actually dumping core. It's just reporting the problem in /var/log/messages... -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: Followup On Perl Dumping Core
On 6/18/2010 2:09 PM, Matthew Seaman wrote: On 18/06/2010 19:56:26, Tim Daneliuk wrote: I should mention that I don't think it is actually dumping core. It's just reporting the problem in /var/log/messages... You'll only get a core file if the current working directory of the process is writable by the process. Normally. There are various sysctls you can use to affect core-dumping: kern.corefile: process corefile name format string kern.coredump: Enable/Disable coredumps kern.sugid_coredump: Enable coredumping set user/group ID processes See core(5). It is possible to set kern.corefile to an absolute path -- eg /tmp/%N.core -- to always record corefiles in a writable directory. Also, look at setrlimit values for the maximum size core file permitted. Cheers, Matthew Well ... I've figured out what's causing it, but I still don't know why. This is caused when '/usr/local/etc/rc.d/mailscanner restart' is issued from a script I run to reset the mail system. However, it does not happen every time ... go figure. --- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: Followup On Perl Dumping Core
On 6/18/2010 2:33 PM, Greg Larkin wrote: Tim Daneliuk wrote: On 6/18/2010 2:09 PM, Matthew Seaman wrote: On 18/06/2010 19:56:26, Tim Daneliuk wrote: I should mention that I don't think it is actually dumping core. It's just reporting the problem in /var/log/messages... You'll only get a core file if the current working directory of the process is writable by the process. Normally. There are various sysctls you can use to affect core-dumping: kern.corefile: process corefile name format string kern.coredump: Enable/Disable coredumps kern.sugid_coredump: Enable coredumping set user/group ID processes See core(5). It is possible to set kern.corefile to an absolute path -- eg /tmp/%N.core -- to always record corefiles in a writable directory. Also, look at setrlimit values for the maximum size core file permitted. Cheers, Matthew Well ... I've figured out what's causing it, but I still don't know why. This is caused when '/usr/local/etc/rc.d/mailscanner restart' is issued from a script I run to reset the mail system. However, it does not happen every time ... go figure. Hi Tim, I apologize if you mentioned this before, but are you using Spamassassin with mailscanner? This message describes a problem that sounds very similar to yours, and there's a solution included: http://old.nabble.com/Re%3A-amavisd---exited-on-signal-11---FreeBSD-8-with-Perl-5.10-p28627858.html Hope that helps, Greg Aha! Der plot thickens. I am indeed running SA. I've just clobbered /root/.spamassassin/* This may well be the issue ... Many thanks. Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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
Perl Dumping Core
I am running 8.1-PRERELEASE and seeing a half dozen of these a day: (perl5.10.1), uid 0: exited on signal 11 Anyone have theories on this? -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: Perl Dumping Core
On 6/16/2010 9:18 AM, Matthew Seaman wrote: On 16/06/2010 15:11:15, Tim Daneliuk wrote: I am running 8.1-PRERELEASE and seeing a half dozen of these a day: (perl5.10.1), uid 0: exited on signal 11 Anyone have theories on this? You have a perl process or processes owned by root that are dying due to segmentation violations. Unfortunately, we don't do omniscience[*] or clairvoyance or anything like that, so unless you give us some useful information to work with, that's literally all we can tell you. 'Sorry, I wasn't more specific :) And I DO expect you do be omniscient BTW, after all, my users/clients expect ME to be ... Start by inspecting the output of ps(1) to find likely looking perl processes. If you've actually got perl.core files you may be able to investigate with a debugger and work out what is producing them, but I wouldn't hold out too much hope of that. Cheers, Matthew [*] well, only occasionally. It seems that the long running perl processes are there in support of Mailman. I know it periodically restarts itself but I don't know how gracefully it shuts down the perl processess ... ___ 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: can i use flags at once?
On 6/8/2010 9:50 AM, Giorgos Tsiapaliokas wrote: On 8 June 2010 14:47, Giorgos Tsiapaliokas terie...@gmail.com wrote: for example when i was starting compiling kde i gave the commands, /usr/ports/x11/kde4 make install clean after these commands,the kde package asked me which flags i want to use. with packages like this it is easy,but then i left away from the pc and when i went back i saw that the system wanted my confirmation for some flags. can i make all the flags confirmations in the begging of the installiation of the packages? http://forums.freebsd.org/showthread.php?t=3718 -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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
SMBFS Question
I have DAGS and cannot find a good explanation for this, so if some kind soul could help it would be appreciated... I use FreeBSD (various versions/flavors) to connect to a USB drive shared off a WinXP machine to write large backup files. I mount this using the SMBFS capabilities. On a pretty regular basis, I see log messages in the form: smb_iod_recvall: drop resp with mid 30562 Are these benign? What exactly do they mean? TIA, Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: ssh: port 22: connection refuused
On 5/6/2010 12:21 PM, Gary Kline wrote: can anybody help me with ne of my last problems: getting ssh Into my new comuter? i am able to ssh outside. need to scp my config files over. sshd is running on zen This generally involves two or three steps: 1) Make sure /etc/rc.conf has this in it: sshd_enable=YES 2) Make sure /etc/hosts.allow permits access to your machine via ssh. Something like this: sshd: 192.168. a_host-name.com an.ip.add.ress :ALLOW Some people do this: sshd: ALL :ALLOW That's fine if the machine sits on a trusted LAN, but I don't much like this for machines that are internet-facing ... it just provides another vector for attack. So, for such machines, I explicitly name the address and names that are permitted ssh access. 3) If you're running a firewall, make sure that the sshd ports (22/tcp and 22/udp) are open for those machines/addresses you want to connect into your FreeBSD box. If you are still having trouble, go to the client machine and invoke your session like this: ssh -v your_freebsd_machine It will barf out a bunch of interesting information about why the connection isn't working that may help you figure out what's going on. Happy Trails, Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: Accessing file from windows or to windows
On 5/6/2010 3:47 PM, Jean-Paul Natola wrote: Hi all, I have a file I need in my bsd box, would it be easier, or is it possible, to mount an NTFS share , or should I try to map a directory from the windows box. TIA, I have Xp Win7 Win2003 Win2008 Freebsd 6.4 thanx Same machine or two separate machines? Two separate machines is trivial - share a directory on the Win machine and use smbfs on FBSD to get to it. For same machine, boot FBSD, and do a mount with -t ntfs as an arg well, I don't recall if 6.4 supported this or not, now that I think about it. One-time or frequent transfer? There are tons of other options, especially if you're running separate machines. Not all of these are elegant, but they all will work and have their place for infrequent transfers: - Email the file to yourself from one OS and retrieve it from the other. - Copy the file to a thumbdrive - Copy the file to a private website which can then be subsequently retrieved by another machine/OS image. Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: Accessing file from windows or to windows-
On 5/6/2010 4:19 PM, Jean-Paul Natola wrote: SNIP Well my book (absolute BSD) yes its old, says: writing to an NTFS partition may corrupt the partition - I'm guessing this is not the case anymore and to answer your question; 1. Its 2 separate machines 2. As a security standard I have disabled flash drives in the office 3. It will be a monthly taks 4. No web access on the bsd box Forgot the main one, when I tried to mount I get the error mount_smbfs: unable to open connection: syserr = Authentication error This means Windows is looking for login credentials before it will allow you to access the share. Suppose you are user 'Jean' on your Windows machine,WINDOZE and you use a password of foo. You want to get to the Windows share called MYSHARE and mount it locally on your FBSD box on /mnt. Then the command is: mount_smbfs //j...@windoze/MYSHARE /mnt You'll get prompted for a password and, when you enter it, the mount will be established. You can automate this whole business by learning how to populate the /etc/nsmb.conf file with the right stuff. -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: Accessing file from windows or to windows
On 5/6/2010 4:12 PM, Jean-Paul Natola wrote: On 5/6/2010 3:47 PM, Jean-Paul Natola wrote: Hi all, I have a file I need in my bsd box, would it be easier, or is it possible, to mount an NTFS share , or should I try to map a directory from the windows box. TIA, I have Xp Win7 Win2003 Win2008 Freebsd 6.4 thanx Same machine or two separate machines? Two separate machines is trivial - share a directory on the Win machine and use smbfs on FBSD to get to it. For same machine, boot FBSD, and do a mount with -t ntfs as an arg well, I don't recall if 6.4 supported this or not, now that I think about it. One-time or frequent transfer? There are tons of other options, especially if you're running separate machines. Not all of these are elegant, but they all will work and have their place for infrequent transfers: - Email the file to yourself from one OS and retrieve it from the other. - Copy the file to a thumbdrive - Copy the file to a private website which can then be subsequently retrieved by another machine/OS image. Well my book (absolute BSD) yes its old, says: writing to an NTFS partition may corrupt the partition - I'm guessing this is not the case anymore and to answer your question; 1. Its 2 separate machines 2. As a security standard I have disabled flash drives in the office 3. It will be a monthly taks 4. No web access on the bsd box Quite simple then: 1) Share the directory on the windows machine where the file of interest can be found. 2) Use FreeBSD's mount_smbfs command to access the Windows share over the network. Reading and writing over such a mount has been quite reliable in my experience. BTW, the quote to which you allude above wouldn't be relevant in your case. They're talking about a *single* machine that wants to mount an ntfs partition on the locally-attached hard drive. I'd be curious to know if it is still the case that ntfs writes are not reliable in that situation. There are times when doing this can be handy on a dual-boot laptop, for example. 'Anyone out there care to comment on the state of ntfs rw access? -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: Accessing file from windows or to windows
On 5/6/2010 4:30 PM, Modulok wrote: In order to 'provide' shares to a windows network you would need to run a daemon on FreeBSD which provides such services. The most popular solution is 'samba'. I think the package is called 'samba3'. You install it, edit its config file, which specifies what to share and how to share it. You then run the daemon and poof, your windows machines can access the shares you've configured. This is entirely correct, however, judging from the OP's question, this sounds like real overkill. mount_smbfs is in the base FBSD system and does not require a port install to use. Just my .1 cents worth. On the other hand, if the windows machines are providing a shared folder you want to access, you can just mount that share via the 'mount_smbfs' command. For example, if I had a windows computer named 'apollo' with username 'guest' and a folder named 'shared' I wanted to access, I could do this from my FreeBSD machine: # As root: mount_smbfs //gu...@apollo/shared /mnt I would now have the contents of apollo's 'shared' folder available in my '/mnt' directory. See 'mount_smbfs(8)' for more. Other options could involve setting up an SSH client/server on the two machines and use 'sftp' or 'scp' to transfer files, among others. -Modulok- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: Accessing file from windows or to windows-
On 5/6/2010 4:32 PM, Jean-Paul Natola wrote: -Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of Tim Daneliuk Sent: Thursday, May 06, 2010 5:28 PM To: FreeBSD Mailing List Subject: Re: Accessing file from windows or to windows- On 5/6/2010 4:19 PM, Jean-Paul Natola wrote: SNIP Well my book (absolute BSD) yes its old, says: writing to an NTFS partition may corrupt the partition - I'm guessing this is not the case anymore and to answer your question; 1. Its 2 separate machines 2. As a security standard I have disabled flash drives in the office 3. It will be a monthly taks 4. No web access on the bsd box Forgot the main one, when I tried to mount I get the error mount_smbfs: unable to open connection: syserr = Authentication error This means Windows is looking for login credentials before it will allow you to access the share. Suppose you are user 'Jean' on your Windows machine,WINDOZE and you use a password of foo. You want to get to the Windows share called MYSHARE and mount it locally on your FBSD box on /mnt. Then the command is: mount_smbfs //j...@windoze/MYSHARE /mnt You'll get prompted for a password and, when you enter it, the mount will be established. Same error: milter# mount_smbfs //jnat...@fcisql01/DATA /mnt Password: mount_smbfs: unable to open connection: syserr = Authentication error milter# This sounds like you have a permissions problem on the Windows share. In Windows Explorer, right click on the shared directory and look at Properties-Sharing-Permissions. Make sure that 'jnatola' has an account on that machine and that this account is permitted access to that share. If that's all waorking, my guess would be you have the wrong password. If you can, try accessing the share from another Windows machine to make sure the share is working properly. -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: Accessing file from windows or to windows
On 5/6/2010 4:36 PM, Modulok wrote: writing to an NTFS partition may corrupt the partition - I'm guessing this is not the case anymore. That's only when you have directly mounted an NTFS on the local machine. Like if you jacked a hard drive out of a windows machine and plugged it into your BSD machine. If you're accessing it across a network you're never directly accessing the file system. There is always an intermediary between you and it; the daemon which handles file i/o requests. Notice: It handles your *requests*; you never actually access the underlying file system. Yes, I know this. That was not my question. My question is that when you DO attach to a local NTFS partition, has the write corruption problem for the NTFS driver been fixed, and if so, as of what release of FreeBSD? I know this is now claimed to work in Linux as for ntfs3 support. 'Just wondering where FreeBSD is in that evolution, that's all. Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: ssh: port 22: connection refuused
On 5/6/2010 4:35 PM, Gary Kline wrote: On Thu, May 06, 2010 at 12:32:18PM -0500, Tim Daneliuk wrote: On 5/6/2010 12:21 PM, Gary Kline wrote: can anybody help me with ne of my last problems: getting ssh Into my new comuter? i am able to ssh outside. need to scp my config files over. sshd is running on zen This generally involves two or three steps: 1) Make sure /etc/rc.conf has this in it: sshd_enable=YES Yes; this was my first try. no diff. 2) Make sure /etc/hosts.allow permits access to your machine via ssh. Something like this: sshd: 192.168. a_host-name.com an.ip.add.ress :ALLOW Some people do this: sshd: ALL :ALLOW That's fine if the machine sits on a trusted LAN, but I don't much like this for machines that are internet-facing ... it just provides another vector for attack. So, for such machines, I explicitly name the address and names that are permitted ssh access. ok. itried this; have not rebooted yet. no difference right now. 3) If you're running a firewall, make sure that the sshd ports (22/tcp and 22/udp) are open for those machines/addresses you want to connect into your FreeBSD box. i'm runnning a pfSense computer; pretty sure that things are sett correctly there. If you are still having trouble, go to the client machine and invoke your session like this: ssh -v your_freebsd_machine the files in /etc/ssh were the first thing i thought of editing. didn't see many differences between rel 8.0 and my current 7.3. still, here is the verbose output. pl 14:20 tao [5036] ssh zen ssh: connect to host zen port 22: Connection refused pl 14:20 tao [5037] ssh - zen OpenSSH_5.1p1 FreeBSD-20080901, OpenSSL 0.9.8e 23 Feb 2007 debug1: Reading configuration data /etc/ssh/ssh_config debug2: ssh_connect: needpriv 0 debug1: Connecting to zen [10.47.0.190] port 22. debug1: connect to address 10.47.0.190 port 22: Connection refused ssh: connect to host zen port 22: Connection refused pl 14:22 tao [5038] any idea what the ``needpriv 0'' means? What's in your /etc/hosts.allow file? It will barf out a bunch of interesting information about why the connection isn't working that may help you figure out what's going on. Happy Trails, Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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 -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: ssh: port 22: connection refuused
On 5/6/2010 4:41 PM, Tim Daneliuk wrote: On 5/6/2010 4:35 PM, Gary Kline wrote: On Thu, May 06, 2010 at 12:32:18PM -0500, Tim Daneliuk wrote: On 5/6/2010 12:21 PM, Gary Kline wrote: can anybody help me with ne of my last problems: getting ssh Into my new comuter? i am able to ssh outside. need to scp my config files over. sshd is running on zen This generally involves two or three steps: 1) Make sure /etc/rc.conf has this in it: sshd_enable=YES Yes; this was my first try. no diff. 2) Make sure /etc/hosts.allow permits access to your machine via ssh. Something like this: sshd: 192.168. a_host-name.com an.ip.add.ress :ALLOW Some people do this: sshd: ALL :ALLOW That's fine if the machine sits on a trusted LAN, but I don't much like this for machines that are internet-facing ... it just provides another vector for attack. So, for such machines, I explicitly name the address and names that are permitted ssh access. ok. itried this; have not rebooted yet. no difference right now. 3) If you're running a firewall, make sure that the sshd ports (22/tcp and 22/udp) are open for those machines/addresses you want to connect into your FreeBSD box. i'm runnning a pfSense computer; pretty sure that things are sett correctly there. If you are still having trouble, go to the client machine and invoke your session like this: ssh -v your_freebsd_machine the files in /etc/ssh were the first thing i thought of editing. didn't see many differences between rel 8.0 and my current 7.3. still, here is the verbose output. pl 14:20 tao [5036] ssh zen ssh: connect to host zen port 22: Connection refused pl 14:20 tao [5037] ssh - zen OpenSSH_5.1p1 FreeBSD-20080901, OpenSSL 0.9.8e 23 Feb 2007 debug1: Reading configuration data /etc/ssh/ssh_config debug2: ssh_connect: needpriv 0 debug1: Connecting to zen [10.47.0.190] port 22. debug1: connect to address 10.47.0.190 port 22: Connection refused ssh: connect to host zen port 22: Connection refused pl 14:22 tao [5038] any idea what the ``needpriv 0'' means? What's in your /etc/hosts.allow file? Oh ... one other thing ... make sure sshd is actually running. If you changed the /etc/rc.conf enable line without either rebooting or doing a kill -HUP 1, you may not have a running daemon. -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: Accessing file from windows or to windows-
On 5/6/2010 4:52 PM, Jean-Paul Natola wrote: will be established. Same error: milter# mount_smbfs //jnat...@fcisql01/DATA /mnt Password: mount_smbfs: unable to open connection: syserr = Authentication error milter# This sounds like you have a permissions problem on the Windows share. In Windows Explorer, right click on the shared directory and look at Properties-Sharing-Permissions. Make sure that 'jnatola' has an account on that machine and that this account is permitted access to that share. If that's all waorking, my guess would be you have the wrong password. This is the company wide share everyone has access to it, It even fails if I use the domain and enterprise admin accounts- And as I'm typing this, could that be the reason, because im using domain accounts? It could be. I've never tried mount_smbfs in a Domain, only a Workgroup. I'm not saying it won't work, I just don't know. I do know there is some magic in how SMB passwords get encrypted and that it is possible for FreeBSD to do it differently than the Win machine and thus the mount will fail. One more thing to try would be to create a share that requires NO password and see what happens then. -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: Accessing file from windows or to windows-
On 5/6/2010 5:06 PM, Jean-Paul Natola wrote: This is the company wide share everyone has access to it, It even fails if I use the domain and enterprise admin accounts- And as I'm typing this, could that be the reason, because im using domain accounts? ___ That was it , I was using a domain instead of an account on the local box Thanks everyone, At least now I am aware of all the options Where shall we send the bill? :) Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: ssh: port 22: connection refuused
On 5/6/2010 4:41 PM, Tim Daneliuk wrote: SNIP pl 14:20 tao [5036] ssh zen ssh: connect to host zen port 22: Connection refused pl 14:20 tao [5037] ssh - zen OpenSSH_5.1p1 FreeBSD-20080901, OpenSSL 0.9.8e 23 Feb 2007 debug1: Reading configuration data /etc/ssh/ssh_config debug2: ssh_connect: needpriv 0 debug1: Connecting to zen [10.47.0.190] port 22. debug1: connect to address 10.47.0.190 port 22: Connection refused ssh: connect to host zen port 22: Connection refused pl 14:22 tao [5038] any idea what the ``needpriv 0'' means? The more I look at this, the more it looks to me like your sshd is not running at all, isn't running on port 22, or is being blocked by some kind of firewall. Just for snicks, I tried to ssh to a machine on our network that I know does not have an ssh daemon running. Look at the results: ssh -v sylvester OpenSSH_5.4p1 FreeBSD-20100308, OpenSSL 0.9.8k 25 Mar 2009 debug1: Reading configuration data /etc/ssh/ssh_config debug2: ssh_connect: needpriv 0 debug1: Connecting to sylvester.tundraware.com [192.168.0.102] port 22. debug1: connect to address 192.168.0.102 port 22: Connection refused ssh: connect to host sylvester.tundraware.com port 22: Connection refused Look familiar? :-) P.S. You are running a VERY old version of OpenSSH. I believe there were significant security problems back that far. Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: ssh: port 22: connection refuused
On 5/7/2010 12:13 AM, Gary Kline wrote: SNIP What's in your /etc/hosts.allow file? # Start by allowing everything (this prevents the rest of the file # from working, so remove it when you need protection). # The rules here work on a First match wins basis. ALL : ALL : allow that i moused and pasted from my main desktop. OK and you've indicated that sshd is running. A few other thoughts: 1) Is there a firewall running on your machine that could be preventing the connection? 2) Is there a firewall running on your *client* machine that could be interfering. 3) Log into the FreeBSD machine and see if you can ssh to localhost to just to confirm that sshd is working. If that works, try sshing to the same machine using its IP, and then its address to make sure DNS is resolving properly. Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: Setup Fail2Ban on FreeBSD
On 4/23/2010 8:03 PM, Zhu Jing wrote: On Sat, Apr 24, 2010 at 1:49 AM, Bauer, Aaron J. aaron.j.ba...@saic.comwrote: I am currently using FreeNAS 0.7 for a file server. I have multiple SSH bruteforce attacks each week, and wish to use fail2ban to prevent this. I don't have much experience with BSD, and am having trouble getting everything to work. I ran pkg_add -r python25 and pkg_add -r py25-fail2ban. I now have all the files for Fail2Ban, and did the cp jail.conf jail.local as the other distro's for linux use. However, how do I start using fail2ban? I have configured it for CentOS and Ubuntu, and it starts in init.d. I don't know how to add it to /etc/rc.d to get it to work correctly.. Any help is greatly appreciated. If you need more info, please let me know. Aaron Software Research Intern aaron.j.ba...@saic.com I came up with another approach to this problem that involves dynamic control of TCP Wrappers. It's freely available at: http://www.tundraware.com/Software/tperimeter/ Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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
RTC BIOS diagnostic error 80clock_battery?
I see this error on every boot of an Intel 946GZ mobo with a Pentium D 3GHz CPU and 2G memory. The problem does not go away after a new BIOS battery is installed, nor does it go away after going into BIOS and re-saving the configuration. This machine is running 8.0-STABLE very nicely, so I don't know if this is a big deal or not. Ideas anyone? -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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
Preventing Bad SMB Mount From Stalling A Boot
I mount my SMB shares from /etc/fstab on a FBSD 8.x production machine like this: //u...@winserver/SHARE /mountpointsmbfs rw 0 0 The problem is that after an outage, WINSERVER doesn't come up before the FBSD machine. So, the FBSD machine tries to boot and then hangs permanently because it cannot get the SMB share points mounted. This recently happened after a catastrophic power outage that cooked the share info on WINSERVER. Even after it came up, it was no longer serving the proper shares and the FBSD machine could never find the SMB shares and thus hung permanently. The SMB mounts are not essential for systems operations. Is there a way to tell the FBSD to try and mount SMB, but keep going and complete the boot if it cannot? -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: Preventing Bad SMB Mount From Stalling A Boot
On 4/6/2010 1:36 PM, Dan Naumov wrote: I mount my SMB shares from /etc/fstab on a FBSD 8.x production machine like this: //USER at WINSERVER/SHARE /mountpointsmbfs rw 0 0 The problem is that after an outage, WINSERVER doesn't come up before the FBSD machine. So, the FBSD machine tries to boot and then hangs permanently because it cannot get the SMB share points mounted. This recently happened after a catastrophic power outage that cooked the share info on WINSERVER. Even after it came up, it was no longer serving the proper shares and the FBSD machine could never find the SMB shares and thus hung permanently. The SMB mounts are not essential for systems operations. Is there a way to tell the FBSD to try and mount SMB, but keep going and complete the boot if it cannot? A bit of an ugly hack, but have you considered attempting to mount the share via an automatic script after the system has finished booting? - Sincerely, Dan Naumov Actually that is what I was doing via a script in /usr/local/etc/rc.d before I switched over to the /etc/fstab scheme. I may have to fall back to the rc.d approach. It seems odd to me that there's best effort to mount semantic option for fstab entries... -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: Preventing Bad SMB Mount From Stalling A Boot
On 4/6/2010 1:50 PM, Tim Daneliuk wrote: On 4/6/2010 1:36 PM, Dan Naumov wrote: I mount my SMB shares from /etc/fstab on a FBSD 8.x production machine like this: //USER at WINSERVER/SHARE /mountpointsmbfs rw 0 0 The problem is that after an outage, WINSERVER doesn't come up before the FBSD machine. So, the FBSD machine tries to boot and then hangs permanently because it cannot get the SMB share points mounted. This recently happened after a catastrophic power outage that cooked the share info on WINSERVER. Even after it came up, it was no longer serving the proper shares and the FBSD machine could never find the SMB shares and thus hung permanently. The SMB mounts are not essential for systems operations. Is there a way to tell the FBSD to try and mount SMB, but keep going and complete the boot if it cannot? A bit of an ugly hack, but have you considered attempting to mount the share via an automatic script after the system has finished booting? - Sincerely, Dan Naumov Actually that is what I was doing via a script in /usr/local/etc/rc.d before I switched over to the /etc/fstab scheme. I may have to fall back to the rc.d approach. It seems odd to me that there's best effort to mount semantic option for fstab entries... I meant to say that there is NO such semantic. -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: amd64 won't install on Core Duo
On 3/5/2010 6:28 PM, Chad Perrin wrote: The amd64 arch installer for 8.0-RELEASE fails to start on a ThinkPad T60 with an Intel Centrino Core Duo. What am I doing wrong? error message: CPU doesn't support long mode You have a CPU that does not have 64-bit extensions. You need to install the i386 version. -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: Thousands of ssh probes
On 3/5/2010 7:44 PM, Erik Norgaard wrote: On 05/03/10 13:54, John wrote: My nightly security logs have thousands upon thousands of ssh probes in them. One day, over 6500. This is enough that I can actually feel it in my network performance. Other than changing ssh to a non-standard port - is there a way to deal with these? Every day, they originate from several different IP addresses, so I can't just put in a static firewall rule. Is there a way to get ssh to quit responding to a port or a way to generate a dynamic pf rule in cases like this? This is a frequent question on the list, search the archives. Basically there are few things that you can do: 1. limit the access to a range of IPs, for example, even if you travel a lot you go to al limited number of countries, why permit access from other continents? 2. limit access to certain users, there is no need to allow games or root user to authenticate via ssh. Use AllowUsers or AllowGroups to restrict access to real users. 3. limit the amount of concurrent non-authenticated connections, number of failed attempts and similar. 4. prohibit password authentication. If the problem is that these attacks consume significant bandwidth then moving your service to a different port may be a good solution, but if your concern is security, then the above is more effective. BR, Erik I solved this problem a slightly different way with dynamic TCP wrapper control: http://www.tundraware.com/Software/tperimeter/ -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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
Perl 5.8 - 5.10 On Current Production System
Is there a recommended procedure I can read somewhere on how to upgrade an entire production system from Perl 5.8 to 5.10 (or whatever is current) cleanly? -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: Perl 5.8 - 5.10 On Current Production System
On 3/4/2010 10:13 AM, Leslie Jensen wrote: On 2010-03-04 17:06, Tim Daneliuk wrote: Is there a recommended procedure I can read somewhere on how to upgrade an entire production system from Perl 5.8 to 5.10 (or whatever is current) cleanly? /usr/ports/UPDATING ;-) Thanks to all for pointing to this. However, when I run: portupgrade -o lang/perl5.10 -f perl-5.8\.* I get this problem: --- Upgrading 'perl-5.8.9_3' to 'perl-5.10.1' (lang/perl5.10) --- Building '/usr/ports/lang/perl5.10' === Cleaning for perl-5.10.1 === perl-5.10.1 conflicts with installed package(s): perl-5.8.9_3 They install files into the same place. Please remove them first with pkg_delete(1). *** Error code 1 I supposed I could do a forced manual removal of perl, but isn't that what the '-f' arg in the portupgrade is supposed to do? -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: Perl 5.8 - 5.10 On Current Production System
On 3/4/2010 11:13 AM, Matthew Seaman wrote: portupgrade -m DISABLE_CONFLICTS=yes -o lang/perl5.10 -f perl-5.8\.* Thanks for that. I'm not sure to whom I'd complain and/or if it would make any difference ;) -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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
Help ipfw / nat / JetDirect Pain Appreciated
I would appreciate any insight you folk here might have for the following problem. What I am trying to do is have wireless clients on one network print to a JetDirect-connected printer on another network as follows: Machine A is a NATing firewall (FBSD 8.0) for nonroutable network A - 192.168.0.x Machine A is a NATing wireless router (Linksys WRT-54G) for nonroutable network B - 192.168.1.x Both Machine A and B have static routable addresses and are directly connected to the internet. They are also on the same subnet. In fact, they're plugged into the same switch that the internet hose comes in on. There is an HP Laserjet connected via JetDirect on the first network at 192.168.0.122. I have added this to machine A's NAT config to make that port appear on the outside IP address: redirect_port tcp 192.168.0.102:9100 machine.A.IP.addr:9100 natd was then restarted. I then added this firewall rule on Machine A: ipfw add allow tcp from machine.B.IP.addr to machine.A.IP.addr 9100 And the firewall was restarted. Now, I jump onto a machine on (wireless) Network B and attempt to telnet to port 9100 on machine A, just to see if the port is properly being redirected and I can get to it. Machine A burps out the following in /var/log/security: ipfw: 7500 Deny TCP machine.B.IP.addr:49192 192.168.0.102:9100 in via fxp0 Anyone have an idea what's going on here? It looks like the telnet is attempting to rendezvous on port 49192 but the firewall isn't letting that happen. Any idea how I add a rule to permit this? TIA, -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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
FBSD 8.0 littering the filesystem with *.gmon files
I realize that developers find these helpful, but is there a way to suppress the creation of these files all over the filesystem? -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: FBSD 8.0 littering the filesystem with *.gmon files
On 2/9/2010 11:57 PM, Dan Nelson wrote: In the last episode (Feb 09), Tim Daneliuk said: I realize that developers find these helpful, but is there a way to suppress the creation of these files all over the filesystem? You must have enabled profiling in CFLAGS somewhere; it's not on by default. Search for -p or -pg in /etc/make.conf or you shell's startup scripts. Nope - not set either place. In fact, CFLAGS isn't even set in the envirnment or mentioned in /etc/make.conf. Curiouser and curiouser... -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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
Follow Up Question On Upgrading And Ports
My ordinary practice with production FreeBSD machines is to: - Regularly (weekly), update the sources, rebuild and reinstall world and kernels. - Regularly (several times a week), do a 'portupgrade -arR' - Somewhat frequently do a 'pkgdb -F' IOW, I keep the OS, kernels, and ports fairly up-to-date. However, per the thread on the proper updating method a few days ago, I just ran 'make delete-old' and 'make delete-old-libs' for the first time ever. After a reboot the system started grumbling about not being able to find libssl.so.4. I reinstalled the compat5,6,7 ports and all is well again. Running 'make delete-old-libs' seems to no longer want to get rid of libssl.so.4. This leads to my questions: 1) With all the regular portupgrades I do, why is libssl.so.4 even being used any more? Isn't this a relic from the FBSD 4.x branch? 2) Why did the initial 'make delete-old-libs' clobber this file, but after the compat reinstalls, the same command no longer cares? 3) If I do an in-place upgrade to 8.x (I'll probably wait until 8.1) and immediately follow it with a 'portupgrade -arR', will I be guaranteed that every port will be migrated to the very latest 8.x libs? Thanks, -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: Follow Up Question On Upgrading And Ports
On 2/8/2010 12:30 PM, Matthew Seaman wrote: On 08/02/2010 17:38, Tim Daneliuk wrote: My ordinary practice with production FreeBSD machines is to: - Regularly (weekly), update the sources, rebuild and reinstall world and kernels. This implies you're running one of the -STABLE branches, rather than -RELEASE: updates to -RELEASE happen much less frequently than weekly... - Regularly (several times a week), do a 'portupgrade -arR' - Somewhat frequently do a 'pkgdb -F' IOW, I keep the OS, kernels, and ports fairly up-to-date. Yep. It's good to do that, although your methodology would be pretty hard to cope with on any more than a few machines. Yup, 'tis -stable. And, no, I wouldn't do a farm of machines this way. For that, I wrote/use this: http://www.tundraware.com/Software/tbku/ Matthew Lowell - thanks for taking the time ... Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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
Clarification Of In Place Upgrade Process
When migrating from 6.x to 7.x and to do system refreshes within a given release branch, I did/do this: - Get sources - mergemaster -i - make buildworld buildkernel - go single user - make installworld installkernel - reboot I now wish to do the same to get to the 8.x branch, BUT ... somewhere on USENET, someone commented that you have to also reinstall/rebuild all the packages/ports when you do this. This was news to me. Is there some reason the entire application base has to be reinstalled when moving to a new branch? If so, has this always been the case or is it new for 8.x? My 6.x - 7.x upgrade went flawlessly using the method above without touching the ports/packages tree. TIA, -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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
7.2-Stable - smbfs.ko Is Missing
I just did an update and make world/kernel with the stable sources as of this morning. The boot process grumbles and goes single user because it cannot find smbfs.ko to mount some SMB shares. Any ideas why this module has suddenly disappeared and/or a workaround? Thanks, -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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
7.2-Stable - smbfs.ko Is Missing
I just did an update and make world/kernel with the stable sources as of this morning. The boot process grumbles and goes single user because it cannot find smbfs.ko to mount some SMB shares. Any ideas why this module has suddenly disappeared and/or a workaround? Thanks, -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: 7.2-Stable - smbfs.ko Is Missing
Tim Daneliuk wrote: I just did an update and make world/kernel with the stable sources as of this morning. The boot process grumbles and goes single user because it cannot find smbfs.ko to mount some SMB shares. Any ideas why this module has suddenly disappeared and/or a workaround? Thanks, Nevermind - a new make world/kernel fixed things ... it may have been an artifact of a full /tmp filesystem ... -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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
Updated 'bind' And FreeBSD 6.3
Is there an expected date when the latest version of bind9 (that fixes the recently discussed DNS vulnerability) will be merged into the 6.3-STABLE tree. I patch and update fairly regularly and bind -v gives me: BIND 9.3.5-P1 I believe the patched version is something like 9.5.0-P?... TIA, -- Tim Daneliuk [EMAIL PROTECTED] PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Updated 'bind' And FreeBSD 6.3
Matthew Seaman wrote: Tim Daneliuk wrote: Is there an expected date when the latest version of bind9 (that fixes the recently discussed DNS vulnerability) will be merged into the 6.3-STABLE tree. I patch and update fairly regularly and bind -v gives me: BIND 9.3.5-P1 I believe the patched version is something like 9.5.0-P?... TIA, Patches against the Kaminsky attack were released for all of the supported BIND branches. 9.3.5-P1 is a patched version. You can verify that your bind is patched by using the dns oarc tester: https://www.dns-oarc.net/oarc/services/dnsentropy or manually by: dig +short porttest.dns-oarc.net TXT If it reports 'poor' you still need to fix your server. Beware of NAT gateways which can reduce the randomness with which source ports are used in passing. Cheers, Matthew Thanks all - I do indeed have the patches and can now no longer spend nights worried about these ;) -- Tim Daneliuk [EMAIL PROTECTED] PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD for webserver?
Chris St Denis wrote: VeeJay wrote: Hi there I am going to make 2 Webserver at my work going to handle 50 mil hits per month... They are using Linux already. But being a FreeBSD fan, I have proposed FreeBSD to my Boss convincing him that FreeBSD is more Fast and Secure solution for his needs... And now I want to show the results... *Hardware:* Dell PowerEdge 2950 III having 2 x CPU 3,0 GHz Intel Xeon L5450 Quad-Core 2x6MB cache WITH 16 GB RAM. *Tools:* 1. FreeBSD 7 Production Release 2. Apache 2.2.9 3. MySQL 5.1.26 4. PHP 5.2.6 My question is, *To get the speed, performance and security*: Should I use Ports or Packages to install all these tools One by One? *OR* Should I use TAR files and compile them manually. For example giving command line arguments and commands like ./configure --prefix=/www --enable-module=so make make install cd ../php-xxx ./configure --with-mysql --with-apxs=/www/bin/apxs make make install etc I have googled but still haven't reached to solution...personally I would prefer comiling them with command line arguments but then I seek some help from you guys i.e. How should I write this ./configure..stuff in FreeBSD and what would be the best options combination, I must choose to get the speed, performane and security in Apache, MySQL and PHP? Any suggestion is very welcomed! Best to just use the ports. They take care of all of the dependencies for you and have extra patches to make them work optimally for FreeBSD. Why ./configure by hand when the port's makefile will do it for you? +1 Also, using ports makes it much easier to update systems with portupdate later on. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Making World For amd64
Is there anything special one has to do when doing a make world intended for 64-bit FreeBSD or is it sufficient to build the 64-bit kernel and make world as everywhere else? -- Tim Daneliuk [EMAIL PROTECTED] PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Making World For amd64
Kris Kennaway wrote: Tim Daneliuk wrote: Is there anything special one has to do when doing a make world intended for 64-bit FreeBSD or is it sufficient to build the 64-bit kernel and make world as everywhere else? The same as everywhere else. Kris So, I take it that this means that all the userspace programs, ports, packages, utilities, etc. do *not* take advantage of the 64-bit extensions. That is, only the kernel gets the benefit of the wider word. Is that correct? -- Tim Daneliuk [EMAIL PROTECTED] PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Making World For amd64
Kris Kennaway wrote: Tim Daneliuk wrote: Kris Kennaway wrote: Tim Daneliuk wrote: Is there anything special one has to do when doing a make world intended for 64-bit FreeBSD or is it sufficient to build the 64-bit kernel and make world as everywhere else? The same as everywhere else. Kris So, I take it that this means that all the userspace programs, ports, packages, utilities, etc. do *not* take advantage of the 64-bit extensions. That is, only the kernel gets the benefit of the wider word. Is that correct? No, everything is 100% native. Kris OK, these may be really stupid questions but: 1) How does make world know whether to build 32-bit or 64-bit binaries? 2) Can a binary from a 32-bit FreeBSD system be run unmodified on the 64-bit system? 3) If I reboot with 32-bit or 64-bit kernels, does the system magically somehow make the userland stuff work natively at the word width? If so, how? TIA, -- Tim Daneliuk [EMAIL PROTECTED] PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Making World For amd64
Sean Cavanaugh wrote: -- From: Tim Daneliuk [EMAIL PROTECTED] Sent: Thursday, June 26, 2008 4:51 PM To: Kris Kennaway [EMAIL PROTECTED]; FreeBSD Mailing List freebsd-questions@FreeBSD.org Subject: Re: Making World For amd64 Kris Kennaway wrote: Tim Daneliuk wrote: Kris Kennaway wrote: Tim Daneliuk wrote: Is there anything special one has to do when doing a make world intended for 64-bit FreeBSD or is it sufficient to build the 64-bit kernel and make world as everywhere else? The same as everywhere else. Kris So, I take it that this means that all the userspace programs, ports, packages, utilities, etc. do *not* take advantage of the 64-bit extensions. That is, only the kernel gets the benefit of the wider word. Is that correct? No, everything is 100% native. Kris OK, these may be really stupid questions but: 1) How does make world know whether to build 32-bit or 64-bit binaries? 2) Can a binary from a 32-bit FreeBSD system be run unmodified on the 64-bit system? 3) If I reboot with 32-bit or 64-bit kernels, does the system magically somehow make the userland stuff work natively at the word width? If so, how? TIA, I take this to mean you have an i386 install and want to compile amd64 on it. No - although that is an interesting question in its own right. I was more interested in the general question of whether 32-bit and 64-bit binaries are the same or different. I would assume that something has to be compiled to take advantage of 64-bit operations. But this then leads to the two questions: How does makeworld know which way to build the binaries and Can a 32bit binary be run on a 64bit system (or vice versa) in some compatibility or degraded mode... -- Tim Daneliuk [EMAIL PROTECTED] PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Making World For amd64
Erik Trulsson wrote: 1) How does make world know whether to build 32-bit or 64-bit binaries? It will build for whatever system you have installed. If you are running a 32-bit system it will make 32-bit binaries, and if you are running a 64-bit system it will make 64-bit binaries. By running, you mean which kernel is booted, I presume. 2) Can a binary from a 32-bit FreeBSD system be run unmodified on the 64-bit system? Assuming the 32-bit system is 'i386' and the 64-bit system is 'amd64' then you are supposed to be able to do so (but I don't know how well it works in practice). Otherwise no. (Running a i386 binary on a sparc64 system won't work.) Right. I should have been more clear. It would be unreasonable to expect binaries for entirely different machine architecture to run on other kinds of machinery. My question was limited to x86 class machines. -- Tim Daneliuk [EMAIL PROTECTED] PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Making World For amd64
Kris Kennaway wrote: Tim Daneliuk wrote: Kris Kennaway wrote: Tim Daneliuk wrote: Kris Kennaway wrote: Tim Daneliuk wrote: Is there anything special one has to do when doing a make world intended for 64-bit FreeBSD or is it sufficient to build the 64-bit kernel and make world as everywhere else? The same as everywhere else. Kris So, I take it that this means that all the userspace programs, ports, packages, utilities, etc. do *not* take advantage of the 64-bit extensions. That is, only the kernel gets the benefit of the wider word. Is that correct? No, everything is 100% native. Kris OK, these may be really stupid questions but: 1) How does make world know whether to build 32-bit or 64-bit binaries? It always uses the native format. amd64 == 64 bit, i386 == 32 bit Don't mean to beat this to death, but can you say just a bit more about this please. If I am running an i386 kernel on 64-bit capable processor, I assume I will get 32-bit binaries or not? IOW, what triggers makeworld to do something in 32- vs. 64-bit mode? The *kernel* currently executing or the underlying hardware capability? TIA, Tim Daneliuk [EMAIL PROTECTED] PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Making World For amd64
Tim Daneliuk wrote: Kris Kennaway wrote: Tim Daneliuk wrote: Kris Kennaway wrote: Tim Daneliuk wrote: Kris Kennaway wrote: Tim Daneliuk wrote: Is there anything special one has to do when doing a make world intended for 64-bit FreeBSD or is it sufficient to build the 64-bit kernel and make world as everywhere else? The same as everywhere else. Kris So, I take it that this means that all the userspace programs, ports, packages, utilities, etc. do *not* take advantage of the 64-bit extensions. That is, only the kernel gets the benefit of the wider word. Is that correct? No, everything is 100% native. Kris OK, these may be really stupid questions but: 1) How does make world know whether to build 32-bit or 64-bit binaries? It always uses the native format. amd64 == 64 bit, i386 == 32 bit Don't mean to beat this to death, but can you say just a bit more about this please. If I am running an i386 kernel on 64-bit capable processor, I assume I will get 32-bit binaries or not? IOW, what triggers makeworld to do something in 32- vs. 64-bit mode? The *kernel* currently executing or the underlying hardware capability? Let me be even more specific: If I install 32-bin x86 FreeBSD on, say, a Pentium D machine that is 64-bit capable, when I makeworld, will this result in 32- or 64-bit binaries? Ditto if I do makekernel. -- Tim Daneliuk [EMAIL PROTECTED] PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Making World For amd64
Chris Whitehouse wrote: Tim Daneliuk wrote: Kris Kennaway wrote: Tim Daneliuk wrote: Kris Kennaway wrote: Tim Daneliuk wrote: Is there anything special one has to do when doing a make world intended for 64-bit FreeBSD or is it sufficient to build the 64-bit kernel and make world as everywhere else? The same as everywhere else. Kris So, I take it that this means that all the userspace programs, ports, packages, utilities, etc. do *not* take advantage of the 64-bit extensions. That is, only the kernel gets the benefit of the wider word. Is that correct? No, everything is 100% native. Kris OK, these may be really stupid questions but: 1) How does make world know whether to build 32-bit or 64-bit binaries? 2) Can a binary from a 32-bit FreeBSD system be run unmodified on the 64-bit system? 3) If I reboot with 32-bit or 64-bit kernels, does the system magically somehow make the userland stuff work natively at the word width? If so, how? TIA, This might be a really stupid answer :p and maybe I have misunderstood the context of your question but when you initially downloaded an ISO to install you already chose whether it is 32 or 64 bit. Everything else, like which source and ports you get when you upgrade, follows from that (barring fancy stuff like cross compiling etc) Chris I guess I should have been a bit clearer about *why* I care. (BTW, all the answers were very helpful, so thanks all for that.) First, I was just generally curious about how 32- vs. 64-bit support was decided at compile time. Secondly, what got me started looking into this is when I realized I had 64-bit capable hardware in my lab, which I'd always had running 32-bit OSs. As I installed AMD64, I got to wondering just what level of compatibility existed (at the binary) level between the two, hence all my questions. Incidentally, I ran into a problem - that has nothing to do with word width AFAICT - when I installed 64-bit FreeBSD on one of the machines that historically has run 32-bit Linux (without the problem). The specific problem is that I have an MSI P4M900M2-L mobo and Pentium D on this machine that FreeBSD cannot find the APIC, so it always runs uniproc even with an SMP kern. I have to go back and check, but I am pretty sure this is not a 32-bit vs. 64-bit problem. Like I said, SUSE Linux has no problem running SMP on this same exact hardware, so it does seem to be a FreeBSD thing. Anyone else seen this kind of problem before? -- Tim Daneliuk [EMAIL PROTECTED] PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Unstable File Server
Marcel Grandemange wrote: Good day! I hope someone might be able to assist me over here! I have a multipurpose FreeBSD server, and one of the roles is being a file server. This role however seems to continuously bring the machine to it's knees. I have tried seeking help elsewhere namely http://www.daemonforums.org/showthread.php?t=980 But still can't seem to get this going. Id really appreciate some input, thank you! Have you tried swapping out the drive cables with new/UDMA133 ones. Every time I think I've found a problem w/FBSD disk handling it ends up being the cables :) __ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [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: Wipe a drive clean
Wojciech Puchar wrote: I'm having no luck finding hits for wipe drive or zero drive in the mail list archives and I can't believe I'm the first to ask this question but here it is anyway. How can I simply write 0's across a USB thumb drive? I'd rather not install a port, if I can avoid it. I was thinking that something like dd would work, but everything I've tried thus far is not working. What suggestions does everyone have? Will... dd if=/dev/zero of=/dev/disk dd if=/dev/zero of=/dev/disk bs=1m bs may be smaller but not the default 512 bytes. it's a block size. having very small block will make the process slow ...work? Steve I like this tool for nuking drives: http://dban.sourceforge.net/ -- Tim Daneliuk [EMAIL PROTECTED] PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: shellscript conditional to check for external disk
Roland Smith wrote: On Sat, Jun 21, 2008 at 09:44:09PM +, Helge Rohde wrote: Hello List, I need to write a backup script, and one of the required actions would be a copy of the backup to an external firewire drive. I would like to make this as easy as possible for the local staff, so i'd like to check whether the drive is attached, if necessary mount it, copy over the backup and unmount it again, so that the local staff can swap the external disks when they're not used. Is there a canonical way to achieve what i want? I played with the idea of simply checking for /dev/da0s1d's existance, but that won't disappear on disconnect, so that would leave the is a possibility that although da0 is in /dev, it might not be connected. Use glabel(8) to give the device an unique label. There is no telling which device /dev/da0s1d is pointing to! After labeling you can check for /dev/fstype/yourlabel, which should be unique. Make sure to unmount the drive at the end of the backup script, or you'll get a kernel panic when staff pulls the plug on a mounted device. Roland A variant of this approach that is filesystem independent would be to simply write an identifying zero-length file in the root of the removable backup drive: mount /mountpoint /dev/device cd /mountpoint touch ThisIsABackupDrive Your backup script can just look for the presence of the file ThisIsABackupDrive whenever it is checking to see whether the drive is mounted. Since this is done at the filename level rather than in the disk metadata, your script doesn't care/have to change if the removable drive is formatted NTFS, FAT32, ufs, etc. I use such disks myself for the exact reason you do, but I keep them FAT32 because pretty much everything can read this filesystem. Of course, FAT32 cannot preserve the file naming and permissions semantics of ufs, so I just make by backups into a tarball and then copy the tarball to the removable drive. Shameless Plug Follows I wrote a script to automate much of this: http://www.tundraware.com/Software/tbku/ HTH, -- Tim Daneliuk [EMAIL PROTECTED] PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Mounting smbfs At Boot Time
I have this in my /etc/fstab: [EMAIL PROTECTED]/SHARE /localmountsmbfs rw 0 0 This very nicely mounts an smbfs filesystem at boot time. HOWEVER, if SRV happens to not be up at the time FreeBSD boots, FBSD will halt and prompt to go into single user mode thinking that there is a catastrophic problem. I want the mount to occur if possible, and to be retried later if not possible at boot time. But I want this to occur automatically without my having to poke at the machine manually to see to it. 'noauto' was a tempting solution, but it seems not to work the way I'd expect. I added it to the entry, manually unmounted /localmount, and then did a 'mount -a'. The smbmount did not come back. Ideas anyone? -- Tim Daneliuk [EMAIL PROTECTED] PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Rsync From FreeBSD To Windows
I have an smbfs share that mounts at boot time on a 6.3-STABLE system. I want to rsync from a FreeBSD directory to the Windows share. For reasons I seem to not be able to discover, rsync insists on copying every file, every time. The exact command is: rsync -va /FreeBSD-dir-tree /windows-mount I have tried -O -no-p without success. I'm guessing this is a problem mapping the filesystem semantics from FreeBSD to SMB so that rsync always thinks the files on the destination SMB share are out of date, but I cannot seem to find the right magic to overcome this. Ideas? (And TIA), -- Tim Daneliuk [EMAIL PROTECTED] PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Rsync From FreeBSD To Windows
Tim Daneliuk wrote: I have an smbfs share that mounts at boot time on a 6.3-STABLE system. I want to rsync from a FreeBSD directory to the Windows share. For reasons I seem to not be able to discover, rsync insists on copying every file, every time. The exact command is: rsync -va /FreeBSD-dir-tree /windows-mount I have tried -O -no-p without success. I'm guessing this is a problem mapping the filesystem semantics from FreeBSD to SMB so that rsync always thinks the files on the destination SMB share are out of date, but I cannot seem to find the right magic to overcome this. Ideas? (And TIA), Inevitably, as soon as I posted this, I finally discovered the problem, which is worth describing here to save other people the same suffering: 1) The problem occurs when the SMB mount is a FAT formatted drive. In this case, it was a USB drive plugged into the WinXP machine being used as removable backup medium. 2) The problem occurs because the FAT file entry has insufficient resolution to maintain exactly the same timestamp as FreeBSD. i.e., FreeBSD (and I presume Linux or other Unix variants) have a finer timestamp resolution than does FAT. 3) The fix is to tell rsync to not be so fussy about exact timestamp matches: rsync -va --modify-window=1 src dest 4) This assumes that the FreeBSD server and the Windows machine hosting the share are more-or-less synchronized to the correct absolute time. If they are not, the --modify-window= parameter may have to be larger to accommodate the difference in what each machine thinks the correct time is. -- Tim Daneliuk [EMAIL PROTECTED] PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Trouble Upgrading gvfs
System: 6.3-STABLE as of 1300 UTC today. I've been having trouble with the gvfs port. First it started with libcdio: test -z /usr/local/libdata/pkgconfig || /usr/ports/sysutils/libcdio/work/libcdio-0.78.2/install-sh -d /usr/local/libdata/pkgconfig install -o root -g wheel -m 444 'libcdio.pc' '/usr/local/libdata/pkgconfig/libcdio.pc' install -o root -g wheel -m 444 'libiso9660.pc' '/usr/local/libdata/pkgconfig/libiso9660.pc' gmake[2]: Leaving directory `/usr/ports/sysutils/libcdio/work/libcdio-0.78.2' gmake[1]: Leaving directory `/usr/ports/sysutils/libcdio/work/libcdio-0.78.2' install-info --quiet /usr/local/info/libcdio.info /usr/local/info/dir === Running ldconfig /sbin/ldconfig -m /usr/local/lib === Registering installation for libcdio-0.78.2_1 This was failing, claiming that libcdio was already installed. I 'fixed' this by setting FORCE_PACKAGE_REGISTER. However, when it then goes on to do the gvfs upgrade, I get an installation of what appears to still be a broken port: === Returning to build of gvfs-0.2.3_3 Error: shared library cdio_paranoia.0 does not exist *** Error code 1 Stop in /usr/ports/devel/gvfs. *** Error code 1 The installation is forced at this point, but I suspect the port is broken. Ideas? -- Tim Daneliuk [EMAIL PROTECTED] PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Trouble Upgrading gvfs
Michael Johnson wrote: On Fri, Apr 18, 2008 at 1:58 PM, Tim Daneliuk [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: System: 6.3-STABLE as of 1300 UTC today. I've been having trouble with the gvfs port. First it started with libcdio: run 'make config' in libcdio and select PARANOIA then reinstall libcdio Yup that did it ... many thanks. -- Tim Daneliuk [EMAIL PROTECTED] PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Question About Ports Update Cycle
Is there some regular interval at which new ports are processed by the FreeBSD team? I submitted a port (for a very minor utility) 3/20/2008 but it is still not in the tree. I'm not complaining in the slightest - the folks who do this work are volunteering their time, and I get/respect that. I'm just curious if there is some window you have to hit to get stuff in. Just curious, not beefin', Tim Daneliuk [EMAIL PROTECTED] PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
ANN: 'tbku' 1.115 - Backup And System Imaging Tool
'tbku 1.115 is released and available at: http://www.tundraware.com/Software/tbku/ What Is 'tbku'? === 'tbku' is a utility for producing tarball backups of some- or all of your files. It is useful both for producing incremental backups or for systemwide images or snapshots. The tool can be run either from the command line or, more typically, as a cron job to automate system backup tasks. 'tbku' can also be used to capture system images which can then later be used to (re)provision other machines. The distribution includes explanations of how to image systems from a tarball produced with 'tbku', using FreeBSD and SUSE Linux as examples. 'tbku' uses standard utilities common on Unix-like systems, like 'tar', 'sed', and 'uname'. It uses no other special or custom tools. For this reason, it is highly portable across many variants of these systems. 'tbku' was originally developed as a backup tool for FreeBSD servers. Since then, it has been updated to also work with SUSE Linux, both servers and desktops. 'tbku' should work with little- or no modification on any other Unix-like system. For example, 'tbku' will run without modification (other than default locations) in a cywgin environment under MS-Windows. There is no charge for the use of 'tbku', but please take a moment to read the licensing terms. WHATSNEW For 'tbku' 1.115(Wed Mar 19 18:29:31 CDT 2008) -- First public release of program and docs. Tim Daneliuk [EMAIL PROTECTED] PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
6.3 And VIA 8237S Controller
I just bought a new MSI P4M900M2 mobo. It works just fine with both Windoze and SUSE Linux. When I tried booting 6.2 on it, it refused to set the drive (ad0 - I tried several different drives) into the higher speed UDMA modes. So, I downloaded 6.3, and it *seemed* to be fine. The drives come up as UDMA 100 or UDMA 133. But ... under long disk operations - say untaring a 2G tarball stored on a USB drive - I start to see this: ad0: WARNING WRITE_DMA UDMA ICRC ERROR And eventually: ad0: FAILURE WRITE_DMA Status=51 Error=84 g_vfs_done():ad0s1f ... What's going on here? Is there a known driver problem with the VIA chipsets? I took the two drives I tried this with, and stuck them in another machine - no problem, so I kind of doubt this is a drive problem. I have replaced the IDE cables as well. Again, this same mobo and drive combo worked flawlessly doing the same thing under SUSE Linux, so I'm thinking this is a software problem. Any help much appreciated... -- Tim Daneliuk [EMAIL PROTECTED] PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.3 And VIA 8237S Controller
Tim Daneliuk wrote: One point of clarification I neglected to mention in the description below. I have not actually installed FreeBSD on the disk. I paritioned/labeled the disk with the install disk, then rebooted the install disk, went into the Fixit environment and manually mounted ad0x under the various /mnt directories. I then insert the USB drive into the system that has a full image of FreeBSD from another machine on it, stored in a tarball, and mount it under /mnt/mnt. I then start to untar it (to load that image onto my newly labeled disk), and that's when I see the errors. The OS running at that time is the FreeBSD 6.3 Fixit environment. I just bought a new MSI P4M900M2 mobo. It works just fine with both Windoze and SUSE Linux. When I tried booting 6.2 on it, it refused to set the drive (ad0 - I tried several different drives) into the higher speed UDMA modes. So, I downloaded 6.3, and it *seemed* to be fine. The drives come up as UDMA 100 or UDMA 133. But ... under long disk operations - say untaring a 2G tarball stored on a USB drive - I start to see this: ad0: WARNING WRITE_DMA UDMA ICRC ERROR And eventually: ad0: FAILURE WRITE_DMA Status=51 Error=84 g_vfs_done():ad0s1f ... What's going on here? Is there a known driver problem with the VIA chipsets? I took the two drives I tried this with, and stuck them in another machine - no problem, so I kind of doubt this is a drive problem. I have replaced the IDE cables as well. Again, this same mobo and drive combo worked flawlessly doing the same thing under SUSE Linux, so I'm thinking this is a software problem. Any help much appreciated... -- Tim Daneliuk [EMAIL PROTECTED] PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.3 And VIA 8237S Controller - Also USB Drive Problem
Tim Daneliuk wrote: I just bought a new MSI P4M900M2 mobo. It works just fine with both Windoze and SUSE Linux. When I tried booting 6.2 on it, it refused to set the drive (ad0 - I tried several different drives) into the higher speed UDMA modes. So, I downloaded 6.3, and it *seemed* to be fine. The drives come up as UDMA 100 or UDMA 133. But ... under long disk operations - say untaring a 2G tarball stored on a USB drive - I start to see this: ad0: WARNING WRITE_DMA UDMA ICRC ERROR I have resolved this and thought I'd share with the class in case anyone else runs into the problem. It occurred to me that this chipset has been around long enough that it was very likely not a driver problem. I went back and replaced the IDE cable with another one known to be good and, voila', problem solved. What's weird about this is that the bad cable is a more-or-less new low profile round IDE cable I got from Tiger Direct a while back. It is the 20 variety which may be contributing noise to the problem. Weirder still is that neither Linux nor Windows seemed to have problems with it, though I did not test as thoroughly with those OSs. I'd guess that the FBSD driver is perhaps trying to squeeze the last bit of optimization out of the controller and thus drives the IDE bus to its limits, hence the problem shows up there. Either that, or I just didn't pound on the machine hard enough with Linux especially to see the problem. I should have guessed cable problem right away, but given the relative newness of the cable, that seemed unlikely. In a related note: I also discovered that the FreeBSD install CD Fixit environment does flakey things when you try to untar a large file from a USB drive plugged in through an external hub. Plugging the drive directly into one of the mobo ports made that problem go away. -- Tim Daneliuk [EMAIL PROTECTED] PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Using Install CD To Prepare Hard Disk
I would like to use the CD install menus to only prepare the hard disk (Partition, Label, Format) without actually installing anything on the drive. Can this be done? There seems to be no None option for Distributions, and I cannot find the right magic to make the installer go ahead and prepare the drive w/o resorting to at least a minimal install. I assume if the answer is no then that means this has to be done manually from the fixit command line Thanks, -- Tim Daneliuk [EMAIL PROTECTED] PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Using Install CD To Prepare Hard Disk
Chuck Swiger wrote: On Mar 13, 2008, at 3:28 PM, Tim Daneliuk wrote: I would like to use the CD install menus to only prepare the hard disk (Partition, Label, Format) without actually installing anything on the drive. Can this be done? There should be a (W)rite option on the various pages which let you at least partition the drive without installing the software. Yup that was the magic - I missed it entirely. The option appears in the label editor menu... Thanks! -- Tim Daneliuk [EMAIL PROTECTED] PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: telnet and rlogin problems
Grammas, August wrote: Rel: FreeBSD 6.2 Summary: I am unable to get either telnet or rlogin to function Details: To several of my PCs, that had been running 4.11, I have installed release 6.2. To the rc.conf, which was used for 4.11, I added: rcpbind_enable=YES rpc_lockd_enable=YES rpc_statd_enable=YES nfs_server_enable=YES nfs_client_enable=YES mountd_enable=YES ftpd_enable=YES Don't believe any of these are relevant to your stated problem. To hosts.allow, I added: rpcbind | ALL | allow Again, I don't think this is relevant to your stated problem. try adding: telnetd: whatever : ALLOW Note the use of ':' - I have no idea whether the wrappers will allow you to use '|'. As a general matter, service: ALL : ALLOW is very bad if your machine is connected to the internet. You really do want your allow statements to be in the form: service: exact list of machines or networks that should be allowed :ALLOW Now then ... one last thing: DON'T USE TELENT AND RLOGIN - get out of the habit of using them even on local networks. They are painfully bad security holes. Learn to use ssh instead. HTH, -- Tim Daneliuk [EMAIL PROTECTED] PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
