[2678] in Release_7.7_team
bleeding-linux
daemon@ATHENA.MIT.EDU (andrew m. boardman)
Tue Apr 3 18:40:11 2001
Date: Tue, 3 Apr 2001 18:40:06 -0400 (EDT)
Message-Id: <200104032240.SAA85045@karst.mit.edu>
From: "andrew m. boardman" <amb@MIT.EDU>
To: release-team@mit.edu
I've gotten enough inquiries lately about how people can have their own
bleeding-linux install that I'm writing a canned piece about it. Does
anyone have any quibbles with the following?
==============================================================================
How to switch an Athena Linux machine into the bleeding-linux cluster:
0: Make very sure you want to do this. Running bleeding-linux on your
machine moves you several steps beyond unsupported and into the realm
of "asking for it". You could very well lose everything you ever
cared about on the machine. One might even say that, eventually,
this is likely. Since the bleeding-linux distrubution is rebuilt on a
more-or-less daily schedule, your machine will also update itself
frequently. But if you're sure you want to do this...
1: Edit /etc/athena/rc.conf; set PUBLIC=false if it's not thus already.
Setting AUTOUPDATE=true is also generally preferred.
2: You need to get your machine into the bleeding_linux cluster. If you
want to do this more-or-less permanently, send mail to hesreq and ask
for a cluster change for your machine, although you probably want to
do the following step for instant gratification, anyway. If you
only wish to lose for a day, put the following two lines into
/etc/athena/cluster.local (which probably won't exist) on your machine:
syscontrol control/control-bleeding
sysprefix /afs/dev.mit.edu/system/rhlinux
3: As root, run /etc/athena/update_ws and reboot.
4: Add yourself to the testers mailing list, for advance warning of
any impending doom.
5: To go back to regular Athena 8.4, you can *try* deleting the
bleeding_linux cluster information you created in step 2 and then
running "update_ws 8.4". It's entirely likely you'll have to simply
reinstall, though.
