search for: parentage

I regularly use ssh-agent with a subcommand; my X11 session is spawned through ssh-agent, and sometimes i'll run a special agent for a certain subset of commands, like this: ssh-agent bash ... and then do work within that shell. From the man page: > If a commandline is given, this is executed as a subprocess of the agent. > When the command dies, so does the agent. But

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The server rebuild was a complete failure. For some reason, neither FC3 nor SuSE 9.2 like the graphics card in the box. I have reinstalled the old hard drive and the server is back on line. - -Tom - -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net

For whatever reason I decided to implement the validator class tonight. It''s my first go at implementing the class. My first run at it looked pretty good. I just added a generic .i for it and it all compiled. Sadly, the samples didn''t work because the base Validator class can''t actually be used as a validator! You have to derive from GenericValidator. I

...te is another: https://sqlite.org/ > It doesn't need to be as fancy as github Fossil?s web UI is more advanced than GitHub in some ways: 1. I find Fossil?s timeline view more useful than GitHub?s closest equivalent, the ?Commits? page. The commits all look ?flat? to me in GitHub, whereas parentage, branches, etc. are clearer in Fossil?s web timeline view. I suspect this is actually a reflection of a difference in the underlying philosophies of these two DVCSes rather than some UI designer?s idiosyncratic preference, but I?ll get back to that later. 2. Fossil makes it easy to diff two versi...

Hello, Set up a CentOS 7.5 VM linode for git now that github has been bought. I'm not anti-microsoft but I'm worried they will make changes that I don't like (e.g. requiring ms account, changing billing, etc.) so I figured better take control now. Currently moving my private repos and have them set up in my home directory there, but my public repos - I want to set them up with a

A good number of the samples I have tested are outright or subtly broken on Windows now. I''m trying to determine what the cause is. Mostly it seems related to the initialize function not being created when it should be. Case in point: ClientDC.i The caret example won''t work at all because initialize isn''t declared any longer. If you comment out the import

...lass (metadata) object involved any superclasses (or later on, subclasses), the manipulations required would occur at the object level, not at the *name* level. I can see why it is necessary to update the metadata object itself, because functions like `setIs` and `setClassUnion` allow the upstream parentage of a class to be altered post hoc in ways which depend upon what else is loaded, and a class must be able to find that type of information if inheritance is going to work. But at the moment it seems that it is necessary to import the *name* of the superclass(es) into the `mypkg` namespace as well,...

On looking more closely, the purpose of finding the class definition is to update the entry for the new relationship, as the warning message suggests. That requires that the namespace holding the definition be writable. In the case of subclass information, the original namespace is very likely to be locked, if it's not the package currently being loaded. Copying the definition in order to

Hi: I have a Dockerfile, which builds an image which installed R 3.3.2 in Ubuntu 14.04, but building using that Dockerfile seems to have stopped working and I am unclear why. I believe the relevant error is: Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, On November 30th, FreeBSD 6.4 and FreeBSD 8.0 will have reached their End of Life and will no longer be supported by the FreeBSD Security Team. Since FreeBSD 6.4 is the last remaining supported release from the FreeBSD 6.x stable branch, support for the FreeBSD 6.x stable branch will also cease at the same point. Users of either of

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, On November 30th, FreeBSD 6.4 and FreeBSD 8.0 will have reached their End of Life and will no longer be supported by the FreeBSD Security Team. Since FreeBSD 6.4 is the last remaining supported release from the FreeBSD 6.x stable branch, support for the FreeBSD 6.x stable branch will also cease at the same point. Users of either of