Downtime?
in [Slackware]
|
From: Manuel Reimer on 25 Feb 2010 02:29 Sylvain Robitaille wrote: > While you're at it, make sure to install and enable ssh so that next > time you're in a similar situation you'll be able to install your own > package on them all remotely. This would require them all to be online at once and them all to be registered at some "dyndns" service. And it would require me to upload the package to somewhere with my slow 64kbit upstream. Most probably it would be faster to copy the packages to USB memory and install anything manually... The only real solution may be to get a root server, install Slackware on this system and let the server compile the package and host it for my clients to auto-update from there. This way, I only would have to send the compile request via SSH and the server would do the work. Expensive and exaggerated for a handful of clients. ... still waiting for some feedback, what is going on backstage. Eric??? That's one small disadvantage of Slackware: Missing feedback to users. BTW: I think PV should start to blog ;-) So far, gentoo also has no patch. They still wait for arches to test: https://bugs.gentoo.org/show_bug.cgi?id=305689 Means: Gentoo is no alternative to Slackware, at least from the security point of view. CU Manuel
From: goarilla on 25 Feb 2010 13:27 On Thu, 25 Feb 2010 08:29:05 +0100, Manuel Reimer wrote: > Sylvain Robitaille wrote: >> While you're at it, make sure to install and enable ssh so that next >> time you're in a similar situation you'll be able to install your own >> package on them all remotely. > > This would require them all to be online at once and them all to be > registered at some "dyndns" service. And it would require me to upload > the package to somewhere with my slow 64kbit upstream. Most probably it > would be faster to copy the packages to USB memory and install anything > manually... > > The only real solution may be to get a root server, install Slackware on > this system and let the server compile the package and host it for my > clients to auto-update from there. This way, I only would have to send > the compile request via SSH and the server would do the work. Expensive > and exaggerated for a handful of clients. or just put up your own repositories
From: goarilla on 25 Feb 2010 13:29 On Tue, 23 Feb 2010 10:40:39 -0500, Michael Black wrote: > On Tue, 23 Feb 2010, Manuel Reimer wrote: > >> Hi, >> >> no updates since January 31. >> >> No security patch package for SeaMonkey 2.0.3. >> >> Does anyone know what's going on? >> >> Yours >> >> Manuel >> >> > Related or not, there was that weekend or so when the server wasn't > responding. But it had stuck at Jan 31st for a while before that > happened. > > It may be one of those periods when there are no updates, only to > suddenly have a whole bunch at one time, which suggests a level of > interaction so they had to be done together. > > Around the time of the last US election, there was a similar "dead" > period, and when someone asked, the US election was suggested as the > reason for the lull. > > Michael it could be he's just on vacation, or doesn't really care atm
From: Stuart Winter on 27 Feb 2010 11:00 >> Related or not, there was that weekend or so when the server wasn't >> responding. But it had stuck at Jan 31st for a while before that >> happened. [..] > it could be he's just on vacation, or doesn't really care atm He's definitley not on vacation, and the outage of www.slackware.com is unrelated. Just to tease you. This is the changelog of Slackware64-current since "Sun Jan 31 19:28:54 UTC 2010" (the public tree). root(a)wizbit:~/slackware64-current# grep -ci upgraded ChangeLog.txt 355 There's a lot going on! There haven't been any updates since then because so many updates need a lot of package rebuilds (or upgrades) in order to stabilise the tree. -- Stuart Winter www.slackware.com/~mozes Slackware for ARM: www.armedslack.org
From: Grant on 27 Feb 2010 14:48 On 27 Feb 2010 16:00:11 GMT, Stuart Winter <not.a.real.address(a)interlude.org.uk> wrote: >>> Related or not, there was that weekend or so when the server wasn't >>> responding. But it had stuck at Jan 31st for a while before that >>> happened. >[..] > >> it could be he's just on vacation, or doesn't really care atm > >He's definitley not on vacation, and the outage of www.slackware.com >is unrelated. > >Just to tease you. This is the changelog of Slackware64-current >since "Sun Jan 31 19:28:54 UTC 2010" (the public tree). > >root(a)wizbit:~/slackware64-current# grep -ci upgraded ChangeLog.txt >355 > >There's a lot going on! > >There haven't been any updates since then because so many updates need >a lot of package rebuilds (or upgrades) in order to stabilise the tree. They broke it!?! -- http://bugs.id.au/
First
|
Prev
|
Next
|
Last
Pages: 1 2 3 4 Prev: Alt.OS.Linux.Slackware FAQ pointer Next: libgtk-1.2.so.0 |