@@
%prep
%setup -q
%patch0 -p1 -b .shadow
+%patch1 -p1 -b .cclink
%build
@@ -70,5 +72,9 @@
%{_bindir}/otppasswd
%changelog
+* Mon Nov 03 2008 Douglas Bagnall doug...@paradise.net.nz 0.3.3-3
+- revert '-fno-stack-protector', use gcc instead of ld to link.
+* Fri Oct 24 2008 Douglas Bagnall
Martin wrote:
- we don't have any scripts that write, but we will likely do, so
mounting ro is not a good idea
I'm pretty sure the xs-otp scripts write to the usb drive, if you have
that enabled. Not that anyone does that, or we'd have seen a stream of
queries about servers that are very
Sameer Verma wrote:
- xs-activity-server which stores .xo activities
Now, this is interesting. How do the activities get pushed to the XOs?
via a USB drive. The format is described here:
http://dev.laptop.org/git/users/martin/xs-activity-server.git/tree/README
- xs-rsync - anything
I wrote:
- xs-activity-server which stores .xo activities
Now, this is interesting. How do the activities get pushed to the XOs?
via a USB drive. The format is described here:
Ah sorry, I misread. (swine flu).
Via http, and it isn't perfect, because the XOs don't know to use it
rather
[Apologies to bystanders trying to follow this email: it mainly
consists of disjointed snippets I need to tell Martin]
After a fairly straightforward substitution of postgresql for mnesia,
ejabberd's performance is spectacularly unchanged. Of course, this is
to be expected.
Also, the behaviour
Guillaume:
I hope to soon rebase ejabberd off 2.0.2.
Would be good as Gadget requires at least this version to work properly.
Well, it seems to work, though I have run out of time to really be sure.
http://dev.laptop.org/git?p=users/dbagnall/ejabberd-rpm.git;a=summary
Jack Zielke discovered that xs-activity-server was sorting activities
versions lexically, so that version 2 would appear newer than version
10. This is fixed in git and in the following rpm, but is broken in
XS-0.5.
Martin Langhoff wrote:
http://wiki.laptop.org/go/Ejabberd_resource_tests/tls_comparison
The graphs all have different y scales, which makes them hard to
compare. Can you fix them easily to all be with the same y scale? Or
put a big blinking warning -
I've taken out the minimum graphs for
Caroline Meeks Martin Langhoff:
What releases are the control setup? IS the New TLS released code?
The 'control' setup is the ejabberd-xs package we ship for XS-0.5. The
new TLS code is a patch we could consider 'beta' quality -- there's
been no significnat QA on it.
In case anyone does
last week, Martin Langhoff wrote:
I'm not near a school server, so I haven't been able to test the
xs-tools usbmount script.
I'm happy to wait untilyou have a chance to test it before calling the
release done :-)
It works. I've tagged it as v0.4.
BTW, Reuben is about to start playing
The bad news is the last lot of testing I did is very untrustworthy,
due to the shared roster not working[1].
The good news is I've repeated the tests, with the shared roster. Not
so good, is the results aren't so good.
http://wiki.laptop.org/go/Ejabberd_resource_tests/try_5
Counting only
hi Bill
So I've got an XS 0.4 system running and I have an XO running 8.2
registered with the server and automated backups seem to be happening
fine. If I log onto the server and look at the XOs backup directory I
see the following:
[...]
drwxr-xr-x+ 3 CSN74800E35 CSN74800E35 4096
This is an implementation of the ideas described at
http://wiki.laptop.org/go/XS_Blueprints:OTP_root_passwords
There's an RPM at
http://xs-dev.laptop.org/xsrepos/testing/olpc/9/i386/xs-otp-0.4-1.xs9.noarch.rpm
and a repository at
Michael Stone [EMAIL PROTECTED]:
2. If you want to disable root login via the system password, touch
/etc/xs-otp/disable-root-password. This file will eventually exist
by default, but for now this option should be used with care. It
*could* leave you with no way of logging into the
Evgeniy Khramtsov wrote:
Does anyone have any tips, patches, or configuration options that might
help?
Most likely, OpenSSL eats all the memory. So, the solution is to rewrite
SSL/TLS code without this library :)
Right, thanks.
That looks easy in the sense that it seems to only involve the
Gary C Martin wrote:
http://wiki.laptop.org/go/Ejabberd_resource_tests#Try_4:_a_few_thousand_users
One extra figure that would be interesting is the server response latency to
client requests, not sure if hyperactivity gives you that easily.
No, I don't think hyperactivity does measure
I wrote:
I've written up my recent testing of ejabberd for the wiki:
http://wiki.laptop.org/go/Ejabberd_resource_tests
It is not completely satisfactory: I don't have the resources to test
up to 3000 active users which I believe is an important target. At
lower numbers, however, ejabberd's
I've written up my recent testing of ejabberd for the wiki:
http://wiki.laptop.org/go/Ejabberd_resource_tests
It is not completely satisfactory: I don't have the resources to test
up to 3000 active users which I believe is an important target. At
lower numbers, however, ejabberd's memory
I wrote:
It is not completely satisfactory: I don't have the resources to test
up to 3000 active users which I believe is an important target.
Just to clarify this: it was actually client resources I ran out of,
not the server (though that must have been getting close to melt
down).
I used
hi Greg
How do you tell what XS version you have installed? Someone tried the
usual way but it only gives me the Fedora version.
[EMAIL PROTECTED] ~]# cat /etc/redhat-release
Fedora release 7 (Moonshine)
Good question. Part of the answer is that that will work in 0.5 and onwards:
[EMAIL
Martin Langhoff wrote:
Bad news:
- idmgr dies with an sqlalchemy error
- xs-config has errors in %postinst
Tomorrow,
- fiddle with pungi to the kickstart included in the initrd and to
add grub options
- fix xs-config, idmgr
In an unrelated goose chase, I removed sqlalchemy from
Scott wrote:
The bitfrost.leases.crypto module contains routines to verify a given
activation lease or developer key; the intention was that the school
server never replace a valid key with an invalid or shorter key.
The trouble is the server doesn't necessarily know the laptop's UUID,
so it
http://dev.laptop.org/git?p=users/dbagnall/xs-activation.git
I've attached the README below.
Douglas
---
XS Activation Server
This package allows the school server to activate laptops over the
network, and
To preempt this FAQ, the F7 school server is quite inconsistent in its
IPv6 support, and some work would have been necessary to get it to a
state where I could test it. With the immanent jump to F9, and a new
networking setup, this didn't seem very worthwhile. I'll revisit it
again when IPv6 is
As per ticket #7606, until now XO users have had full shell access
over ssh. This (with related commits in ds-backup and xs-config),
confines them to rsync over ssh only.
The update_users.py script fixes existing users, while create_user
will now set the shell of new
XO users were being given their UUIDs as passwords, which was
unnecessary.
In case the user storage system changes again in the future, the post
installation scripts reference /home/idmgr/storage_format_version to
decide what to do.
diff --git a/Makefile b/Makefile
index
The status returned by /etc/init.d/idmgr stop is less often the inverse
of its actual success.
/etc/init.d/idmgr start will not start if the daemon is already running.
/etc/init.d/idmgr condrestart works.
diff --git a/conf.schoolserver/idmgr
This removes the named XO users from both the SQL and system databases.
To remove all users, use something like
/home/idmgr/remove_user `sqlite3 /home/idmgr/identity.db \
select serial from laptops`
diff --git a/Makefile b/Makefile
index fad74be..1065310 100644
The create_user script tries to give useful information to syslogd, and
ensures that the username it is given is a valid XO serial. It also checks
the ssh public key, but is not terribly strict. If a system user is created
but some later process fails, create_user tries to
hi Greg
One thing you could do while you are still new is to update and improve
our documentation as you go through it.
This is a good point. I will try to keep it in mind as I go. It's a
bit easy to fall into the habit of bypassing rather than improving bad
documentation.
I especially want
a typical New Zealand
art gallery. Designing and deploying tolerably cheap and fail-safe
systems has been a large part of my work.
Anyway, I'm glad to helping the OLPC project.
cheers,
Douglas Bagnall
___
Server-devel mailing list
Server-devel
31 matches
Mail list logo
