Sponsored Content
Full Discussion: Mach drivers
Top Forums UNIX for Dummies Questions & Answers Mach drivers Post 302467621 by pludi on Saturday 30th of October 2010 10:11:32 AM
Old 10-30-2010
If it's not already supported: yes. And support depends on which implementation of the Mach concept you choose.
 

8 More Discussions You Might Find Interesting

1. Programming

state mach{ne...

hi, I am looking for some info on how can we implement state machines. Conceptually it appears to be good but while implementing it causes lot of confusion.. I have some doubts regarding this concept. (my explanation may look wired, as I am also not clear on this front) The commonly... (2 Replies)
Discussion started by: parasa
2 Replies

2. Solaris

Drivers

Hi guys, Im totally new to solaris 10, I've just installed it & it works fine However, I get no sound when playing cds. Am wondering where I get the solaris 10 drivers for my soundblaster live from and how to install them? Thx in advance. Frizz (0 Replies)
Discussion started by: Frizz
0 Replies

3. AIX

Drivers

I seem to be having a driver issue installing a PCI SCSI card. Any ideas where I can track these down.. I can't seem to find them on the OS install disk. I'm using AIX 5.3. cfgmgr: 0514-621 WARNING: The following device packages are required for device support but are not currently... (7 Replies)
Discussion started by: eth0
7 Replies

4. UNIX for Dummies Questions & Answers

drivers unix 5.01 is compatible with drivers epson fx-2190

Please, I'm From Argentina, And I Need To Know If The Drivers Of Program Unix, Version 5.01 Is Compatible Whit Drivers Of The Printer Epson Fx-2190 Thanks, And I Hope Yuor Answer. (0 Replies)
Discussion started by: juan alberghina
0 Replies

5. UNIX for Dummies Questions & Answers

Compiling Mach 3.0 Kernel

Hi, I am very new to this. I would like to compile the Mach 3.0 kernel. Can someone explain, step-by-step, how to turn all the Mach 3.0 kernel code into a single binary file that will run directly on an x86 computer? Also, once (and if) I get it working, what software works on it? My goal is... (2 Replies)
Discussion started by: dublinus
2 Replies

6. Shell Programming and Scripting

Help to mach "usb" exactly with sed or awk

HI experts I updated my question here to eg: $cat file ABC: abc ABC FDFD USB: usb usb_name usb_disk usbdriver USB PA: PA pa paa I want to how many usb exactly matched(not match usb_name or usbdriver) in the line cotains"USB:" thanks in advance (19 Replies)
Discussion started by: yanglei_fage
19 Replies

7. UNIX for Dummies Questions & Answers

Mach IPC

hey everyone, I'm reading a tutorial on the Mach kernel principles, however, the port and port rights part are kind of confusing to me. I don't know if the book has typos or something but it seems a bit contradictory. It says that "ports, themselves, are not named. It is the port rights that are"... (10 Replies)
Discussion started by: neur0n
10 Replies

8. Shell Programming and Scripting

egrep line with perfect mach

Hi Input File A L006 AL01 0 (OCK) L006 A006 0 (OCK) L011 AR11 1 (NLOCK) Input File B L006 AL01 0 (OCK) L006 A006 0 (OCK) Need Egrep Command for perfect Match Thanks (4 Replies)
Discussion started by: asavaliya
4 Replies
GET_END(3)						     Library Functions Manual							GET_END(3)

NAME
get_end, get_etext, get_edata - get values of UNIX link editor defined symbols SYNOPSIS
#include <mach-o/getsect.h> unsigned long get_end(); unsigned long get_etext(); unsigned long get_edata(); DESCRIPTION
These routines provide a stopgap measure to programs that use the UNIX link-editor defined symbols. Use of these routines is very strongly discouraged. The problem is that any program that is using UNIX link editor defined symbols (_end, _etext or _edata) is making assumptions that the program has the memory layout of a UNIX program. This is an incorrect assumption for a program built by the Mach-O link editor. The reason that these routines are provided is that if very minimal assumptions about the layout are used and the default format and memory layout of the Mach-O link editor is used to build the pro- gram, some things may work by using the values returned by these routines in place of the addresses of their UNIX link-editor defined sym- bols. So use at your own risk, and only if you know what your doing. Or better yet, convert the program to use the appropriate Mach or Mach-O functions. If you are trying to allocate memory use vm_allocate(2), if you are trying to find out about your address space use vm_region(2) and if you are trying to find out where your program is loaded use the dyld(3) functions. The values of the UNIX link-editor defined symbols _etext, _edata and _end are returned by the routines get_etext, get_edata, and get_end respectively. In a Mach-O file they have the following values: get_etext returns the first address after the (__TEXT,__text) section, note this my or may not be the only section in the __TEXT segment. get_edata returns the first address after the (__DATA,__data) section, note this my or may not be the last non-zero fill section in the __DATA segment. get_end returns the first address after the last segment in the executable, note a shared library may be loaded at this address. SEE ALSO
ld(1), dyld(3) Apple Computer, Inc. April 10, 1998 GET_END(3)
All times are GMT -4. The time now is 05:52 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy