You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(105) |
Sep
(33) |
Oct
(8) |
Nov
(30) |
Dec
(15) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(1) |
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(8) |
| 2007 |
Jan
(1) |
Feb
(3) |
Mar
(1) |
Apr
(5) |
May
(7) |
Jun
(7) |
Jul
(5) |
Aug
(38) |
Sep
(15) |
Oct
(13) |
Nov
(12) |
Dec
(3) |
| 2008 |
Jan
(5) |
Feb
(5) |
Mar
(30) |
Apr
(26) |
May
(21) |
Jun
(12) |
Jul
(22) |
Aug
(12) |
Sep
(10) |
Oct
(9) |
Nov
(13) |
Dec
(5) |
| 2009 |
Jan
(74) |
Feb
(49) |
Mar
(10) |
Apr
(35) |
May
(99) |
Jun
(75) |
Jul
(43) |
Aug
(16) |
Sep
(24) |
Oct
(38) |
Nov
(7) |
Dec
(5) |
| 2010 |
Jan
|
Feb
|
Mar
(36) |
Apr
(57) |
May
(73) |
Jun
(59) |
Jul
(54) |
Aug
(57) |
Sep
(26) |
Oct
(3) |
Nov
|
Dec
|
| 2011 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Scott F. <sj...@ra...> - 2000-11-22 02:44:34
|
OK, I just checked a new version of parsech into CVS. In it is the code to do DBM databases. However, the linkage is currently lost in the transfer to DBM. Does anyone have some good suggestions on how to store links in there? As the second part of this message, I will say what I'll do when the linkage is taken care of. After that's done, I'm going to start work on a python browser for the files. It's going to read in the DBMs I'm making. Any thoughts, suggestions, or jelly donughts would be appreciated. -Scott -- -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.0.2 (GNU/Linux) Comment: For info see http://www.gnupg.org mQGiBDmoHL8RBACt7yc65iKzR4IW2kKF0wjfZlRVwcwEws6HueM9uKF6HCzyFtyM XJiHz8f3LI2NY/GedfF+XTFc2zQlPummiOrHfAx9Y2hV4ajEpxNgqm36BT21vLuI iTB6roHHm+EiK9dRINyc+kB4v5QV5S9BGxPuygm/3yLZLmGH6RUmSxis1wCgvGnX n3qhbP7Yf/mLO1Du3oEJhR8EAI+TFhyxg3y2xv++xCxKOL9ofF+wPA4EkXPCAokW 10hDmeGY246wOMPWC0Hou1QJqqRN82n5BbJAzUnE/Iht82SEJgM1vhIbp0uShUdS jzKPnBBUTzLQFPbAG9hDaU/98JklsyDIbacavCuCtky6Xs/wmPjESUJsIl6FiHRv Uz9jA/96nxsDQ8YMEr51F3sHubn7BwrYqGOZLT5btLMG1i9OnWyy0npQ5wKvM2bT t2i6QPcHydTAkX+DLXQv8UeJE+Qpq+duoofMpxdFOKgqW3x0kKWGP14UoOqSQFGL K4fStiwR7fCtExrMFKUHaP5Sij7v8VoyBtyK+w45LoWFFXsPeLQhU2NvdHQgRmVu dG9uIDxzajEyZm5AcmFzY2hrZS5uZXQ+iFYEExECABYFAjmoHL8ECwoEAwMVAwID FgIBAheAAAoJEGtrXbm1pSX6WZoAnRzHUYn+/MSVAsmK7bLJrAfmn8Y+AJ4uzZEX OxVuc0sGg/J0AqlYNpMcqrkBDQQ5qBzcEAQAhJgZzAKBjuKwS0owgknuN+5kSu9U tk75ZKRpBMTFfW1Js2E5v96M3Z4XAvyJFhQYaXWZn0QQY4PkrbbfKib4X3Onn/Gx M1mdtWKAXxb1+JuEH/dpVemt2EDLn6b2VVI5iE6U0HcrJjkvt7DLKsvQFRnnqd6M SHdN3XmxhY+VakcAAwUD/iTTv+fpM+Nn2izo7z0BmRu/+GwQgvOF8Qc+8YA6JgaA UUrD7nO3xUpkoK6gr1se2Wu98BFv2GSKRZZF9QljXn2vGNreYRRI9ZhWpKm3zflz uC7lz63QaiZdAPup37yWYXyaAvUvYufORC4hS9mZUgKbbOC+O6xdzkLBerBk/FK+ iEYEGBECAAYFAjmoHNwACgkQa2tdubWlJfqAvQCfWMWnlCab4pUJEvE4gjSFJ+EV 5LsAn2yeJT+7MWYKIQpPmGMMjeGkykK1 =tjOP -----END PGP PUBLIC KEY BLOCK----- |
|
From: Scott F. <sj...@ra...> - 2000-11-19 13:09:37
|
Hello all. I just got parsech to get vertical_order right, so the VCG output is /finally/ done. For my next act (drumroll please), parsech will do a python data structure dump. After that, I'm going to write up a Python browser to do something like what Chris is writing up. Chris, what do you think of this? Feel free to respond. -Scott -- -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.0.2 (GNU/Linux) Comment: For info see http://www.gnupg.org mQGiBDmoHL8RBACt7yc65iKzR4IW2kKF0wjfZlRVwcwEws6HueM9uKF6HCzyFtyM XJiHz8f3LI2NY/GedfF+XTFc2zQlPummiOrHfAx9Y2hV4ajEpxNgqm36BT21vLuI iTB6roHHm+EiK9dRINyc+kB4v5QV5S9BGxPuygm/3yLZLmGH6RUmSxis1wCgvGnX n3qhbP7Yf/mLO1Du3oEJhR8EAI+TFhyxg3y2xv++xCxKOL9ofF+wPA4EkXPCAokW 10hDmeGY246wOMPWC0Hou1QJqqRN82n5BbJAzUnE/Iht82SEJgM1vhIbp0uShUdS jzKPnBBUTzLQFPbAG9hDaU/98JklsyDIbacavCuCtky6Xs/wmPjESUJsIl6FiHRv Uz9jA/96nxsDQ8YMEr51F3sHubn7BwrYqGOZLT5btLMG1i9OnWyy0npQ5wKvM2bT t2i6QPcHydTAkX+DLXQv8UeJE+Qpq+duoofMpxdFOKgqW3x0kKWGP14UoOqSQFGL K4fStiwR7fCtExrMFKUHaP5Sij7v8VoyBtyK+w45LoWFFXsPeLQhU2NvdHQgRmVu dG9uIDxzajEyZm5AcmFzY2hrZS5uZXQ+iFYEExECABYFAjmoHL8ECwoEAwMVAwID FgIBAheAAAoJEGtrXbm1pSX6WZoAnRzHUYn+/MSVAsmK7bLJrAfmn8Y+AJ4uzZEX OxVuc0sGg/J0AqlYNpMcqrkBDQQ5qBzcEAQAhJgZzAKBjuKwS0owgknuN+5kSu9U tk75ZKRpBMTFfW1Js2E5v96M3Z4XAvyJFhQYaXWZn0QQY4PkrbbfKib4X3Onn/Gx M1mdtWKAXxb1+JuEH/dpVemt2EDLn6b2VVI5iE6U0HcrJjkvt7DLKsvQFRnnqd6M SHdN3XmxhY+VakcAAwUD/iTTv+fpM+Nn2izo7z0BmRu/+GwQgvOF8Qc+8YA6JgaA UUrD7nO3xUpkoK6gr1se2Wu98BFv2GSKRZZF9QljXn2vGNreYRRI9ZhWpKm3zflz uC7lz63QaiZdAPup37yWYXyaAvUvYufORC4hS9mZUgKbbOC+O6xdzkLBerBk/FK+ iEYEGBECAAYFAjmoHNwACgkQa2tdubWlJfqAvQCfWMWnlCab4pUJEvE4gjSFJ+EV 5LsAn2yeJT+7MWYKIQpPmGMMjeGkykK1 =tjOP -----END PGP PUBLIC KEY BLOCK----- |
|
From: Scott F. <sj...@ra...> - 2000-11-15 02:16:13
|
On Wed, Nov 15, 2000 at 12:58:38AM +0100, the keyboard of Christophe Fergeau was alleged to have written: > > Le mer, 15 nov 2000 00:42:50, Scott Fenton a écrit : > > On Tue, Nov 14, 2000 at 11:37:28AM +0100, the keyboard of Christophe > > Fergeau was alleged to have written: > > > Concerning the release of 1.0, you seem to focus on the amount of data > > > we have. That's ok for me. But some day, we'll have to think of a way > > to > > > really be able to browse and visualize all these data. Indeed, the > > current > > > output format are not sufficient at all and the user can't have a > > global > > > view and really select what he is really interested in. With my > > browser, I > > > tried to make it easier to view the data we have but it is far from > > being > > > finished and currently, I am too busy to improve it (I think an editor > > > option would be nice as well as a display of each node in html). > > > > Sounds good in theory, but the thing is that in pratice it's a little > > hard to merge a CVS database and a web-vased wiewing. > > > For the display of each node in html, I just wanted to use the gtkhtml > widget to replace the ugly textmode display of the browser. It shouldn't be > difficult if I could find some doc concerning gtkhtml. > Have you tried hunting around gtk.org? > Another thing I forgot, I think we should start adding photos of the old > hardware (cpu, computers, ...) we are referencing. Now there's a thought that never occurred to me. That does sound like a god idea. I'll consider adding an Image: field to the syntax. > > Christophe > > _______________________________________________ > Comp-hist-devel mailing list > Com...@li... > http://lists.sourceforge.net/mailman/listinfo/comp-hist-devel -- -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.0.2 (GNU/Linux) Comment: For info see http://www.gnupg.org mQGiBDmoHL8RBACt7yc65iKzR4IW2kKF0wjfZlRVwcwEws6HueM9uKF6HCzyFtyM XJiHz8f3LI2NY/GedfF+XTFc2zQlPummiOrHfAx9Y2hV4ajEpxNgqm36BT21vLuI iTB6roHHm+EiK9dRINyc+kB4v5QV5S9BGxPuygm/3yLZLmGH6RUmSxis1wCgvGnX n3qhbP7Yf/mLO1Du3oEJhR8EAI+TFhyxg3y2xv++xCxKOL9ofF+wPA4EkXPCAokW 10hDmeGY246wOMPWC0Hou1QJqqRN82n5BbJAzUnE/Iht82SEJgM1vhIbp0uShUdS jzKPnBBUTzLQFPbAG9hDaU/98JklsyDIbacavCuCtky6Xs/wmPjESUJsIl6FiHRv Uz9jA/96nxsDQ8YMEr51F3sHubn7BwrYqGOZLT5btLMG1i9OnWyy0npQ5wKvM2bT t2i6QPcHydTAkX+DLXQv8UeJE+Qpq+duoofMpxdFOKgqW3x0kKWGP14UoOqSQFGL K4fStiwR7fCtExrMFKUHaP5Sij7v8VoyBtyK+w45LoWFFXsPeLQhU2NvdHQgRmVu dG9uIDxzajEyZm5AcmFzY2hrZS5uZXQ+iFYEExECABYFAjmoHL8ECwoEAwMVAwID FgIBAheAAAoJEGtrXbm1pSX6WZoAnRzHUYn+/MSVAsmK7bLJrAfmn8Y+AJ4uzZEX OxVuc0sGg/J0AqlYNpMcqrkBDQQ5qBzcEAQAhJgZzAKBjuKwS0owgknuN+5kSu9U tk75ZKRpBMTFfW1Js2E5v96M3Z4XAvyJFhQYaXWZn0QQY4PkrbbfKib4X3Onn/Gx M1mdtWKAXxb1+JuEH/dpVemt2EDLn6b2VVI5iE6U0HcrJjkvt7DLKsvQFRnnqd6M SHdN3XmxhY+VakcAAwUD/iTTv+fpM+Nn2izo7z0BmRu/+GwQgvOF8Qc+8YA6JgaA UUrD7nO3xUpkoK6gr1se2Wu98BFv2GSKRZZF9QljXn2vGNreYRRI9ZhWpKm3zflz uC7lz63QaiZdAPup37yWYXyaAvUvYufORC4hS9mZUgKbbOC+O6xdzkLBerBk/FK+ iEYEGBECAAYFAjmoHNwACgkQa2tdubWlJfqAvQCfWMWnlCab4pUJEvE4gjSFJ+EV 5LsAn2yeJT+7MWYKIQpPmGMMjeGkykK1 =tjOP -----END PGP PUBLIC KEY BLOCK----- |
|
From: Christophe F. <chr...@en...> - 2000-11-14 23:57:16
|
Le mer, 15 nov 2000 00:42:50, Scott Fenton a écrit : > On Tue, Nov 14, 2000 at 11:37:28AM +0100, the keyboard of Christophe > Fergeau was alleged to have written: > > Concerning the release of 1.0, you seem to focus on the amount of data > > we have. That's ok for me. But some day, we'll have to think of a way > to > > really be able to browse and visualize all these data. Indeed, the > current > > output format are not sufficient at all and the user can't have a > global > > view and really select what he is really interested in. With my > browser, I > > tried to make it easier to view the data we have but it is far from > being > > finished and currently, I am too busy to improve it (I think an editor > > option would be nice as well as a display of each node in html). > > Sounds good in theory, but the thing is that in pratice it's a little > hard to merge a CVS database and a web-vased wiewing. > For the display of each node in html, I just wanted to use the gtkhtml widget to replace the ugly textmode display of the browser. It shouldn't be difficult if I could find some doc concerning gtkhtml. Another thing I forgot, I think we should start adding photos of the old hardware (cpu, computers, ...) we are referencing. Christophe |
|
From: Scott F. <sj...@ra...> - 2000-11-14 23:43:10
|
On Tue, Nov 14, 2000 at 11:37:28AM +0100, the keyboard of Christophe Fergeau was alleged to have written: > Concerning the release of 1.0, you seem to focus on the amount of data > we have. That's ok for me. But some day, we'll have to think of a way to > really be able to browse and visualize all these data. Indeed, the current > output format are not sufficient at all and the user can't have a global > view and really select what he is really interested in. With my browser, I > tried to make it easier to view the data we have but it is far from being > finished and currently, I am too busy to improve it (I think an editor > option would be nice as well as a display of each node in html). Sounds good in theory, but the thing is that in pratice it's a little hard to merge a CVS database and a web-vased wiewing. > We could also implement a web database of what we have using php. Sounds like a good idea. I was kinda thinking something like this would work with DBM, CGI, and perl. > I already wrote all of this before 0.5 and my point of view did not > change. Sorry about that, but since late september, school has kinda got me working my ass off. > If you have other ideas concerning the display of our database, I'll > really like to discuss about it. > Otherwise, information about old sun hardware can be found at > www.obsolyte.com > and > www.sunhelp.org > > Christophe Thanks for the tip. > > > _______________________________________________ > Comp-hist-devel mailing list > Com...@li... > http://lists.sourceforge.net/mailman/listinfo/comp-hist-devel -- -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.0.2 (GNU/Linux) Comment: For info see http://www.gnupg.org mQGiBDmoHL8RBACt7yc65iKzR4IW2kKF0wjfZlRVwcwEws6HueM9uKF6HCzyFtyM XJiHz8f3LI2NY/GedfF+XTFc2zQlPummiOrHfAx9Y2hV4ajEpxNgqm36BT21vLuI iTB6roHHm+EiK9dRINyc+kB4v5QV5S9BGxPuygm/3yLZLmGH6RUmSxis1wCgvGnX n3qhbP7Yf/mLO1Du3oEJhR8EAI+TFhyxg3y2xv++xCxKOL9ofF+wPA4EkXPCAokW 10hDmeGY246wOMPWC0Hou1QJqqRN82n5BbJAzUnE/Iht82SEJgM1vhIbp0uShUdS jzKPnBBUTzLQFPbAG9hDaU/98JklsyDIbacavCuCtky6Xs/wmPjESUJsIl6FiHRv Uz9jA/96nxsDQ8YMEr51F3sHubn7BwrYqGOZLT5btLMG1i9OnWyy0npQ5wKvM2bT t2i6QPcHydTAkX+DLXQv8UeJE+Qpq+duoofMpxdFOKgqW3x0kKWGP14UoOqSQFGL K4fStiwR7fCtExrMFKUHaP5Sij7v8VoyBtyK+w45LoWFFXsPeLQhU2NvdHQgRmVu dG9uIDxzajEyZm5AcmFzY2hrZS5uZXQ+iFYEExECABYFAjmoHL8ECwoEAwMVAwID FgIBAheAAAoJEGtrXbm1pSX6WZoAnRzHUYn+/MSVAsmK7bLJrAfmn8Y+AJ4uzZEX OxVuc0sGg/J0AqlYNpMcqrkBDQQ5qBzcEAQAhJgZzAKBjuKwS0owgknuN+5kSu9U tk75ZKRpBMTFfW1Js2E5v96M3Z4XAvyJFhQYaXWZn0QQY4PkrbbfKib4X3Onn/Gx M1mdtWKAXxb1+JuEH/dpVemt2EDLn6b2VVI5iE6U0HcrJjkvt7DLKsvQFRnnqd6M SHdN3XmxhY+VakcAAwUD/iTTv+fpM+Nn2izo7z0BmRu/+GwQgvOF8Qc+8YA6JgaA UUrD7nO3xUpkoK6gr1se2Wu98BFv2GSKRZZF9QljXn2vGNreYRRI9ZhWpKm3zflz uC7lz63QaiZdAPup37yWYXyaAvUvYufORC4hS9mZUgKbbOC+O6xdzkLBerBk/FK+ iEYEGBECAAYFAjmoHNwACgkQa2tdubWlJfqAvQCfWMWnlCab4pUJEvE4gjSFJ+EV 5LsAn2yeJT+7MWYKIQpPmGMMjeGkykK1 =tjOP -----END PGP PUBLIC KEY BLOCK----- |
|
From: Christophe F. <cfe...@en...> - 2000-11-14 10:41:42
|
Concerning the release of 1.0, you seem to focus on the amount of data we have. That's ok for me. But some day, we'll have to think of a way to really be able to browse and visualize all these data. Indeed, the current output format are not sufficient at all and the user can't have a global view and really select what he is really interested in. With my browser, I tried to make it easier to view the data we have but it is far from being finished and currently, I am too busy to improve it (I think an editor option would be nice as well as a display of each node in html). We could also implement a web database of what we have using php. I already wrote all of this before 0.5 and my point of view did not change. If you have other ideas concerning the display of our database, I'll really like to discuss about it. Otherwise, information about old sun hardware can be found at www.obsolyte.com and www.sunhelp.org Christophe |
|
From: Kurt R. <ku...@ra...> - 2000-11-14 01:55:39
|
Since there's been a bit of confusion recently about the status of parsech, I thought that it might be a good idea for me to share my viewpoint on what needs doing: 1. Parsech doesn't use the date data in its VCG output. In other words, the transistor and the Tera MTA are on the same level, even though they were not created at the same time. 2. The most recent version of parsech in CVS broke support for shapes in VCG output, so now all entries are boxes. This isn't the way it used to be, so obviously something's changed that broke shape support. Scott, I'm not trying to minimize your efforts on parsech, I'm simply trying to summarize what needs to be done. -Kurt |
|
From: Kurt R. <ku...@ra...> - 2000-11-13 01:52:10
|
On Sun, Nov 12, 2000 at 02:52:49PM -0500, Scott Fenton wrote: > On Sun, Nov 12, 2000 at 10:23:32AM -0500, the keyboard of Kurt Raschke was alleged to have written: > > Well, we're now somewhat closer to 1.0 with the release of 0.9.1, and so I thought that this would be an ideal time to discuss what needs to be done. I've taken some of this from doc/goals, but it hasn't been updated in a long time, and thus isn't an accurate indicator. So, I'm just going to give a list of what I think needs to be done: > > Sun and SGI have directories and corp entries, but no data other that that. Well, actually the Solaris and SunOS trees are done, but that's it. > > I'm afraid that Sun and SGI HW will be hard to do, seeing as the two corp websites are utterly useless. > > > The Mac hardware tree is a mess. It's partially complete, and I'm not sure what to do with it. > > The Palm tree is on its way to being done, since the only thing that needs to be finished is PalmOS. > > The NeXT hardware tree is not moving, due to a lack of resources. We may want to do something about this. > > There have been between 2-3 web form submissions that haven't been dealt with, although it's completely possible that they were dealt with and I just missed it. Anyway, if you go to the following URL, you can see all of the submissions: > > http://www.geocrawler.com/search/?config=5378&words=web+submission+form+feedback > > > > Finally, parsech isn't done yet, and I think that that is a definite prerequisite for the release of 1.0. > > How is parsech not done? I mean, the only time we'll add to it is for new formats. While I ded make an earlier statement saying that parsech is done, now that I look at its VCG output, I found that it doesn't do dates. Tovcg did, so I don't know what happened there. Scott, I'd appreciate it if you could rectify this, since I'm getting rather confused by this situation. -Kurt > > > Scott and others, feel free to add to this, since I'm not completely sure of what needs to be done. > > > > -Kurt > > _______________________________________________ > > Comp-hist-devel mailing list > > Com...@li... > > http://lists.sourceforge.net/mailman/listinfo/comp-hist-devel > > -- > pub 1024D/B5A525FA 2000-08-26 Scott Fenton <sj...@ra...> > sub 1024g/A41E2502 2000-08-26 > _______________________________________________ > Comp-hist-devel mailing list > Com...@li... > http://lists.sourceforge.net/mailman/listinfo/comp-hist-devel |
|
From: Kurt R. <ku...@ra...> - 2000-11-13 01:38:30
|
On Sun, Nov 12, 2000 at 02:52:49PM -0500, Scott Fenton wrote: > On Sun, Nov 12, 2000 at 10:23:32AM -0500, the keyboard of Kurt Raschke was alleged to have written: > > Well, we're now somewhat closer to 1.0 with the release of 0.9.1, and so I thought that this would be an ideal time to discuss what needs to be done. I've taken some of this from doc/goals, but it hasn't been updated in a long time, and thus isn't an accurate indicator. So, I'm just going to give a list of what I think needs to be done: > > Sun and SGI have directories and corp entries, but no data other that that. Well, actually the Solaris and SunOS trees are done, but that's it. > > I'm afraid that Sun and SGI HW will be hard to do, seeing as the two corp websites are utterly useless. However, that doesn't mean that there won't be other sites that provide useful information. > > > The Mac hardware tree is a mess. It's partially complete, and I'm not sure what to do with it. > > The Palm tree is on its way to being done, since the only thing that needs to be finished is PalmOS. > > The NeXT hardware tree is not moving, due to a lack of resources. We may want to do something about this. > > There have been between 2-3 web form submissions that haven't been dealt with, although it's completely possible that they were dealt with and I just missed it. Anyway, if you go to the following URL, you can see all of the submissions: > > http://www.geocrawler.com/search/?config=5378&words=web+submission+form+feedback > > > > Finally, parsech isn't done yet, and I think that that is a definite prerequisite for the release of 1.0. > > How is parsech not done? I mean, the only time we'll add to it is for new formats. OK, I was confused, parsech IS done. > > > Scott and others, feel free to add to this, since I'm not completely sure of what needs to be done. > > > > -Kurt > > _______________________________________________ > > Comp-hist-devel mailing list > > Com...@li... > > http://lists.sourceforge.net/mailman/listinfo/comp-hist-devel > > -- > pub 1024D/B5A525FA 2000-08-26 Scott Fenton <sj...@ra...> > sub 1024g/A41E2502 2000-08-26 > _______________________________________________ > Comp-hist-devel mailing list > Com...@li... > http://lists.sourceforge.net/mailman/listinfo/comp-hist-devel |
|
From: Scott F. <sj...@ra...> - 2000-11-12 19:52:54
|
On Sun, Nov 12, 2000 at 10:23:32AM -0500, the keyboard of Kurt Raschke was alleged to have written: > Well, we're now somewhat closer to 1.0 with the release of 0.9.1, and so I thought that this would be an ideal time to discuss what needs to be done. I've taken some of this from doc/goals, but it hasn't been updated in a long time, and thus isn't an accurate indicator. So, I'm just going to give a list of what I think needs to be done: > Sun and SGI have directories and corp entries, but no data other that that. Well, actually the Solaris and SunOS trees are done, but that's it. I'm afraid that Sun and SGI HW will be hard to do, seeing as the two corp websites are utterly useless. > The Mac hardware tree is a mess. It's partially complete, and I'm not sure what to do with it. > The Palm tree is on its way to being done, since the only thing that needs to be finished is PalmOS. > The NeXT hardware tree is not moving, due to a lack of resources. We may want to do something about this. > There have been between 2-3 web form submissions that haven't been dealt with, although it's completely possible that they were dealt with and I just missed it. Anyway, if you go to the following URL, you can see all of the submissions: > http://www.geocrawler.com/search/?config=5378&words=web+submission+form+feedback > > Finally, parsech isn't done yet, and I think that that is a definite prerequisite for the release of 1.0. How is parsech not done? I mean, the only time we'll add to it is for new formats. > Scott and others, feel free to add to this, since I'm not completely sure of what needs to be done. > > -Kurt > _______________________________________________ > Comp-hist-devel mailing list > Com...@li... > http://lists.sourceforge.net/mailman/listinfo/comp-hist-devel -- -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.0.2 (GNU/Linux) Comment: For info see http://www.gnupg.org mQGiBDmoHL8RBACt7yc65iKzR4IW2kKF0wjfZlRVwcwEws6HueM9uKF6HCzyFtyM XJiHz8f3LI2NY/GedfF+XTFc2zQlPummiOrHfAx9Y2hV4ajEpxNgqm36BT21vLuI iTB6roHHm+EiK9dRINyc+kB4v5QV5S9BGxPuygm/3yLZLmGH6RUmSxis1wCgvGnX n3qhbP7Yf/mLO1Du3oEJhR8EAI+TFhyxg3y2xv++xCxKOL9ofF+wPA4EkXPCAokW 10hDmeGY246wOMPWC0Hou1QJqqRN82n5BbJAzUnE/Iht82SEJgM1vhIbp0uShUdS jzKPnBBUTzLQFPbAG9hDaU/98JklsyDIbacavCuCtky6Xs/wmPjESUJsIl6FiHRv Uz9jA/96nxsDQ8YMEr51F3sHubn7BwrYqGOZLT5btLMG1i9OnWyy0npQ5wKvM2bT t2i6QPcHydTAkX+DLXQv8UeJE+Qpq+duoofMpxdFOKgqW3x0kKWGP14UoOqSQFGL K4fStiwR7fCtExrMFKUHaP5Sij7v8VoyBtyK+w45LoWFFXsPeLQhU2NvdHQgRmVu dG9uIDxzajEyZm5AcmFzY2hrZS5uZXQ+iFYEExECABYFAjmoHL8ECwoEAwMVAwID FgIBAheAAAoJEGtrXbm1pSX6WZoAnRzHUYn+/MSVAsmK7bLJrAfmn8Y+AJ4uzZEX OxVuc0sGg/J0AqlYNpMcqrkBDQQ5qBzcEAQAhJgZzAKBjuKwS0owgknuN+5kSu9U tk75ZKRpBMTFfW1Js2E5v96M3Z4XAvyJFhQYaXWZn0QQY4PkrbbfKib4X3Onn/Gx M1mdtWKAXxb1+JuEH/dpVemt2EDLn6b2VVI5iE6U0HcrJjkvt7DLKsvQFRnnqd6M SHdN3XmxhY+VakcAAwUD/iTTv+fpM+Nn2izo7z0BmRu/+GwQgvOF8Qc+8YA6JgaA UUrD7nO3xUpkoK6gr1se2Wu98BFv2GSKRZZF9QljXn2vGNreYRRI9ZhWpKm3zflz uC7lz63QaiZdAPup37yWYXyaAvUvYufORC4hS9mZUgKbbOC+O6xdzkLBerBk/FK+ iEYEGBECAAYFAjmoHNwACgkQa2tdubWlJfqAvQCfWMWnlCab4pUJEvE4gjSFJ+EV 5LsAn2yeJT+7MWYKIQpPmGMMjeGkykK1 =tjOP -----END PGP PUBLIC KEY BLOCK----- |
|
From: Kurt R. <ku...@ra...> - 2000-11-12 15:23:36
|
Well, we're now somewhat closer to 1.0 with the release of 0.9.1, and so I thought that this would be an ideal time to discuss what needs to be done. I've taken some of this from doc/goals, but it hasn't been updated in a long time, and thus isn't an accurate indicator. So, I'm just going to give a list of what I think needs to be done: Sun and SGI have directories and corp entries, but no data other that that. Well, actually the Solaris and SunOS trees are done, but that's it. The Mac hardware tree is a mess. It's partially complete, and I'm not sure what to do with it. The Palm tree is on its way to being done, since the only thing that needs to be finished is PalmOS. The NeXT hardware tree is not moving, due to a lack of resources. We may want to do something about this. There have been between 2-3 web form submissions that haven't been dealt with, although it's completely possible that they were dealt with and I just missed it. Anyway, if you go to the following URL, you can see all of the submissions: http://www.geocrawler.com/search/?config=5378&words=web+submission+form+feedback Finally, parsech isn't done yet, and I think that that is a definite prerequisite for the release of 1.0. Scott and others, feel free to add to this, since I'm not completely sure of what needs to be done. -Kurt |
|
From: <sna...@w3...> - 2000-11-08 13:20:39
|
Below is the result of your feedback form. It was submitted by Fábio R. Schmidlin (sna...@w3...) on Wednesday, November 8, 2000 at 05:20:38 --------------------------------------------------------------------------- type: add othersubj: MSX nodes: Microsoft, ASCII message: Virtually unknown on USA, the MSX system was one of the greatest systems ever build. As a open system, all major manufacturers like Panasonic, Sony, Sharp, Philips, Casio, Yamaha, Sanyo, Toshiba, Mitsubishi build their machines. Only one manufacturer build a very simple MSX1 on USA: Spectravideo. But they broke before the sales raise. 1983: MSX1 1985: MSX2 1988: MSX2+ 1990: MSX Turbo-R More information can be found on: http://www.faq.msxnet.org/ http://www.homecomputer.de/ (gallery->machine pics->MSX) --------------------------------------------------------------------------- REMOTE_ADDR: 200.250.58.147 HTTP_USER_AGENT: Mozilla/4.75 [en] (X11; U; Linux 2.2.14-14cl i586) |
|
From: Kurt R. <ku...@ra...> - 2000-10-30 20:13:51
|
Version 0.9.1 of the Computer History Graphing Project, a project that aims to create a history tree for all of computerdom, today released version 0.9.1. This version contains a new GTK-based visual tree browser, and an updated version of the new, unified parser program, parsech. The history trees themselves have also been updated, including the new tree for PalmOS devices. The project can be found at http://comp-hist.sourceforge.net, and you can reach the developers at ku...@us..., or sj...@us.... -Kurt Raschke |
|
From: Scott F. <sj...@ra...> - 2000-10-09 12:21:00
|
Sure, send it to me. I'll post it. On Mon, Oct 09, 2000 at 12:50:59PM +0200, the keyboard of Christophe Fergeau was alleged to have written: > I have just written a browser using gtk which hierarchically displays the > contents of a data file (I will add a modification option soon). > Unfortunately, I can't put it to cvs and I have > no means to make it available to everyone for testing. The file is 100k > tgz (because Glade added a lot of extra stuff). May I send it to someone > who can then make it available for everyone? > > Christophe > > _______________________________________________ > Comp-hist-devel mailing list > Com...@li... > http://lists.sourceforge.net/mailman/listinfo/comp-hist-devel -- -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.0.2 (GNU/Linux) Comment: For info see http://www.gnupg.org mQGiBDmoHL8RBACt7yc65iKzR4IW2kKF0wjfZlRVwcwEws6HueM9uKF6HCzyFtyM XJiHz8f3LI2NY/GedfF+XTFc2zQlPummiOrHfAx9Y2hV4ajEpxNgqm36BT21vLuI iTB6roHHm+EiK9dRINyc+kB4v5QV5S9BGxPuygm/3yLZLmGH6RUmSxis1wCgvGnX n3qhbP7Yf/mLO1Du3oEJhR8EAI+TFhyxg3y2xv++xCxKOL9ofF+wPA4EkXPCAokW 10hDmeGY246wOMPWC0Hou1QJqqRN82n5BbJAzUnE/Iht82SEJgM1vhIbp0uShUdS jzKPnBBUTzLQFPbAG9hDaU/98JklsyDIbacavCuCtky6Xs/wmPjESUJsIl6FiHRv Uz9jA/96nxsDQ8YMEr51F3sHubn7BwrYqGOZLT5btLMG1i9OnWyy0npQ5wKvM2bT t2i6QPcHydTAkX+DLXQv8UeJE+Qpq+duoofMpxdFOKgqW3x0kKWGP14UoOqSQFGL K4fStiwR7fCtExrMFKUHaP5Sij7v8VoyBtyK+w45LoWFFXsPeLQhU2NvdHQgRmVu dG9uIDxzajEyZm5AcmFzY2hrZS5uZXQ+iFYEExECABYFAjmoHL8ECwoEAwMVAwID FgIBAheAAAoJEGtrXbm1pSX6WZoAnRzHUYn+/MSVAsmK7bLJrAfmn8Y+AJ4uzZEX OxVuc0sGg/J0AqlYNpMcqrkBDQQ5qBzcEAQAhJgZzAKBjuKwS0owgknuN+5kSu9U tk75ZKRpBMTFfW1Js2E5v96M3Z4XAvyJFhQYaXWZn0QQY4PkrbbfKib4X3Onn/Gx M1mdtWKAXxb1+JuEH/dpVemt2EDLn6b2VVI5iE6U0HcrJjkvt7DLKsvQFRnnqd6M SHdN3XmxhY+VakcAAwUD/iTTv+fpM+Nn2izo7z0BmRu/+GwQgvOF8Qc+8YA6JgaA UUrD7nO3xUpkoK6gr1se2Wu98BFv2GSKRZZF9QljXn2vGNreYRRI9ZhWpKm3zflz uC7lz63QaiZdAPup37yWYXyaAvUvYufORC4hS9mZUgKbbOC+O6xdzkLBerBk/FK+ iEYEGBECAAYFAjmoHNwACgkQa2tdubWlJfqAvQCfWMWnlCab4pUJEvE4gjSFJ+EV 5LsAn2yeJT+7MWYKIQpPmGMMjeGkykK1 =tjOP -----END PGP PUBLIC KEY BLOCK----- |
|
From: Christophe F. <cfe...@en...> - 2000-10-09 10:53:52
|
I have just written a browser using gtk which hierarchically displays the contents of a data file (I will add a modification option soon). Unfortunately, I can't put it to cvs and I have no means to make it available to everyone for testing. The file is 100k tgz (because Glade added a lot of extra stuff). May I send it to someone who can then make it available for everyone? Christophe |
|
From: Kurt R. <ku...@ra...> - 2000-10-04 00:46:39
|
I suppose we could pull the <BR> tag out of the HTML DTD, although then we should also make the "link" tag function as a link within the browser, if it doesn't already. Under what license are the W3C DTDs? If it permits use in derivative works, then we should be fine. If not, then we may have problems. -Kurt On Tue, Oct 03, 2000 at 05:50:06PM -0400, Scott Fenton wrote: > On Tue, Oct 03, 2000 at 03:44:19PM -0400, the keyboard of Kurt Raschke was alleged to have written: > > I've been looking over the output of the XML parser, and I see a few bugs. For onw thing, a number of the dates are fouled up, and yet they are correct in the data files. Also, some of the nodes that use a status field have invalid entries. Also, are there plans to integrate an html output function into parsech? > > I noticed that too. I can't figure out why that happens, though. And yes, I will soon add html to the targets (along with correct VCG and GViz). > > > > > On a related note, what is the current handling of \n in parsech? I know the C parsers don't seem to translate it to a CR, or a <p> in html. > > > > \n was always handled by the dot and VCG tools themselves, so I'm still debating how to handle it in parsech. However, a <br /> tag in CHML would nice. > > -Scott > > > -- > pub 1024D/B5A525FA 2000-08-26 Scott Fenton <sj...@ra...> > sub 1024g/A41E2502 2000-08-26 > _______________________________________________ > Comp-hist-devel mailing list > Com...@li... > http://lists.sourceforge.net/mailman/listinfo/comp-hist-devel |
|
From: Scott F. <sj...@ra...> - 2000-10-03 21:50:23
|
On Tue, Oct 03, 2000 at 03:44:19PM -0400, the keyboard of Kurt Raschke was alleged to have written: > I've been looking over the output of the XML parser, and I see a few bugs. For onw thing, a number of the dates are fouled up, and yet they are correct in the data files. Also, some of the nodes that use a status field have invalid entries. Also, are there plans to integrate an html output function into parsech? I noticed that too. I can't figure out why that happens, though. And yes, I will soon add html to the targets (along with correct VCG and GViz). > > On a related note, what is the current handling of \n in parsech? I know the C parsers don't seem to translate it to a CR, or a <p> in html. > \n was always handled by the dot and VCG tools themselves, so I'm still debating how to handle it in parsech. However, a <br /> tag in CHML would nice. -Scott -- -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.0.2 (GNU/Linux) Comment: For info see http://www.gnupg.org mQGiBDmoHL8RBACt7yc65iKzR4IW2kKF0wjfZlRVwcwEws6HueM9uKF6HCzyFtyM XJiHz8f3LI2NY/GedfF+XTFc2zQlPummiOrHfAx9Y2hV4ajEpxNgqm36BT21vLuI iTB6roHHm+EiK9dRINyc+kB4v5QV5S9BGxPuygm/3yLZLmGH6RUmSxis1wCgvGnX n3qhbP7Yf/mLO1Du3oEJhR8EAI+TFhyxg3y2xv++xCxKOL9ofF+wPA4EkXPCAokW 10hDmeGY246wOMPWC0Hou1QJqqRN82n5BbJAzUnE/Iht82SEJgM1vhIbp0uShUdS jzKPnBBUTzLQFPbAG9hDaU/98JklsyDIbacavCuCtky6Xs/wmPjESUJsIl6FiHRv Uz9jA/96nxsDQ8YMEr51F3sHubn7BwrYqGOZLT5btLMG1i9OnWyy0npQ5wKvM2bT t2i6QPcHydTAkX+DLXQv8UeJE+Qpq+duoofMpxdFOKgqW3x0kKWGP14UoOqSQFGL K4fStiwR7fCtExrMFKUHaP5Sij7v8VoyBtyK+w45LoWFFXsPeLQhU2NvdHQgRmVu dG9uIDxzajEyZm5AcmFzY2hrZS5uZXQ+iFYEExECABYFAjmoHL8ECwoEAwMVAwID FgIBAheAAAoJEGtrXbm1pSX6WZoAnRzHUYn+/MSVAsmK7bLJrAfmn8Y+AJ4uzZEX OxVuc0sGg/J0AqlYNpMcqrkBDQQ5qBzcEAQAhJgZzAKBjuKwS0owgknuN+5kSu9U tk75ZKRpBMTFfW1Js2E5v96M3Z4XAvyJFhQYaXWZn0QQY4PkrbbfKib4X3Onn/Gx M1mdtWKAXxb1+JuEH/dpVemt2EDLn6b2VVI5iE6U0HcrJjkvt7DLKsvQFRnnqd6M SHdN3XmxhY+VakcAAwUD/iTTv+fpM+Nn2izo7z0BmRu/+GwQgvOF8Qc+8YA6JgaA UUrD7nO3xUpkoK6gr1se2Wu98BFv2GSKRZZF9QljXn2vGNreYRRI9ZhWpKm3zflz uC7lz63QaiZdAPup37yWYXyaAvUvYufORC4hS9mZUgKbbOC+O6xdzkLBerBk/FK+ iEYEGBECAAYFAjmoHNwACgkQa2tdubWlJfqAvQCfWMWnlCab4pUJEvE4gjSFJ+EV 5LsAn2yeJT+7MWYKIQpPmGMMjeGkykK1 =tjOP -----END PGP PUBLIC KEY BLOCK----- |
|
From: Kurt R. <ku...@ra...> - 2000-10-03 19:44:34
|
I've been looking over the output of the XML parser, and I see a few bugs. For onw thing, a number of the dates are fouled up, and yet they are correct in the data files. Also, some of the nodes that use a status field have invalid entries. Also, are there plans to integrate an html output function into parsech? On a related note, what is the current handling of \n in parsech? I know the C parsers don't seem to translate it to a CR, or a <p> in html. -Kurt |
|
From: <chr...@en...> - 2000-10-02 09:34:21
|
Soory for not doing much for the project for the moment but I have a lot of work to do. When I have time, I'll have a try with a php or a gtk interface to edit the data in our database unless it is not useful (I didn't look at 0.9 yet) On Slashdot, there is a link to an article on the UK's Daily Telegraph which contains security restriction about the first digital computer (didn't read it). It may be interesting Christophe |
|
From: <dp...@en...> - 2000-10-01 02:28:52
|
Below is the result of your feedback form. It was submitted by Daniel Price (dp...@en...) on Saturday, September 30, 2000 at 19:28:51 --------------------------------------------------------------------------- type: add othersubj: Solaris Corrections nodes: Solaris 2.6, Solaris 2.5\n(SunOS 5.5), SunOS 5\n(Solaris 1.3) message: A new node should be added: Solaris 2.5.1 (SunOS 5.5.1) Type: OS Date: May 1996 Successor to: Solaris 2.5 The Solaris 2.6 node should be replaced with a more accurate date, and include the SunOS number scheme. Solaris 2.6 (SunOS 5.6) Type: OS Date: Aug. 1997 Successor to: Solaris 2.5.1 This entry: SunOS 5\n(Solaris 1.3) Type : OS Date : 1994 Oct Reference : http://perso.wanadoo.fr/levenez/unix/index.html Status : released Successor to : SunOS 4.1.4\n(Solaris 1.1.2) Is inaccurate and should be deleted, as far as I can discover. --------------------------------------------------------------------------- REMOTE_ADDR: 192.9.25.21 HTTP_USER_AGENT: Mozilla/4.75 [en] (X11; U; SunOS 5.8 sun4u; Nav) |
|
From: Scott F. <sj...@ra...> - 2000-09-30 17:47:17
|
Yes, I have put 0.9 out. Yes, this took /way/ too long, but I've been tied up lately, so here it is. FM will be announcing us soon. -Scott -- -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.0.2 (GNU/Linux) Comment: For info see http://www.gnupg.org mQGiBDmoHL8RBACt7yc65iKzR4IW2kKF0wjfZlRVwcwEws6HueM9uKF6HCzyFtyM XJiHz8f3LI2NY/GedfF+XTFc2zQlPummiOrHfAx9Y2hV4ajEpxNgqm36BT21vLuI iTB6roHHm+EiK9dRINyc+kB4v5QV5S9BGxPuygm/3yLZLmGH6RUmSxis1wCgvGnX n3qhbP7Yf/mLO1Du3oEJhR8EAI+TFhyxg3y2xv++xCxKOL9ofF+wPA4EkXPCAokW 10hDmeGY246wOMPWC0Hou1QJqqRN82n5BbJAzUnE/Iht82SEJgM1vhIbp0uShUdS jzKPnBBUTzLQFPbAG9hDaU/98JklsyDIbacavCuCtky6Xs/wmPjESUJsIl6FiHRv Uz9jA/96nxsDQ8YMEr51F3sHubn7BwrYqGOZLT5btLMG1i9OnWyy0npQ5wKvM2bT t2i6QPcHydTAkX+DLXQv8UeJE+Qpq+duoofMpxdFOKgqW3x0kKWGP14UoOqSQFGL K4fStiwR7fCtExrMFKUHaP5Sij7v8VoyBtyK+w45LoWFFXsPeLQhU2NvdHQgRmVu dG9uIDxzajEyZm5AcmFzY2hrZS5uZXQ+iFYEExECABYFAjmoHL8ECwoEAwMVAwID FgIBAheAAAoJEGtrXbm1pSX6WZoAnRzHUYn+/MSVAsmK7bLJrAfmn8Y+AJ4uzZEX OxVuc0sGg/J0AqlYNpMcqrkBDQQ5qBzcEAQAhJgZzAKBjuKwS0owgknuN+5kSu9U tk75ZKRpBMTFfW1Js2E5v96M3Z4XAvyJFhQYaXWZn0QQY4PkrbbfKib4X3Onn/Gx M1mdtWKAXxb1+JuEH/dpVemt2EDLn6b2VVI5iE6U0HcrJjkvt7DLKsvQFRnnqd6M SHdN3XmxhY+VakcAAwUD/iTTv+fpM+Nn2izo7z0BmRu/+GwQgvOF8Qc+8YA6JgaA UUrD7nO3xUpkoK6gr1se2Wu98BFv2GSKRZZF9QljXn2vGNreYRRI9ZhWpKm3zflz uC7lz63QaiZdAPup37yWYXyaAvUvYufORC4hS9mZUgKbbOC+O6xdzkLBerBk/FK+ iEYEGBECAAYFAjmoHNwACgkQa2tdubWlJfqAvQCfWMWnlCab4pUJEvE4gjSFJ+EV 5LsAn2yeJT+7MWYKIQpPmGMMjeGkykK1 =tjOP -----END PGP PUBLIC KEY BLOCK----- |
|
From: Scott F. <sj...@ra...> - 2000-09-28 20:22:10
|
On Wed, Sep 27, 2000 at 10:33:51AM +0100, the keyboard of Hans B Pufal was alleged to have written: > My be you have seen this, came across it by accident today: > > <http://www.sucs.swan.ac.uk/~firefury/university/CS_309/dissertation/> > > It includes what appears to be quite a complete family tree of Unix > derivatives at the end of the paper. > > -- Hans Thanks for the link, but the tree is the one I just merged in a few weeks ago! Thanks anyway. -Scott -- -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.0.2 (GNU/Linux) Comment: For info see http://www.gnupg.org mQGiBDmoHL8RBACt7yc65iKzR4IW2kKF0wjfZlRVwcwEws6HueM9uKF6HCzyFtyM XJiHz8f3LI2NY/GedfF+XTFc2zQlPummiOrHfAx9Y2hV4ajEpxNgqm36BT21vLuI iTB6roHHm+EiK9dRINyc+kB4v5QV5S9BGxPuygm/3yLZLmGH6RUmSxis1wCgvGnX n3qhbP7Yf/mLO1Du3oEJhR8EAI+TFhyxg3y2xv++xCxKOL9ofF+wPA4EkXPCAokW 10hDmeGY246wOMPWC0Hou1QJqqRN82n5BbJAzUnE/Iht82SEJgM1vhIbp0uShUdS jzKPnBBUTzLQFPbAG9hDaU/98JklsyDIbacavCuCtky6Xs/wmPjESUJsIl6FiHRv Uz9jA/96nxsDQ8YMEr51F3sHubn7BwrYqGOZLT5btLMG1i9OnWyy0npQ5wKvM2bT t2i6QPcHydTAkX+DLXQv8UeJE+Qpq+duoofMpxdFOKgqW3x0kKWGP14UoOqSQFGL K4fStiwR7fCtExrMFKUHaP5Sij7v8VoyBtyK+w45LoWFFXsPeLQhU2NvdHQgRmVu dG9uIDxzajEyZm5AcmFzY2hrZS5uZXQ+iFYEExECABYFAjmoHL8ECwoEAwMVAwID FgIBAheAAAoJEGtrXbm1pSX6WZoAnRzHUYn+/MSVAsmK7bLJrAfmn8Y+AJ4uzZEX OxVuc0sGg/J0AqlYNpMcqrkBDQQ5qBzcEAQAhJgZzAKBjuKwS0owgknuN+5kSu9U tk75ZKRpBMTFfW1Js2E5v96M3Z4XAvyJFhQYaXWZn0QQY4PkrbbfKib4X3Onn/Gx M1mdtWKAXxb1+JuEH/dpVemt2EDLn6b2VVI5iE6U0HcrJjkvt7DLKsvQFRnnqd6M SHdN3XmxhY+VakcAAwUD/iTTv+fpM+Nn2izo7z0BmRu/+GwQgvOF8Qc+8YA6JgaA UUrD7nO3xUpkoK6gr1se2Wu98BFv2GSKRZZF9QljXn2vGNreYRRI9ZhWpKm3zflz uC7lz63QaiZdAPup37yWYXyaAvUvYufORC4hS9mZUgKbbOC+O6xdzkLBerBk/FK+ iEYEGBECAAYFAjmoHNwACgkQa2tdubWlJfqAvQCfWMWnlCab4pUJEvE4gjSFJ+EV 5LsAn2yeJT+7MWYKIQpPmGMMjeGkykK1 =tjOP -----END PGP PUBLIC KEY BLOCK----- |
|
From: Hans B P. <ha...@di...> - 2000-09-28 05:52:44
|
> Hans B Pufal wrote: > > My be you have seen this, came across it by accident today: > > <http://www.sucs.swan.ac.uk/~firefury/university/CS_309/dissertation/> Apologies for posting the entire dissertation! I thought I was posting just the link! -- Hans |
|
From: Hans B P. <ha...@di...> - 2000-09-27 08:35:52
|
My be you have seen this, came across it by accident today: <http://www.sucs.swan.ac.uk/~firefury/university/CS_309/dissertation/> It includes what appears to be quite a complete family tree of Unix derivatives at the end of the paper. -- Hans |
|
From: Scott F. <sj...@ra...> - 2000-09-24 01:42:42
|
OK, I have offically given up on /ever/ getting ParseCH to work correctly. Instead, we now have parsech, a maser perl parser. It is one parser that will (eventually) obsolete tovcg, todot, info, reference, and toxml. It will take a switch that controls the output format. Oh, and it will have POD documentation too. The beginnings of this parser are now in CVS. I got a lot done quickly by taking tovcg and stripping out the output subroutine. It will, of course, soon be reimpimented (along with dot, xml, html, and vrml output formats). Take a look! -Scott -- -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.0.2 (GNU/Linux) Comment: For info see http://www.gnupg.org mQGiBDmoHL8RBACt7yc65iKzR4IW2kKF0wjfZlRVwcwEws6HueM9uKF6HCzyFtyM XJiHz8f3LI2NY/GedfF+XTFc2zQlPummiOrHfAx9Y2hV4ajEpxNgqm36BT21vLuI iTB6roHHm+EiK9dRINyc+kB4v5QV5S9BGxPuygm/3yLZLmGH6RUmSxis1wCgvGnX n3qhbP7Yf/mLO1Du3oEJhR8EAI+TFhyxg3y2xv++xCxKOL9ofF+wPA4EkXPCAokW 10hDmeGY246wOMPWC0Hou1QJqqRN82n5BbJAzUnE/Iht82SEJgM1vhIbp0uShUdS jzKPnBBUTzLQFPbAG9hDaU/98JklsyDIbacavCuCtky6Xs/wmPjESUJsIl6FiHRv Uz9jA/96nxsDQ8YMEr51F3sHubn7BwrYqGOZLT5btLMG1i9OnWyy0npQ5wKvM2bT t2i6QPcHydTAkX+DLXQv8UeJE+Qpq+duoofMpxdFOKgqW3x0kKWGP14UoOqSQFGL K4fStiwR7fCtExrMFKUHaP5Sij7v8VoyBtyK+w45LoWFFXsPeLQhU2NvdHQgRmVu dG9uIDxzajEyZm5AcmFzY2hrZS5uZXQ+iFYEExECABYFAjmoHL8ECwoEAwMVAwID FgIBAheAAAoJEGtrXbm1pSX6WZoAnRzHUYn+/MSVAsmK7bLJrAfmn8Y+AJ4uzZEX OxVuc0sGg/J0AqlYNpMcqrkBDQQ5qBzcEAQAhJgZzAKBjuKwS0owgknuN+5kSu9U tk75ZKRpBMTFfW1Js2E5v96M3Z4XAvyJFhQYaXWZn0QQY4PkrbbfKib4X3Onn/Gx M1mdtWKAXxb1+JuEH/dpVemt2EDLn6b2VVI5iE6U0HcrJjkvt7DLKsvQFRnnqd6M SHdN3XmxhY+VakcAAwUD/iTTv+fpM+Nn2izo7z0BmRu/+GwQgvOF8Qc+8YA6JgaA UUrD7nO3xUpkoK6gr1se2Wu98BFv2GSKRZZF9QljXn2vGNreYRRI9ZhWpKm3zflz uC7lz63QaiZdAPup37yWYXyaAvUvYufORC4hS9mZUgKbbOC+O6xdzkLBerBk/FK+ iEYEGBECAAYFAjmoHNwACgkQa2tdubWlJfqAvQCfWMWnlCab4pUJEvE4gjSFJ+EV 5LsAn2yeJT+7MWYKIQpPmGMMjeGkykK1 =tjOP -----END PGP PUBLIC KEY BLOCK----- |