| 1 |
On Thursday 11 February 2010 22:37:00 Mark Knecht wrote: |
| 2 |
> On Thu, Feb 11, 2010 at 12:24 PM, Alan McKinnon <alan.mckinnon@×××××.com> |
| 3 |
wrote: |
| 4 |
> > On Thursday 11 February 2010 22:09:28 Mark Knecht wrote: |
| 5 |
> >> Can someone comment on why I do or do not want to include config files |
| 6 |
> >> when making quickpkg files? |
| 7 |
> >> |
| 8 |
> >> Seems like there is the issue of hand edits being saved which would be |
| 9 |
> >> a good reason to keep them. I'm not overly worried about someone |
| 10 |
> >> stealing them and getting access to settings, but I can see that might |
| 11 |
> >> be a good reason not to. |
| 12 |
> >> |
| 13 |
> >> If I don't save them and then after a crash want to use binary |
| 14 |
> >> packages to get a machine running quickly it seems like I'd want to |
| 15 |
> >> include everything I could. |
| 16 |
> >> |
| 17 |
> >> What would the more experienced user do for the single-user desktop type |
| 18 |
> >> user? |
| 19 |
> > |
| 20 |
> > The config of the package you quickpkg'ed likely works. |
| 21 |
> > emerge -k is most often used to revert your own mistakes, so you want the |
| 22 |
> > thing to work. Your latest configs are suspect, why insist they take |
| 23 |
> > priority? You can always rename them to <name>.bak if you think they |
| 24 |
> > might get nuked. |
| 25 |
> > |
| 26 |
> > Why do you care if someone steals your quickpkgs? Put them in a directory |
| 27 |
> > owned by root, they are then as safe as your stuff in /etc. To get to the |
| 28 |
> > tarballs, they must get to a place where they can just read the |
| 29 |
> > originals.... |
| 30 |
> |
| 31 |
> Thanks Alan. That confirms what I was thinking. |
| 32 |
> |
| 33 |
> My comment about things getting stolen is that I might burn them to |
| 34 |
> DVD for safe keeping in which case anyone can walk off with the DVD. |
| 35 |
> I'm not overly worried about that and it's far and away less of an |
| 36 |
> issue than getting the machine back to a running state. |
| 37 |
|
| 38 |
OK, I see. |
| 39 |
|
| 40 |
As long as you know which configs have password in them and take precautions, |
| 41 |
you should be OK. |
| 42 |
|
| 43 |
For the truly paranoid (and there will be someone who is validly so) another |
| 44 |
option is to store /etc in a remote SVN instance that is secured, and not |
| 45 |
store configs with the quickpkgs |
| 46 |
|
| 47 |
-- |
| 48 |
alan dot mckinnon at gmail dot com |
Archives