On Thu, Apr 19, 2001 at 03:31:08PM -0800, Ethan Benson wrote:
On Thu, Apr 19, 2001 at 10:51:17AM -0500, W. Crowshaw wrote:
Actually, it doesn't hurt anything if the MacOS HFS FS is mounted on the
kernel
and hmount'ed with hfsutils. I access the HFS FS both mounted and hmounted
all the
On Wednesday 18 April 2001 23:14, Joseph Red wrote:
Michael Schmitz wrote:
Seriously: I've never had any luck with unsit or macunpack or the like.
.sit files are essentially useless on the Linux side.
Then why does bootx come packaged on the 2.2r2 CD as a .sit file? I'm
clueless when
to deal with if you don't have the right
stuffit on your system. But there are still some hurdles left for
you to cross. Good luck, Grasshopper.
a
Joseph Red wrote:
Michael Schmitz wrote:
Seriously: I've never had any luck with unsit or macunpack or the like.
.sit files are essentially
It's not just that you _should_ unpack BootX on the Mac side, it's that
you have to. It is a Mac OS application, and therefore has a filetype,
creator code, and resource fork. While you might be able to extract the
bitstreams of all these (and the data fork), they won't do you much good.
What
On Thu, Apr 19, 2001 at 12:55:26AM -0400, Michael D. Crawford wrote:
It's not just that you _should_ unpack BootX on the Mac side, it's that
you have to.
No you don't. When I bought my Mac second hand, it had a _minimal_ install
of MacOS 9 on it. When I say minimal, I mean no web browser, no
Seriously: I've never had any luck with unsit or macunpack or the like.
.sit files are essentially useless on the Linux side.
Then why does bootx come packaged on the 2.2r2 CD as a .sit file? I'm
Maybe because BootX is a MacOS application, and it is generally assumed
that if you use
On Thu, Apr 19, 2001 at 03:02:48AM -0300, Peter Cordes wrote:
Agreed! They should use macbinary, or gzipped macbinary (since most people
have an extractor capable of handling gzip).
there is only two files for bootx that even require macbinary, the
extention and the application.
On Thu, Apr 19, 2001 at 03:02:48AM -0300, Peter Cordes wrote:
On Thu, Apr 19, 2001 at 12:55:26AM -0400, Michael D. Crawford wrote:
It is a Mac OS application, and therefore has a filetype,
creator code, and resource fork. While you might be able to extract the
bitstreams of all these (and
On Thu, Apr 19, 2001 at 10:51:17AM -0500, W. Crowshaw wrote:
Actually, it doesn't hurt anything if the MacOS HFS FS is mounted on the
kernel
and hmount'ed with hfsutils. I access the HFS FS both mounted and hmounted
all the time.
then you have been lucky. the kernel will NOT be aware of the
On Thu, Apr 19, 2001 at 03:31:08PM -0800, Ethan Benson wrote:
On Thu, Apr 19, 2001 at 10:51:17AM -0500, W. Crowshaw wrote:
Actually, it doesn't hurt anything if the MacOS HFS FS is mounted on the
kernel
and hmount'ed with hfsutils. I access the HFS FS both mounted and hmounted
all the
Is anyone know if there is a tool with or without GUI to compress/uncompress
.sit files.
Thanks in advance
Damien GUIHAL
On Wed, 18 Apr 2001, Damien GUIHAL wrote:
Is anyone know if there is a tool with or without GUI to
compress/uncompress .sit files.
A quick search on package content for stable at
http://packages.debian.org/ confirms what I believe I have once used with
success: a tiny tool called unsit
On Wed, Apr 18, 2001 at 12:11:18PM +0200, Jonas Smedegaard wrote:
On Wed, 18 Apr 2001, Damien GUIHAL wrote:
Is anyone know if there is a tool with or without GUI to
compress/uncompress .sit files.
A quick search on package content for stable at
http://packages.debian.org/ confirms what
On Wed, Apr 18, 2001 at 10:21:32AM +0200, Damien GUIHAL wrote:
Is anyone know if there is a tool with or without GUI to
compress/uncompress .sit files.
/bin/rm
That was the compress part. Uncompress with
/bin/dd if=/dev/zero of=$1
Seriously: I've never had any luck with unsit
14 matches
Mail list logo
