GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Rock Ridge cdroms
Operating System - HP-UX
1847276
Members
3344
Online
110263
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-19-2003 02:13 AM
04-19-2003 02:13 AM
Rock Ridge cdroms
I wanto to master a depot directory to HP-UX cd. I used
mkisofs and it seems to work
if I mount the CD with rock ridge extension
Is it necessary use the rrip on mastering ? Is there any other mode to master a CD that contains a depot tree ?
Thanks
mkisofs and it seems to work
if I mount the CD with rock ridge extension
Is it necessary use the rrip on mastering ? Is there any other mode to master a CD that contains a depot tree ?
Thanks
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-19-2003 04:54 PM
04-19-2003 04:54 PM
Re: Rock Ridge cdroms
The basic ISO-9660 standard will create files with a maximum of 8 characters and a 3 character extension--which won't work for HP-UX as many files and directories exceed these value. Rock Ridge extensions allow for long names and must be mastered with rrip options as well as mounted with the rrip option in HP-UX. Note that prior to 11.0, you'll have to use the cumbersome PFS tools. For 11.0 and 11i, you can apply the latest RockRidge patches and the CD will mount (and filenames appear) correctly.
Bill Hassell, sysadmin
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-19-2003 09:09 PM
04-19-2003 09:09 PM
Re: Rock Ridge cdroms
Here are some scripts for rock ridge. You can't use these mounts on HP cd's
This is a start stop script in /sbin/init.d
#!/sbin/sh
#
# @(#) $Revision: 82.1 $
#
# NOTE: This script is not configurable! Any changes made to this
# script will be overwritten when you upgrade to the next
# release of HP-UX.
#
# WARNING: Changing this script in any way may lead to a system that
# is unbootable. Do not modify this script.
#
#
#
# Allowed exit values:
# 0 = success; causes "OK" to show up in checklist.
# 1 = failure; causes "FAIL" to show up in checklist.
# 2 = skip; causes "N/A" to show up in the checklist.
# Use this value if execution of this script is overridden
# by the use of a control variable, or if this script is not
# appropriate to execute for some other reason.
# 3 = reboot; causes the system to be rebooted after execution.
# 4 = background; causes "BG" to show up in the checklist.
# Use this value if this script starts a process in background mode.
# Input and output:
# stdin is redirected from /dev/null
#
# stdout and stderr are redirected to the /etc/rc.log file
# during checklist mode, or to the console in raw mode.
PATH=/usr/sbin:/usr/bin:/sbin
export PATH
export LOGFILE=/etc/rc.log
# NOTE: If your script executes in run state 0 or state 1, then /usr might
# not be available. Do not attempt to access commands or files in
# /usr unless your script executes in run state 2 or greater. Other
# file systems typically not mounted until run state 2 include /var
# and /opt.
rval=0# Check the exit value of a command run by this script. If non-zero, the
# exit code is echoed to the log file and the return value of this script
# is set to indicate failure.
set_return() {
x=$?
if [ $x -ne 0 ]; then
echo "EXIT CODE: $x"
rval=1 # script FAILed
fi
}
# Kill the named process(es).
# $1=
killproc() { # kill the named process(es)
echo stopping $1
pid=`/usr/bin/ps -e |
/usr/bin/grep "$1" |
/usr/bin/sed -e 's/^ *//' -e 's/ .*//'`
[ "$pid" != "" ] && kill $pid
}
findproc() { # return pid of the named process(es)
pid=`/usr/bin/ps -e |
/usr/bin/grep "$1" |
/usr/bin/sed -e 's/^ *//' -e 's/ .*//'`
}
case $1 in
'start_msg')
# Emit a _short_ message relating to running this script with
# the "start" argument; this message appears as part of the checklist.
echo "Starting the pfs_mount subsystem"
;;
'stop_msg')
# Emit a _short_ message relating to running this script with
# the "stop" argument; this message appears as part of the checklist.
echo "Stopping the pfs_mount subsystem"
;;
'start') # source the system configuration variables
# Execute the commands to start your subsystem
/usr/sbin/pfs_mountd & >> $LOGFILE
/usr/sbin/pfsd & >> $LOGFILE
:
;;
'stop')
# source the system configuration variables
:
# Execute the commands to stop your subsystem
for i in pfsd pfs_mountd
do
killproc $i
done
;;
*) echo "usage: $0 {start|stop|start_msg|stop_msg}"
rval=1
;;
esac
exit $rval
It sets up the daemons you need to run.
after that its just pfs_mount /cdrom
You are rock ridge ready..
SEP
This is a start stop script in /sbin/init.d
#!/sbin/sh
#
# @(#) $Revision: 82.1 $
#
# NOTE: This script is not configurable! Any changes made to this
# script will be overwritten when you upgrade to the next
# release of HP-UX.
#
# WARNING: Changing this script in any way may lead to a system that
# is unbootable. Do not modify this script.
#
#
#
# Allowed exit values:
# 0 = success; causes "OK" to show up in checklist.
# 1 = failure; causes "FAIL" to show up in checklist.
# 2 = skip; causes "N/A" to show up in the checklist.
# Use this value if execution of this script is overridden
# by the use of a control variable, or if this script is not
# appropriate to execute for some other reason.
# 3 = reboot; causes the system to be rebooted after execution.
# 4 = background; causes "BG" to show up in the checklist.
# Use this value if this script starts a process in background mode.
# Input and output:
# stdin is redirected from /dev/null
#
# stdout and stderr are redirected to the /etc/rc.log file
# during checklist mode, or to the console in raw mode.
PATH=/usr/sbin:/usr/bin:/sbin
export PATH
export LOGFILE=/etc/rc.log
# NOTE: If your script executes in run state 0 or state 1, then /usr might
# not be available. Do not attempt to access commands or files in
# /usr unless your script executes in run state 2 or greater. Other
# file systems typically not mounted until run state 2 include /var
# and /opt.
rval=0# Check the exit value of a command run by this script. If non-zero, the
# exit code is echoed to the log file and the return value of this script
# is set to indicate failure.
set_return() {
x=$?
if [ $x -ne 0 ]; then
echo "EXIT CODE: $x"
rval=1 # script FAILed
fi
}
# Kill the named process(es).
# $1=
killproc() { # kill the named process(es)
echo stopping $1
pid=`/usr/bin/ps -e |
/usr/bin/grep "$1" |
/usr/bin/sed -e 's/^ *//' -e 's/ .*//'`
[ "$pid" != "" ] && kill $pid
}
findproc() { # return pid of the named process(es)
pid=`/usr/bin/ps -e |
/usr/bin/grep "$1" |
/usr/bin/sed -e 's/^ *//' -e 's/ .*//'`
}
case $1 in
'start_msg')
# Emit a _short_ message relating to running this script with
# the "start" argument; this message appears as part of the checklist.
echo "Starting the pfs_mount subsystem"
;;
'stop_msg')
# Emit a _short_ message relating to running this script with
# the "stop" argument; this message appears as part of the checklist.
echo "Stopping the pfs_mount subsystem"
;;
'start') # source the system configuration variables
# Execute the commands to start your subsystem
/usr/sbin/pfs_mountd & >> $LOGFILE
/usr/sbin/pfsd & >> $LOGFILE
:
;;
'stop')
# source the system configuration variables
:
# Execute the commands to stop your subsystem
for i in pfsd pfs_mountd
do
killproc $i
done
;;
*) echo "usage: $0 {start|stop|start_msg|stop_msg}"
rval=1
;;
esac
exit $rval
It sets up the daemons you need to run.
after that its just pfs_mount /cdrom
You are rock ridge ready..
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP