2016-07-27 11:00:02 -0500 commented answer What does not need to be specified in "BuildRequires" & "Requires" sections of a RPM spec file I agree that I can always test my spec file with mock. But that is a bit of a trial and error way of going about knowing what I should include in BuildRequires & Requires. It also would not tell me if I have included a package in either listing which does not need to be there because it is included by default. I seem to remember seeing an official list of packages which do not need to be specified because they are so common. I just can not seem to find it anymore. I also understand that this may well be a moving target, depending on what is included in the minimal mock environment. 2016-07-27 09:50:44 -0500 received badge ● Student (source) 2016-07-27 09:21:37 -0500 asked a question What does not need to be specified in "BuildRequires" & "Requires" sections of a RPM spec file I was writing an RPM spec file and I remembered that there was a list of packages which were "included by default" in the BuildRequires & Requires sections. I have had a look through various bits of documentation and I can not seem to find any mention of such a list anywhere. Can somebody tell me what is included in such a list, or where it is documented? I am guessing that it would include those packages listed by: dnf group info 'Core'  What is the current best practice? Should I include everything that is required including things like bash, coreutils, curl and ncurses? 2016-07-23 19:04:21 -0500 received badge ● Good Answer (source) 2016-07-23 19:04:21 -0500 received badge ● Enlightened (source) 2016-07-14 06:25:51 -0500 received badge ● Supporter (source) 2016-06-29 17:44:31 -0500 received badge ● Nice Answer (source) 2016-06-29 15:24:39 -0500 received badge ● Teacher (source) 2016-06-29 09:42:12 -0500 commented answer Best Fedora based backup server? You're welcome. Judging by the Ask fedora guidelines and [Sticky] Why so many unsolved questions?, you should mark the answer as correct if it was helpful to you. If and when other answers come in you can up/down vote them according to their level of helpfulness! 2016-06-28 11:45:52 -0500 answered a question Best Fedora based backup server? I don't know that I can answer all of your questions but I'm going to try and make a start which others can hopefully build on… Backup can get a bit complicated. The best solution for you depends on your particular circumstances. People have written whole books on the subject, here's one that I found very useful: Backup & Recovery by W. Curtis Preston. However, the most important thing to remember is that pretty much any kind of backup is better than no backup at all! So don't obsess over planning the perfect backup solution without getting round to actually doing something. Better to do something really quick & simple right away — then look to improve on it. Here's what I would recommend as a starting point given my understanding of your situation. Yes, use your external USB 3.0 drive for backup. While there is nothing wrong with having a backup on your internal drives as one of your layers of backup, you definitley would not want it to be your only backup. Your internal drives are always connected to your computer and so would be an example of On-line storage. In contrast your external USB drive could be an example of Off-line storage i.e. disconnected from your computer most of the time and only connected when you are performing backups. While less convienient, Off-line storage is less vunerable to things like accidental deletion & malware. Create an off-site, off-line backup: Label your external USB drive something like "My_Backup_A" and buy a second extetnal drive and label it something like "My_Backup_B". Set these drives up the same and keep one of them at home and take the other off-site e.g. friends or parents house, a draw at work, etc. Swap them over regularly, so you always have a reasonably fresh backup off-site. Encryption can be taken care of by creating one or more LUKS encrypted partitions on your external drives. You can do this easily with the gnome-disks graphical utility in Fedora. In order to support the backup of windows machines you could set up your backup server as a iSCSI SAN target or SAMBA server. Each windows machine can then mount a partition or directory on your backup server and use it as the storage location for its own native windows Backup and Restore client. This method would work for Macs too, allowing them to use their native "Time Machine" backup software. If you want to be space efficient then it sounds like you want to use a backup utility which is capable of file-based, incremental backups. Both amanda and deja-dup do this, as well as my personal favourite rdiff-backup. I haven't used amanda, but my understanding is that it is very mature and powerful — capable of backing up entire networks. It uses standard tools like tar underneath. It has a native windows client so it could handle your windows machines without needing to resort to the SAN/SAMBA method I mentioned above ...