shell server 2004

Shell server 2004

Posted April 7, 2004
Updated Aug 7, 2004 with specific cutover date

There's a new shell server in town-- or at least the start of one. We'll be moving to a FreeBSD server for the next instantiation of shell.mv.net . It's currently under construction and will probably be being sculpted for some time.

However, we thought that current shell users might want to have access to the system during this process. It might help you see where things are going, and it may also give us valuable feedback as well.

Everyone who has a shell account now also has an account on the new system. The new accounts are completely empty, though! Read on for further info and caveats.

Why a new shell server?

It's time to move away from the BSD/OS operating system that we've been using for so many years. BSD/OS was and is a great product, however it's been put on end-of-life status. We will be moving to a FreeBSD system since it provides a highly compatible environment.

Caveats and Guidelines

Some caveats and guidelines:

the new system might be rebooted at any time without much notice. (We don't expect a lot of that, but it could happen.)
Current home directories are empty.
Your files from the current shell server are available via NFS mounts. When you log in, an environment variable OD is set to point to your cross-mounted home directory. These are mounted read-only, so you can read them but not write new files there. Unlike the last migration (in 1999) we have chosen not to share home directories. The last time it was merely an OS upgrade (with new hardware); this time there are more differences and trying to share the home directories would give more risks than it's worth.
When the new system eventually becomes shell.mv.net, files in your new home directories on that system will be overwritten with files from your old directories. So don't put anything there that you don't want overwritten. (Any new filename that doesn't have a corresponding old file name will probably not be in danger though: the eventualy copy will only overwrite files that exist on the current/old shell server.)
The system is being built to think of itself using the various shell system names: e.g., 'mv.mv.com' or 'shell.mv.net' . If you try to send mail to shell.mv.net from the new server, it will send to itself (not to the current shell server). To send mail to the new server, use its underlying system name. However, use that name for test only: it's not guaranteed to work when the systems get renamed. If you send mail out from the new system, by default the From address will look like it comes from the current system.
You may find minor differences between the two systems because of the change in OS and the updates in software packages.

Getting to the new shell server

The new server is available as osmium.mv.net . We recommend ssh'ing to the server, but telnet is also open to support shell users who can only reach us via telnet.

When will it be changed?

The move to the new shell server will happen over the weekend of August 21 through August 23. We expect to perform the cutover on Sunday August 22, 2004. During the transition on that date, the shell server will be unavailable while user files and accounts are being moved to the new server. We expect this process to be complete by Sunday evening. Once it is done, the old server will no longer be accessible.

Feedback

Please give any feedback to the usenet newsgroup mv.forum.shell . You may also send email suggestions to mem AT admin.mv.net, where they will be read (if not always replied to).