05-29-2012
Would it be possible for you to show us the "netstat -in" output on bothe the AIX and the FreeBSD boxes?
"netstat -in" shows the interface details with the name of the NIC. How are you getting "link#" as the output? Something is fishy here.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
i'm following the, "How to setup and secure Snort, MySQL and Acid on FreeBSD 4.6 Release" off of the snort.org website.
in the documentation it says snort should be installed through the following:
-----
make -DWITH_MYSQL -DWITH_FLEXRESP ; make install
-----
later it says to do the... (13 Replies)
Discussion started by: xyyz
13 Replies
2. UNIX for Dummies Questions & Answers
I have been using Linux for 3 years now, and I think I am getting enough knowledge (and confidence) to try some more 'traditional' unix variants. I installed FreeBSD 5.0-CURRENT. I have a couple of questions for the time being:
1) Frequently when I need to compile software packages they can't... (16 Replies)
Discussion started by: cbkihong
16 Replies
3. UNIX for Dummies Questions & Answers
I'm a n00b to UNIX, but I'm making much progress. My preferred browser is Opera, and the ported version with FBSD 5.4 is Opera 7.54. Because I lost my opera key, I'd prefer to have version 8 which does not require a key. How can I install the .tar.gz on FreeBSD? I am somewhat familiar with... (2 Replies)
Discussion started by: DrgnInterrupted
2 Replies
4. BSD
All,
I am a bit of a BSD newbie and haven't really played with it for years, but I have had a recent situation whereby someone attempted to load a custom kernel module and ended up breaking my BSD server.
I managed to fix it by doing the following:
Booting into loader mode:
unload
set... (3 Replies)
Discussion started by: drbabbers
3 Replies
5. Solaris
I have installed OpenSolaris SVN_100a on my Hp pavillion a6230n a cuple of days ago.
The network administration panel under Syste. Administration >> network is missing.
How do i fix this issue?
------------------ next ----------------------
File sharing
I have a macbook 13''... (0 Replies)
Discussion started by: FloridaBSD
0 Replies
6. Web Development
Server: FreeBSD 7.2-RELEASE
MYSQL Version: MYSQL 5.1.36
PHP Version: 5.2.10 (apache2handler)
IP.Board Version: v3.0.2
Safe Mode: OFF
For the most part previously IP.Board, forum software, has run fine without any issues. Regular web pages and .php pages seem to load fine without any issues.... (2 Replies)
Discussion started by: Dark Severance
2 Replies
7. UNIX for Dummies Questions & Answers
I wrote a script to batch-create directories with .htaccess and .htpasswd files.
I am using the following line to create the .htpasswd file:
htpasswd -cb .htpasswd $USER $PASS
However, I keep getting this message in return:
Usage: htpasswd passwordfile username
The -c flag creates a new... (1 Reply)
Discussion started by: Spetnik
1 Replies
8. BSD
Hello Friends,
I'm a newbie to FreeBSD. Trying to implement a IEEE paper : Energy consumption models for ad-hoc terminals (Computers).
The test setup with 3 Computers & Wireless NIC goes as follows:
Transmitter (A) --------------- Forwarder (B) -------------- Receiver (C)
10.0.1.1/24 ... (0 Replies)
Discussion started by: Govindaraj
0 Replies
9. BSD
Hi!
I have a major issue with FreeBSD 7.1 i386.
We did a change in our Unix env where we exchanged home storage from a NetAPP running udp to a NetAPP running tcp.
Now I cant mount homedirs since NFS/AMD seem to fallback to udp :(
Trying to force it with amd options nfs_proto=tcp and so on.
... (0 Replies)
Discussion started by: Esaia
0 Replies
10. BSD
I just got FreeBSD up and running with an XFCE desktop on an old Gateway laptop. It works great, except the wireless setup is scaring me. I can connect to my home WiFi fine most of the time, but I'm concerned about other WiFi that I will need to connect to away from home.
I understand that I can... (1 Reply)
Discussion started by: BrentBANKS
1 Replies
AOUT(4) BSD Kernel Interfaces Manual AOUT(4)
NAME
aout -- kernel support for executing binary files in legacy a.out format
SYNOPSIS
kldload a.out
DESCRIPTION
The a.out(5) executable format was used before the release of FreeBSD 3.0. Since i386 was the only supported architecture at that time,
a.out(5) executables can only be activated on platforms that support execution of i386 code, such as i386 and amd64.
To add kernel support for old syscalls and old syscall invocation methods, place the following options in the kernel configuration file:
options COMPAT_43
options COMPAT_FREEBSD32
The COMPAT_FREEBSD32 option is only required on 64-bit CPU architectures.
The aout.ko module needs to be loaded with the kldload(8) utility in order to support the a.out(5) image activator:
kldload aout
Alternatively, to load the module at boot time, place the following line in loader.conf(5):
aout_load="YES"
The a.out(5) format was mainstream quite a long time ago. Reasonable default settings and security requirements of modern operating systems
today contradict the default environment of that time and require adjustments of the system to mimic natural environment for old binaries.
The following sysctl(8) tunables are useful for this:
security.bsd.map_at_zero Set to 1 to allow mapping of process pages at address 0. Some very old ZMAGIC executable images require
text mapping at address 0.
kern.pid_max Old versions of FreeBSD used signed 16-bit type for pid_t. Current kernels use 32-bit type for pid_t, and
allow process id's up to 99999. Such values cannot be represented by old pid_t, mostly causing issues for
processes using wait(2) syscalls, for example shells. Set the sysctl to 30000 to work around the problem.
kern.elf32.read_exec Set to 1 to force any accessible memory mapping performed by 32-bit process to allow execution, see mmap(2).
Old i386 CPUs did not have a bit in PTE which disallowed execution from the page, so many old programs did
not specify PROT_EXEC even for mapping of executable code. The sysctl forces PROT_EXEC if mapping has any
access allowed at all. The setting is only needed if the host architecture allows non-executable mappings.
SEE ALSO
execve(2), a.out(5), elf(5), sysctl(8)
HISTORY
The a.out(5) executable format was used on ancient AT&T UNIX and served as the main executable format for FreeBSD from the beginning up to
FreeBSD 2.2.9. In FreeBSD 3.0 it was superseded by elf(5).
AUTHORS
The aout manual page was written by Konstantin Belousov <kib@FreeBSD.org>.
BUGS
On 64bit architectures, not all wrappers for older syscalls are implemented.
BSD
August 14, 2012 BSD