Linux

Yes, SCO shurely was a test animal to burn while making software patent negotiations a working business.

And, I guess it paved the land for lots of other things which are going on in the legal sector right now.

But, we also see, judges aren't as clueless as we always might think, and some meanwhile are getting more encuraged to slapping the offender.

I hope this trend continues.

 I am new to linux, fleeing Windows, and want to host a linux-based BBS.

 In thhe past, I have run a Windows-based Cit BBS, but I don't want to do so now.

 I'd like to download a simple linux-based Cit program that can handle telnet users.

 I know that this BBS code can do a whole lot more than that, but, for now, I just

 want to support the telnet side of things at first. Apache and the web side can come later.

 I have a linux-based server to run the Cit on. I just need a download webpage

 for this or any other Cit BBS that can hhandle telnet users that runs native in linux.

 Any and all help will be greatly appreciated.

 Thanks in advance,

 Harry.

hello harry!

Have you had a look at http://citadel.org/doku.php?id=installation:start ?

Which flavour of linux are you running? Getting the telnet part up and running should be fairly easy. 

have a look at

http://citadel.org/doku.php?id=installation:start

Fri Nov 04 2011 07:36:24 EDT from IGnatius T Foobar @ Uncensored

Oooh, I like the idea of a "rolling" distribution. It's definitely not for everyone, but the idea of simply getting constant updates instead of ever having a Big New Version (tm) seems attractive for an end user.

Let us know how that works out for you.

Just remembered to let you know, LMDE XFCE 64bit worked out just fine, as near as we can tell.

No problems yet, anyway.

Just revisited this as we are upgrading our backup to the new 201204 version to get the Citadel 8.14 in place.

Seems ok so far.

LMDE turns out to be more of a 'lurching' adventure than a rolling distribution as the updates are generally waiting on

clusters of upgrades to make it through the vetting process before getting into the updates arena.  A debian characteristic of sorts.

The heartburn of worrying about whether everything will hold together after an upgrade

 is probably just about as focus-intensive as a full bare-metal reinstall but the thought is that

 everything remains more or less in the same place each time without those moments

 where you discover that some of your key software no longer works at all because

someone decided to remove all the wheels, for no particularly urgent reason.  (I also use SeisUnix, which has had moments)

This business of improving software by cyclically adding unrelated functionality seems to be a disease with no cure,

 as the saga with KDE and now GNOME seems to illustrate.  A global epidemic?

They should have forked off with their grand ideas and left the train on the same rails (I do use KDE4 now sometimes, but....)

If you cannot just upgrade in place, and are required to re-Frakking-install each and every time the basis iterates,

  there is a fundamental problem in someones 'big picture' program.

-- 

TheOneLaw

Why not use a real rolling distro like Arch or Gentoo (where the package maintainer is currently procrastinanting with other stuff instead of updating the ebuilds..... ;)? I don't know if there is an arch... build script or something, but could be done, I think.

The other way of dealing with this stuff is using a LTS version of a distro. As a conservativ debian (and derivates) hater, I chose centos for some of my servers. Centos6 is going to stay for a while. On the other hand, I am considering ClearOS as an alternative for more SBS like installs.

I wouldn't run a debian stable on a desktop.

testing usualy is stable enough (unless the first 2 months after stable is released...)

there are also backports, if you like to install more modern software on the aging stable stuff.