Mick wrote:
>
> I can think of 3 things, but more learned M/L contributors may add to these:
>
> 1. The SATA connection has come loose. With time and movement it can come
> (slightly) adrift. Pushing it back in fully fixes this problem - also see No.
> 2 below.
>
> 2. The physical connector's co
On Thursday, 7 March 2019 10:10:53 GMT Peter Humphrey wrote:
> On Wednesday, 6 March 2019 16:31:27 GMT Laurence Perkins wrote:
> > On Fri, 2019-03-01 at 10:12 +, Peter Humphrey wrote:
> > > [OT]
> > > Evidence is mounting that the Atom box is in terminal decline. I get
> > > things like batches
On Wednesday, 6 March 2019 16:31:27 GMT Laurence Perkins wrote:
> On Fri, 2019-03-01 at 10:12 +, Peter Humphrey wrote:
> > [OT]
> > Evidence is mounting that the Atom box is in terminal decline. I get
> > things like batches of files in the portage tree changing owner, and then
> > when I corr
On 06/03/19 17:39, Alan Mackenzie wrote:
> Up to now, I've never had a HDD or SDD fail on me. :-) I hope that
> when this does eventually happen, I'll be prepared.
I don't think I've had one of mine fail. I have, however, done recovery
jobs on two drives that did fail that I managed to revive lo
Hello, Rich.
I'd like to say hello again to everybody, just to mark that I'm still
here and still using Gentoo, and thank people for (a lot of) help
rendered in the past. My system, used mainly for SW development, has
been stable and well behaved, with very occasional exceptions, for some
while n
On Wed, Mar 6, 2019 at 11:31 AM Laurence Perkins wrote:
>
> If it's just that the SSD is failing, then get a new one before
> something important gets damaged and you have to redo the whole thing.
IMO any kind of storage device should be treated as if it could fail
at any time without warning. Y
On Fri, 2019-03-01 at 10:12 +, Peter Humphrey wrote:
> On Thursday, 28 February 2019 15:47:41 GMT Rich Freeman wrote:
>
> > In general it is usually simplest to just remove /usr/portage
> > anytime
> > you change the sync settings. At least until portage gets smarter
> > about it.
>
> That
On Thursday, 28 February 2019 15:47:41 GMT Rich Freeman wrote:
> In general it is usually simplest to just remove /usr/portage anytime
> you change the sync settings. At least until portage gets smarter
> about it.
That works well on a sufficiently powerful box; it only took - oh, I don't
know
On Thu, Feb 28, 2019 at 10:41 AM Peter Humphrey wrote:
>
> On Thursday, 28 February 2019 08:43:13 GMT Davyd McColl wrote:
>
> > Well, that's pretty-much how git works -- that local repo was still pointing
> > to the old remote. Updating your repos.conf won't change that as the old
> > remote is st
On Thursday, 28 February 2019 08:43:13 GMT Davyd McColl wrote:
> > On 2019/02/28 10:36:35, Peter Humphrey wrote:
> > I have a little server box on my LAN, which I use as a git server. I'm
> > having a bit of trouble with it pro tem so I decided to switch the git
> > sync source on this box.
> >
I filed a bug report https://bugs.gentoo.org/679040.
Yes, currently you need to update your git config manually everytime you
change your git remote.
On 2019/02/28 10:36:35, Peter Humphrey wrote:
Hello list,
I have a little server box on my LAN, which I use as a git server. I'm having
a bit of trouble with it pro tem so I decided to switch the git sync source on
this box.
I removed the entry pointing to the local server in repos.conf/gentoo.c
Hello list,
I have a little server box on my LAN, which I use as a git server. I'm having
a bit of trouble with it pro tem so I decided to switch the git sync source on
this box.
I removed the entry pointing to the local server in repos.conf/gentoo.conf and
put in 'sync-uri = https://github.co
13 matches
Mail list logo
