While we're on the subject, PAMINA is unreachable via telnet, and I
haven't been able to telnet into TINA in almost 2 weeks. Any idea
what's been happening at update? I miss TINA's othello. :)
Thanks,
Mark
Johnny Billquist wrote:
Oh, you want updates? :-)
Let's see...
FNATTE have been decomissioned for good, I think.
PONDUS is now an 11/93 with 4 MB.
PAMINA is also KLH-10
Johnny
Bob Armstrong wrote:
Where is PDXVAX still noted as a 4000/VLC?
Well, on my list for one.
http://www.sparetimegizmos.com/Downloads/DCN%20Node%20List.pdf
Nobody sent me any corrections ...
Bob
What is this "grass" you speak off? Some kind of furniture?
Grass it the stuff that we pay other men hundreds of dollars over the course of the warmer months to trim regularly.
I'm not so sure that the "lack of outside space" is necessarily undesirable. :-)
--Marc
Ok, I get your point but I just thought that if I took my current INFO.TXT file from CHIMPY say:
Welcome to CHIMPY::, part of the SAMPSACOM network.
Currently active users for email include:
SAMPSA
DAVIDSON
ARI
We offer the follow guest logons:
ACCOUNT - Use this to request an account on CHIMPY::
B4BBS - Gateway to the SAMPSACOM Bulletin Board System, B4BBS.
TETRIS - Awesome VT100 tetris game.
Thank you,
Sampsa Laine (CHIMPY::SAMPSA)
and then added a single line of information meant for the list generator after that, it would a) not visually affect the human reader and b) provide the relevant information for the list generator. Your format works as well, of course, but is more visually significant.
Also, whilst this is a almost irrelevant point, parsing a simple field/separator piece of text is a tiny bit more trivial than your format.
Sampsa
On 19 Oct 2009, at 19:54, Johnny Billquist wrote:
Sampsa Laine wrote:
Guys, the reason I suggested a one line format was that I thought it would just sit at the end of a human readable file. We could have a second info file that is machine readable.
How did you think that one-liner would be created, if not by a human?
So why not have the whole file human readable, and human writeable.
After all, computers should try to accomodate human peculiarities, and
not vice versa. :-)
Johnny
On 19 Oct 2009, at 16:58, Brian Hechinger wrote:
On Mon, Oct 19, 2009 at 05:45:27PM +0200, Johnny Billquist wrote:
Such as (just as an example):
======
HOST: MIM
HARDWARE: E11 (PDP-11/74)
OS: RSX-11M-PLUS V4.6
LOCATION: UPPSALA, SWEDEN
MANAGER: Johnny Billquist
EMAIL: bqt at update.uu.se
EMAIL: MIM::BILLQUIST
======
Keep the format simple, and very relaxed. Let software figure out if
they can do anything with it or not.
Uppercase, lowercase, free flowing text. Just keep the tags standard to
start with. Maybe we can have some tags with a more formalized value, if
needed, such as a POS: value with LAT/LONG if people want to add that?
Hmm, that looks a LOT like an LDIF file. :)
-brian
--
"Coding in C is like sending a 3 year old to do groceries. You gotta
tell them exactly what you want or you'll end up with a cupboard full of
pop tarts and pancake mix." -- IRC User (http://www.bash.org/?841435)
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
What is this "grass" you speak off? Some kind of furniture?
(sorry, obvious joke at myself and the lack of outside space in Central London)
On 19 Oct 2009, at 19:38, Brian Hechinger wrote:
On Mon, Oct 19, 2009 at 11:18:39AM -0700, Bob Armstrong wrote:
To you guys? I don't mind you guys knowing where I live ...
Depends on whether I remembered to mow the grass before the Google truck
came around...
Bah, get in line for the "my grass is too long" thing. I mow it when it's
working its way to knee high. ;)
-brian
--
"Coding in C is like sending a 3 year old to do groceries. You gotta
tell them exactly what you want or you'll end up with a cupboard full of
pop tarts and pancake mix." -- IRC User (http://www.bash.org/?841435)
Sampsa Laine wrote:
Guys, the reason I suggested a one line format was that I thought it would just sit at the end of a human readable file. We could have a second info file that is machine readable.
How did you think that one-liner would be created, if not by a human?
So why not have the whole file human readable, and human writeable.
After all, computers should try to accomodate human peculiarities, and
not vice versa. :-)
Johnny
On 19 Oct 2009, at 16:58, Brian Hechinger wrote:
On Mon, Oct 19, 2009 at 05:45:27PM +0200, Johnny Billquist wrote:
Such as (just as an example):
======
HOST: MIM
HARDWARE: E11 (PDP-11/74)
OS: RSX-11M-PLUS V4.6
LOCATION: UPPSALA, SWEDEN
MANAGER: Johnny Billquist
EMAIL: bqt at update.uu.se
EMAIL: MIM::BILLQUIST
======
Keep the format simple, and very relaxed. Let software figure out if
they can do anything with it or not.
Uppercase, lowercase, free flowing text. Just keep the tags standard to
start with. Maybe we can have some tags with a more formalized value, if
needed, such as a POS: value with LAT/LONG if people want to add that?
Hmm, that looks a LOT like an LDIF file. :)
-brian
--
"Coding in C is like sending a 3 year old to do groceries. You gotta
tell them exactly what you want or you'll end up with a cupboard full of
pop tarts and pancake mix." -- IRC User (http://www.bash.org/?841435)
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
Brian Hechinger wrote:
On Mon, Oct 19, 2009 at 01:19:30PM -0400, John Wilson wrote:
OK I'll try to control myself now -- PDP-11 stuff probably isn't that
interesting to most HECnet people.
I'm all for it, I think most of us here are PDP-11 junkies. :-D
There are all kinds on this list, including long time PDP-10 junkies,
who I think are not always so amused by getting too deep into PDP-11
specific hardware issues. We should perhaps try to limit this somewhat
to HECnet related stuff to not totally swap some peoples mailboxes with
stuff that they haven't subscribed to.
Apologies to people who are not that amused by PDP-11 hardware. We got a
little sidetracked. For those who are interested in this, we can keep on
talking offlist.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
On Mon, Oct 19, 2009 at 11:18:39AM -0700, Bob Armstrong wrote:
To you guys? I don't mind you guys knowing where I live ...
Depends on whether I remembered to mow the grass before the Google truck
came around...
Bah, get in line for the "my grass is too long" thing. I mow it when it's
working its way to knee high. ;)
-brian
--
"Coding in C is like sending a 3 year old to do groceries. You gotta
tell them exactly what you want or you'll end up with a cupboard full of
pop tarts and pancake mix." -- IRC User (http://www.bash.org/?841435)
On Mon, 19 Oct 2009, Bob Armstrong wrote:
To you guys? I don't mind you guys knowing where I live ...
Depends on whether I remembered to mow the grass before the Google truck
came around...
Hehe... Hmmm, I wish there was a datestamp that shows when Google had
driven by. I know it was apparently on a Tuesday, but no idea what year. Actually might be 2007. Interesting seeing how a couple things looked prior
to our buying the house. I'm not surprised to see zero difference between
the house then, and the house now, but the neighborhood has definitely
changed.
Zane
To you guys? I don't mind you guys knowing where I live ...
Depends on whether I remembered to mow the grass before the Google truck
came around...
Bob
To you guys? I don't mind you guys knowing where I live, you all seem pretty cool. Now I wouldn't post the info on my blog or Facebook, I tend to say more controversial things there.
Sampsa
On 19 Oct 2009, at 18:55, Zane H. Healy wrote:
On Mon, 19 Oct 2009, Bob Armstrong wrote:
so we can look at satellite map and see real location of node :)
I'm not sure I want to tell :-)
I have to question how many people want to let out that level of detail.
Zane
