No, all the other slices of the disk were cleared and re-created. The upgrade process from RHEL 6.X to RHEL 7.X is destructive and is effectively a new installation - the rest of the disk entries from the kick start file are.
I'm guessing that this is some kind of problem with the installer, where if you match an existing partition exactly the format fails - even if you select the format option.
Hello all,
1) I want to have a GUI application that will call Unix shell scripts,
2) that GUI application should be able to reside on windows ( if possible) and then call Unix shell script either directly or through a server residing on unix.
That is for example.
If a is windows gui (... (1 Reply)
Hey ppl,
I've been asked to automate the build and test process for my team at office.we work on Linux and use Perforce for SCM. I've just joined this company and dont have much knowledge on unix scripts. Could someone tell me how to go about doing this? (0 Replies)
Hey ppl,
I've been asked to automate the build and test process for my team at office.we work on Linux and use Perforce for SCM. I've just joined this company and dont have much knowledge on unix scripts. Could someone tell me how to go about doing this?:confused: (8 Replies)
Hi,
I heard a command that can collect all RHEL 5 log in a single compress file before I forget.
Does any body know...What the command is ?
Thanks. (4 Replies)
Hi all,
Im studying rhcsa as of now, so yum installation and dependencies are messing me to not workit out.
i have dual os, win 7 & rhel 6.
i have tried this installation of vsftpd package with rhel 6 dvd in VM rhel 6 in win 7 as well as host rhel 6.still the same issue.
below error... (6 Replies)
Hi Friends,
So we have an internal link in my project. We generally login into it with our ids , then enter some generic values to check whether the functionality is working fine. If it is fine, the webpage delivers a successful preview or else throws error.
What i want to do is write a... (3 Replies)
I have 2 RHEL 5.9 system where customized applications are running.
These 2 servers are with in a network (LAN) with each other.One application in say Server 1 can talk to another application in server 2 and vice versa.
The applications are exchanging data among each other.
Recently I am... (0 Replies)
Hello,
In our Production system one process is in S state(interruptible)and after killing and restarting the process gives 'advertise error'.
This error goes after rebooting the Server.
I have RHEL 5.9 (tikanga) OS in our server.
We tried debugging the issue with the help of 'strace' command... (9 Replies)
Discussion started by: Rohits
9 Replies
LEARN ABOUT DEBIAN
pmt-ehd
pmt-ehd(8) pam_mount pmt-ehd(8)Name
pmt-ehd - create an encrypted disk image
Syntax
pmt-ehd [-DFx] [-c fscipher] [-h hash] [-k fscipher_keybits] [-t fstype] -f container_path -s size_in_mb
Options
Mandatory options that are absent are inquired interactively, and pmt-ehd will exit if stdin is not a terminal.
-D Turn on debugging strings.
-F Force operation that would otherwise ask for interactive confirmation. Multiple -F can be specified to apply more force.
-c cipher
The cipher to be used for the filesystem. This can take any value that cryptsetup(8) recognizes, usually in the form of "cipher-
mode[-extras]". Recommended are aes-cbc-essiv:sha256 (this is the default) or aes-xts-essiv:sha256.
-f path
Store the new disk image at path. If the file already exists, pmt-ehd will prompt before overwriting unless -F is given. If path
refers to a symlink, pmt-ehd will act even more cautious.
-h hash
Message digest/hash used for key derivation in the PBKDF2 stage. The default is sha512.
-i cipher
(This option had been removed in pam_mount/pmt_ehd 2.11.)
-k keybits
The keysize for the cipher specified with -c. Some ciphers support multiple keysizes, AES for example is available with at least the
keysizes 192 and 256. Defaults to 256 (to match aes-cbc-essiv). Note that XTS uses two keys, but drawn from the same key material,
so aes-cbc-256 is equivalent to aes-xts-512, and aes-cbc-128 is to aes-xts-256.
-p path
(This option had been removed in pam_mount/pmt_ehd 2.11.)
-s size
The initial size of the encrypted filesystem, in megabytes. This option is ignored when the filesystem is created on a block device.
-t fstype
Filesystem to use for the encrypted filesystem. Defaults to xfs.
-u user
Give the container and fskey files to user (because the program is usually runs as root, and the files would otherwise retain root
ownership).
-x Do not initialize the container with random bytes. This may impact secrecy.
Description
pmt-ehd can be used to create a new encrypted container, and replaces the previous mkehd script as well as any HOWTOs that explain how to
do it manually. Without any arguments, pmt-ehd will interactively ask for all missing parameters. To create a container with a size of 256
MB, use:
pmt-ehd -f /home/user.cont -s 256
pam_mount 2011-Aug-05 pmt-ehd(8)