Help choosing distro


 
Thread Tools Search this Thread
Operating Systems Linux Help choosing distro
# 1  
Old 05-17-2016
Help choosing distro

Hi,

I just ordered an Skylake NUC and will run Linux on it.

My distro of choice has been Ubuntu but I am fed up with the release cycle and would like more of a rolling release. I would say I am an intermediate level Linux user.

It's going to be a HTPC, I want to have the latest kernels (4.6+). I will run Valve Steam, Plex Media Server (VDENC) and Kodi on there (files are stored on a Solaris NFS server).

What do you all think?

Has 16.04 got a semi-automated way to keep the kernel and packages for Steam, PMS and Kodi on the latest developer versions?

Thanks for looking.

Richard
Login or Register to Ask a Question

Previous Thread | Next Thread

8 More Discussions You Might Find Interesting

1. Linux

Choosing a UNIX

i have a project in numerical calculus in c language what unix i get better for this? (7 Replies)
Discussion started by: gitac
7 Replies

2. Cybersecurity

Choosing the right distro, Locked down from within.

I'm looking to put a box at a client site which will be connected to the client's home router for internet. That box will have remote access software on it and will have untrustworthy contractors logging in and using the browser. So, I'm looking for a distro that would be LOCKED DOWN to the max... (1 Reply)
Discussion started by: artranc3
1 Replies

3. Shell Programming and Scripting

choosing executable depending on distro

Hi, I have an application in 2 different directories, one is for OpenSuSE and the other for CentOS. I wrote a script which chooses the right executable for the distribution. But it does not work. ------------------- #!/bin/bash if then ( DN="/home/apps/applicationXY/Version3.1" )... (2 Replies)
Discussion started by: serverjunge
2 Replies

4. Slackware

Help for choosing Slackware

Dear Friends, If I use Slackware for learning whether it will make any confusion in administering/using Redhat and SuSE since I have checked slackware is more like BSD. Thank you. (4 Replies)
Discussion started by: Tlogine
4 Replies

5. Linux

Choosing the best distro.

