Re: Logbook - RCS
On Wed, Dec 17, 2003 at 02:41:11PM -0800, Gruessle said > > From: Tom [mailto:[EMAIL PROTECTED] > > On Wed, Dec 17, 2003 at 02:06:52PM -0800, Gruessle wrote: > > > > > > arch comes up as "print machine architecture" > > > what is the arch you are taking about? > > > > apt-cache show arch says look for larch > > apt-cache show larch says you should really use tla > > > > so I guess you should read apt-cache show tla > > > > I don't get any of that > apt-cache show arch says revision control system It's in the tla package in sid. Make sure you use 1.1, it has an enormous number of improvements over 1.0 and larch. The binary is "tla" and you'll want to read the tutorial (linked from http://regexps.srparish.net/) and the primer (http://repose.cx/ArchPrimer.html, iirc). > can't find the stuff you been finding. > But I don't get it if I type arch I get i686, which is my AMD > and arch --help says "print machine architecture" Yes, this is the "arch" command from the util-linux package. -- Rob Weir <[EMAIL PROTECTED]> | [EMAIL PROTECTED] | Do I look like I want a CC? Words of the day: offensive information warfare rs9512c AGT. AMME codes signature.asc Description: Digital signature
Re: Logbook - RCS
On Wed, Dec 17, 2003 at 02:08:08PM -0800, Nunya said > On Wed, Dec 17, 2003 at 02:06:52PM -0800, Gruessle wrote: > > > > arch comes up as "print machine architecture" > > what is the arch you are taking about? > > apt-cache show arch says look for larch Arch is the name for the...concept, sort of. There are several implementations. > apt-cache show larch says you should really use tla larch is the original sh-based prototype, tla is the new re-write in C. The C version is both faster and more correct, so make sure you use it. It's almost completely backward-compatible with larch, too. There's also ArX, but it seems sort of stalled. > so I guess you should read apt-cache show tla Yup, but make sure you're using 1.1. -- Rob Weir <[EMAIL PROTECTED]> | [EMAIL PROTECTED] | Do I look like I want a CC? Words of the day: AK-47 fraud CID anarchy mailbomb cryptographic class struggle signature.asc Description: Digital signature
Re: Logbook - RCS
On Wed, Dec 17, 2003 at 09:11:02AM -0800, Gruessle wrote: > > > I found following in the "Configuration HOWTO" manual. > My question is what software do U use as Logbook and what in RCS? Regarding keeping a log book - I would highly recommend buying a real, physical notebook and keeping notes about configuration, commands etc. that you learn in that. You may find an electronic logbook inaccessible, or you may frag your storage, or re-install your OS a few times whilst learning, and the paper notebook will survive all of that. > -- Jon Dowland http://jon.dowland.name/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Logbook - RCS
On Wed, 17 Dec 2003 at 17:11 GMT, Gruessle penned: > > > I found following in the "Configuration HOWTO" manual. My question is > what software do U use as Logbook and what in RCS? Assuming you mean "what *is* RCS?" ... RCS is "Revision Control System". It's a tool that lets you track changes in individual files. CVS is (sort of) directory-aware, but uses RCS under the covers. > > 2.2. Start the Logbook! To keep your installation in shape, it's > essential that you know exactly what happened to your machine, which > packages you installed that day, what you removed or modified, and so > on. So, the first thing you'll do before you tamper with your machine > is start a ``logbook''. Therein you'll take note of every move you > make as root; in my own logbook I also keep a section where I list all > modified system files, additional .rpms, and .tar.gz I installed. > Optimally, backtracking your moves you should be able to re-obtain a > fresh installation. > > Make a backup copy of the system files you touch. Better still, use > RCS; you'll be able to backtrack all changes. Never work as root > without logging your moves! > > -- monique -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Logbook - RCS
On Wed, Dec 17, 2003 at 02:41:11PM -0800, Gruessle wrote: > > From: Tom [mailto:[EMAIL PROTECTED] > > On Wed, Dec 17, 2003 at 02:06:52PM -0800, Gruessle wrote: > > > > > > arch comes up as "print machine architecture" > > > what is the arch you are taking about? > > > > apt-cache show arch says look for larch > > apt-cache show larch says you should really use tla > > > > so I guess you should read apt-cache show tla > > > > I don't get any of that > apt-cache show arch says revision control system > can't find the stuff you been finding. > But I don't get it if I type arch I get i686, which is my AMD > and arch --help says "print machine architecture" I'm using SID $ apt-cache show arch; apt-cache show larch; apt-cache show tla Package: arch [snip] Description: transitional package This dummy package exists only to smooth upgrades to larch. It may be removed once the upgrade has completed. Package: larch [snip] Description: revision control system arch is a revision control system with features that are ideal for projects characterised by widely distributed development, concurrent support of multiple releases, and substantial amounts of development on branches. It can be a replacement for CVS and corrects many mis-features of that system. . larch is the implementation of arch in shell and C, by Tom Lord. . It is HIGHLY RECOMMENDED that you use tla instead of larch. This package is provided for backwards-compatibility purposes, since tla is not a drop-in replacement for larch. Package: tla [snip] Description: arch revision control system arch is a revision control system with features that are ideal for projects characterised by widely distributed development, concurrent support of multiple releases, and substantial amounts of development on branches. It can be a replacement for CVS and corrects many mis-features of that system. . tla is an implementation of arch in C, by Tom Lord. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: Logbook - RCS
> From: Tom [mailto:[EMAIL PROTECTED] > On Wed, Dec 17, 2003 at 02:06:52PM -0800, Gruessle wrote: > > > > arch comes up as "print machine architecture" > > what is the arch you are taking about? > > apt-cache show arch says look for larch > apt-cache show larch says you should really use tla > > so I guess you should read apt-cache show tla > I don't get any of that apt-cache show arch says revision control system can't find the stuff you been finding. But I don't get it if I type arch I get i686, which is my AMD and arch --help says "print machine architecture" -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Logbook - RCS
On Wed, Dec 17, 2003 at 02:06:52PM -0800, Gruessle wrote: > > arch comes up as "print machine architecture" > what is the arch you are taking about? apt-cache show arch says look for larch apt-cache show larch says you should really use tla so I guess you should read apt-cache show tla -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Logbook - RCS
Rob Weir said on Thu, Dec 18, 2003 at 08:59:55AM +1100: > I've started keeping my various /etc's in Arch, and it's working out > quite well. Arch versions both the symlinks in there and the file > permissions, as well as file changes/moves/deletions/etc. Not the file > *ownership*, however, so I'll need to be careful if/when I have to > restore a /etc. Oh, the other advantage is that I can trivially mirror > the archives via sftp, so my backups are handled, too ;-) I have been using CVS and CVSup for this, but it doesn't handle symlinks or file moves well. I'll have to take a look at Arch. Subversion appears to have the ability to be extended to manage owner and permissions via plugins, but I can't find any pointers to anyone who has done so. M pgp0.pgp Description: PGP signature
RE: Logbook - RCS
> From: Rob Weir [mailto:[EMAIL PROTECTED] > On Wed, Dec 17, 2003 at 03:17:27PM -0500, David Z Maze said > > "Gruessle" <[EMAIL PROTECTED]> writes: > > > Make a backup copy of the system files you touch. Better > still, use RCS; > > > > Install the rcs package, then read rcsintro(1). (Again, > though, this > > is something I don't generally do, though I understand why it's Good > > Practice (TM). I do use version control for my Emacs dotfiles, if > > that makes things better.) > > I've started keeping my various /etc's in Arch, and it's working out > quite well. Arch versions both the symlinks in there and the file > permissions, as well as file changes/moves/deletions/etc. > Not the file > *ownership*, however, so I'll need to be careful if/when I have to > restore a /etc. Oh, the other advantage is that I can > trivially mirror > the archives via sftp, so my backups are handled, too ;-) > arch comes up as "print machine architecture" what is the arch you are taking about? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Logbook - RCS
On Wed, Dec 17, 2003 at 03:17:27PM -0500, David Z Maze said > "Gruessle" <[EMAIL PROTECTED]> writes: > > Make a backup copy of the system files you touch. Better still, use RCS; > > Install the rcs package, then read rcsintro(1). (Again, though, this > is something I don't generally do, though I understand why it's Good > Practice (TM). I do use version control for my Emacs dotfiles, if > that makes things better.) I've started keeping my various /etc's in Arch, and it's working out quite well. Arch versions both the symlinks in there and the file permissions, as well as file changes/moves/deletions/etc. Not the file *ownership*, however, so I'll need to be careful if/when I have to restore a /etc. Oh, the other advantage is that I can trivially mirror the archives via sftp, so my backups are handled, too ;-) -- Rob Weir <[EMAIL PROTECTED]> | [EMAIL PROTECTED] | Do I look like I want a CC? Words of the day:mania JPL IDEA Defcon Panama propaganda AGT. AMME Pakistan signature.asc Description: Digital signature
Re: Logbook - RCS
"Gruessle" <[EMAIL PROTECTED]> writes: > I found following in the "Configuration HOWTO" manual. > My question is what software do U use as Logbook and what in RCS? > > 2.2. Start the Logbook! > To keep your installation in shape, it's essential that you know exactly > what happened to your machine, which packages you installed that day, > what you removed or modified, and so on. If I kept a logbook file, I'd do it using vi. Your favorite text editor should be more than adequate for this. (Though my Debian machines tend to be pretty close to stock; the only software on my laptop that's not either from a Debian package or in $HOME is an X server in /usr/local.) > Make a backup copy of the system files you touch. Better still, use RCS; Install the rcs package, then read rcsintro(1). (Again, though, this is something I don't generally do, though I understand why it's Good Practice (TM). I do use version control for my Emacs dotfiles, if that makes things better.) -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ "Theoretical politics is interesting. Politicking should be illegal." -- Abra Mitchell -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Logbook - RCS
I found following in the "Configuration HOWTO" manual. My question is what software do U use as Logbook and what in RCS? 2.2. Start the Logbook! To keep your installation in shape, it's essential that you know exactly what happened to your machine, which packages you installed that day, what you removed or modified, and so on. So, the first thing you'll do before you tamper with your machine is start a ``logbook''. Therein you'll take note of every move you make as root; in my own logbook I also keep a section where I list all modified system files, additional .rpms, and .tar.gz I installed. Optimally, backtracking your moves you should be able to re-obtain a fresh installation. Make a backup copy of the system files you touch. Better still, use RCS; you'll be able to backtrack all changes. Never work as root without logging your moves! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
