3 Aug
2004
3 Aug
'04
7:13 p.m.
Hi Hans,
nice to hear that you would like to use SmallWiki for your home-page.
- wie startet man dann automatisch im Image, z.B. mit
headless Squeak ?
I don't know a lot about the port of SmallWiki to Squeak, I'm only
responsible for the development of the original version in VisualWorks.
- Chris Burkert meint, der Squeak Port sei nicht zu
empfehlen, wie
siehst Du das ?
I think for a personal home-page it should be possible to use
VisualWorks, as this there is commercial (you don't earn money) use
then.
Cheers,
Lukas
--
Lukas Renggli
http://renggli.freezope.org
3 Aug
3 Aug
9:59 p.m.
New subject: Squeak SmallWiki
Hi Hans and Lukas,
> - wie startet man dann automatisch im Image, z.B.
mit headless Squeak ?
You should create one storage process by hand:
Smalltalk at: #Server put: (SWKom startOn: 8080).
Server storage: SWImageStorage new.
Server storage delay: 60 * 5.
Then save the image and use a startup script config.st with something like
(you can put your config in here but be careful in using the storage:
message which will create many trouble causing storage processes over
time):
Server stop.
Server port: 9002.
Server start.
Start the server on Unix via:
squeak -headless squeak.image file:///path/to/config.st &
> - Chris Burkert meint, der Squeak Port sei nicht
zu empfehlen, wie
> siehst Du das ?
The problem is, that I don't have the time to sync the squeak port with
the VW version any more. Besides this the current version is quite stable.
So if you want to have an up to date Smallwiki use the VW version. If you
can be happy with the squeak port ... use it!
If somebody likes to take the maintainership of the squeak port I would be
happy!
cheers Chris Burkert
4 Aug
4 Aug
3:44 p.m.
New subject: Squeak SmallWiki
chris(a)chrisburkert.de wrote:
Hi Hans and Lukas,
Under Squeak, a few months ago there was a problem with SWImageStorage
saving unrunnable images. Has that been fixed? What was the problem?
I first saw the problem reported by Maurice Rabb, on 2/13/04. The
problem was confirmed by Chris Burket on a post later that day. Then on
3/17/04 I reported that I had also seen the problem. I've pasted below
my own post, which also has the earlier ones.
Later, on 3/18/04 Chris said he planned on looking at it over the next
few days to find and fix the problem.
So, Chris, whatever became of this? Does it work now (for Squeak)?
What was the problem?
Nevin
************* Message from 3/17/04 and earlier pasted below ************
>- wie startet man dann automatisch im Image,
z.B. mit headless Squeak ?
>
>
You should create one storage process by hand:
Smalltalk at: #Server put: (SWKom startOn: 8080).
Server storage: SWImageStorage new.
Server storage delay: 60 * 5.
Then save the image and use a startup script config.st with something like
(you can put your config in here but be careful in using the storage:
message which will create many trouble causing storage processes over
time):
Server stop.
Server port: 9002.
Server start.
Start the server on Unix via:
squeak -headless squeak.image file:///path/to/config.st &
Chris Burkert wrote:
Hi Maurice,
Maurice Rabb wrote:
I saw this problem one time-- but it was enough to make me set the
storage persistence to nil, and do manual image saves. I'm using Squeak
3.6 final.
How do I tell what version of SmallWiki I've got loaded?
What was the cause of the image hang?
Can SWImageStorage be relied upon? As I read the above, there is some
implication that as long as I do a 'server storage snapshot' one time
before the delay expires, then afterwards everything is OK? Or will the
image hang with the next expirary?
Nevin
I am having some trouble with my SmallWiki.
server _ SWKom startOn: 8888.
storage _ SWImageStorage new.
storage delay: 3 * 60.
server storage: storage. When the delay expires, it stores a
snapshot as expected but the VM freezes up. There is some problem
with the image it saves. It is not runnable.
However eveything seems to work properly if I execute:
server storage snapshot.
before the delay expires. I can do this repeatedly, but if it is
done via the delay it hoses the image.
Has anyone else experienced this? I would appreciate any suggestions.
Yes I can reproduce this. Thanks for the report. Unfortunatly I can't
have a look at this in the next days ... exams. I will sync the Squeak
Port with VW in about 3-4 weeks and fix some bugs including this one.
I hope you can wait till then or send me your own fix
Regards
Chris Burkert 
6:34 p.m.
New subject: Squeak SmallWiki
Hi Nevin,
Under Squeak, a few months ago there was a problem
with SWImageStorage
saving unrunnable images. Has that been fixed? What was the problem?
[snip]
So, Chris, whatever became of this? Does it work now (for Squeak)?
What was the problem?
Yes, that has been fixed, but I don't remember what exactly the problem
was. I believe I have answered to this list when I did the fix. There's a
site [1] which runs Squeak SmallWiki several months. So it seems to be
quite stable as it is. Simply load the current SmallWiki from SqueakMap.
regards Chris Burkert
1: http://duala.africapolyglotta.net/
7 Aug
7 Aug
3:43 p.m.
New subject: Squeak SmallWiki
chris(a)chrisburkert.de wrote:
Hi Nevin,
I "upgraded" yesterday. The problem is still there. The image hung
over the evening.
I'm using Squeak 3.6 final, on FreeBSD. The latest version of SmallWiki
on SqueakMap is 0.9.23-- this actually seems to be a "backrev" from the
one I started with last fall:
(on the "new" image) SWSmallWiki versionString --> 'SmallWiki
0.9.23'
(on the "old" image) SWSmallWiki versionString --> 'SmallWiki
1.0'
For what its worth, when the install asks if I want the Star Browser, or
any of the other extras, I say "no".
Nevin
--
Nevin Pratt
Bountiful Baby
http://www.bountifulbaby.com
The Most Complete Reborn Supply Store On The Web!
(801) 992-3137
Under Squeak, a few months ago there was a problem
with SWImageStorage
saving unrunnable images. Has that been fixed? What was the problem?
[snip]
Yes, that has been fixed, but I don't remember what exactly the problem
was. I believe I have answered to this list when I did the fix. There's a
site [1] which runs Squeak SmallWiki several months. So it seems to be
quite stable as it is. Simply load the current SmallWiki from SqueakMap.
regards Chris Burkert
3:56 p.m.
New subject: Squeak SmallWiki
I "upgraded" yesterday. The problem is still there. The image hung
over the evening.
I'm using Squeak 3.6 final, on FreeBSD. The latest version of
SmallWiki on SqueakMap is 0.9.23-- this actually seems to be a
"backrev" from the one I started with last fall:
(on the "new" image) SWSmallWiki versionString --> 'SmallWiki
0.9.23'
(on the "old" image) SWSmallWiki versionString --> 'SmallWiki
1.0'
For what its worth, when the install asks if I want the Star Browser,
or any of the other extras, I say "no".
Nevin
Oh, and I loaded it fresh into a virgin 3.6 image.
Nevin
--
Nevin Pratt
Bountiful Baby
http://www.bountifulbaby.com
The Most Complete Reborn Supply Store On The Web!
(801) 992-3137
8 Aug
8 Aug
1:43 p.m.
New subject: Squeak SmallWiki
Hi Nevin,
I "upgraded" yesterday. The problem is
still there. The image hung
over the evening.
could you please take a look in you process browser and make sure that
there is only one storage process?!? The best is to kill all and create a
new one.
I'm using Squeak 3.6 final, on FreeBSD. The
latest version of SmallWiki
on SqueakMap is 0.9.23-- this actually seems to be a "backrev" from the
one I started with last fall:
(on the "new" image) SWSmallWiki versionString --> 'SmallWiki
0.9.23'
(on the "old" image) SWSmallWiki versionString --> 'SmallWiki
1.0'
I changed this version string which came from the VW version, because it
was not the correct string. You the versioning numbers from SM. Currently
it should be 0.9.23-6 for the kernel which means it is revision 6 of
0.9.23.
For what its worth, when the install asks if I want
the Star Browser, or
any of the other extras, I say "no".
You don't have to load these packages. So "no" and "yes" are
correct answers.
Chris Burkert
PS: I'm away for 2 weeks so please don't expect answers for this time. I'm
cycling from the ore mountains in saxony to wallis in switzerland and
back. Till then ...
11 Aug
11 Aug
4:13 a.m.
New subject: Squeak SmallWiki
OK, I had time to look at this again.
There is only one storage process-- the SWImageStorage
It looks like SWImageStorage does not attempt an image save unless it
detects that the swiki changed. But, if it attempts to save the image,
the image is hosed, and the resulting image is also hosed.
The problem is definitely still there.
Nevin
chris(a)chrisburkert.de wrote:
Hi Nevin,
--
Nevin Pratt
Bountiful Baby
http://www.bountifulbaby.com
The Most Complete Reborn Supply Store On The Web!
(801) 992-3137
I "upgraded" yesterday. The problem is
still there. The image hung
over the evening.
could you please take a look in you process browser and make sure that
there is only one storage process?!? The best is to kill all and create a
new one.
I'm using Squeak 3.6 final, on FreeBSD. The
latest version of SmallWiki
on SqueakMap is 0.9.23-- this actually seems to be a "backrev" from the
one I started with last fall:
(on the "new" image) SWSmallWiki versionString --> 'SmallWiki
0.9.23'
(on the "old" image) SWSmallWiki versionString --> 'SmallWiki
1.0'
I changed this version string which came from the VW version, because it
was not the correct string. You the versioning numbers from SM. Currently
it should be 0.9.23-6 for the kernel which means it is revision 6 of
0.9.23.
For what its worth, when the install asks if I
want the Star Browser, or
any of the other extras, I say "no".
You don't have to load these packages. So "no" and "yes" are
correct answers.
Chris Burkert
PS: I'm away for 2 weeks so please don't expect answers for this time. I'm
cycling from the ore mountains in saxony to wallis in switzerland and
back. Till then ...
4:36 p.m.
New subject: Squeak SmallWiki
I just ran the same image under Win XP. Instead of hanging the image,
it pegged the CPU at 99%.
Nevin
Nevin Pratt wrote:
OK, I had time to look at this again.
There is only one storage process-- the SWImageStorage
It looks like SWImageStorage does not attempt an image save unless it
detects that the swiki changed. But, if it attempts to save the
image, the image is hosed, and the resulting image is also hosed.
The problem is definitely still there.
Nevin
chris(a)chrisburkert.de wrote:
--
Nevin Pratt
Bountiful Baby
http://www.bountifulbaby.com
The Most Complete Reborn Supply Store On The Web!
(801) 992-3137
Hi Nevin,
--
Nevin Pratt
Bountiful Baby
http://www.bountifulbaby.com
The Most Complete Reborn Supply Store On The Web!
(801) 992-3137
I "upgraded" yesterday. The problem is
still there. The image hung
over the evening.
could you please take a look in you process browser and make sure that
there is only one storage process?!? The best is to kill all and create a
new one.
I'm using Squeak 3.6 final, on FreeBSD. The
latest version of SmallWiki
on SqueakMap is 0.9.23-- this actually seems to be a "backrev" from the
one I started with last fall:
(on the "new" image) SWSmallWiki versionString --> 'SmallWiki
0.9.23'
(on the "old" image) SWSmallWiki versionString --> 'SmallWiki
1.0'
I changed this version string which came from the VW version, because it
was not the correct string. You the versioning numbers from SM. Currently
it should be 0.9.23-6 for the kernel which means it is revision 6 of
0.9.23.
For what its worth, when the install asks if I
want the Star Browser, or
any of the other extras, I say "no".
You don't have to load these packages. So "no" and "yes" are
correct answers.
Chris Burkert
PS: I'm away for 2 weeks so please don't expect answers for this time. I'm
cycling from the ore mountains in saxony to wallis in switzerland and
back. Till then ...
4:42 p.m.
New subject: Squeak SmallWiki
The same in my case, running on linux
Sebastián Sastre
HYPERLINK "mailto:ssastre@seaswork.com.ar"ssastre@seaswork.com.ar
HYPERLINK "http://www.seaswork.com.ar/"www.seaswork.com.ar
-----Mensaje original-----
De: owner-smallwiki(a)iam.unibe.ch [mailto:owner-smallwiki@iam.unibe.ch]
En nombre de Nevin Pratt
Enviado el: Miércoles, 11 de Agosto de 2004 11:36
Para: smallwiki(a)iam.unibe.ch
Asunto: Re: Squeak SmallWiki
I just ran the same image under Win XP. Instead of hanging the image,
it pegged the CPU at 99%.
Nevin
Nevin Pratt wrote:
OK, I had time to look at this again.
There is only one storage process-- the SWImageStorage
It looks like SWImageStorage does not attempt an image save unless it
detects that the swiki changed. But, if it attempts to save the image,
the image is hosed, and the resulting image is also hosed.
The problem is definitely still there.
Nevin
HYPERLINK "mailto:chris@chrisburkert.de"chris@chrisburkert.de wrote:
Hi Nevin,
I "upgraded" yesterday. The problem is still there. The image hung
over the evening.
could you please take a look in you process browser and make sure that
there is only one storage process?!? The best is to kill all and create
a
new one.
I'm using Squeak 3.6 final, on FreeBSD. The latest version of SmallWiki
on SqueakMap is 0.9.23-- this actually seems to be a "backrev" from the
one I started with last fall:
(on the "new" image) SWSmallWiki versionString --> 'SmallWiki
0.9.23'
(on the "old" image) SWSmallWiki versionString --> 'SmallWiki
1.0'
I changed this version string which came from the VW version, because it
was not the correct string. You the versioning numbers from SM.
Currently
it should be 0.9.23-6 for the kernel which means it is revision 6 of
0.9.23.
For what its worth, when the install asks if I want the Star Browser, or
any of the other extras, I say "no".
You don't have to load these packages. So "no" and "yes" are
correct
answers.
Chris Burkert
PS: I'm away for 2 weeks so please don't expect answers for this time.
I'm
cycling from the ore mountains in saxony to wallis in switzerland and
back. Till then ...
--
Nevin Pratt
Bountiful Baby
HYPERLINK "http://www.bountifulbaby.com"http://www.bountifulbaby.com
The Most Complete Reborn Supply Store On The Web!
(801) 992-3137
--
Nevin Pratt
Bountiful Baby
HYPERLINK "http://www.bountifulbaby.com"http://www.bountifulbaby.com
The Most Complete Reborn Supply Store On The Web!
(801) 992-3137
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.735 / Virus Database: 489 - Release Date: 06/08/2004
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.735 / Virus Database: 489 - Release Date: 06/08/2004
12 Aug
12 Aug
9:08 p.m.
New subject: Squeak SmallWiki
Hi Nevin,
From what I remember, I had the same problem that you describe.
However, I noticed that if I directly commanded (from a workspace) a
SWImageStorage to save, everything worked fine.
I think I deduced that what was hosing the images was a bad Semaphore.
I never have time to dig around and track down the exact source the
error.
Maurice
Maurice Rabb
773-281-6003
mr(a)MauriceRabb.com
On Aug 10, 2004, at 9:13 PM, Nevin Pratt wrote:
OK, I had time to look at this again.
There is only one storage process-- the SWImageStorage
It looks like SWImageStorage does not attempt an image save unless it
detects that the swiki changed. But, if it attempts to save the
image, the image is hosed, and the resulting image is also hosed.
The problem is definitely still there.
Nevin
chris(a)chrisburkert.de wrote:
Hi Nevin,
I "upgraded" yesterday. The problem is still there. The image hung
over the evening.
could you please take a look in you process browser and make sure that
there is only one storage process?!? The best is to kill all and
create a
new one.
I'm using Squeak 3.6 final, on FreeBSD. The latest version of
SmallWiki
on SqueakMap is 0.9.23-- this actually seems to be a "backrev" from the
one I started with last fall:
(on the "new" image) SWSmallWiki versionString --> 'SmallWiki
0.9.23'
(on the "old" image) SWSmallWiki versionString --> 'SmallWiki
1.0'
I changed this version string which came from the VW version, because
it
was not the correct string. You the versioning numbers from SM.
Currently
it should be 0.9.23-6 for the kernel which means it is revision 6 of
0.9.23.
For what its worth, when the install asks if I want the Star Browser,
or
any of the other extras, I say "no".
You don't have to load these packages. So "no" and "yes" are
correct
answers.
Chris Burkert
PS: I'm away for 2 weeks so please don't expect answers for this time.
I'm
cycling from the ore mountains in saxony to wallis in switzerland and
back. Till then ...
--
Nevin Pratt
Bountiful Baby
http://www.bountifulbaby.com
The Most Complete Reborn Supply Store On The Web!
(801) 992-3137
9:45 p.m.
New subject: Squeak SmallWiki
Yes, you can evaluate 'server storage snapshot' from a workspace without
it hanging the image.
The actual image save accomplished by the SWImageStorage storage manager
is just
Smalltalk saveImageInFileNamed: (Smalltalk fullNameForImageNamed:
newName).
For this not to work suggests some kind of issue with the fact that it
is issued from within a thread (the storage manager runs in its own
green thread). Which, of course, in turn could be a Semaphore issue--
who knows.
In any case, SmallWiki on Squeak is not ready for production, and won't
be until there is a reliable storage manager.
Nevin
Maurice Rabb wrote:
Hi Nevin,
From what I remember, I had the same problem that you describe.
However, I noticed that if I directly commanded (from a workspace) a
SWImageStorage to save, everything worked fine.
I think I deduced that what was hosing the images was a bad Semaphore.
I never have time to dig around and track down the exact source the
error.
Maurice
Maurice Rabb
773-281-6003
mr(a)MauriceRabb.com
On Aug 10, 2004, at 9:13 PM, Nevin Pratt wrote:
OK, I had time to look at this again.
There is only one storage process-- the SWImageStorage
It looks like SWImageStorage does not attempt an image save unless
it detects that the swiki changed. But, if it attempts to save
the image, the image is hosed, and the resulting image is also hosed.
The problem is definitely still there.
Nevin
chris(a)chrisburkert.de wrote:
Hi Nevin,
I "upgraded" yesterday. The problem is still there. The image hung
over the evening.
could you please take a look in you process browser and make sure
that
there is only one storage process?!? The best is to kill all and
create a
new one.
I'm using Squeak 3.6 final, on FreeBSD. The latest version of
SmallWiki
on SqueakMap is 0.9.23-- this actually seems to be a "backrev"
from the
one I started with last fall:
(on the "new" image) SWSmallWiki versionString --> 'SmallWiki
0.9.23'
(on the "old" image) SWSmallWiki versionString --> 'SmallWiki
1.0'
I changed this version string which came from the VW version,
because it
was not the correct string. You the versioning numbers from SM.
Currently
it should be 0.9.23-6 for the kernel which means it is revision 6 of
0.9.23.
For what its worth, when the install asks if I want the Star
Browser, or
any of the other extras, I say "no".
You don't have to load these packages. So "no" and "yes" are
correct answers.
Chris Burkert
PS: I'm away for 2 weeks so please don't expect answers for this
time. I'm
cycling from the ore mountains in saxony to wallis in switzerland and
back. Till then ...
--
Nevin Pratt
Bountiful Baby
http://www.bountifulbaby.com
The Most Complete Reborn Supply Store On The Web!
(801) 992-3137
--
Nevin Pratt
Bountiful Baby
http://www.bountifulbaby.com
The Most Complete Reborn Supply Store On The Web!
(801) 992-3137
13 Aug
13 Aug
5:40 p.m.
New subject: Squeak SmallWiki
I don't remember if Squeak has something like VW's BOSS, I am sure that
there must exist some sort of object serializer. I built very quickly a
StorageManager (VW SmallWiki obviously) based on Boss and it works like a
charm. A test on essentially the default root structure shows that it is
10x smaller than a SIXX based storage and the entire time to snapshot
which includes maintaining a FIFO type versioning for the last 10
snapshots takes about 300 ms. Of course this does not address what seems
to be a threading issue but I personally get nervous about snapshoting
live images , sometimes things can get funky.
-Charles
On Thu, 12 Aug 2004 12:45:30 -0700, Nevin Pratt <nevin(a)bountifulbaby.com>
wrote:
Yes, you can evaluate 'server storage
snapshot' from a workspace without
it hanging the image.
The actual image save accomplished by the SWImageStorage storage manager
is just
Smalltalk saveImageInFileNamed: (Smalltalk fullNameForImageNamed:
newName).
For this not to work suggests some kind of issue with the fact that it
is issued from within a thread (the storage manager runs in its own
green thread). Which, of course, in turn could be a Semaphore issue--
who knows.
In any case, SmallWiki on Squeak is not ready for production, and won't
be until there is a reliable storage manager.
Nevin
Maurice Rabb wrote:
--
Using Opera's revolutionary e-mail client: http://www.opera.com/m2/
Hi Nevin,
From what I remember, I had the same problem that you describe.
However, I noticed that if I directly commanded (from a workspace) a
SWImageStorage to save, everything worked fine.
I think I deduced that what was hosing the images was a bad Semaphore.
I never have time to dig around and track down the exact source the
error.
Maurice
Maurice Rabb
773-281-6003
mr(a)MauriceRabb.com
On Aug 10, 2004, at 9:13 PM, Nevin Pratt wrote:
OK, I had time to look at this again.
There is only one storage process-- the SWImageStorage
It looks like SWImageStorage does not attempt an image save unless
it detects that the swiki changed. But, if it attempts to save
the image, the image is hosed, and the resulting image is also
hosed.
The problem is definitely still there.
Nevin
chris(a)chrisburkert.de wrote:
Hi Nevin,
I "upgraded" yesterday. The problem is still there. The image hung
over the evening.
could you please take a look in you process browser and make sure
that
there is only one storage process?!? The best is to kill all and
create a
new one.
I'm using Squeak 3.6 final, on FreeBSD. The latest version of
SmallWiki
on SqueakMap is 0.9.23-- this actually seems to be a "backrev"
from the
one I started with last fall:
(on the "new" image) SWSmallWiki versionString --> 'SmallWiki
0.9.23'
(on the "old" image) SWSmallWiki versionString --> 'SmallWiki
1.0'
I changed this version string which came from the VW version,
because it
was not the correct string. You the versioning numbers from SM.
Currently
it should be 0.9.23-6 for the kernel which means it is revision 6 of
0.9.23.
For what its worth, when the install asks if I want the Star
Browser, or
any of the other extras, I say "no".
You don't have to load these packages. So "no" and "yes" are
correct answers.
Chris Burkert
PS: I'm away for 2 weeks so please don't expect answers for this
time. I'm
cycling from the ore mountains in saxony to wallis in switzerland
and
back. Till then ...
--
Nevin Pratt
Bountiful Baby
http://www.bountifulbaby.com
The Most Complete Reborn Supply Store On The Web!
(801) 992-3137
9:25 p.m.
New subject: Squeak SmallWiki
oops, the 300ms is not the time it takes to snapshot a wiki with a default
structure, the wiki although by no means large has a usefully decent
amount of content.
On Fri, 13 Aug 2004 10:40:43 -0500, Charles A. Monteiro
<charles(a)datasof.com> wrote:
I don't remember if Squeak has something like
VW's BOSS, I am sure that
there must exist some sort of object serializer. I built very quickly a
StorageManager (VW SmallWiki obviously) based on Boss and it works like
a charm. A test on essentially the default root structure shows that it
is 10x smaller than a SIXX based storage and the entire time to snapshot
which includes maintaining a FIFO type versioning for the last 10
snapshots takes about 300 ms. Of course this does not address what seems
to be a threading issue but I personally get nervous about snapshoting
live images , sometimes things can get funky.
-Charles
On Thu, 12 Aug 2004 12:45:30 -0700, Nevin Pratt
<nevin(a)bountifulbaby.com> wrote:
--
Using Opera's revolutionary e-mail client: http://www.opera.com/m2/
Yes, you can evaluate 'server storage
snapshot' from a workspace without
it hanging the image.
The actual image save accomplished by the SWImageStorage storage manager
is just
Smalltalk saveImageInFileNamed: (Smalltalk fullNameForImageNamed:
newName).
For this not to work suggests some kind of issue with the fact that it
is issued from within a thread (the storage manager runs in its own
green thread). Which, of course, in turn could be a Semaphore issue--
who knows.
In any case, SmallWiki on Squeak is not ready for production, and won't
be until there is a reliable storage manager.
Nevin
Maurice Rabb wrote:
Hi Nevin,
From what I remember, I had the same problem that you describe.
However, I noticed that if I directly commanded (from a workspace) a
SWImageStorage to save, everything worked fine.
I think I deduced that what was hosing the images was a bad Semaphore.
I never have time to dig around and track down the exact source the
error.
Maurice
Maurice Rabb
773-281-6003
mr(a)MauriceRabb.com
On Aug 10, 2004, at 9:13 PM, Nevin Pratt wrote:
OK, I had time to look at this again.
There is only one storage process-- the SWImageStorage
It looks like SWImageStorage does not attempt an image save unless
it detects that the swiki changed. But, if it attempts to save
the image, the image is hosed, and the resulting image is also
hosed.
The problem is definitely still there.
Nevin
chris(a)chrisburkert.de wrote:
Hi Nevin,
I "upgraded" yesterday. The problem is still there. The image hung
over the evening.
could you please take a look in you process browser and make sure
that
there is only one storage process?!? The best is to kill all and
create a
new one.
I'm using Squeak 3.6 final, on FreeBSD. The latest version of
SmallWiki
on SqueakMap is 0.9.23-- this actually seems to be a "backrev"
from the
one I started with last fall:
(on the "new" image) SWSmallWiki versionString --> 'SmallWiki
0.9.23'
(on the "old" image) SWSmallWiki versionString --> 'SmallWiki
1.0'
I changed this version string which came from the VW version,
because it
was not the correct string. You the versioning numbers from SM.
Currently
it should be 0.9.23-6 for the kernel which means it is revision 6
of
0.9.23.
For what its worth, when the install asks if I want the Star
Browser, or
any of the other extras, I say "no".
You don't have to load these packages. So "no" and "yes" are
correct answers.
Chris Burkert
PS: I'm away for 2 weeks so please don't expect answers for this
time. I'm
cycling from the ore mountains in saxony to wallis in switzerland
and
back. Till then ...
--
Nevin Pratt
Bountiful Baby
http://www.bountifulbaby.com
The Most Complete Reborn Supply Store On The Web!
(801) 992-3137
22 Aug
22 Aug
1:37 p.m.
New subject: Squeak SmallWiki
Nevin Pratt wrote:
In any case, SmallWiki on Squeak is not ready for
production, and won't
be until there is a reliable storage manager.
Yes! And that is the reason why it is beta. You always should use the VW
version for a production environment! I did the port mainly for myself
... to learn something about it. Currently I don't have the time to
maintain it further. So if somebody wants to make a try write me and I
will pass the maintainership.
Regards
Chris Burkert
--
http://www.chrisburkert.de/
6:56 p.m.
New subject: Squeak SmallWiki
Chris,
do you know how to move the contents of a wiki from squeak to
VW?
regards,
Sebastián Sastre
ssastre(a)seaswork.com.ar
www.seaswork.com.ar
-----Mensaje original-----
De: owner-smallwiki(a)iam.unibe.ch
[mailto:owner-smallwiki@iam.unibe.ch] En nombre de Chris Burkert
Enviado el: Domingo, 22 de Agosto de 2004 08:37
Para: smallwiki(a)iam.unibe.ch
Asunto: Re: Squeak SmallWiki
Nevin Pratt wrote:
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.740 / Virus Database: 494 - Release Date: 16/08/2004
In any case, SmallWiki on Squeak is not ready for
production, and
won't
be until there is a reliable storage manager.
Yes! And that is the reason why it is beta. You always should
use the VW
version for a production environment! I did the port mainly
for myself
... to learn something about it. Currently I don't have the time to
maintain it further. So if somebody wants to make a try write
me and I
will pass the maintainership.
Regards
Chris Burkert
--
http://www.chrisburkert.de/
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.740 / Virus Database: 494 - Release Date: 16/08/2004
10:20 p.m.
New subject: Squeak SmallWiki
Hi sebastian
there is no mechanism for that. We were working on that but got
distracted. I could give you what we have now.
Stef
On Aug 22, 2004, at 6:56 PM, Sebastian Sastre wrote:
Chris,
do you know how to move the contents of a wiki from squeak to
VW?
regards,
Sebastián Sastre
ssastre(a)seaswork.com.ar
www.seaswork.com.ar
-----Mensaje original-----
De: owner-smallwiki(a)iam.unibe.ch
[mailto:owner-smallwiki@iam.unibe.ch] En nombre de Chris Burkert
Enviado el: Domingo, 22 de Agosto de 2004 08:37
Para: smallwiki(a)iam.unibe.ch
Asunto: Re: Squeak SmallWiki
Nevin Pratt wrote:
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.740 / Virus Database: 494 - Release Date: 16/08/2004
In any case, SmallWiki on Squeak is not ready for
production, and
won't
be until there is a reliable storage manager.
Yes! And that is the reason why it is beta. You always should
use the VW
version for a production environment! I did the port mainly
for myself
... to learn something about it. Currently I don't have the time to
maintain it further. So if somebody wants to make a try write
me and I
will pass the maintainership.
Regards
Chris Burkert
--
http://www.chrisburkert.de/
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.740 / Virus Database: 494 - Release Date: 16/08/2004
7187
days inactive
7206
days old
16 comments
8 participants
participants (8)
-
Charles A. Monteiro -
Chris Burkert -
chris＠chrisburkert.de
-
Lukas Renggli -
Maurice Rabb -
Nevin Pratt -
Sebastian Sastre -
stéphane ducasse