On 6/26/08, Joerg Schilling <[EMAIL PROTECTED]> wrote: > "Dennis Clarke" <[EMAIL PROTECTED]> wrote: > > > This *should* extract that file and overwrite anything involved neatly : > > > > -bash-3.2# cd / > > -bash-3.2# sync;sync > > -bash-3.2# /opt/csw/bin/star -x -v -U -bz > > file=/root/ksh93_integration_20080624_snapshot_i386.tar.bz2 > > x etc/ksh.kshrc 2934 bytes, 6 tape blocks > > x etc/magic 19592 bytes, 39 tape blocks > > . > > . > > . > > > > I have no idea how I managed to bork this up but my session is dead as > > a doornail and the extraction of that tarball blew up because star > > claims that there was something ... not quite kosher : > > > > x usr/lib/amd64/libast.so symbolic link to libast.so.1 > > /opt/csw/bin/star: File 'usr/lib/amd64/libast.so' not removed. > > /opt/csw/bin/star: File exists. Cannot create symbolic link > > 'usr/lib/amd64/libast.so' to 'libast.so.1'. > > > > full details at : > > > > http://www.blastwave.org/dclarke/ksh93/ksh93_extract_bork_bork_bork.txt > > > > am I dead in the water for any user that was using ksh93 ? > > > > > I am not sure where the problems are but star -U still noes not include the > permission to remove old files. > > If you like to use star to _install_ software over an existing installation, > you may like to call "scpio -u" instead or use star with the right options to > permit file removal. > > Calling scpio is similar to call: star -x -U -install -force-remove > -remove-recursive > > See man page for mire information.
You are using the correct word despite the spelling. Yes, your man page is a "mire" and in there I get stuck. > The reason why you did missunderstand things may be that Sun tar > and Sun cpio implement a lot of undocumented behavior that is not > in the standard and thus unknown to most users. Where is this standard that you refer to? At the OpenGroup ? Dennis _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
