Sponsored Content
Operating Systems SCO Expanding the root area on SCO 5.07? Post 302245701 by jpradley on Friday 10th of October 2008 06:00:00 PM
Old 10-10-2008
get BackupEDGE from microlite.com, save your system,. then use RevcioverEDGE to change the disk arrangment before restoring.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Fortgot root password SCO 5.0.

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

Maximum size of root filesystem in SCO 5.0.7

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

sco openserver 5.0.0 boot / root disk

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

Root Folder Space Maintenance (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

Overwritten /dev/root -recovery of SCO OpenServer 5.0.4

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

SCO 5.0.7 no root disk controller found error during install

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

root out of space in sco 5

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

Reset root OR crack old sco 3.2 machine

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

SCO Openserver 5 root password and disk full

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

SCO unresponsive after root disk

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
IPFS(8) 						      System Manager's Manual							   IPFS(8)

NAME
ipfs - saves and restores information for NAT and state tables. SYNOPSIS
ipfs [-nv] -l ipfs [-nv] -u ipfs [-nv] [ -d <dirname> ] -R ipfs [-nv] [ -d <dirname> ] -W ipfs [-nNSv] [ -f <filename> ] -r ipfs [-nNSv] [ -f <filename> ] -w ipfs [-nNSv] -f <filename> -i <if1>,<if2> DESCRIPTION
ipfs allows state information created for NAT entries and rules using keep state to be locked (modification prevented) and then saved to disk, allowing for the system to experience a reboot, followed by the restoration of that information, resulting in connections not being interrupted. OPTIONS
-d Change the default directory used with -R and -W options for saving state information. -n Don't actually take any action that would affect information stored in the kernel or on disk. -v Provides a verbose description of what's being done. -i <ifname1>,<ifname2> Change all instances of interface name ifname1 in the state save file to ifname2. Useful if you're restoring state information after a hardware reconfiguration or change. -N Operate on NAT information. -S Operate on filtering state information. -u Unlock state tables in the kernel. -l Lock state tables in the kernel. -r Read information in from the specified file and load it into the kernel. This requires the state tables to have already been locked and does not change the lock once complete. -w Write information out to the specified file and from the kernel. This requires the state tables to have already been locked and does not change the lock once complete. -R Restores all saved state information, if any, from two files, ipstate.ipf and ipnat.ipf, stored in the /var/db/ipf directory unless otherwise specified by the -d option. The state tables are locked at the beginning of this operation and unlocked once complete. -W Saves in-kernel state information, if any, out to two files, ipstate.ipf and ipnat.ipf, stored in the /var/db/ipf directory unless otherwise specified by the -d option. The state tables are locked at the beginning of this operation and unlocked once complete. FILES
/var/db/ipf/ipstate.ipf /var/db/ipf/ipnat.ipf /dev/ipl /dev/ipstate /dev/ipnat SEE ALSO
ipf(8), ipl(4), ipmon(8), ipnat(8) DIAGNOSTICS
Perhaps the -W and -R operations should set the locking but rather than undo it, restore it to what it was previously. Fragment table information is currently not saved. BUGS
If you find any, please send email to me at darrenr@pobox.com IPFS(8)
All times are GMT -4. The time now is 05:16 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy