Author: "Kenneth L. Owen" <tx836519 AT bellsouth DOT net>
Date: Fri, 10 Oct 2008 23:05:00 -0400
Hello all, For a number of years I have run a small home network of windows machines. I recently decided to move my computing to Linux. I now have two machines running Fedora 8. The first machine ass
Author: "Michael Mansour" <mic AT npgx.com DOT au>
Date: Sat, 11 Oct 2008 14:22:57 +1100
Hi, Why choose Fedora 8 and not Fedora 9? Fedora 8 has an End of Life next month: http://poelstra.fedorapeople.org/schedules/f-10/f-10-all-tasks.html No more support for it after that. Regards, Micha
Author: "Kenneth L. Owen" <tx836519 AT bellsouth DOT net>
Date: Fri, 10 Oct 2008 23:56:03 -0400
When I started this transition, Fedora 8 was issued and stable. When I am more stable with Linux, I'll be willing to be more adventurous. -- ken Hi, Why choose Fedora 8 and not Fedora 9? Fedora 8 has
Author: "Nils Breunese (Lemonbit)" <nils AT lemonbit DOT com>
Date: Sat, 11 Oct 2008 13:05:41 +0200
Actually, using Fedora for servers *is* being adventurous, because it has such a short lifecycle. If want a stable server and don't like having to upgrade the OS every couple of months I'd go with Ce
Author: "Nils Breunese (Lemonbit)" <nils AT lemonbit DOT com>
Date: Sat, 11 Oct 2008 13:10:59 +0200
If you're using Linux I actually advise *against* using smb as your transfer method. Use rsync over SSH or rsyncd. From the docs [0]: "The preferred setup for linux/unix clients is to set $Conf{XferM
Author: Rob Owens <rob.owens AT biochemfluidics DOT com>
Date: Sat, 11 Oct 2008 16:17:01 -0400
I agree with Nils that CentOS would be a better choice for you. If you like Fedora, you'll find that CentOS is nearly identical. If you're looking to try new things (sounds like you aren't, though),
Definitely go with rsync for backups. This is a better choice. Also, fedora 8 is a perfectly fine OS but I would suggest using either ubuntu 8.04 or centos5.2. Both are modern, stable distros tha tar
Author: "Kenneth L. Owen" <tx836519 AT bellsouth DOT net>
Date: Sun, 12 Oct 2008 18:33:36 -0400
Thanks to all for responding. So far, I’ve learned several things: Fedora distributions are short lived. Rsync is the preferred transport. Well, I kind of learned something. I had already figur
Author: Adam Goryachev <mailinglists AT websitemanagers.com DOT au>
Date: Mon, 13 Oct 2008 10:31:55 +1100
You should login as root, and then use: su - backuppc This will "switch" to the backuppc user even if the user doesn't have any password set. If that doesn't work try this: grep backuppc /etc/passwd
Author: "Kenneth L. Owen" <tx836519 AT bellsouth DOT net>
Date: Sun, 12 Oct 2008 21:36:38 -0400
Well, I have news good and bad. First, your instructions were very clear, precise and easy to follow. BUT, it didn't work. [ken@Archiver ~]$ su - Password: [root@Archiver ~]# grep backuppc /etc/passw
Author: "Stephen Vaughan" <stephenvaughan AT gmail DOT com>
Date: Mon, 13 Oct 2008 12:55:35 +1100
Why choose Fedora 8 and not Fedora 9? Fedora 8 has an End of Life next month: http://poelstra.fedorapeople.org/schedules/f-10/f-10-all-tasks.html No more support for it after that. Regards, Michael.
Author: Adam Goryachev <mailinglists AT websitemanagers.com DOT au>
Date: Mon, 13 Oct 2008 14:18:24 +1100
Actually, yes, this is the default prompt, which is usually modified in your ~/.bashrc or ~/.bash_profile files, but the backuppc user doesn't have/use these files.... After you su - backuppc do: mkd
Author: "Nils Breunese (Lemonbit)" <nils AT lemonbit DOT com>
Date: Mon, 13 Oct 2008 10:34:03 +0200
Correct. I believe that is that case, yes. Or 'whoami'. Also: you didn't really need to change the login shell for the backuppc user. You could have used 'su -s /bin/bash - backuppc' to specify bash
Author: "Nils Breunese (Lemonbit)" <nils AT lemonbit DOT com>
Date: Mon, 13 Oct 2008 10:39:14 +0200
If you're used to the Fedora way (a.k.a. Red Hat way) of things and want a distribution with a long lifecycle then I'd say CentOS (or RHEL if you need paid support) is a better choice than Debian. De
Author: "Michael Mansour" <mic AT npgx.com DOT au>
Date: Mon, 13 Oct 2008 20:03:11 +1100
Hi, So are so many other Linux distributions... one of the best things about Linux is the range available. I personally use Scientific Linux on all my servers (and clients servers) and have been for
Author: Rob Owens <rob.owens AT biochemfluidics DOT com>
Date: Mon, 13 Oct 2008 07:50:43 -0400
Here's some background on how ssh keys work. There are 2 basic types of keys: keys which identify a server, and keys which are used for user authentication. Note that they are not really different in
Author: royden yates <royden.yates AT gmail DOT com>
Date: Mon, 13 Oct 2008 20:02:33 +0200
As you have been pointed to rsync in a windows context, please remember that rsync over ssh on a Windows client is likely to freeze mysteriously (search this list as well as the rsync and cygwin foru
Author: "Kenneth L. Owen" <tx836519 AT bellsouth DOT net>
Date: Mon, 13 Oct 2008 14:11:34 -0400
With the feedback and help with command line, I was able to create the rsa keys (Thanks Nils). When I finished creating the keys, I ran the test given in the instructions: [root@Archiver .ssh]# su -s
Author: "Kenneth L. Owen" <tx836519 AT bellsouth DOT net>
Date: Mon, 13 Oct 2008 14:22:09 -0400
Maybe I did not make the path clear. I am moving away from Windows. I already have a system to maintain the Windows system and am trying to set up a means to have disaster recovery as I transition to
Author: Adam Goryachev <mailinglists AT websitemanagers.com DOT au>
Date: Tue, 14 Oct 2008 09:55:29 +1100
Backuppc will connect using the *name* rather than the IP address. You should test like this: su -s /bin/bash - backuppc ssh -l root <hostname> whoami where hostname is what you have in your backuppc