Milan,

yes it would be nice if squeak could handle the setup by itself. I think
you don't want to have the OS package system deal with that. On a
multiuser
system that would mean that during the installation of squeak copies of
the
default image/changes files (>10MB) would be placed in every user's home
directory regardless, if the user wants to use squeak or not.

The purpose of inisqueak is to get you started. It does this by doing
the
following:

1.	Places a copy of the default squeak image (that came within the
rpm)
	named squeak.image in the current directory
2.	Places a copy of the associated changes file named
squeak.changes in
	the same dir
3.	Creates a soft link named SqueakV3.sources to the actual file.
This
	file is immutable and can be shared by all users of the system.

If you launch the squeak vm without any filename as a command line
argument,
it looks for a file named squeak.image in the current directory and
starts
with this if it can find it. So after running inisqueak just execute
squeak
and there you go.

If you used and saved the image a few times and feel you want to start
over again using the default image, then just remove(1) the image and
changes file and invoke inisqueak in that dir once more. After some time
you might find it usefull to keep several images around. For example a
stable image, a development image, a bfav(2) image for bug hunting and
maybe a personal base image suited to your needs (eg. additional tools
like RefactoringBrowser) and taste (eg. Fonts, Colors, ...).

Alex

(1) BEWARE that by removing these files you will lose everything you've
done so far in this image, if you didn't saved your code or your
projects in any other way.
(2) http://minnow.cc.gatech.edu/squeak/3214