06-15-2009
Porting OSE to Linux
Hi,
I was trying to port efs_mount(OSE system call) to a LInux.The efs_mount function is used to mount a volume on the indicated device dev.Upon successful completion of this OSE sytem call a volume manager (VM) will be available through which files on this volume are accessed. The Syntax for this syetm call is like :
Syntax: EfsStatus efs_mount(const char *volume, const char *format, const char *dev, const char *params);
Code :
vol_name= /st_dmx_dd0
drv_name= st_dmx_dd0
confm means Console format manager handling a serial channel.
efs_mount(vol_name, "confm", drv_name, "");
If it returns success, we open the file descriptors for input,output and std error and use it for further processing.
Could anyone help me out on how can I port the above system call to LINUX?
Thanks and Regards
Roshan
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi all,
i wanted to port some HP-UX code to linux. can anybody point to some documents or resources that would help me in doing the porting..
thanks in advance
Arun Prakash (0 Replies)
Discussion started by: arunprakash
0 Replies
2. Programming
Gents,
i'm a senior applications developer and need to port a Linux server application ( no additional / special libraries or unique header files ) to a HPUX enviroment.
Any chance to compile it on the Linux using flags to create an HPUX binary with gcc? (8 Replies)
Discussion started by: anak0nda
8 Replies
3. Linux
helo,
i m porting HP-UX socket application to Linux SSL-socket application.
I have use htonl() in HP-UX.
so when i use it in Linux, data transf is not done and application become soem time crashed.
now when i remove htonl() in linux, then i got data but it will not proper order or some data may... (1 Reply)
Discussion started by: amitpansuria
1 Replies
4. Linux
Hello All,
I have a code of DHCP which is implemented on Linux. During porting this code from Linux to VxWorks, I come up with following errors:-
jects\freedom\ap\udhcp\socket.c
C:\projects\freedom\ap\udhcp\socket.c: In function `read_interface':
C:\projects\freedom\ap\udhcp\socket.c:79:... (1 Reply)
Discussion started by: Sunny Shivam
1 Replies
5. IP Networking
DHCP Porting (2 Replies)
Discussion started by: Sunny Shivam
2 Replies
6. Programming
I am new to Linux programming and my work involves changing an abstraction layer which made Nucleus calls, to Linux calls.
In Case of Events Nucleus has calls like
NU_Set_Events()
NU_Retrieve_Events()
Can I use the POSIX thread conditional variables for Linux?
Can I use the System V calls... (1 Reply)
Discussion started by: taklubaba
1 Replies
7. Solaris
Hi all,
Has anyone experience with proting a Linux driver (C-code) to Solaris 10?
I have a Sunix SATA card with a inicio1622 chipset, but no driver available. From the website of inicio I downloaded the drivercode for Linux 2.4.
Having done some investigation I found a Solaris driver... (4 Replies)
Discussion started by: longwave
4 Replies
8. Shell Programming and Scripting
Can any one please help the use of "cu command in Solaris" and as well as in Linux :confused: (1 Reply)
Discussion started by: sabee.prakash
1 Replies
9. Programming
I am challenged with porting an old application from Solaris to Red Hat. The application uses Rogue Wave and I am searching for a Red Hat implementation. Your help is appreciated! (2 Replies)
Discussion started by: FunkyWinkerbean
2 Replies
10. Shell Programming and Scripting
I have a script which has commands that are located in different paths on my Linux o/s than on Solaris. For example, to make uname work, I need to do it this way in Solaris:
my $host= `/usr/bin/uname -n` But in Linux it is:
my $host = `/bin/uname -n`I have this issue with at least 5... (8 Replies)
Discussion started by: newbie2010
8 Replies
LEARN ABOUT DEBIAN
mount.crypt
mount.crypt(8) pam_mount mount.crypt(8)
Name
mount.crypt - mount a dm-crypt encrypted volume
Syntax
mount.crypt [-nrv] [-o options] device directory
Options
-o options
Set further mount options. mount.crypt will take out its own options it recognizes and passes any remaining options on to the under-
lying mount program. See below for possible options.
-n Do not update /etc/mtab. Note that this makes it impossible to unmount the volume by naming the container - you will have to pass
the mountpoint to umount.crypt.
-r Set up the loop device (if necessary) and crypto device in read-only mode. (The mount itself will necessarily also be read-only.)
Note that doing a remount using `mount /mnt -o remount,rw` will not make the mount readwrite. The crypto and loop devices will have
to be disassociated first.
-v Turn on debugging and be a bit more verbose.
Mount options
cipher The cryptsetup cipher used for the encrypted volume. This option is mandatory for PLAIN (non-LUKS) volumes. pmt-ehd(8) defaults to
creating volumes with "aes-cbc-essiv:sha256" as a cipher.
crypto_name
Select the name for the crypto device (optional). This option is currently only usable with dm-crypt systems.
fsck Run fsck on the container before mounting it.
fsk_cipher
The OpenSSL cipher used for the filesystem key. The special keyword "none" can be used to bypass decryption and pass the file con-
tents directly to libcryptsetup.
fsk_hash
The OpenSSL hash used for producing key and IV.
fstype The exact type of filesystem in the encrypted container. The default is to let the kernel autodetect.
hash The cryptsetup hash used for the encrypted volume. This defaults to no hashing, because pam_mount assumes EHD volumes with strong
and simple fskey generation.
keyfile
The path to the key file. This option is mandatory for "normal" crypto volumes and should not be used for LUKS volumes.
remount
Causes the filesystem to be remounted with new options. Note that mount.crypt cannot switch the underlying loop device (if applies)
or the crypto device between read-only and read-write once it is created; only the actual filesystem mount can be changed, with lim-
its. If the loop device is read-only, the crypto device will be read-only, and changing the mount to read-write is impossible. Sim-
ilarly, going from rw to ro will only mark the mount read-only, but not the crypto or loop device, thus making it impossible to set
the filesystem the crypto container is located on to read-only.
ro Same as the -r option.
verbose
Same as the -v option.
Obsolete mount options
This section is provided for reference.
loop This option used to set up a loop device, because cryptsetup(8) expects a block device. The option is ignored because mount.crypt
can figure this out on its own.
pam_mount 2011-12-15 mount.crypt(8)