09-10-2008
This is what is used on the HP Nxxx systems here. Depending one your system and HPUX version it may vary a little bit.
Reboot server
When booting at somepoint it will ask if you want to interupt booting "Interact".
press "y"
at the prompt type "hpux -is"
you will then need to mount the filesystem
This should work, unless you need to fsck the partitions.
mount -a
Then you will need to fingure what you can remove to clean up the file system.
10 More Discussions You Might Find Interesting
1. HP-UX
Hello,
I try to make a change on the root password on HP UX. I use sam but it didn't work here.
I try to login as root but I failed however, I login to my name and then change to su and su password then it is o.k
There is not much different from root and su but how do we use root?
Thanks so... (4 Replies)
Discussion started by: mle06
4 Replies
2. SCO
I have forgotten password of the system.I am having SCO Unixware 2.1.2.I am trying to change the password of the system by booting it with boot floopy.I edited the shadow file and made the password field blank.But I am not able to login.When I try to change the password of root or any id using... (1 Reply)
Discussion started by: girish_shukla
1 Replies
3. Solaris
Hi All,
I would like to find out when the root password changed last time..! :p Please guys help me Out (2 Replies)
Discussion started by: bullz26
2 Replies
4. Shell Programming and Scripting
Hi Friends.
I am new to scripting now i want to change the root password using the script with standard password.
which is the easy scripting to learn for the beginner, Thanks in advance. (2 Replies)
Discussion started by: kurva
2 Replies
5. Solaris
Hello All,
I have several solaris boxes running Solaris 8. When changing root passwords on them, all will simply ask for the new root password to change and of course to re-type the new password. One of the systems however asks for the existing root password before it will display the new password... (8 Replies)
Discussion started by: tferrazz
8 Replies
6. UNIX for Advanced & Expert Users
I tried to change the root password. but it shows the following error.
passwd: Authentication token manipulation error
passwd: password unchanged
If I login as a normal user that time I'm able to change my (user) password.
If I login as a ROOT then I'm not able to change the password root... (6 Replies)
Discussion started by: ungalnanban
6 Replies
7. HP-UX
I need to change password of a non-root user on HPUX. Due to some local policy, it is not allowing me to do so. I need to keep same (previous) password, as that is application user. Can I bypass policy for this time, for this user somehow ? I am root on this machine.
# uname -a
HP-UX thprnv02... (3 Replies)
Discussion started by: solaris_1977
3 Replies
8. Ubuntu
We are having a little problem on a server. We want that some users should be able to do e.g. sudo and become root, but with the restriction that the user can't change root password. That is, a guarantee that we still can login to that server and become root no matter of what the other users will... (2 Replies)
Discussion started by: 244an
2 Replies
9. UNIX for Dummies Questions & Answers
Hi,
I tired changing password for mqm user in linux server with root user.
But still I couldn't able to login mqm user with changed password.
Can anyone please help on this.
# passwd mqm
Thanks,
Anusha (4 Replies)
Discussion started by: Anusha M
4 Replies
10. UNIX for Beginners Questions & Answers
i do not have root on a solairs 10 server , however i do have the root role, i was wondering if I can change the root password as a a role with the passwd command? I have not tried yet.
and do i have to use the # chgkey -p afterwards?
i need to patch is why i am asking.
thanks (1 Reply)
Discussion started by: goya
1 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)