|
|
| Author |
Message |
| 25 new of 467 responses total. |
janc
|
|
response 252 of 467:
| 
Oct 24 19:18 UTC 2004 |
There was some talk recently of settng up a staff wiki where we can
document procedures and such like. I thought this was a good idea,
and that maybe other, more public, uses for wiki's could be found on
Grex. I took a quick look around and decided to try mediawiki, the
one that is used for wikipedia.
It requires php, so I set out to install php from the ports tree.
This was a mistake. The ports tree is a wee bit confused. First
problem is that it decided to install quite a few extension modules,
and their dependencies. For instance, it decided to install the
interface to PostgreSQL, but since I hadn't installed PostgreSQL, it
decided that I needed PostgreSQL, so it installed that. In this way
it installed quite a few different packages that I don't think we
particularly need. I don't mind very much, but I hope we can find a
cleaner way to do this on the next OS upgrade.
However, it turned out that it did not install the mysql interface,
which mediawiki does need. All attempts to install this from the
ports tree give an error message saying that the mysql package
requires x11, which we don't have and don't want. However, this is
absurd. Of course the mysql interface does not require x11.
Since this wasn't working, I decided to try to use the php "pear"
tool that is used to fetch and install extensions. However, only a
small part of pear seems to be installed, although it is supposed to
be standard in PHP 4.3.0 and later, which we have. All that is
there though is /usr/local/bin/pear which is a short sh script that
figures out where php is installed and runs the pearcmd.php program.
This program is missing.
So this is a pathetic mess. Probably I should back it all out and
try to install it from either an OpenBSD package or from the
original PHP distribution. Foo.
I guess I also don't have any idea how to enable PHP for the system
web pages, but not for user web pages.
|
cross
|
|
response 253 of 467:
|
Oct 24 19:22 UTC 2004 |
Why not use PostgreSQL instead of MySQL and be happy? And what's wrong
with TWiki? That, to my knowledge, doesn't require a SQL RDBMS.
|
aruba
|
|
response 254 of 467:
|
Oct 24 19:24 UTC 2004 |
The inventory database is written to MySQL, so we need to have that whether
or not we have PostgreSQL. (I understand it's already there; Jan is talking
about the PHP interface to these databases, I think.)
|
cross
|
|
response 255 of 467:
|
Oct 24 22:42 UTC 2004 |
Yes, Jan is referring to the latter. However, it was my understanding
that the inventory database was for msql, which is again a different
beast (and much older and less widely used). It'd require some tweaking
to get running under either; I'd prefer to see it go to pgsql instead
of mysql if work hasn't already been done.
Regardless, TWiki doesn't need an RDBMS, and it uses CVS for versioning.
I'd say let's try that instead of mediawiki.
|
janc
|
|
response 256 of 467:
|
Oct 24 23:59 UTC 2004 |
I got php to work correctly by installing it from the package instead from
the ports tree. I should probably do more package installs instead of ports
installs. But they are in some ways clumsier to use.
It turns out I didn't have mysql fully installed - I only had the client and
not the server. I got it fully up and configured. Invent uses MySQL, not
msql. Nuget uses msql, and will need to be replaced.
Neither mediawiki nor anything else that we now have requires postgreSQL.
I'll probably uninstall it. I expect we'll be using MySQL for many things.
I got mediawiki working, but I'm not very happy with it. It is rather
stupidly configured, with the file containing the MySQL database password
residing under the document route. It's a .php file, so you shouldn't be
able to see the source under ordinary circumstances, but why put it there
in the first place. I'm not entirely happy at the idea of having the Grex
Staff Collective Memory buried in a database that can only be easily read
via this particular application. If apache, php, mysql and the wiki aren't
all working, you can't read it. There're a couple other things I don't much
like about it either. Which is too bad. I like way it looks from the
outside.
Maybe I'll look at twiki.
|
janc
|
|
response 257 of 467:
|
Oct 25 00:05 UTC 2004 |
Looks like Twiki is based on RCS not CVS. Written in Perl. Might be a better
fit.
|
mfp
|
|
response 258 of 467:
|
Oct 25 01:46 UTC 2004 |
Point.
|
gelinas
|
|
response 259 of 467:
|
Oct 25 02:30 UTC 2004 |
The new grex machine's name is grease.cyberspace.org. Is that the name people
are using? Is that the name giving DNS trouble?
At least once a day, I check the name server on grex (dns.cyberspace.org) to
make sure it's offering up information. Occasionally, I check some of our
secondary name servers, as well. I've not noticed any problems yet. Despite
the fact that named is restarting and dumping core (probably not in that
order) frequently.
|
janc
|
|
response 260 of 467:
|
Oct 25 02:50 UTC 2004 |
Which named is doing that? On nextGrex?
I uninstalled mediawiki and php. I installed Twiki. I haven't figured it
out, but I have the impression it will do the job.
I set it up to authenticate out of /etc/passwd, just like backtalk. However,
it still kind of wants you to register.
Ideally I'd set up a Staff Web that can only be modified by staff. Possibly
there would be some pages in that that could only be read by staff. Don't
really know how to do this though. Don't really want to spend the time
figuring it out right now either. Should get back to working on more critical
things.
If any other staffers want to test this, it's at
http://grease.cyberspace.org/twiki/bin/view/
|
gelinas
|
|
response 261 of 467:
|
Oct 25 02:58 UTC 2004 |
The named on the current grex, Jan. I should probably take a look at the one
on grease, too.
|
mfp
|
|
response 262 of 467:
|
Oct 25 03:01 UTC 2004 |
Trying 216.93.104.38...
Connected to grease.cyberspace.org.
Escape character is '^]'.
OpenBSD/i386 (grex.cyberspace.org) (ttyp3)
User not authenticated. Using plaintext username and password
login: newuser
Password:
Login incorrect
|
naftee
|
|
response 263 of 467:
|
Oct 25 05:14 UTC 2004 |
savage.
|
cross
|
|
response 264 of 467:
|
Oct 25 05:30 UTC 2004 |
Oh, is it really RCS? Tom Limoncelli lied to me.
|
naftee
|
|
response 265 of 467:
|
Oct 25 05:30 UTC 2004 |
What do you get when you cross a Lemon and a Cello ?
|
tod
|
|
response 266 of 467:
|
Oct 25 05:31 UTC 2004 |
There's always room from JELL-O!
|
tod
|
|
response 267 of 467:
|
Oct 25 05:33 UTC 2004 |
I'd be glad to test connectivity from Seattle..
|
naftee
|
|
response 268 of 467:
|
Oct 25 05:37 UTC 2004 |
Doesn't traceroute do that for you?
|
mfp
|
|
response 269 of 467:
|
Oct 25 05:50 UTC 2004 |
Point.
|
naftee
|
|
response 270 of 467:
|
Oct 25 05:57 UTC 2004 |
Point.
|
mfp
|
|
response 271 of 467:
|
Oct 25 06:45 UTC 2004 |
Point.
|
gelinas
|
|
response 272 of 467:
|
Oct 25 12:18 UTC 2004 |
The named on grease has been up and running since the last reboot.
|
mfp
|
|
response 273 of 467:
|
Oct 25 17:55 UTC 2004 |
Point.
|
naftee
|
|
response 274 of 467:
|
Oct 25 19:56 UTC 2004 |
soup@m-net-bash-2.05a$ ft grease:
FrontTalk 0.3.2
Copyright 2001, Jan Wolter
Connect to 'grease' failed.
Unknown system 'grease'.
:(
Point.
|
mfp
|
|
response 275 of 467:
|
Oct 25 20:06 UTC 2004 |
Point.
|
gelinas
|
|
response 276 of 467:
|
Oct 26 04:34 UTC 2004 |
It took a bit longer than I expected in #198 above, but I've begun updating
the web pages on the new grex machine. I started with faq.html.
Has java been installed?
|
