Re: SEBSD is dead?
On 17 December 2010 22:20, David Brodbeck g...@gull.us wrote: On Fri, Dec 17, 2010 at 8:02 AM, Jerry McAllister jerr...@msu.edu wrote: Anyway, SeLinux ain't 100% popular over there I noticed. Maybe it is just a matter of getting used to it. I got tired of reading the posts on it, so haven't figured out if they were substantive or just whiney. The problem with SELinux is it becomes very difficult to configure properly if you don't have a normal, out-of-the-box configuration. For example, I never did figure out how to keep it from blocking an rsync backup. I disabled it after that, because a system I can't back up is pretty useless no matter how secure it is. :) ___ 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 not sure if it will work on all linuxs but this works fine for me on centos in enforcing mode setsebool -P rsync_disable_trans on ___ 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: /usr/include/machine/endian.h:123: syntax error
On Thursday 16 December 2010 07:49:41 Dennis Glatting wrote:
While compiling a port...
btw uname -a
FreeBSD btw 8.2-PRERELEASE FreeBSD 8.2-PRERELEASE #55: Sat Dec 11 22:48:59
PST 2010 r...@btw:/usr/src/sys/amd64/compile/BTW amd64
btw# portupgrade devel/libgdata
snip
GISCAN gdata/GData-0.0.gir
/usr/include/machine/endian.h:123: syntax error, unexpected '{' in '
return (__extension__ ({ register __uint64_t __X = (_x); __asm (bswap %0
: +r (__X)); __X; }));' at '{'
I couldn't reproduce this. Do you have any special CFLAGS perhaps?
signature.asc
Description: This is a digitally signed message part.
Re: binutils problem? WAS [Re: static linking error: ELF binary type 0 not known. Exec format error. Binary file not executable.]
On Wed, Dec 15, 2010 at 06:58:50PM +0100, Tijl Coosemans wrote: On Monday 06 December 2010 16:16:30 Anton Shterenlikht wrote: On Mon, Dec 06, 2010 at 02:06:22PM +0100, Tijl Coosemans wrote: On Monday 29 November 2010 14:04:16 Anton Shterenlikht wrote: - Forwarded message from Marcel Moolenaar xcl...@mac.com - On Nov 10, 2010, at 5:32 AM, Anton Shterenlikht wrote: [ia64] ia64% file a.out a.out: ELF 64-bit LSB executable, IA-64, version 1 (SYSV), statically linked, not stripped [amd64] amd64% file a.out a.out: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), statically linked, for FreeBSD 9.0 (900023), not stripped The branding on ia64 is wrong. The executable is not marked as being a FreeBSD executable. It's declared as SYSV, whereas on amd64 it's properly declared as FreeBSD. This is a binutils problem. Anybody here can explain better what Marcel meant by binutils problem, and how to fix it? I've binutils-2.20.1_3 installed from devel/binutils. As a workaround you could manually brand the executable: brandelf -f 9 a.out this works fine. A fix has been committed to CURRENT, 8-STABLE and 7-STABLE. You should no longer have to brand executables manually. yes, just checked, many thanks. anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ 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
geli(8) and amd(8) working together?
Hi, I'm wondering how to get the most out of geli(8) encrypted volumes, in combination with something like amd(8) (but without the overhead of NFS, if at all possible) that mounts and umounts file systems only as needed. Basically, I'd like to mount a geli volume on demand (e.g. via amd), but when amd umounts the volume for lack of activity after some time, the geli provider should also forget (overwrite in RAM) the key, i.e. detach itself from the underlying geom provider. When amd tries to mount the geli volume again, geli should then ask for the key again (e.g. on the console). The idea is to protect geli encrypted partitions that are idle, so that even if the box is compromized and the power is maintained (somehow), encrypted partition(s) would still require a key after being idle for some time. Any way or ideas how to implement this? Thanks, -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ 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: avahi-app port build fails on one system, not other
On Friday 17 December 2010 6:44:01 pm Marco Beishuizen wrote: On Fri, 17 Dec 2010, Steven Friedrich wrote: I even tried portupgrade -fR avahi-app. Here's the last of the log: ... /libexec/ld-elf.so.1: Shared object libicui18n.so.38 not found, required by libavahi-glib.so.1 ... I'm having this too. I think this happens because the portupgrade of devel/icu installs a new version of libicui18n (libicui18n.so.46) and deletes the old one (so.38). Lots of ports still need the old version like libavahi-app. I'll try to make a symlink so.38 to so.46 and see what happens. Regards, Marco I tried portupgrade -fR avahi-app and several others ports. Eventuall, out of frustration I pkg_deinstall -f avahi-app\* and then portupgrade -n avahi-app was successful. I don't know why, but it worked. -- System Name: laptop2.StevenFriedrich.org Hardware:2.80GHz Intel Pentium 4 (HTT) with 2 GB memory OS version: FreeBSD 8.1-RELEASE-p2 i386 (5.1 MB kernel) Window Manager(s): kde4-4.5.4 X Window System: xorg-7.5X.Org X Server 1.7.5 FreeBSD Audio Driver (newpcm: 32bit 2009061500/i386) Installed devices: pcm0: Intel ICH6 (82801FB) (play/rec) default ___ 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: avahi-app port build fails on one system, not other
Apologies for top-post. Because many other ports depend on icu, it might be preferable to update everything at the same time rather than piecemeal: # portupgrade -rf icu-\* Caution: This'll take a while. Jud Sent from my iPhone On Dec 18, 2010, at 5:18 PM, Steven Friedrich free...@insightbb.com wrote: On Friday 17 December 2010 6:44:01 pm Marco Beishuizen wrote: On Fri, 17 Dec 2010, Steven Friedrich wrote: I even tried portupgrade -fR avahi-app. Here's the last of the log: ... /libexec/ld-elf.so.1: Shared object libicui18n.so.38 not found, required by libavahi-glib.so.1 ... I'm having this too. I think this happens because the portupgrade of devel/icu installs a new version of libicui18n (libicui18n.so.46) and deletes the old one (so.38). Lots of ports still need the old version like libavahi-app. I'll try to make a symlink so.38 to so.46 and see what happens. Regards, Marco I tried portupgrade -fR avahi-app and several others ports. Eventuall, out of frustration I pkg_deinstall -f avahi-app\* and then portupgrade -n avahi-app was successful. I don't know why, but it worked. -- System Name: laptop2.StevenFriedrich.org Hardware:2.80GHz Intel Pentium 4 (HTT) with 2 GB memory OS version: FreeBSD 8.1-RELEASE-p2 i386 (5.1 MB kernel) Window Manager(s): kde4-4.5.4 X Window System: xorg-7.5X.Org X Server 1.7.5 FreeBSD Audio Driver (newpcm: 32bit 2009061500/i386) Installed devices: pcm0: Intel ICH6 (82801FB) (play/rec) default ___ 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 ___ 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: avahi-app port build fails on one system, not other
On Sun, 19 Dec 2010, Jud wrote: Apologies for top-post. Because many other ports depend on icu, it might be preferable to update everything at the same time rather than piecemeal: # portupgrade -rf icu-\* Caution: This'll take a while. Jud This is what I did, but then several ports don't install because of the missing libicui18n.so.38. I eventually made a symlink so.38 to so.46 and after this all upgrades went well. Marco -- The Advertising Agency Song: When your client's hopping mad, Put his picture in the ad. If he still should prove refractory, Add a picture of his factory. ___ 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
where are the handbooks?
Which of the 8.1-RELEASE distribution sets contains the handbook, developer's handbook, porter's handbook, etc? I thought I had searched everywhere, but must have missed something. ___ 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: avahi-app port build fails on one system, not other
On Saturday 18 December 2010 6:23:30 pm Jud wrote: Apologies for top-post. Because many other ports depend on icu, it might be preferable to update everything at the same time rather than piecemeal: # portupgrade -rf icu-\* Caution: This'll take a while. Jud Sent from my iPhone On Dec 18, 2010, at 5:18 PM, Steven Friedrich free...@insightbb.com wrote: On Friday 17 December 2010 6:44:01 pm Marco Beishuizen wrote: On Fri, 17 Dec 2010, Steven Friedrich wrote: I even tried portupgrade -fR avahi-app. Here's the last of the log: ... /libexec/ld-elf.so.1: Shared object libicui18n.so.38 not found, required by libavahi-glib.so.1 ... I'm having this too. I think this happens because the portupgrade of devel/icu installs a new version of libicui18n (libicui18n.so.46) and deletes the old one (so.38). Lots of ports still need the old version like libavahi-app. I'll try to make a symlink so.38 to so.46 and see what happens. Regards, Marco I tried portupgrade -fR avahi-app and several others ports. Eventuall, out of frustration I pkg_deinstall -f avahi-app\* and then portupgrade -n avahi-app was successful. I don't know why, but it worked. ___ 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 I had been updating icu with protupgrade -fr icu, but ahavi-app failed to build. I went through trying to update avahi-app for a couple days to no avail. I finally deinstalled and reinstalled. ANd it worked. -- System Name: laptop2.StevenFriedrich.org Hardware:2.80GHz Intel Pentium 4 (HTT) with 2 GB memory OS version: FreeBSD 8.1-RELEASE-p2 i386 (5.1 MB kernel) Window Manager(s): kde4-4.5.4 X Window System: xorg-7.5X.Org X Server 1.7.5 FreeBSD Audio Driver (newpcm: 32bit 2009061500/i386) Installed devices: pcm0: Intel ICH6 (82801FB) (play/rec) default ___ 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: where are the handbooks?
On Sat, 18 Dec 2010 18:09:16 -0800 per...@pluto.rain.com wrote: Which of the 8.1-RELEASE distribution sets contains the handbook, developer's handbook, porter's handbook, etc? I thought I had searched everywhere, but must have missed something. Those distributions were a mystery to me the first time I installed FreeBSD and they still are. I've never understood why anyone would want to lump together significant ports installation with minor base-system penny-pinching in such an opaque way. In recent versions of sysinstall the documentation is packaged, so IIWY I'd just install the appropriate port or package. $ ls -d /usr/ports/misc/freebsd-doc-* /usr/ports/misc/freebsd-doc-all /usr/ports/misc/freebsd-doc-ja /usr/ports/misc/freebsd-doc-bn/usr/ports/misc/freebsd-doc-mn /usr/ports/misc/freebsd-doc-da/usr/ports/misc/freebsd-doc-nl /usr/ports/misc/freebsd-doc-de/usr/ports/misc/freebsd-doc-pl /usr/ports/misc/freebsd-doc-el/usr/ports/misc/freebsd-doc-pt /usr/ports/misc/freebsd-doc-en/usr/ports/misc/freebsd-doc-ru /usr/ports/misc/freebsd-doc-es/usr/ports/misc/freebsd-doc-sr /usr/ports/misc/freebsd-doc-fr/usr/ports/misc/freebsd-doc-tr /usr/ports/misc/freebsd-doc-hu/usr/ports/misc/freebsd-doc-zh_cn /usr/ports/misc/freebsd-doc-it/usr/ports/misc/freebsd-doc-zh_tw ___ 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
Realtime
I can't seem to get my head on straight with the realtime scheduling in FBSD despite all my googling. Can someone give me a pointer to the latest info? As far as I can tell FBSD has it, but only root(?) can use it? I'm interested in who can use it, and how to allow a user to obtain the realtime access. Cheers ___ 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: where are the handbooks?
RW rwmailli...@googlemail.com wrote: On Sat, 18 Dec 2010 18:09:16 -0800 per...@pluto.rain.com wrote: Which of the 8.1-RELEASE distribution sets contains the handbook, developer's handbook, porter's handbook, etc? Those distributions were a mystery to me the first time I installed FreeBSD and they still are. I've never understood why anyone would want to lump together significant ports installation with minor base-system penny-pinching in such an opaque way. ... the documentation is packaged ... $ ls -d /usr/ports/misc/freebsd-doc-* /usr/ports/misc/freebsd-doc-all /usr/ports/misc/freebsd-doc-ja ... Thanks. It would never have occurred to me to look for documentation of the _base_ system in a _port_. The porter's handbook, maybe, but the others? Seems to me like a POLA violation. Anyway, problem solved after fetching the package. ___ 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: /usr/include/machine/endian.h:123: syntax error
On Sat, 18 Dec 2010, Tijl Coosemans wrote:
On Thursday 16 December 2010 07:49:41 Dennis Glatting wrote:
While compiling a port...
btw uname -a
FreeBSD btw 8.2-PRERELEASE FreeBSD 8.2-PRERELEASE #55: Sat Dec 11 22:48:59
PST 2010 r...@btw:/usr/src/sys/amd64/compile/BTW amd64
btw# portupgrade devel/libgdata
snip
GISCAN gdata/GData-0.0.gir
/usr/include/machine/endian.h:123: syntax error, unexpected '{' in '
return (__extension__ ({ register __uint64_t __X = (_x); __asm (bswap %0
: +r (__X)); __X; }));' at '{'
I couldn't reproduce this. Do you have any special CFLAGS perhaps?
Not intentionally:
btw# cat /etc/make.conf
USA_RESIDENT= YES
FORCE_PKG_REGISTER= YES
HAVE_MOTIF= YES
WITHOUT_PERL_MALLOC=YES
WITH_THREADS= YES
WITHOUT_SAMBA= YES
WITHOUT_LDAP= YES
WITHOUT_NLS=YES
OVERRIDE_LINUX_BASE_PORT=f10
OVERRIDE_LINUX_NONBASE_PORTS=f10
WITH_TCL_VER=85
SENDMAIL_CFLAGS=-I/usr/local/include/sasl -DSASL
SENDMAIL_LDFLAGS=-L/usr/local/lib
SENDMAIL_LDADD=-lsasl2
# added by use.perl 2010-12-15 20:47:32
PERL_VERSION=5.12.2
___
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
