In the past, I have run several Renegade BBSes. Now the renegade support ring doesn't want anything to do with me because they have supposedly been around since 92. Anyway I close BBSes when I move, when my computer crashes, when I don't have any internet ect. I never close a BBS because there are not enough user activity. I always found my little Renegade BBS to be a secure way to access my own computer remotely. I installed Fossil DSZ, and SEXYz from Rob swindle, anyway I could send and recieve files over Zmodem. Although Psuedo Dos is not very good editor, you can still use Renegade's built in full screen text editor.
So if you must, then you must, but consider keeping it for yourself so you can program your computer from anywhere in the world, that has an internet conmnection.

Sincerely,
JamTone
P.S. The reason I wanted you to erase the messages in Planets because it has
a bunch of advertisements for Bible BBS, and I closed that BBS
when we moved back in March.

--- Renegade v1.18/Alpha
* Origin: The Realms of Blue BBS - blues.zapto.org (1:261/220)

Folks,

Just one question:

What has this to do with the 10th amendment to the U.S.
constitution?

Richard
---
* Origin: (1:116/901)

What has this to do with the 10th amendment to the U.S.
constitution?

i suspect that 261/220 has crosslinked their bases... no telling what zone that
is but i'm going to assume Z1 and send a message to that sysop over there about
it ;)

)\/(ark


* Origin: (1:3634/12)

HI Mark,

On Sat 2012-Oct-06 15:44, mark lewis (1:3634/12) wrote to Richard Webb:

What has this to do with the 10th amendment to the U.S.
constitution?

i suspect that 261/220 has crosslinked their bases... no telling
what zone that is but i'm going to assume Z1 and send a message to
that sysop over there about it ;)

Was thinkign about doing that, but wasn't sure where the
crosslink was. Hopefully that'll resolve this. That's
about the only traffic I see here is crosslinked stuff from
apparently dovenet.

Regards,
Richard
... Love is being owned by a rottweiler!
---
* Origin: (1:116/901)

What has this to do with the 10th amendment to the U.S.
constitution?

i suspect that 261/220 has crosslinked their bases... no telling
what zone that is but i'm going to assume Z1 and send a message to
that sysop over there about it ;)

Was thinkign about doing that, but wasn't sure where the
crosslink was.

i gather that it is at the originating node...

Hopefully that'll resolve this. That's about the only traffic I
see here is crosslinked stuff from apparently dovenet.

yes and those are mostly synchronet systems, IIRC... how the message base areas
are configured to so easily allow for crosslinking is something else, though...

)\/(ark


* Origin: (1:3634/12)

HI Mark,

On Sat 2012-Oct-06 17:46, mark lewis (1:3634/12) wrote to Richard Webb:

Was thinkign about doing that, but wasn't sure where the
crosslink was.

i gather that it is at the originating node...

Would think you're right, from path lines I was went from
that system to a system in n266, then to 140/1, to Ross, to
you, to me. That would tell me z1 as well.

Hopefully that'll resolve this. That's about the only traffic I
see here is crosslinked stuff from apparently dovenet.

yes and those are mostly synchronet systems, IIRC... how the message
base areas are configured to so easily allow for crosslinking is
something else, though...

True, and that's waht I'm not aware of, as I've never used
it. But, it seems to happen a lot with them, and this echo
seems to be the dumping ground.

Regards,
Richard
---
* Origin: (1:116/901)

HI Nicholas,

On Sat 2012-Oct-06 20:39, Nicholas Boel (1:154/10.1) wrote to mark lewis:

yes and those are mostly synchronet systems, IIRC... how the message base areas are configured to so easily allow for crosslinking is something
else, though...

FYI, there's absolutely nothing in a default Synchronet
configuration that would come anywhere close to having 10TH_AMD as
any kind of data file, or echotag.

It's obviously operator error.

I'd be inclined to agree with that assessment. I've seen
others in this echo from dovenet or whatever it is with
different FIdonet addresses, but that's what makes me think
somebody's got soemthing crosslinked, and maybe we finally
hit upon it. IT's only an occasional thing, but it's been
about the only consistent traffic in this echo since I
linked up a few years ago. There's more off topic content
than on topic here <grin>.

However, I do have an interest in the stated topic, which is why I remain linked. Obviously whoever founded the echo
wasn't interested enough though to maintain a listing in the echolist, or look after it. <oh well>

You might be right, we'll see if communications from Mark
and I to the suspected system clear it up. IF not,
delinking might be the option. I'd suggest a further step
of removing it from the backbone as well if it doesn't.

Regards,
Richard
---
* Origin: (1:116/901)

yes and those are mostly synchronet systems, IIRC... how the
message base areas are configured to so easily allow for
crosslinking is something else, though...

FYI, there's absolutely nothing in a default Synchronet
configuration that would come anywhere close to having 10TH_AMD as
any kind of data file, or echotag.

It's obviously operator error.

that's what i said, nick... but there have been a lot of similar crosslinks in recent history which is why i also mentioned the possible conflict situation...

)\/(ark


* Origin: (1:3634/12)

that's what i said, nick... but there have been a lot of similar
crosslinks in recent history which is why i also mentioned the possible conflict situation...

What, exactly, are you referring to as "recent history?" The past 10 years?
Or the past year? The past year I think there's been like 2. So that's not
that many. Even if they were both Synchronet systems, I'm letting you know
as a Synchronet sysop that there's nothing remotely close to 10TH_AMD in Synchronet whatsoever. So basically, we're blaming it on new sysops that
setup Fidonet, and post in the first Fidonet echo on the backbone.

The fact that it might have been Synchronet systems recently, is because Synchronet is probably one of the most popular BBS packages for new or returning sysops these days, as much as noone wants to admit it.

--- Mystic BBS v1.10 A20 (Linux)
* Origin: thePharcyde_ http://www.pharcyde.org (Wisconsin) (1:154/10.1)

True, and that's waht I'm not aware of, as I've never used
it. But, it seems to happen a lot with them, and this echo
seems to be the dumping ground.

Like you said before, if the *only* messages in this echo are
crossposted ones, maybe getting rid of the echo altogether would
solve the issue as well. :)

getting rid of the echo on the cross-posting board, sure... but not in a whole network of folks who still carry it... go ahead and throw the eggs out with the
basket, eh?

)\/(ark


* Origin: (1:3634/12)

getting rid of the echo on the cross-posting board, sure... but not in a whole network of folks who still carry it... go ahead and throw the eggs out with the basket, eh?

Yup! I'd also like to see your 10-20 dead echos, besides robot posts, leave
the backbone as well. At least you're here to maintain them, though, even though there's nothing to maintain. :(

--- Mystic BBS v1.10 A20 (Linux)
* Origin: thePharcyde_ http://www.pharcyde.org (Wisconsin) (1:154/10.1)

yes and those are mostly synchronet systems, IIRC... how the message base areas are configured to so easily allow for crosslinking is something
else, though...

FYI, there's absolutely nothing in a default Synchronet configuration that would come anywhere close to having 10TH_AMD as any kind of data file, or echotag.

It's obviously operator error.

--- Mystic BBS v1.10 A20 (Linux)
* Origin: thePharcyde_ http://www.pharcyde.org (Wisconsin) (1:154/10.1)

True, and that's waht I'm not aware of, as I've never used
it. But, it seems to happen a lot with them, and this echo
seems to be the dumping ground.

Like you said before, if the *only* messages in this echo are crossposted
ones, maybe getting rid of the echo altogether would solve the issue as
well. :)

--- Mystic BBS v1.10 A20 (Linux)
* Origin: thePharcyde_ http://www.pharcyde.org (Wisconsin) (1:154/10.1)

What has this to do with the 10th amendment to the U.S.
constitution?

Nothing at all.. :)

i suspect that 261/220 has crosslinked their bases... no telling
what zone that is but i'm going to assume Z1 and send a message to
that sysop over there about it ;)

No crosslinked echos here. Just a user posting in the incorrect area. I will try to explain it to him.. :)

Hopefully that'll resolve this. That's about the only traffic I
see here is crosslinked stuff from apparently dovenet.

Dovenet.. ick.. no dovenet here.. (no offence to you sync/dovenet guys and gals)

yes and those are mostly synchronet systems, IIRC... how the message base areas are configured to so easily allow for crosslinking is something else

No sync board here either. I think a telnet bbs is insecure enough without all the extra stuff that synchronet adds for hackers to play with.

Sorry for the original post. I haven't been paying much attention to the board this past summer. I will try to keep my users in line. :)

Thanks,

Scott....

... Get a taste of religion. Bite a preacher.

--- Renegade v1.18/Alpha
* Origin: The Realms of Blue BBS - blues.zapto.org (1:261/220)