i am planning to upgrade Zedler to Solaris 10 Update 1 at some point,
probably tonight/tomorrow morning (UTC).
assuming everything goes as planned, there should be no disruption during
the upgrade, but a reboot will be required when it's finished.
apologies for any inconvenience.
k.
The program presented here is simple and should be easy to translate
into Perl, C or any other reasonable computer language.
A basic knowledge of lisp list processing operators (car, cdr, etc) is
all that is required to understand this program, which is written in
the Guile dialect of Scheme.
The program analyzes the revision table and uses vandalism reverts as
a proxy for vandalism. This relies on the assumption that vandalism
is quickly detected and corrected by reverting to an earlier version,
and also assumes that administrators do not abuse the rollback
facility to perform non-vandalism reverts. It further assumes that
editors do not incorrectly label edit warring as vandalism. These
assumptions are broadly valid for the article chosen, [[en:George W.
Bush]], but may not be true for all popular articles.
The program is configured to work in English, but it may be possible
to apply the same methods in other languages by changing the match
patterns for vandalism reverts.
Multibyte characters may break this program. Sorry, it isn't my area
of expertise.
http://en.wikipedia.org/wiki/User:Tony_Sidaway/Dubya_vandalism
hi.
i've noticed some users seem to be unaware of either rules specific to
Zedler, or general php security issues.
please be aware that:
* you must not install third-party web applications on Zedler. this
includes putting mediawiki source code in your public_html, even if
you don't configure it. this also includes phpmyadmin. this also
includes applications protected by passwords or other access
restrictions. there are no exceptions to this. (if you believe you
have a very good reason to do this, ask me first.)
if you must use it, put it elsewhere, and keep it up to date. DO NOT
provide access to it via HTTP. the only valid reason for installing
MediaWiki is to run maintenance scripts from the command line, or using
MW libraries in your own applications.
this is extremely important. i will start disabling applications
which do not conform to this rule.
* do not place sensitive information (such as passwords) in
world-readable files. since CGI scripts, including PHP, run as your
uid, there is no need to do this.
* when you use data from $_GET, $_POST, etc. in SQL queries, you MUST
escape it. please familiarise yourself with this function:
http://uk.php.net/mysql_real_escape_string
* when you print user-supplied data in HTML, you must also escape it:
http://uk.php.net/manual/en/function.htmlspecialchars.php
neither of the last two are specific to PHP, but for some reason PHP code
seems to be a lot worse, on average.
if you have not already done so, please ensure you are familiar with the
rules for Zedler users:
http://meta.wikimedia.org/wiki/Toolserver/Rules
k.
I'm hitting dumb stuff that arises from my unfamiliarity with working
in a 32/64-bit split universe on a Solaris box.
Is there some magic phrase I can tell configure that will make it
realise I want to pick up the 32-bit /opt/mysql50/include/mysql
include files, and not the include files that lives at
/usr/sfw/include/mysql that it seems to prefer? I can go around
editing Makefiles, or even install my own 32-bit mysql client, but
there has to be a better way.
Or maybe the information here is out of date:
http://meta.wikimedia.org/wiki/Toolserver/For_users#software
It suggests that I should link to the /opt/mysql50 code for a 32-bit build.
if there's some amazing advantage to compiling all my code for 64
bits, please feel free to convince me. In private email. I think it
more likely that I'm just being dumb.
several users have complained about Zedler not having a GNU userland.
in an attempt to make the system easier to use for these people, some
changes are being made to where software is installed.
the most important change is the GNU software installed in /opt/csw/bin/
will be moving. utilities which conflict with the base OS, such as
"ls", will move to /usr/local/gnu/bin/. everything else (including
non-GNU software currently installed in /opt/csw) will move to
/usr/local/bin/.
as a result of this, if you want to use the GNU utilities by default,
you can place /usr/local/gnu/bin/ in your path prior to any other
directories (such as /usr/bin/). if you don't want this, don't change
anything.
users using script interpreters (including Perl) currently installed in
/opt/csw/ will need to change their paths to the new locations these
tools will be at.
hopefully, once this is done, things will be a lot happier. please let
me know if anything isn't working as it should.
k.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I'd like to use the php extension "pspell", which appears to not be
installed. Could we get that installed? :)
- --
Stephanie Amanda S.
Encrypted Email Preferred
OpenPGP key ID: C9774A04
http://tinyurl.com/8wxzb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFDnhdlqqXvz8l3SgQRAhVMAJwNn/5EUX/cnD8knZp0U39Wwz/g7QCeMfgv
q1RQZSsljeqKcI9r/jYwR6Y=
=9WvE
-----END PGP SIGNATURE-----
Am I being dense, or is there no GNU source level debugger (gdb)
installed on zedler?
I've tried using dbx to load an image, but it just spawns the
executable and then seems to hang forever waiting for it.
Hi all
while we are waiting for new disks, it would be quite useful to have
static dumps of two or three small wikipedias (like nds, for instance)
on zedler, for testing.
Would that be possible? I would at least be able to show people the
tools i'm making, even if they are not very useful with so little data.
Thanks,
Daniel
--
Homepage: http://brightbyte.de
i've been fiddling with OpenGrok, the OpenSolaris source code browser:
http://tools.wikimedia.de/source/xref/
maybe it would be nice to use this to publish the source of people's tools (it
does cross-referencing, searching and so on as well as browsing).
anyone interested?
(downsides: it doesn't support PHP; but that shouldn't be too hard to add.)
kate.