|
|
| Author |
Message |
| 25 new of 467 responses total. |
eprom
|
|
response 303 of 467:
| 
Nov 20 03:29 UTC 2004 |
chop chop!!!
|
naftee
|
|
response 304 of 467:
|
Nov 22 05:06 UTC 2004 |
I volunteer.
|
mfp
|
|
response 305 of 467:
|
Nov 22 19:03 UTC 2004 |
I also volunteer.
|
dpc
|
|
response 306 of 467:
|
Nov 23 15:41 UTC 2004 |
I would also appreciate a list of things remaining to do on NextGrex.
|
janc
|
|
response 307 of 467:
|
Nov 23 17:50 UTC 2004 |
I posted one here a while back when I decided to take a break. If it
has changed, it's news to me.
|
janc
|
|
response 308 of 467:
|
Nov 23 17:52 UTC 2004 |
resp:277 is it.
|
dpc
|
|
response 309 of 467:
|
Nov 23 21:58 UTC 2004 |
When was the equipment for NextGrex purchased?
|
gelinas
|
|
response 310 of 467:
|
Nov 24 00:03 UTC 2004 |
May, 2003, IIRC.
|
naftee
|
|
response 311 of 467:
|
Nov 24 00:59 UTC 2004 |
I volunteer to generally test everything.
|
mfp
|
|
response 312 of 467:
|
Nov 24 07:51 UTC 2004 |
I volunteer.
|
janc
|
|
response 313 of 467:
|
Dec 19 20:10 UTC 2004 |
I've installed patches 021 through 024 on NextGrex. None were especially
important.
We need a staff member to subscribe to whatever OpenBSD mailing list
announcies new patches and take responsibility making sure that they get
applied in a timely manner (ie, for important security patches, almost
instantly). I don't want to subscribe to the OpenBSD mailing list, though
I'd usually be available to help with applying patches if there are any
problems. (I've never encountered any.)
We need to start doing this even before we move onto the new system.
Applying security patches is pretty straight forward. My procedure is:
(1) Look at the directory /usr/src/patch. All applied patches should
be in here. If a patch is here, you can assume someone else already
applied it.
(2) Download a copy of the patch to /usr/src/patch.
(3) Apply the patch as described by the patch. Usually this is just
a matter of cut/pasting four or five commands.
(4) If necessary, rebuild the kernal. Patches to the kernel source
include a reminder to rebuild the kernel. To do this, follow
instructions in grexdoc/openbsd/04-kernel. Basically, you need to
cut paste 7 commands from that file to do the build, and then copy
the new kernel into place.
(5) Reboot, if needed.
|
twenex
|
|
response 314 of 467:
|
Dec 19 22:58 UTC 2004 |
Sounds like Gmail would be a good idea, but as I understand it you can only
use it if you've been invited, at the moment. If someone wants to subscribe
to the OpenBSD mailing list(s), I'll be happy to send out an invitation.
Please include an email address I can send it too.
|
janc
|
|
response 315 of 467:
|
Dec 20 03:15 UTC 2004 |
What is Gmail, and why would it be of any danged use?
|
twenex
|
|
response 316 of 467:
|
Dec 20 08:44 UTC 2004 |
Have you been living under a rock?! ;-) Gmail is webmail from Google, with
1000 MB of storage space per user.
|
janc
|
|
response 317 of 467:
|
Dec 20 14:01 UTC 2004 |
But in what way would this help us monitor OpenBSD release notices? All
staff members already have email accounts.
|
twenex
|
|
response 318 of 467:
|
Dec 20 14:05 UTC 2004 |
Well, I admit it was due to a presumption on my part, the presumption being
that you didn't want lots of OpenBSD-related mail clogging up your inbox(en).
If you used a Gmail account just for that, that would give you LOTS of room
to manoeuvre.
|
janc
|
|
response 319 of 467:
|
Dec 20 17:11 UTC 2004 |
I've got a reasonable first draft of the log rolling set up, and have ported
the birthday wisher.
|
cross
|
|
response 320 of 467:
|
Dec 20 18:21 UTC 2004 |
Don't all the OpenBSD security adisories go to announce@OpenBSD.ORG or
something similar? Isn't that an extremely low volume list? Why not
just subscribe the staff email list to it and go from there?
|
janc
|
|
response 321 of 467:
|
Dec 20 18:32 UTC 2004 |
Beats me. Why not?
|
janc
|
|
response 322 of 467:
|
Dec 20 20:03 UTC 2004 |
Am digging through /usr/local/bin on Old Grex, looking for stuff to move.
Does anyone know what /usr/local/bin/charm is?
|
twenex
|
|
response 323 of 467:
|
Dec 20 20:21 UTC 2004 |
Running /usr/local/bin/charm --help brings up the following message:
Bad switch char <h>
Usage: charm olduid newuid newgid paths...
This suggests it's a command for changing the (you guessed it) user and group
id's for multiple files; it also suggests it needs superuser privilege to
run (and thus test) it.
|
marcvh
|
|
response 324 of 467:
|
Dec 20 20:45 UTC 2004 |
I guess the name is derived from "chown" somehow?
|
janc
|
|
response 325 of 467:
|
Dec 20 21:15 UTC 2004 |
Well, it's probably not moving to the new system, as I can't find any source
code for it. Also currently unlikely to move:
bbsed
chill
csplit
es
dircolors
dn
factor
fullname
fv
I've gotten as far as the g's in reviewing Old Grex's motd but my brain has
melted, so I'm going to stop.
The 'board' command on Grex needs to be updated by someone who knows who is
on the board now.
|
twenex
|
|
response 326 of 467:
|
Dec 20 21:29 UTC 2004 |
bbsed and es appear to be line editors, which probably no-one will want
anyway; csplit splits files, and I'm fairly sure we have the technology in
OpenBSD or the GNU tools anyway; chill appears to be a bizarre link to gcc;
the function of dircolors can probably replicated by a shell-script even if
there is no command "dircolors" on OpenBSD (but there may well be, as this
sounds familiar); dn is for finding the tld of a country, factor for finding
factorials, fullname appears to be for finding full names from finger info
(rewrite as shell script or use finger); fv is a binary editor.
I don't think we'll miss much on that list.
|
cross
|
|
response 327 of 467:
|
Dec 21 00:00 UTC 2004 |
I'm pretty sure factor actually attempts to find the prime factors of
sufficiently small numbers, not factorials! Es was, if I'm not mistaken,
written by Marcus Watts, who seems mostly UA these days. The rest seem
unlikely to be used.
|
