11 May
2013
11 May
'13
10:56 p.m.
So, has anyone done the upgrade yet to the newly released Debian stable
Wheezy?
As ever, I don't want to be the first :)
Ian
11 May
11 May
11:14 p.m.
On Sat, May 11, 2013 at 11:56:31PM +0100, Ian wrote:
So, has anyone done the upgrade yet to the newly
released Debian
stable Wheezy?
As ever, I don't want to be the first :)
I've done it on non-bitfolk machines. I haven't done my bitfolk VPS yet.
I'm not sure if bitfolk is running a relevant kernel, but watch out for
this bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637234
Michael
11:54 p.m.
Michael Stevens said:
I'm not sure if bitfolk is running a relevant
kernel, but watch out for
this bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637234
I've seen somewhere recently that someone has had problems with ext4 on
'too fast' disks - SSDs, I think.
Ian
12 May
12 May
12:56 a.m.
I've done it. Did a trial run on a machine at home and decided that the
easiest way was not upgrade a live machine, but to go for a clean install
using the Bitfolk offer of a VPS for 2 weeks to upgrade. Have encountered
no problems (he says touching wood)
On 12 May 2013 00:54, Ian <ian(a)lovingboth.com> wrote:
Michael Stevens said:
I'm not sure if bitfolk is running a relevant kernel, but watch out for
I've seen somewhere recently that someone has had problems with ext4 on
'too fast' disks - SSDs, I think.
Ian
______________________________**_________________
users mailing list
users(a)lists.bitfolk.com
https://lists.bitfolk.com/**mailman/listinfo/users<https://lists.bitfolk…
--
Keith Williams
Keith's Place www.keiths-place.co.uk
Tailor Made English www.tmenglish.org
West Norfolk RSPCA www.westnorfolkrspca.org.uk
7:54 a.m.
On Sun, 12 May 2013 01:56:14 +0100
Keith Williams <keithwilliamsnp(a)gmail.com> wrote:
I've done it. Did a trial run on a machine at home
and decided that
the easiest way was not upgrade a live machine, but to go for a clean
install using the Bitfolk offer of a VPS for 2 weeks to upgrade. Have
encountered no problems (he says touching wood)
almost a me-too ;-) I did it on a EeePC 900 that originally had the
'toy' interface which I'd replaced with Debian's EeePC specific
distro.
I did the two/three stage upgrade to wheezy - apt-get upgrade,
apt- get linux -image whatever followed by a reboot and then the
apt-get full-upgrade.
I had no problems with any of the packages although I was a little
surprised about the number of packages to be installed and a couple
of times I had to stop and do and apt-get clean as I was getting error
messages about lack of space in /var/cache/apt/archives. The upgrade
continued OK (with another apt-get upgrade) once I cleared some
space.
I suspect that full Debian with gnome is too big for this little
machine, some am going to purge gnome, and anything else I don't really
need as I no longer require "mobile computing", from it and use xfce
instead.
I'm a bit reluctant to do an upgrade on my live VPS so may go down the
temp VPS route too but there is no rush, the old-stable is just fine
for now.
--
John Lewis
Debian & the GeneWeb genealogical data server
8:28 a.m.
Keith Williams said:
I suspect that full Debian with gnome is too big for
this little
machine, some am going to purge gnome, and anything else I don't really
need as I no longer require "mobile computing", from it and use xfce
instead.
On the Eee900, xfce (or something lighter still) is definitely the way
to go.
Ian
13 May
13 May
11:27 a.m.
On Sun, 12 May 2013 09:28:34 +0100
Ian <ian(a)lovingboth.com> wrote:
Keith Williams said:
I managed to mess up removing the Gnome stuff with the result the EeePC
would no longer boot so have re-installed from scratch using
debian-live-7.0.0-i386-lxde-desktop.iso I loaded onto a usb pen-drive.
So am now using lxde, not quite as nice as xfce but usable.
<off topic>
So that little system will now reside up in the attic workshop where
it will be used to access pdf files regarding constructing a P4 railway
system.
For non-railway modellers P4 is a 'closer to scale' version of OO
gauge which is used for most commercially available models in the UK.
OO uses a rail spacing of 16.5 mm whereas P4 uses a spacing of 18.83
which is a much closer equivalent to the real thing in 4mm = 1ft scale
</off topic>
--
John Lewis
Debian & the GeneWeb genealogical data server
I suspect that full Debian with gnome is too big
for this little
machine, some am going to purge gnome, and anything else I don't
really need as I no longer require "mobile computing", from it and
use xfce instead.
On the Eee900, xfce (or something lighter still) is definitely the
way to go. 
12 May
12 May
2:55 p.m.
Hello,
On Sun, May 12, 2013 at 12:14:14AM +0100, Michael Stevens wrote:
On Sat, May 11, 2013 at 11:56:31PM +0100, Ian wrote:
> So, has anyone done the upgrade yet to the newly released Debian
> stable Wheezy?
I know that two customers have asked for disk snapshots prior to
their upgrade to wheezy, and have later come back saying the
snapshots were no longer needed as the upgrade was successful.
I have done at least 10 upgrades myself on BitFolk VPSes of my own,
but they were all prior to wheezy's release. I didn't experience any
issues, though I would expect any major problems to be restricted to
certain packages. For example, I have heard that the configuration
format for dovecot completely changed between squeeze and wheezy.
I'm not sure if bitfolk is running a relevant
kernel, but watch out for
this bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637234
There are some nodes which run kernels that would lead to barrier
operations failing in this way, so it's probably best if you try it
and see. If you do experience it then you'll need to put "barrier=0"
in your /etc/fstab and reboot.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
4:03 p.m.
The whole Dovecot config set up has changed. But if, like me, you last set
it up a couple or more years ago, you need to follow the HOWTOs on the web.
It's very straight forward and you can infact forget the include files and
just set up one straight forward conf file from scratch
On 12 May 2013 15:55, Andy Smith <andy(a)bitfolk.com> wrote:
Hello,
On Sun, May 12, 2013 at 12:14:14AM +0100, Michael Stevens wrote:
--
Keith Williams
Keith's Place www.keiths-place.co.uk
Tailor Made English www.tmenglish.org
West Norfolk RSPCA www.westnorfolkrspca.org.uk
On Sat, May 11, 2013 at 11:56:31PM +0100, Ian
wrote:
> So, has anyone done the upgrade yet to the newly released Debian
> stable Wheezy?
I know that two customers have asked for disk snapshots prior to
their upgrade to wheezy, and have later come back saying the
snapshots were no longer needed as the upgrade was successful.
I have done at least 10 upgrades myself on BitFolk VPSes of my own,
but they were all prior to wheezy's release. I didn't experience any
issues, though I would expect any major problems to be restricted to
certain packages. For example, I have heard that the configuration
format for dovecot completely changed between squeeze and wheezy.
I'm not sure if bitfolk is running a relevant
kernel, but watch out for
this bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637234
There are some nodes which run kernels that would lead to barrier
operations failing in this way, so it's probably best if you try it
and see. If you do experience it then you'll need to put "barrier=0"
in your /etc/fstab and reboot.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
_______________________________________________
users mailing list
users(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/users
21 May
21 May
2:54 p.m.
I've just done the upgrade on one VPS. I came across two issues.
The first was that, although it doesn't seem to be in the Debian release
notes's list of obsolete packages, the list of packages that will be
removed because it's been dropped includes sysklogd.
So if you use that for syslogd - and as I don't remember installing it,
it was probably in the initial Lenny VPS - you need to install
inetutils-syslogd instead. Before the upgrade is probably best but
either way..
apt-get install inetutils-syslogd
.. will get a working syslogd.
Keith Williams said:
The whole Dovecot config set up has changed. But if,
like me, you last
set it up a couple or more years ago, you need to follow the HOWTOs on
the web. It's very straight forward and you can infact forget the
include files and just set up one straight forward conf file from scratch
The relevant info is not quite as easy to find as it should be, but it
seems to come down to going to /etc/dovecot and..
.. moving the ssl certificates:
/etc/dovecot# mv /etc/ssl/certs/dovecot.pam .
/etc/dovecot# mv /etc/ssl/private/dovecot.pam private/
(per the warning when apt-get fails to upgrade dovecot:
Setting up dovecot-core (1:2.1.7-7) ...
You already have ssl certs for dovecot.
However you should move them out of /etc/ssl
and into /etc/dovecot and update the configuration
in /etc/dovecot/conf.d/10-ssl.conf accordingly.
See /usr/share/doc/dovecot-core/README.Debian.gz for details.)
.. then upgrading the conf files:
/etc/dovecot# mv dovecot.conf dovecot.conf.squeeze
/etc/dovecot# doveconf -n -c dovecot.conf.ucf-old >dovecot.conf
That generates a series of warnings:
doveconf: Warning: NOTE: You can get a new clean config file with:
doveconf -n > dovecot-new.conf
doveconf: Warning: Obsolete setting in dovecot.conf.ucf-old:24: 'imaps'
protocol is no longer necessary, remove it
doveconf: Warning: Obsolete setting in dovecot.conf.ucf-old:24: 'pop3s'
protocol is no longer necessary, remove it
doveconf: Warning: Obsolete setting in dovecot.conf.ucf-old:101:
ssl_cert_file has been replaced by ssl_cert = <file
doveconf: Warning: Obsolete setting in dovecot.conf.ucf-old:103:
ssl_key_file has been replaced by ssl_key = <file
doveconf: Warning: Obsolete setting in dovecot.conf.ucf-old:665:
protocol managesieve {} has been replaced by protocol sieve { }
doveconf: Warning: Obsolete setting in dovecot.conf.ucf-old:814: add
auth_ prefix to all settings inside auth {} and remove the auth {}
section completely
doveconf: Warning: Obsolete setting in dovecot.conf.ucf-old:851: passdb
pam {} has been replaced by passdb { driver=pam }
doveconf: Warning: Obsolete setting in dovecot.conf.ucf-old:888: userdb
passwd {} has been replaced by userdb { driver=passwd }
doveconf: Warning: Obsolete setting in dovecot.conf.ucf-old:960: userdb
passwd {} has been replaced by userdb { driver=passwd }
doveconf: Warning: Obsolete setting in dovecot.conf.ucf-old:1023:
auth_user has been replaced by service auth { user }
.. but the result is working.
(The source for the last bit reckoned you also needed
chmod 644 dovecot.conf
too, but that's what it was.)
If I've missed anything, do let me know.
Ian
22 May
22 May
7:18 p.m.
Thanks for that Ian.
Just a quick question for the list - I'm going to upgrade in a short while
- am I right in thinking that I can reboot the VPS at the end of the
upgrade process (to load the new kernel) without rebooting the machine on
which the VPS resides?
Thanks
Barry
On 21 May 2013 15:54, Ian <ian(a)lovingboth.com> wrote:
I've just done the upgrade on one VPS. I came
across two issues.
The first was that, although it doesn't seem to be in the Debian release
notes's list of obsolete packages, the list of packages that will be
removed because it's been dropped includes sysklogd.
So if you use that for syslogd - and as I don't remember installing it, it
was probably in the initial Lenny VPS - you need to install
inetutils-syslogd instead. Before the upgrade is probably best but either
way..
apt-get install inetutils-syslogd
.. will get a working syslogd.
Keith Williams said:
The whole Dovecot config set up has changed. But if, like me, you last
set it up a couple or more years ago, you need to
follow the HOWTOs on
the web. It's very straight forward and you can infact forget the
include files and just set up one straight forward conf file from scratch
The relevant info is not quite as easy to find as it should be, but it
seems to come down to going to /etc/dovecot and..
.. moving the ssl certificates:
/etc/dovecot# mv /etc/ssl/certs/dovecot.pam .
/etc/dovecot# mv /etc/ssl/private/dovecot.pam private/
(per the warning when apt-get fails to upgrade dovecot:
Setting up dovecot-core (1:2.1.7-7) ...
You already have ssl certs for dovecot.
However you should move them out of /etc/ssl
and into /etc/dovecot and update the configuration
in /etc/dovecot/conf.d/10-ssl.**conf accordingly.
See /usr/share/doc/dovecot-core/**README.Debian.gz for details.)
.. then upgrading the conf files:
/etc/dovecot# mv dovecot.conf dovecot.conf.squeeze
/etc/dovecot# doveconf -n -c dovecot.conf.ucf-old >dovecot.conf
That generates a series of warnings:
doveconf: Warning: NOTE: You can get a new clean config file with:
doveconf -n > dovecot-new.conf
doveconf: Warning: Obsolete setting in dovecot.conf.ucf-old:24: 'imaps'
protocol is no longer necessary, remove it
doveconf: Warning: Obsolete setting in dovecot.conf.ucf-old:24: 'pop3s'
protocol is no longer necessary, remove it
doveconf: Warning: Obsolete setting in dovecot.conf.ucf-old:101:
ssl_cert_file has been replaced by ssl_cert = <file
doveconf: Warning: Obsolete setting in dovecot.conf.ucf-old:103:
ssl_key_file has been replaced by ssl_key = <file
doveconf: Warning: Obsolete setting in dovecot.conf.ucf-old:665: protocol
managesieve {} has been replaced by protocol sieve { }
doveconf: Warning: Obsolete setting in dovecot.conf.ucf-old:814: add auth_
prefix to all settings inside auth {} and remove the auth {} section
completely
doveconf: Warning: Obsolete setting in dovecot.conf.ucf-old:851: passdb
pam {} has been replaced by passdb { driver=pam }
doveconf: Warning: Obsolete setting in dovecot.conf.ucf-old:888: userdb
passwd {} has been replaced by userdb { driver=passwd }
doveconf: Warning: Obsolete setting in dovecot.conf.ucf-old:960: userdb
passwd {} has been replaced by userdb { driver=passwd }
doveconf: Warning: Obsolete setting in dovecot.conf.ucf-old:1023:
auth_user has been replaced by service auth { user }
.. but the result is working.
(The source for the last bit reckoned you also needed
chmod 644 dovecot.conf
too, but that's what it was.)
If I've missed anything, do let me know.
Ian
______________________________**_________________
users mailing list
users(a)lists.bitfolk.com
https://lists.bitfolk.com/**mailman/listinfo/users<https://lists.bitfolk…
7:25 p.m.
On Wed, May 22, 2013 at 08:18:34PM +0100, Barry Watson wrote:
Thanks for that Ian.
Just a quick question for the list - I'm going to upgrade in a short while
- am I right in thinking that I can reboot the VPS at the end of the
upgrade process (to load the new kernel) without rebooting the machine on
which the VPS resides?
Yes.
*First* check that you can log in to the Xen Shell.
Then shut down from within the VPS as normal (don't reboot -- IIRC
there's some issue over doing a simple reboot from within the VPS) and
then use the your Xen Shell login to create/boot the VPS again.
Hugo.
Thanks
Barry
On 21 May 2013 15:54, Ian <ian(a)lovingboth.com> wrote:
> I've just done the upgrade on one VPS. I came across two issues.
>
> The first was that, although it doesn't seem to be in the Debian release
> notes's list of obsolete packages, the list of packages that will be
> removed because it's been dropped includes sysklogd.
>
> So if you use that for syslogd - and as I don't remember installing it, it
> was probably in the initial Lenny VPS - you need to install
> inetutils-syslogd instead. Before the upgrade is probably best but either
> way..
>
> apt-get install inetutils-syslogd
>
> .. will get a working syslogd.
>
> Keith Williams said:
>
> The whole Dovecot config set up has changed. But if, like me, you last
>> set it up a couple or more years ago, you need to follow the HOWTOs on
>> the web. It's very straight forward and you can infact forget the
>> include files and just set up one straight forward conf file from scratch
>>
>
> The relevant info is not quite as easy to find as it should be, but it
> seems to come down to going to /etc/dovecot and..
>
> .. moving the ssl certificates:
>
> /etc/dovecot# mv /etc/ssl/certs/dovecot.pam .
> /etc/dovecot# mv /etc/ssl/private/dovecot.pam private/
>
> (per the warning when apt-get fails to upgrade dovecot:
>
> Setting up dovecot-core (1:2.1.7-7) ...
> You already have ssl certs for dovecot.
> However you should move them out of /etc/ssl
> and into /etc/dovecot and update the configuration
> in /etc/dovecot/conf.d/10-ssl.**conf accordingly.
> See /usr/share/doc/dovecot-core/**README.Debian.gz for details.)
>
> .. then upgrading the conf files:
>
> /etc/dovecot# mv dovecot.conf dovecot.conf.squeeze
> /etc/dovecot# doveconf -n -c dovecot.conf.ucf-old >dovecot.conf
>
> That generates a series of warnings:
>
> doveconf: Warning: NOTE: You can get a new clean config file with:
> doveconf -n > dovecot-new.conf
> doveconf: Warning: Obsolete setting in dovecot.conf.ucf-old:24: 'imaps'
> protocol is no longer necessary, remove it
> doveconf: Warning: Obsolete setting in dovecot.conf.ucf-old:24: 'pop3s'
> protocol is no longer necessary, remove it
> doveconf: Warning: Obsolete setting in dovecot.conf.ucf-old:101:
> ssl_cert_file has been replaced by ssl_cert = <file
> doveconf: Warning: Obsolete setting in dovecot.conf.ucf-old:103:
> ssl_key_file has been replaced by ssl_key = <file
> doveconf: Warning: Obsolete setting in dovecot.conf.ucf-old:665: protocol
> managesieve {} has been replaced by protocol sieve { }
> doveconf: Warning: Obsolete setting in dovecot.conf.ucf-old:814: add auth_
> prefix to all settings inside auth {} and remove the auth {} section
> completely
> doveconf: Warning: Obsolete setting in dovecot.conf.ucf-old:851: passdb
> pam {} has been replaced by passdb { driver=pam }
> doveconf: Warning: Obsolete setting in dovecot.conf.ucf-old:888: userdb
> passwd {} has been replaced by userdb { driver=passwd }
> doveconf: Warning: Obsolete setting in dovecot.conf.ucf-old:960: userdb
> passwd {} has been replaced by userdb { driver=passwd }
> doveconf: Warning: Obsolete setting in dovecot.conf.ucf-old:1023:
> auth_user has been replaced by service auth { user }
>
> .. but the result is working.
>
> (The source for the last bit reckoned you also needed
>
> chmod 644 dovecot.conf
>
> too, but that's what it was.)
>
> If I've missed anything, do let me know.
>
> Ian
>
> ______________________________**_________________
> users mailing list
> users(a)lists.bitfolk.com
>
https://lists.bitfolk.com/**mailman/listinfo/users<https://lists.bitfolk…
>
_______________________________________________
users mailing list
users(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/users
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- Strive for apathy! ---
7:29 p.m.
Hi Barry,
On Wed, May 22, 2013 at 08:18:34PM +0100, Barry Watson wrote:
am I right in thinking that I can reboot the VPS at
the end of the
upgrade process (to load the new kernel) without rebooting the
machine on which the VPS resides?
I'm not sure I follow. You can reboot your VPS whenever you like
using the Xen Shell.
I recommend you acquaint yourself very well with the Xen Shell
before doing anything major like a distribution upgrade:
https://tools.bitfolk.com/wiki/Xen_Shell
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
I'd be interested to hear any (even two word)
reviews of their sofas…
Provides seating. — Andy Davidson
26 May
26 May
4:56 p.m.
I said:
I've just done the upgrade on one VPS. I came
across two issues.
I've now done another one. This time, dovecot went ok (perhaps because I
had copied the certificates ahead of time), but it uninstalled MySQL
rather than upgrading it from 5.1 to 5.5 - just mysql-common was upgraded.
As the previous upgrade also said that 5.1 was going to be removed, I
didn't notice that 5.5 wasn't in the install list. Fortunately, that
this had happened was obvious on restarting. My guess is that it's down
to how it was installed in the first place, possibly as version 5.0 or
5.1 rather than as the generic package.
If I've missed anything, do let me know.
Memory is telling me that in the change from Lenny to Sqeeze, the
correct file ownership of BIND's slave zone files in /var/cache/bind/
changed - syslog would get lots of..
named[2067]: zone example.com/IN: refresh: could not set file
modification time of '/var/cache/bind/example.com.hosts': permission denied
.. messages until the ownership was changed.
It's possible it's changed again (back to what it was?) because the
messages came back. After..
chown bind:bind /var/cache/bind/*
.. everything looks happy.
Ian
27 May
27 May
8:39 p.m.
New subject: Wheezy - pam modules moved
Hi,
On one VPS, but not the other, I am getting an error in
/var/log/auth.log about being unable to load three modules:
adding faulty module: /lib/security/pam_deny.so: 30 Time(s)
adding faulty module: /lib/security/pam_permit.so: 30 Time(s)
adding faulty module: /lib/security/pam_unix.so: 30 Time(s)
It's Perl that's asking, which probably means it's Webmin.
The reason it can't is that they no longer exist.. there, because the
multiarch feature means they're now in /lib/i386-linux-gnu/
security/
Has anyone else had this? I am not sure why it's ok in one but not the
other...
Ian
9:51 p.m.
New subject: Wheezy - pam modules moved
I said:
The reason it can't is that they no longer exist..
there, because the
multiarch feature means they're now in /lib/i386-linux-gnu/
security/
Has anyone else had this? I am not sure why it's ok in one but not the
other...
For example, both have /etc/webmin/pam/config containing...
lib_dirs=/lib/security
pam_dir=/etc/pam.d
ignore=README
mod_equiv=pam_unix_acct.so=pam_pwdb.so pam_unix_auth.so=pam_pwdb.so
pam_unix_passwd.so=pam_pwdb.so pam_unix_session.so=pam_pwdb.so
pam_unix_sess.so=pam_pwdb.so pam_unix.so=pam_pwdb.so
.. yet it's only a problem on one of them.
Ian
28 May
28 May
7:32 a.m.
New subject: Wheezy - pam modules moved
On 27/05/2013 22:51, Ian wrote:
I said:
Have you checked whether /lib/security has been symlinked to
/lib/i386-linux-gnu/security on either system? (particularly the one
that works)
--
Phil
The reason it can't is that they no longer
exist.. there, because the
multiarch feature means they're now in /lib/i386-linux-gnu/
security/
For example, both have /etc/webmin/pam/config containing...
lib_dirs=/lib/security
pam_dir=/etc/pam.d
ignore=README
mod_equiv=pam_unix_acct.so=pam_pwdb.so pam_unix_auth.so=pam_pwdb.so
pam_unix_passwd.so=pam_pwdb.so pam_unix_session.so=pam_pwdb.so
pam_unix_sess.so=pam_pwdb.so pam_unix.so=pam_pwdb.so
.. yet it's only a problem on one of them.
8:36 a.m.
New subject: Wheezy - pam modules moved
Phil Stewart asked:
Have you checked whether /lib/security has been
symlinked to
/lib/i386-linux-gnu/security on either system? (particularly the one
that works)
/lib/security doesn't exist in any form on either of them:
# ls -lha /lib/security
ls: cannot access /lib/security: No such file or directory
My understanding of how multiarch is supposed to work is that things
should look in the places they're supposed to look :) to find the
libraries they are after, rather than assume they are directly off /lib,
but webmin is not in the Debian repositories and quite possibly has not
been made to understand this yet.
In the meantime, changing the lib_dirs setting on the one that didn't
work is making it work (or at least there's nothing in auth.log saying
it isn't...)
Ian
12 Jun
12 Jun
8:27 p.m.
Another change between Squeeze and Wheezy has just come to my attention:
php5-suhosin has been dropped.
<http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657698> has the
reasoning, but if you had it, you now need to live without it or get
compiling :)
To avoid having Apache error logs mention it a lot..
rm /etc/php5/conf.d/suhosin.ini
.. and restart Apache.
Ian
13 May
13 May
3:25 p.m.
I have. The only annoying thing that caught me out is that the new
tmux can't reconnect to the older squeeze tmux sessions. :-)
18 Jun
18 Jun
10:40 p.m.
On Sat, May 11, 2013 at 11:56:31PM +0100, Ian wrote:
So, has anyone done the upgrade yet to the newly
released Debian
stable Wheezy?
As ever, I don't want to be the first :)
Just done my bitfolk VPS. Went unexpectedly well.
I might just be imagining it, but has anyone noticed things seeming
faster after the upgrade?
Michael
3962
days inactive
4000
days old
20 comments
9 participants
participants (9)
-
Andy Smith -
Barry Watson -
Hugo Mills -
Ian -
john lewis -
Kai Hendry -
Keith Williams -
Michael Stevens -
Phil Stewart