https://www.archlinux.org/packages/differences/ says that xdelta3 has
not been updated for 32-bit - why?
https://projects.archlinux.org/svntogit/community.git/commit/trunk?h=packages/xdelta3&id=2a27ff1daadfc44b00e10acd8f32dc9661a6e8a5
https://www.archlinux.org/packages/community/i686/xdelta3/
BTW
2013/7/10 Sébastien Luttringer
> On Tue, Jul 9, 2013 at 12:13 PM, M Saunders wrote:
> > which has some useful tips. But it'd be interesting to hear from
> > people running Arch on production servers, how well it works for them
> > and what (if any) problems they've faced.
> >
>
> I've 9 personal
Hi,
Am 10.07.2013 13:59, schrieb Sébastien Luttringer:
> 7) Security
> Debian is not more secure because their softwares are old. It's a lie.
> Check the number of open flaw in the security bug tracker[10].
> If you want to be in a secure environment stay up-to-date, don't use
> debian stable, use
On Wednesday 10 Jul 2013 13:59:07 Sébastien Luttringer wrote:
> 3) Use a versioned kernel
> One of the most wanted expectation on a server is to avoid reboot.
> Arch official kernel is too often updated for a server _and_ cannot be
> installed without breaking the running kernel (modules mismatch).
On 07/10/2013 01:11 PM, Oliver Kraitschy wrote:
> Hello everyone,
>
> since the update to subversion 1.8.0 i can't make subversion store passwords.
> It asks for the password with every command i execute.
>
> I also tried to tell subversion explicitely to store passwords and to store
> them in
Hello everyone,
since the update to subversion 1.8.0 i can't make subversion store passwords.
It asks for the password with every command i execute.
I also tried to tell subversion explicitely to store passwords and to store
them in plaintext with the following settings in the servers config fi
On Tue, Jul 9, 2013 at 12:13 PM, M Saunders wrote:
> which has some useful tips. But it'd be interesting to hear from
> people running Arch on production servers, how well it works for them
> and what (if any) problems they've faced.
>
I've 9 personal servers running Archlinux (previously under d
Forgot to say - for server setups, I always test updates on a shadow
machine before applying them to server itself - something that is
prudent policy regardless of which distro you're using.
I have run Redhat, Fedora and Arch servers. HAnds down arch wins for a
server setup.
Change happens - always. Wigth Arch the changes are fed to me in small
chunks - I get to deal with one change at a time (e.g. changing to
systemd) Any given change might be smaller or larger but with Arch
9 matches
Mail list logo
