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
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
On Mon, Oct 19, 2009 at 07:17:18PM +0200, Johnny Billquist wrote:
You don't do DMA from CPU to a device. Remember what DMA stands for? :-)
Oh, duh. I knew that. I blame a lack of coffee. ;)
Hmm, I realized one thing, though. With a common Qbus, all interrupts
will probably go to the bus master arbiter, which means that all devices
actually must be attached to CPA, except such devices that are local to
each CPU, such as the console terminal.
That solves that problem. :)
And in RSX speak, the CPUs are called CPA, CPB, CPC and CPD. Here is how
it looks on MIM::
.con dis full att for sys
SYS SYS Online,Accpath
PDP-11/74mP, EIS,UNIBUS_Map,D-Space,SWR,Cache,FPP,
Clock=KW11-L, $TKPS=50., $TTPRM=000002
.con dis full att for cp
CPA CPA Online,Accpath
Cache_control=000001, Timer=Off, Alarm=Off
CPB CPB Offline,Accpath
Cache_control=000001, Timer=Off, Alarm=Off
CPC CPC Online,Accpath
Cache_control=000001, Timer=Off, Alarm=Off
CPD CPD Offline,Accpath
Cache_control=000001, Timer=Off, Alarm=Off
.con dis full att for du
DUA CPA Online,Accpath,Driver
Csr=172150, Vector=000154, Pri=000005, Urm=000001
DU0: CPA DUA0: Online,Accpath,Context,Driver,Type=RZ29
DU1: CPA DUA1: Online,Accpath,Driver,Type=RD53
DU2: CPA DUA2: Online,Accpath,Driver,Type=RD52
DU3: CPA DUA3: Offline,Accpath,Driver
DU4: Online,Accpath,Context,Driver,Type=VRA82
.
Notice that CPA and CPC are online.
And DUA is attached to CPA, and so on...
That's nifty. I can't wait to get mine setup. :)
-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)
