08-20-2014
10 More Discussions You Might Find Interesting
1. Programming
Hi
I'm getting
ld: fatal: option -h and building a dynamic executable are incompatible
ld: fatal: Flags processing errors
When I run
ld -shared -L/usr/dt/lib -lDtSvc -o builtin.so Workspace.o
after running
gcc -fPIC -I/usr/X11R6/include -I/usr/dt/include -c Workspace.c
I'm... (6 Replies)
Discussion started by: laho
6 Replies
2. Red Hat
Hi All,
I am trying to send a mail from my application through SMTP in solaris 9 but unable to send a mail.Same code is able to send mail in Windows.
As unix has more security,So as per me,it is due to security reason..
So please let me know what I need to do to send a mail properly.
what... (5 Replies)
Discussion started by: smartgupta
5 Replies
3. Shell Programming and Scripting
The date increment worked fine until date reached 25/10, which is DLS change date.
/bin/date --date="091025 1 day" +%y%m%d;
the output is 091025
Is this a bug or something missing from the code ! (3 Replies)
Discussion started by: rajbravo
3 Replies
4. UNIX for Advanced & Expert Users
Hello everyone:
I've made a program for AIX, but it's unable to run, by running ld I got the following screen:
ld MyApp
ld: 0711-317 ERROR: Undefined symbol: getenv
ld: 0711-317 ERROR: Undefined symbol: _iob
ld: 0711-317 ERROR: Undefined symbol: fprintf
ld: 0711-317 ERROR: Undefined... (1 Reply)
Discussion started by: edgarvm
1 Replies
5. UNIX for Dummies Questions & Answers
Hi All,
I am very new to unix and to this forum.Suggest me a solution in fixing the below issue.
Actually ia m executing java program through script.
The command is like
java pgm &
The above cmd runs the java program continuous as a background thread.
This script is executed from a... (1 Reply)
Discussion started by: sahan
1 Replies
6. Solaris
I have two physical servers, with zones that mount local storage.
We were using "raw device" in the zonecfg to point to a metadevice on the global zone (it was not mounted in the global zone at any point).
It failed to mount on every boot because the directory existed in the zone.
I... (6 Replies)
Discussion started by: BG_JrAdmin
6 Replies
7. Programming
Incompatiblity of the code due to CC compiler version mismatch.
I have a machine with
Machine A-- Operating System:SunOs 5.8 Generic_117350-45 sun4u sparc SUNW,Ultra-80(solaris 5.8)
CC Compiler:CC: WorkShop Compilers 4.2 16 Jun 1998 C++ 4.2 patch 104631-07
we have compiled C++... (36 Replies)
Discussion started by: Revathi R
36 Replies
8. SCO
Dear Community!
i try to instaled the sco 6 in hp proliant ML350g8
but unsucces,
the trouble when i do instaled it undetected hardisk
please help me
:(:o (7 Replies)
Discussion started by: mnr
7 Replies
9. UNIX for Beginners Questions & Answers
Hello All,
OS: openSUSE 13.1 (Bottle) (armv7hl)
PC: CuBox-i (*mini-pc)
The PC in question is a CuBox-i mini-pc. Since this PC doesn't have a battery, everytime the PC reboots the hardware clock is reset back to the same date every time, which is "2014-07-08 00:00".
I have NTP configured... (5 Replies)
Discussion started by: mrm5102
5 Replies
10. Shell Programming and Scripting
rsync --delay-updates -F --compress --archive --rsh='/usr/bin/ssh -t -a -x' /web/admin/Transfer/data/ user1@destserver1:/tmp/testf
rsync version on sender server is:3.0.9
rsync version on sender server is:3.0.6
Linux sourceserver1 3.10.0-693.17.1.el7.x86_64 #1 SMP Sun Jan 14 10:36:03 EST... (1 Reply)
Discussion started by: mohtashims
1 Replies
LEARN ABOUT NETBSD
compat_30
COMPAT_30(8) BSD System Manager's Manual COMPAT_30(8)
NAME
compat_30 -- setup procedure for backward compatibility on post-3.0 releases
SYNOPSIS
options COMPAT_30
DESCRIPTION
The compat_30 module allows NetBSD to run NetBSD 3.0 executables.
The support is present if the kernel was built with option COMPAT_30. It is not available as a loadable module.
Static executables typically need no additional setup. Dynamic binaries may require shared libraries whose major version number changed
since NetBSD 3.0, which are listed below. A shadow directory under /emul is not used; the libraries can be obtained from a NetBSD 3.0 dis-
tribution and installed in the original directories shown, as the major version number in the file name will prevent conflicts. If an
upgrade installation from NetBSD 3.0 has been done and these libraries are still present, nothing more need be done.
Libraries needed from 3.0
/lib/libcrypto.so.2.1 /lib/libcrypto.so.2
/usr/lib/libcrypto.so.2.1 /usr/lib/libcrypto.so.2
/lib/libevent.so.0.2 /lib/libevent.so.0
/usr/lib/libevent.so.0.2 /usr/lib/libevent.so.0
/usr/lib/libg2c.so.2.0 /usr/lib/libg2c.so.2
/usr/lib/libkadm.so.5.0 /usr/lib/libkadm.so.5
/usr/lib/libkafs.so.6.0 /usr/lib/libkafs.so.6
/usr/lib/libkdb.so.5.0 /usr/lib/libkdb.so.5
/usr/lib/libkrb5.so.19.1 /usr/lib/libkrb5.so.19
/usr/lib/libkrb.so.6.0 /usr/lib/libkrb.so.6
/usr/lib/libkstream.so.2.0 /usr/lib/libkstream.so.2
/usr/lib/libmagic.so.0.1 /usr/lib/libmagic.so.0
/usr/lib/libpcap.so.1.4 /usr/lib/libpcap.so.1
/lib/libradius.so.0.0 /lib/libradius.so.0
/usr/lib/libradius.so.0.0 /usr/lib/libradius.so.0
/usr/lib/libssh.so.1.0 /usr/lib/libssh.so.1
/usr/lib/libssl.so.3.0 /usr/lib/libssl.so.3
/usr/lib/libstdc++.so.5.0 /usr/lib/libstdc++.so.5
/lib/libz.so.0.4 /lib/libz.so.0
/usr/lib/libz.so.0.4 /usr/lib/libz.so.0
/usr/lib/libamu.so.2.1 /usr/lib/libamu.so.2
IMPLEMENTATION NOTES
COMPAT_30 enables the NetBSD 3.0 versions of the following system calls, whose syscall numbers and argument structures were changed after the
3.0 release to accommodate 64-bit filesystems: fhstat(2), fstat(2), getdents(2), lstat(2), stat(2).
The filehandle structure (formerly fhandle_t) was made opaque to userland and variable-sized. A fh_size argument was added to related
syscalls: fhstat(2), fhstatvfs(2), fhstatvfs1(2), fhopen(2), getfh(2). This changes the API and ABI of those syscalls, COMPAT_30 enables
binary compatibility with the old ABI. Source compatibility is not provided, as use of those syscalls is supposed to be rare.
The error code from the socket(2) syscall changed from EPROTONOSUPPORT to EAFNOSUPPORT in the case of an unsupported address family.
COMPAT_30 enables binary compatibility with the old ABI. Source compatiblility is not provided.
The struct ntptimeval used by ntp_gettime(2) changed with the implementation of timecounters.
SEE ALSO
config(1), fhstat(2), fstat(2), getdents(2), lstat(2), stat(2), options(4)
HISTORY
NetBSD offers back-compatibility options back to NetBSD 0.9, but the first to be documented with a manual page is compat_30.
BUGS
The compatible getdents(2) is unable to see directory entries beneath the top layer of a union, even though the real 3.0 getdents() did not
have that problem.
SECURITY CONSIDERATIONS
Programs with security impact that receive incorrect directory contents from getdents() may behave improperly, as when they are unable to
find, or find the wrong versions of, important files.
BSD
December 15, 2007 BSD