u*******n
发帖数: 119 | 1 Thanks at first.
I checked the file "main.c".
SYSV is only defined once in command line.
//sigh
A little hack. SYSV is defined twice (in command line and
in main()), so get rid of the one in main(). |
|
r****y
发帖数: 26819 | 2 While unrelated to Mac OS X, Apple came out with their version of UNIX,
called A/UX, in 1988. A/UX was a POSIX compliant system based on AT&T UNIX
System V (various releases) and BSD4.2/4.3, with a wide spectrum of features
(STREAMS, TCP/IP, FFS, job control, NFS with YP, SCCS, printing, X Window
System, compatibility with SYSV and BSD in addition to POSIX, and so on).
More importantly, A/UX combined various features of the Macintosh with Unix
- A/UX 3.x was a combination of the above mentioned ... 阅读全帖 |
|
g*********i
发帖数: 89 | 3 好像是这样的。
古老的unix都一律用buffer cache来缓存文件系统的所有数据。
modern unix alike的系统都只是用buffer来缓存文件系统元数据，就是指inode,
superblock,block bitmap,inode bitmap之类的数据。
而其他的实际文件数据都是通过page cache来实现的，而实际的管理大多数都是在虚拟
内存管理单元里面完成的。
这种机制好像是从solaris开始的，在sysV中引入的，而sun公司参与了大量的研究。 |
|
N****w
发帖数: 21578 | 4 This is Linux question... on Android.
I compile the pl2303.ko module from kernel 2.6.32 and android SDK, gcc 4.4.1
arm-eabi 4.4.0. Then
I push it to /system/lib/modules on tablet. But insmod failed on it:
# insmod pl2303.ko
insmod: init_module 'pl2303.ko' failed (Exec format error)
# file pl2303.ko
pl2303.ko: ELF 32-bit LSB relocatable, ARM, version 1 (SYSV), not stripped
existing modules on the system is also this type.
Other modules compiled by me all have this problem: uvcvideo.ko, gspca_mai |
|
m*********e
发帖数: 55 | 5 QA是QA变化是变化。
试想，假如你第一个用的Linux就是Fedora 16，你自然会说：
哦，你看linux总算有个能和SMF相提并论的东西了。其他的发行版也来跟进systemd吧
但是你用过sysv init，你就会说这东西真讨厌，为什么要变化。
每个操作系统都在变化，只是开源社区让你看到他们在变。如果你没有激情，那就别看。
没人强迫你升级你的F14 |
|
|
|
|
e*t
发帖数: 9 | 9 多谢了，问题已经找到。新系统的 ELF .hash 有变动。编译时需用 --hash-style=
sysv 设置成老版本方式。数学库本身，没有问题。下来要试试static |
|
m*******m
发帖数: 182 | 10 A little hack. SYSV is defined twice (in command line and
in main()), so get rid of the one in main(). |
|
m*******m
发帖数: 182 | 11 Hmm, can you double check this?
In my source code main.c, I see it in the line 101-109
block.
...
101 #ifdef SVR4
102 #define SYSV /* SVR4 is (approx) superset
of SVR3 */
103 #define ATT
104 #define USE_SYSV_UTMP
105 /*#ifndef sgi*/ /* this doesn't really work,
-ygz */
106 #define USE_TERMIOS
107 /*#endif*/
108 #define HAS_UTMP_UT_HOST
109 #endif
... |
|
m*******m
发帖数: 182 | 12 Hmm, can you double check this?
In my source code main.c, I see it in the line 101-109
block.
...
101 #ifdef SVR4
102 #define SYSV /* SVR4 is (approx) superset
of SVR3 */
103 #define ATT
104 #define USE_SYSV_UTMP
105 /*#ifndef sgi*/ /* this doesn't really work,
-ygz */
106 #define USE_TERMIOS
107 /*#endif*/
108 #define HAS_UTMP_UT_HOST
109 #endif
... |
|
r*****o
发帖数: 28 | 13 I have a shared data structure like this:
struct s {
int ...
...
char *text;
}
While creating the shmid, is it possible to dynamically
allocate the shared memory according to the size of the char*?
Or I should change the structure to:
struct s{
int ...
...
char text[MAXLENTH];
}
and shmid = shmget(..., sizeof(s), ...) ??? |
|
|
