06-08-2008
Expanding the root area on SCO 5.07?
I would like to expand the size of the root area, currently 800 kb, to a size of 2000 kb. Is that possible to do without loosing any data in the /u area? There is plenty of space available in the /u area.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
hello guys The company i work for just got a new client, there old datebase is in Unix SCO openserver 5.0.5.
The manager of this new client can login but not as a root , they forgot there own root password. There old IT company never gave it to them and they have no way of getting a hold of them
... (2 Replies)
Discussion started by: josramon
2 Replies
2. SCO
Does anyone know the maximum size of the root filesystem in SCO 5.0.7.?
It used to be 1GB max. SCO 5.0.7 with Development System does not fit in 1GB.
Is there a limit or has it been removed and the documenation just was not updated?
TIA,
Dan (2 Replies)
Discussion started by: njsco
2 Replies
3. SCO
Hi,
I have an openserver 5.0.0 machine in the office. The sysad of that machine left years ago without leaving the password to anyone.
I was wondering if someone has a copy of the boot / root diskettes (rescue) for this version? Or perhaps if anyone knows a download link / location in the... (0 Replies)
Discussion started by: marcpascual
0 Replies
4. SCO
We have SCO Unix (realease 5.0.5b),
Please advise which files can be safely deleted on the system root folder / to create space? These are mainly spool/message/history etc log files. Where they located and can they be deleted using rm?
The server has been operational for the past 4 years.
... (17 Replies)
Discussion started by: othman
17 Replies
5. SCO
Due to my own stupidity I managed to overwrite my /dev/root device using dd (don't ask).
Current state is
- Have current backup created using cpio (command used was 'find . -mount -depth -print|cpio -ocB > $TAPE')
- Once I realised what was happening powered off the server but this was too... (2 Replies)
Discussion started by: ok2
2 Replies
6. SCO
I'm "attempting" to install SCO 5.0.7 on an HP ML370 G4 server and am ready to bash the keyboard with head now. I keep getting the error message "WARNING hd: no root disk controller found" when running the bootable install cd.
I have a raid 5 array with an online spare created using 4 36.3 GB... (2 Replies)
Discussion started by: FrictionBurn
2 Replies
7. SCO
DEAR Team,
I need some help in sco open server 5
while booting server beloow message giving server
HTFS no space dev HD 1/42
Thanks
Skb (4 Replies)
Discussion started by: sudhir69
4 Replies
8. SCO
I have an old compaq running sco 3.2. the old IT guy died and we need to reset the password OR crack into the machine. I have tried mscreen and at exploits but can't seem to get them to work. I have access with other user accounts. This is a machine we own. (4 Replies)
Discussion started by: herot
4 Replies
9. SCO
Hi,
We have an old SCO Openserver 5.0.7 server that I have inherited that currently has two issues that we are trying to resolve.
1. We do not know the root password. I have contacted the old admin, looked for rescue disk and documentation but there appears to be nothing.
I have tried... (1 Reply)
Discussion started by: acerimmer10
1 Replies
10. SCO
I am working on a system that uses SCO Unix 5. I started later in this troubleshooting process so I have had to play catch up on some of the earlier mistakes that were made.
The HD was formatted using the SCSI controller cards bios.
I have 2 recovery floppies the boot and the root.
After... (19 Replies)
Discussion started by: graysona
19 Replies
LEARN ABOUT CENTOS
tpm_nvdefine
tpm_nvdefine(8) tpm_nvdefine(8)
NAME
tpm_nvdefine
SYNOPSIS
tpm_nvdefine [OPTIONS]
DESCRIPTION
tpm_nvdefine defines a new NVRAM area at the given index and of given size. The user has to provide the permissions that control access to
the NVRAM area.
Owner authentication is necessary once the NVRAM area 0xFFFFFFFF has been defined. The owner password may be provided on the command line
using the owner password option.
The following options are supported:
-h, --help
Display command usage info.
-v, --version
Display command version info.
-l, --log [none|error|info|debug]
Set logging level.
-u, --unicode
Use TSS UNICODE encoding for passwords to comply with applications using TSS popup boxes
-y, --owner-well-known
Use a secret of all zeros (20 bytes of zeros) as the owner's secret.
-z, --area-well-known
Use a secret of all zeros (20 bytes of zeros) as the NVRAM area's secret.
-o, --pwdo (optional parameter)
The owner password.
A password may be directly provided for example by using '--pwdo=password' or '-opassword'. If no password is provided with this option
then the program will prompt the user for the password.
-a, --pwda (optional parameter)
The NVRAM area password.
A password may be directly provided for example by using '--pwda=password' or '-apassword'. If no password is provided with this option
then the program will prompt the user for the password.
-i, --index
The index of the NVRAM area. The parameter must either be a decimal number or a hexadecimal number starting with '0x'.
To select the NVRAM area with index 0x100, the command line parameter should be '-i 0x100' or '--index 0x100'.
-s, --size
The size of the NVRAM area. The parameter must either be a decimal number or a hexadecimal number starting with '0x'.
-p, --permissions
The access permissions associated with the NVRAM area. The parameter must either be a decimal number or a hexadecimal number staring
with '0x'. It is possible to logically 'or' numbers or strings. The following strings are supported:
AUTHREAD
Reading requires NVRAM area authorization.
AUTHWRITE
Writing requires NVRAM area authorization.
PPREAD
Reading requires physical presence.
PPWRITE
Writing requires physical presence.
OWNERREAD
Reading requires owner authorization.
OWNERWRITE
Writing requires owner authorization.
GLOBALLOCK
A write to index 0 locks the NVRAM area until the next TPM_Startup(ST_CLEAR)
READ_STCLEAR
A read with size 0 on the same index prevents further reading until the next TPM_Startup(ST_CLEAR)
WRITE_STCLEAR
A write with size 0 to the same index prevents further writing until the next TPM_Startup(ST_CLEAR)
WRITEDEFINE
A write with size 0 to the same index locks the NVRAM area permanently
WRITEALL
The value must be written in a single operation
An example of a permission parameter is:
--permissions="OWNERREAD|OWNERWRITE"
SEE ALSO
tpm_nvread(8), tpm_nvwrite(8), tpm_nvrelease(8), tpm_nvinfo(8)
REPORTING BUGS
Report bugs to <trousers-users@lists.sourceforge.net>
TPM Management 2011-07-07 tpm_nvdefine(8)