GitLab

available, and check that against the types of the vnodes in the top file. This
way, we can bail early with a comprehensible error message if, say, there are
not enough pc850s free!

This fixes the following item from the todo list:
13.  add type-count checks

+ Added web page to do post-create loading of image from node.

+ Added menu item for page to Show Image Descriptor submenu.

+ Changed warning in newimageid_ez.php3 to suit new reality.

you're also showing them the red dot for a swap request. Second, add a
noignore flag for idle view (and a link to it from idle view) that will
show you all the idle expts, even if they have the idle_ignore bit set.

Nit; remove legend for "+" (recommended) on fields,
since there are no recommended fields!

is sent anyway!

per Eric's request. I had left out the trailing /images/.

be more to my liking.

"generated for <uid>", insert a <br> before the date to leave more room
for the page title.

installed files!).
Reorder some of the misc entries and try to insert a space; might
look funny; we'll see.

Fixed error message.
"There were 0 nodes." --> "There were 0 failed nodes."

the documentation page. Also, move it from www.flux to www.cs .

- Added 'Country' to users table
- Changed "Zip" to "ZIP/Postal Code"
- Reformatted Postal Address Forms

the link to join.  Thus after they inevitable lose the URL, they
won't be deterred from inviting people to join.

reserved table. Whenever you insert a reservation or change a reservation
to a new expt, set vname=node_id.

stored in somewhere more permanent than my gray matter and purple
sticky notes!

of them! The start of an assign cleanup project.

whatever assign_wrapper did. This is different than local nodes where
we allocate the underlying phys node and set its osid. Confusing.

wrong, which may be why lynx was confused.

our last mail, don't show the red dot link to send another mail. Also,
show the red dot for unswappable expts too.

Yeah, it sounds right to me, too.

wrap. Also spellchecked while I was in there.

Added site variables ('sitevars').
These are stored in the sitevariables database table.
Each one has a name, a description (NOT OPTIONAL!), a
default value, and a current value.
If the current value is NULL, the default value is used.

Soon, a mechanism will be added to the install process to
ensure all needed site variables exist before installing;
more on that when it is committed.

 - Added 'editsitevars.php3' page, accessable to admins
   via the 'Edit Site Variables' menu option.

 - Added 'setsitevar' script,
   an interface for listing, viewing in detail, and setting
   site variables.

 - Web interface now uses 'web/nologins' and 'web/message'
   instead of one-off database tables.

NOTE that setting a variable to the default value and
setting a variable to a value which is string-identical
are NOT the same thing.
(This doesn't matter yet, but when we push default values out to
 remote sites as part of our install, it will.)