I am trying to assemble an Opensolaris CD form the three parts that are downloaded:
$ cat sol-nv-b64a-sparc-dvd-iso-a sol-nv-b64a-sparc-dvd-iso-b > sol-nv-b64a-sparc-dvd.iso
cat: write error: File too large
This is apparently a shell problem. Does anyone know of a workaround that will work in Solaris 8? It fails in bash, sh, and ksh.
Thanks -w
That should not be.
The largefile man page mentions which utilities are largefile (2G+) aware. On solaris 8, I see csh, ksh, and sh (all in /usr/bin). So any of those shells should work.
Tcsh and bash aren't on that list, so they probably aren't built with largefile support on that release (but you could build your own).
Any chance you're writing to some odd filesystem that doesn't support large files?
--
Darren
I would be surprised if that is a shell issue.
Have you checked that the filesystem has largefiles enabled.
Run mount and check the mount options for your filesystem..
ulimit -a reported ( at least for root, I log this):
core file size(blocks, -c) unlimited
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
open files(-n) 256
pipe size (512 bytes, -p) 10
stack size(kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes(-u) 16165
virtual memory(kbytes, -v) unlimited
And this was a ufs filesystem with largefile support and recent patches, although the original install was done by someone else long long ago. For other people who have posted this problem , it's been a shell problem. Perhaps in the near future I might download the next OpenSolaris DVD build and try again, with my new Solaris 10 install.
Too late for root cause, I wiped the Solaris 8 install because I wanted to accomplish my Solaris upgrade in less than 12 hours. :-) First , I downloaded the OpenSolaris CD images . They crashed, both B67 and B64a (host is an Ultra 60 with a FFB2+ video card which I think is the source of the problem. I would not be broken hearted if OpenSolaris just CHOSE to blow off 10 year old hardware). I punted back to my trusty Solaris 10 Jumpstart image. Now I have a whole new wonderful world of bugs unfolding before me since it's been a long time since I have ventured into the garden of CDE-free delights that is the Solaris Desktop.
Waaaah waaaah waaaaah, how do I change the screen resolution in Solaris 10, waaaah, waaaah! (Yes, I know ffbconfig but WHY after 10 years is Solaris STILL unable to set screen resolution on the fly? Maybe it's the old hardware ...)
$ /usr/X11/bin/xvidtune
Please install the program before using
Wtf, etc. At least I have a Gtk build from this century now.
Don't worry, most of the Linux distros are just as bad. Don't get me started about Linux fonts!!!!! In fact, the Gnome-ified Solaris Java Desktop does a MUCH better job than most of the Linux distros out there.
I know you've dropped this, but I'm still curious
I just tried this same thing on a Solaris 8 2/02, patched to KU 117350-45.
I had this work on a freshly created 10GB UFS filesystem (newfs -m 1 /dev/vx/rdsk/appsdg/testvol - where testvol is a 10gb volume) - whether I used /sbin/sh /usr/bin/bash or /usr/bin/ksh
other things to note -
root@ih4u2201:/> sysdef|egrep -i size
Infinity:Infinity file size
Infinity:Infinity heap size
0x0000000000800000:Infinity stack size
## snip ##
my ulimit was set identical to yours (when trying bash) and otherwise was similar
in bourne and ksh -
time(seconds)unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes)8192
coredump(blocks)unlimited
nofiles(descriptors) 256
vmemory(kbytes)unlimited
in bash -
bash-2.03# ulimit -a
core file size (blocks)unlimited
data seg size (kbytes)unlimited
file size (blocks) unlimited
open files256
pipe size (512 bytes)10
stack size (kbytes) 8192
cpu time (seconds) unlimited
max user processes 15957
virtual memory (kbytes)unlimited
I would have been nice if at least one of the shells had failed for me :$
I'm glad you've figured out someway around it anyway - jeff
Yes, I can't reproduce this on my Solaris 8 servers, which all have recent, known-good patchlevels. Bash works fine cat-ing three 1.5G files together.
Who knows what kind of junk was installed on my old desktop! Case closed and thanks all for the help.