Hi all Help me find the best distro for the following configurations: Intel pentium IV 1.6 Ghz 128 MB RAM :( 40 GB Hardisk with one very big partition more than 35 gb n another 2 gb partition. windows xp is already installed but has enough free space (26gb). Which linux will be... (0 Replies)
Discussion started by: bbala
0 Replies

6. UNIX for Dummies Questions & Answers

I need help choosing a linux.

There are soo many flavors of linux and i just cant choose/find the right linux for me... I am hopeing for a linux that is a Workhorse Can fit of a seires (or 1) disk(s) Lots of features (admin/mod features) A learning mode or a detailed tutorial Can work side by side with windows... (12 Replies)
Discussion started by: lithuaniaakid
12 Replies

7. UNIX for Dummies Questions & Answers

Choosing a version

I know that the rules say no school questions but I am in advanced topics and am going to go to college for programming and I want to find a easy first OS to start me out, please help, thanks (3 Replies)
Discussion started by: KoKo
3 Replies

8. Programming

Choosing Java or C++

Listen, if you know a bit of programming in C and need to program unix-type operating systems the next transitive stage is for sure C++. However, have in mind that Java is like learning C but 99% object-oriented(o.o.) and with no pointers or memory-management tricks. It would be good for you to see... (5 Replies)
Discussion started by: SolidSnake
5 Replies
Login or Register to Ask a Question
adt-testreport-runloop(1)				     Linux Programmer's Manual					 adt-testreport-runloop(1)

NAME
adt-testreport-runloop - repeatedly choose and test packages SYNOPSYS
adt-testreport-runloop [[!@]variable=value|[!@]settings-file]... DESCRIPTION
adt-testreport-runloop is a rather ad-hoc script which repeatedly invokes adt-testreport-onepackage; it is designed to be invoked from cron. WARNING - it is essential to reconfigure this program before use, as the supplied examples will send emails to people who will become very upset with you! CONFIGURATION
Command-line arguments containing = are interpreted with eval; other arguments are sourced using ., in each case interpreted as bash script. Supplied arguments are both executed by a-t-r and passed through to the invocation of a-t-o. You may prefix an argument with @ to indicate that it is for a-t-onepackage only, or with ! to indicate that it is for a-t-runloop only. Thus the set of variables which can be set is the union of those for a-t-runloop itself and those for a-t-onepackage. See the a-t-o man- page for such information about its configuration as is available. Configuration fragment authors should bear in mind that both programs use set -e. It is quite permissible to set PATH and other needed environmnet variables in the configuration file. The following variables may be set: distro distribution (`suite') to be tested. There is no default. This variable is used only for the default values of testbed_check_path and test_classes. However, it is probably a convenient way of specifying the intended effect particularly as attempting to do cross-distribution testing in a single installation does not work properly right now (see a-t-o's BUGS). max_test_count the maximum number of times to invoke a-t-o. This counts both passed and failed tests, but it doesn't count possible runs which were suppressed. Default: 10. go_anway Run even though the file go does not exist. See SUPPRESSION, below. Default: false. architecture Used in combination with distro when calculating the right default for test_classes. The default is the result from dpkg --print- architecture. testbed_check_path If the file named by this variable doesn't exist, a-t-r will exit. This avoids it spinning and reporting many immediate failures due to a broken testbed. The default is /var/lib/autopkgtest/xenlvm/adt_distro/good if distro is set, which assumes that the Xen- based virtualisation system is being used; if distro is not set then default is /dev/null which nullifies this feature. test_classes Specifies the set of test classes to try, with the details of each test class separated by a colon : from the next. a-t-r will run a-t-o once for each listed test class and then return to the beginning of the list. Tests in each class are thus selected approximately equally often. (If max_test_count is not a multiple of the number of actual test classes then early classes are used slightly more.) Each test class consists of a set of suppression checks, a comma ,, and some configuration arguments for a-t-o. The suppression checks are whitespace-separated words; see SUPPRESSION. The configuration arguments are likewise whitespace-separated. There is no provision for passing configuration arguments containing spaces to a-t-o. a-t-o arguments in test classes override other configura- tion settings. The default is source distro, target=source : binary distro, target=binary-architecture which tests binary packages and source pack- ages from the same distribution in alternation SUPPRESSION
a-t-r is designed to be enabled and disabled by sentinel files. Firstly, if the file go does not exist in its working directory, it will stop at the first sensible opportunity. (See also the go_anyway configuration variable.) Secondly, test classes may specify suppression checks. For each such check classcheck, a-t-r will test for the existence of stop-class- check in its current directory. If that file exists, it will suppress that class of test. Do not suppress all of the tests without remov- ing go. FILES
/var/lib/autopkgtest/xenlvm/adt_distro/good default sentinel file for testbed_check_path. ./go Sentinel file indicating that operation should be enabled. ./stop-classcheck Sentinel file indicating that test classes mentioning classcheck should be suppressed. adt-testreport-runloop does not use any other files directly, but it will probably need a configuration file as an argument, and it will invoke adt-testreport-onepackage which uses many files in the current directory and which invokes an autopkgtest virtualisation server. BUGS AND WARNINGS
It is essential not to use the example configuration! This configuration is likely to send inappropriate emails! There is no locking. Whatever invokes a-t-r should take out a lock of some kind. See the example cronjobs provided in hosts/*/cronjob in the source package. If all of the test classes are suppressed, a-t-r will spin in a tight loop looking for something to do. The testbed_check_path feature is rather ad-hoc. It would be better to query the virtualisation server to be used directly and then sup- press the test class if relevant. (But the infinite loop bug would need to be fixed too.) The design precludes detecting attempts to set incorrectly named configuration options. AUTHORS AND COPYRIGHT
This manpage is part of autopkgtest, a tool for testing Debian binary packages. autopkgtest is Copyright (C) 2006-2007 Canonical Ltd and others. See /usr/share/doc/autopkgtest/CREDITS for the list of contributors and full copying conditions. autopkgtest 2007 adt-testreport-runloop(1)