Menu
▾
▴
comp-hist-devel — This list is for discussion regarding development of the comp-hist project.
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-12-07 14:47:01
|
On Tue, Dec 05, 2000 at 08:10:34PM -0500, the keyboard of Kurt Raschke was alleged to have written: > Scott, what is the status of documentation forthe ParseCH Perl modules and the separate output parsers? I ask this because doc/parsech and http://comp-hist/parsceh.html are all now quite outdated. Also, I was wondering if it would be possible for you to create a small doc describing the interface with ParseCH.pm for those people who want to create a new output module. Try sharpening your perl skills a little and looking through the code to document it. No offense, but I don't really feel like writing POD right now -Scott > > -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-12-06 01:10:51
|
Scott, what is the status of documentation forthe ParseCH Perl modules and the separate output parsers? I ask this because doc/parsech and http://comp-hist/parsceh.html are all now quite outdated. Also, I was wondering if it would be possible for you to create a small doc describing the interface with ParseCH.pm for those people who want to create a new output module. -Kurt |
|
From: Scott F. <sj...@ra...> - 2000-12-04 16:37:42
|
On Sun, Dec 03, 2000 at 08:45:09PM -0500, the keyboard of Kurt Raschke was alleged to have written: > Since the C parser no longer is used by the Makefile, I'd like to get rid of it. Would anyone mind if I did that? No complaints. In fact, I encourage it. > > -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: Scott F. <sj...@ra...> - 2000-12-04 16:35:14
|
On Sun, Dec 03, 2000 at 08:04:28PM -0500, the keyboard of Kurt Raschke was alleged to have written: > Scott, I'd like to add a tag to the repository now to mark the point that parsech got broken up. Any problems with this? Fine by me. -Scott > > > -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-12-04 01:45:15
|
Since the C parser no longer is used by the Makefile, I'd like to get rid of it. Would anyone mind if I did that? -Kurt |
|
From: Kurt R. <ku...@ra...> - 2000-12-04 01:04:33
|
Scott, I'd like to add a tag to the repository now to mark the point that parsech got broken up. Any problems with this? -Kurt |
|
From: Scott F. <sj...@ra...> - 2000-12-03 04:59:31
|
Hello all. After trying parsech out for a while, I've decided that it's an ugly kludge, and it should be tossed. So, I am sending this message to warn all of you that parsech is hearby split. The seperate programs use a perl module to share one parser, and the new modules will be committed to CVS as soon as I finish this message. -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-30 14:48:55
|
On Wed, Nov 29, 2000 at 08:16:42PM -0500, the keyboard of Kurt Raschke was alleged to have written: > I noticed that the POD for the parsech internals is now gone. As a resul, there are a number of broken links in the POD, which should be fixed. However, whatI'm wondering is, what's the rationale for killing off of the internals POD? The rational is that the POD sshould end up being like a man page, and man pages don't describe how the program works. > > Also, what's the purpose of unexpand in the latest Makefile? The parser has been altered to look for a tab at the beginning of each line before a command (like todot orgininally did, remember?). Unexpand changes 8 spaces to a tab, so we get around the stuff I told you about when we first started this. -Scott > > -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: Scott F. <sj...@ra...> - 2000-11-30 02:44:08
|
On Wed, Nov 29, 2000 at 08:52:37PM -0500, the keyboard of Kurt Raschke was alleged to have written: > I have two ideas: > 1. Why not create some sort of text-based spreadsheet-like output format for getting a quick visual overivew of a node's stats? That could work. I'll look into it after the big split. > > 2. It might be nice if there was a option to parsech that would flag and print a note about errors found in the input, instead of silently ignoring them. > That's a little hard to engineer. What the parser thinks as it looks through the file is something like this: "gee does this field match this regexp?" It would be kinda hard to set it to flag an error when it sees one. > -Kurt > On Wed, Nov 29, 2000 at 08:27:59PM -0500, Scott Fenton wrote: > > OK, if any of you have been paying attention to CVS lately, > > you'll notice that I've been making quite a few changes to > > parsech. I'm writing this to explain these changes, and > > why I'm doing them. > > > > First, the what. I'm working to make each subroutine less > > dependent on others. Ulimatly, there will only be the %Opts > > hash as a universal variable. Even though I haven't checked > > it into CVS yet (there are a few kinks in the system), I've > > begun the final stage of all of this on one of the subs. > > > > Now, the why. Quite simply, I'm working to break up parsech. > > I believe it has become an ugly hairball that will be > > impossible to maintain eventually. I'm going to give ParseCH.pm > > another try, see if I can get it this time. > > > > Thoughts? Suggestions? Jelly doughnuts? Reply with them. > > > > -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 > _______________________________________________ > 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-30 01:53:04
|
I have two ideas: 1. Why not create some sort of text-based spreadsheet-like output format for getting a quick visual overivew of a node's stats? 2. It might be nice if there was a option to parsech that would flag and print a note about errors found in the input, instead of silently ignoring them. -Kurt On Wed, Nov 29, 2000 at 08:27:59PM -0500, Scott Fenton wrote: > OK, if any of you have been paying attention to CVS lately, > you'll notice that I've been making quite a few changes to > parsech. I'm writing this to explain these changes, and > why I'm doing them. > > First, the what. I'm working to make each subroutine less > dependent on others. Ulimatly, there will only be the %Opts > hash as a universal variable. Even though I haven't checked > it into CVS yet (there are a few kinks in the system), I've > begun the final stage of all of this on one of the subs. > > Now, the why. Quite simply, I'm working to break up parsech. > I believe it has become an ugly hairball that will be > impossible to maintain eventually. I'm going to give ParseCH.pm > another try, see if I can get it this time. > > Thoughts? Suggestions? Jelly doughnuts? Reply with them. > > -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-11-30 01:28:22
|
OK, if any of you have been paying attention to CVS lately, you'll notice that I've been making quite a few changes to parsech. I'm writing this to explain these changes, and why I'm doing them. First, the what. I'm working to make each subroutine less dependent on others. Ulimatly, there will only be the %Opts hash as a universal variable. Even though I haven't checked it into CVS yet (there are a few kinks in the system), I've begun the final stage of all of this on one of the subs. Now, the why. Quite simply, I'm working to break up parsech. I believe it has become an ugly hairball that will be impossible to maintain eventually. I'm going to give ParseCH.pm another try, see if I can get it this time. Thoughts? Suggestions? Jelly doughnuts? Reply with them. -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-11-30 01:17:09
|
I noticed that the POD for the parsech internals is now gone. As a resul, there are a number of broken links in the POD, which should be fixed. However, whatI'm wondering is, what's the rationale for killing off of the internals POD? Also, what's the purpose of unexpand in the latest Makefile? -Kurt |
|
From: Kurt R. <ku...@ra...> - 2000-11-29 01:08:08
|
Hmm. OK, I thought that it was. -Kurt On Tue, Nov 28, 2000 at 04:54:52PM -0500, Scott Fenton wrote: > On Mon, Nov 27, 2000 at 07:12:55PM -0500, the keyboard of Kurt Raschke was alleged to have written: > > Is the P4 actually out yet? If so, should it be added to intel/pentium? > > Nope, or else Gateway's commercials would be advertising the P4. > > > > > -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-28 21:55:09
|
On Mon, Nov 27, 2000 at 07:12:55PM -0500, the keyboard of Kurt Raschke was alleged to have written: > Is the P4 actually out yet? If so, should it be added to intel/pentium? Nope, or else Gateway's commercials would be advertising the P4. > > -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-28 00:13:16
|
Is the P4 actually out yet? If so, should it be added to intel/pentium? -Kurt |
|
From: <bo...@se...> - 2000-11-23 13:41:01
|
Below is the result of your feedback form. It was submitted by Robert Wertzler (bo...@se...) on Thursday, November 23, 2000 at 05:41:00 --------------------------------------------------------------------------- type: add othersubj: Macy Conferences - Self-Guided Devices - WWII nodes: Research message: During (and for a while after) WWII the Josiah Macy Foundation (as a front for the US Government) sponsored a series of conferences on the Theory of Self-Guided Devices (munitions). The participants included Gregory Bateson, Warren McCullough, and others. The conferences' procedings were totally recorded on film and every scrap of notes and other writings were saved until 1959, when all but summaries of numbers 5-9 disappeared. As I understand it several of the key concepts of practical computer theory were developed, and, later expanded into the cybernetic theories that fed the creation of other systems oriented thinking (Notably Family Systems Therapy and Brief Therapy, and Neural Network theory.) The summaries of 5-9 are (or, were ten years ago) available in print. I have not found yet any specific resources on the conferences on the WWW. --------------------------------------------------------------------------- REMOTE_ADDR: 204.245.58.22 HTTP_USER_AGENT: Mozilla/5.0 (compatible; Konqueror/2.0; X11); Supports MD5-Digest; Supports gzip encoding |
|
From: Kurt R. <ku...@ra...> - 2000-11-23 02:08:33
|
Version 0.9.2 of the Computer History Graphing Project has now been released! The project aims to graph all of computerdom in one large family tree, and we are now even closer to that goal with this latest release. This version contains an updated version of the unified parser program, parsech. It can now optionally output a DBM hash containing the parsed data. The documentation has also been updated, in addition to the data trees. More specifically, the NeXT, Palm, Windows, and Apple Darwin trees have all been updated. If you have any questions or comments, please contact the developers at <sj...@us...>, or <ku...@us...>. The project's web site is located at <http://comp-hist.sourceforge.net>. -Kurt Raschke |
|
From: Scott F. <sj...@ra...> - 2000-11-22 20:13:46
|
On Wed, Nov 22, 2000 at 02:39:03PM -0500, the keyboard of Scott Fenton was alleged to have written: > On Wed, Nov 22, 2000 at 06:29:57AM -0500, the keyboard of Kurt Raschke was alleged to have written: > > On Tue, Nov 21, 2000 at 09:44:16PM -0500, Scott Fenton wrote: > > > 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? > > First of all, I'm a little confused about hhow your code works. Why not just call dbm_open before calling parse, so that when parse tries to store data in the array, it actually goes into the dbm hash. For linking, why not do the same thing with the link array? > > Brain fart. I'll reengineer it to do that now. OK, that much is done. Off to the actual python browser. > > > > > -Kurt > > > > > 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 > > > > > > -- > > > 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 > > > > > > _______________________________________________ > > 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----- > _______________________________________________ > 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: Scott F. <sj...@ra...> - 2000-11-22 19:46:03
|
On Wed, Nov 22, 2000 at 06:12:43AM -0500, the keyboard of Kurt Raschke was alleged to have written: > This is a good idea, and actually it even has potential for hardware, because some computers had to be booted from another - machines like the Xerox Alto, and the Cray T3e, which had to be booted from an attached Cray C90. > Scott, what do you think? Sounds great. I'll look into it after all the DBM stuff is sorted out. > > -Kurt > On Wed, Nov 22, 2000 at 10:22:35AM +0100, Lars Brinkhoff wrote: > > I have an idea for an additional type of information to collect: > > which operating system was used to develop and bootstrap another > > operating system. > > > > For example, the Linux 0.01 entry should maybe look like this: > > > > Linux 0.01 > > Type: OS > > Date: 1991 Sep 17 > > Reference: Linux Kernel Version History > > Influenced by: Minix 1.2 > > Bootstrapped on: Minix 1.2 > > Ran on: > > Intel 80386 SX > > Intel 80386 DX > > Intel 80386 SL > > > > > > Or, the UNICS entry: > > > > Uniplexed Information and Computing Service > > Type: OS > > Date: 1969 Sep > > Reference: Quarter Century of UNIX by Peter Salus, pg 43 > > Status: research > > Influenced by: The Multics Project > > Bootstrapped on: GECOS <some version> > > Runs on: The Digital Equipment Corporation > > Programmed Data Processor, model 7 > > _______________________________________________ > > Comp-hist-devel mailing list > > Com...@li... > > http://lists.sourceforge.net/mailman/listinfo/comp-hist-devel > _______________________________________________ > 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: Scott F. <sj...@ra...> - 2000-11-22 19:39:24
|
On Wed, Nov 22, 2000 at 06:29:57AM -0500, the keyboard of Kurt Raschke was alleged to have written: > On Tue, Nov 21, 2000 at 09:44:16PM -0500, Scott Fenton wrote: > > 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? > First of all, I'm a little confused about hhow your code works. Why not just call dbm_open before calling parse, so that when parse tries to store data in the array, it actually goes into the dbm hash. For linking, why not do the same thing with the link array? Brain fart. I'll reengineer it to do that now. > > -Kurt > > > 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 > > > > -- > > 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 > > > _______________________________________________ > 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: Scott F. <sj...@ra...> - 2000-11-22 19:38:54
|
On Wed, Nov 22, 2000 at 09:51:25AM +0100, the keyboard of Christophe Fergeau was alleged to have written: > Do you plan to switch from the current file format to dbm or are we going > to convert it to dbm at link time? > Link time. > I don't know exactly what dbm is. But I already thought how we could > handle the links in a sql database : the best means would be to use two > different tables : one which lists all the node with all the nodes but the > links and the other which associates a node name with a link > For example, we have : > DBM (I guess I should have explained this before) is a nice simple database format developed at Berkely around the days of 3/4BSD. It's a little less sophisticated than SQL, but you don't need any special software to use it (it's built right into libc). > node nodename 2000/04/12 xxx xxx xxx xxx > > and in another table : > node node2 > node node3 > node node4 > > which indicates the nodes which node is linked to > That would work. I guess I'll do it that way. > I don't know if it is possible in dbm but it would be the easiest > > Otherwise, for your python browser, are you going to use gtk for the > interface or something else? Python GUIs are generally engineered to use Tk. > Once again, I currently can't find enough time to improve my gtk browser > but maybe one day I'll add an editing option... if the python browser > doesn't already do this :-) The python browser is currently nonexistent, but I hope for it to get an editing option before too long. > > 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: Kurt R. <ku...@ra...> - 2000-11-22 11:30:26
|
On Tue, Nov 21, 2000 at 09:44:16PM -0500, Scott Fenton wrote: > 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? First of all, I'm a little confused about hhow your code works. Why not just call dbm_open before calling parse, so that when parse tries to store data in the array, it actually goes into the dbm hash. For linking, why not do the same thing with the link array? -Kurt > 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 > > -- > 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-22 11:13:02
|
This is a good idea, and actually it even has potential for hardware, because some computers had to be booted from another - machines like the Xerox Alto, and the Cray T3e, which had to be booted from an attached Cray C90. Scott, what do you think? -Kurt On Wed, Nov 22, 2000 at 10:22:35AM +0100, Lars Brinkhoff wrote: > I have an idea for an additional type of information to collect: > which operating system was used to develop and bootstrap another > operating system. > > For example, the Linux 0.01 entry should maybe look like this: > > Linux 0.01 > Type: OS > Date: 1991 Sep 17 > Reference: Linux Kernel Version History > Influenced by: Minix 1.2 > Bootstrapped on: Minix 1.2 > Ran on: > Intel 80386 SX > Intel 80386 DX > Intel 80386 SL > > > Or, the UNICS entry: > > Uniplexed Information and Computing Service > Type: OS > Date: 1969 Sep > Reference: Quarter Century of UNIX by Peter Salus, pg 43 > Status: research > Influenced by: The Multics Project > Bootstrapped on: GECOS <some version> > Runs on: The Digital Equipment Corporation > Programmed Data Processor, model 7 > _______________________________________________ > Comp-hist-devel mailing list > Com...@li... > http://lists.sourceforge.net/mailman/listinfo/comp-hist-devel |
|
From: Lars B. <la...@no...> - 2000-11-22 09:22:39
|
I have an idea for an additional type of information to collect:
which operating system was used to develop and bootstrap another
operating system.
For example, the Linux 0.01 entry should maybe look like this:
Linux 0.01
Type: OS
Date: 1991 Sep 17
Reference: Linux Kernel Version History
Influenced by: Minix 1.2
Bootstrapped on: Minix 1.2
Ran on:
Intel 80386 SX
Intel 80386 DX
Intel 80386 SL
Or, the UNICS entry:
Uniplexed Information and Computing Service
Type: OS
Date: 1969 Sep
Reference: Quarter Century of UNIX by Peter Salus, pg 43
Status: research
Influenced by: The Multics Project
Bootstrapped on: GECOS <some version>
Runs on: The Digital Equipment Corporation
Programmed Data Processor, model 7
|
|
From: Christophe F. <cfe...@en...> - 2000-11-22 08:55:57
|
Do you plan to switch from the current file format to dbm or are we going to convert it to dbm at link time? I don't know exactly what dbm is. But I already thought how we could handle the links in a sql database : the best means would be to use two different tables : one which lists all the node with all the nodes but the links and the other which associates a node name with a link For example, we have : node nodename 2000/04/12 xxx xxx xxx xxx and in another table : node node2 node node3 node node4 which indicates the nodes which node is linked to I don't know if it is possible in dbm but it would be the easiest Otherwise, for your python browser, are you going to use gtk for the interface or something else? Once again, I currently can't find enough time to improve my gtk browser but maybe one day I'll add an editing option... if the python browser doesn't already do this :-) Christophe |
929 messages has been excluded from this view by a project administrator.
