search for: distroed

Add a --with-distro=ID argument for configure, so it is possible to manually specify the distro to use for the packages (in case os-release does not provide ID=.., or the ID is not recognized yet). In the case when --with-distro is not set, keep doing the autodetection, but using os-release only, i.e. dropping the checks for all the other -release files -- since there is --with-distro, older

Use /etc/os-release as first option, translating the distro name to the current identifier used. The other options (the release files) are left as following checks, avoiding them if any matches. --- m4/guestfs_appliance.m4 | 25 +++++++++++++++---------- 1 file changed, 15 insertions(+), 10 deletions(-) diff --git a/m4/guestfs_appliance.m4 b/m4/guestfs_appliance.m4 index 8cff51e..b48da74 100644

All SUSE distros have a ID_LIKE=suse, including the fake one used for building that has a ID=Dummy value. Without reading ID_LIKE on SUSE distros, the generated appliance packagelist is not correct. This fix reads ID_LIKE as a fallback if ID contains nothing. --- m4/guestfs_appliance.m4 | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/m4/guestfs_appliance.m4

For those who are using SuSE: At last they've managed to create ready-to-run packages for openSUSE_11.1. They are there since a couple of hours... (For other versions it was allready available for some time on the OBS) /srv/distro/repo/network:/telephony:/asterisk/openSUSE_11.1/x86_64/asterisk16-devel-1.6.0.6-82.2.x86_64.rpm

On Fri, 2017-09-01 at 10:59 +0100, Daniel P. Berrange wrote: > On Fri, Sep 01, 2017 at 11:25:17AM +0200, Cédric Bosdonnat wrote: > > All SUSE distros have a ID_LIKE=suse, including the fake one used > > for building that has a ID=Dummy value. Without reading ID_LIKE > > on SUSE distros, the generated appliance packagelist is not correct. > > > > This fix reads

Le 2 oct. 2017 à 18:37, Rui Ueyama <ruiu at google.com<mailto:ruiu at google.com>> a écrit : Changing default to "both" is probably fine, but what does that change actually mean in practice? I believe clang already passes --hash-style=both to the linker by default. Not exactly. The current Linux driver (I haven't checked other ELF-based systems) reads this

I was slightly too quick off the marks with the first patch. This updated patch modifies all of virt-inspector's output types to take account of distrofamily.

Change distro in the output formally known as virt-inspector to reflect the actual distro. Possible values are now: fedora, rhel, centos, scientific, debian. Add new distrofamily entry which is one of: redhat, debian. Currently all distros except 'debian' are in the redhat family. This allows you to, for example, select a RHEL/CentOS/Scientific Linux specific kernel for installation

Few improvements to the results of the inspection on some distros. Pino Toscano (5): inspect: factorize list of rolling distros inspect: detect Gentoo from os-release inspect: fully detect Arch Linux from os-release inspect: return osinfo short IDs for rolling distros inspect: correct osinfo ID for ALT Linux >= 8 daemon/inspect_fs_unix.ml | 15 +++++++++------

On Thu, 2017-07-20 at 17:01 +0200, Pino Toscano wrote: > On Thursday, 20 July 2017 16:21:40 CEST Cédric Bosdonnat wrote: > > In the appliance used to build the packages for openSUSE, os-release > > is super minimal and only had ID_LIKE=suse. The code setting the > > DISTRO variable only searches for ID variable so far, resulting in > > invalid packagelist on openSUSE.

Has anybody tried to install * in any of these minimalist linux distros like tinylinux? Which linux distro would you use to run * in old P2, P3 boxes? Regards, Victor Perez vperez@mssco.com (469) 221-4189

On Fri, Sep 01, 2017 at 11:25:17AM +0200, Cédric Bosdonnat wrote: > All SUSE distros have a ID_LIKE=suse, including the fake one used > for building that has a ID=Dummy value. Without reading ID_LIKE > on SUSE distros, the generated appliance packagelist is not correct. > > This fix reads ID_LIKE as a fallback if ID contains nothing. > --- > m4/guestfs_appliance.m4 | 10

Support the ID found in openSUSE Leap 15.0 in addition to the other SUSE-related IDs. While there is already --with-distro=ID to force the ID without using os-release, this makes it possible to build OOTB. --- m4/guestfs-appliance.m4 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/m4/guestfs-appliance.m4 b/m4/guestfs-appliance.m4 index 5c2bc3e8d..bcba4c1a1 100644 ---

It seems that all the newer versions of openSUSE have an 'opensuse-' prefix in their distro ID; hence, check for that prefix at once, keeping compatibility for the old "opensuse" ID. Followup of commit a4e53bcbc52594f8863e7866448640f7ac8ab0f9. --- m4/guestfs-appliance.m4 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/m4/guestfs-appliance.m4

Try to guess the possible osinfo-db short ID for the specified OS. Related to: https://bugzilla.redhat.com/show_bug.cgi?id=1544842 --- generator/actions_inspection.ml | 14 ++++++++ lib/Makefile.am | 1 + lib/inspect-osinfo.c | 75 +++++++++++++++++++++++++++++++++++++++++ 3 files changed, 90 insertions(+) create mode 100644 lib/inspect-osinfo.c diff --git

This adds SUSE and openSUSE capabilities to the virt-v2v.db. It also adds a SUSE custom package example, and br0 -> default network map example. --- v2v/virt-v2v.conf | 8 ++++++ v2v/virt-v2v.db | 73 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 81 insertions(+) diff --git a/v2v/virt-v2v.conf b/v2v/virt-v2v.conf index fadce17..6574c0a 100644 ---

Does there seem to be a popular Linux distro folks use specifically for Asterisk? I'd like to move off of FreeBSD but I'm not too familiar with Linux distros. In particular, I'm looking for a free, stable, well supported distro that has a friendly community. Any advice appreciated. Sorry for asking a question that I'm sure has been asked thousands of times. Best regards,

Greetings. If I do this: rsync --hard-links one.server.com::"module/somedir/images/redhat/3.0WS/en/os/i386 module/someotherdir/1.0/images/redhat/3.0WS/en/os/i386" /export/distros I get: /export/distros/i386/... and a conflict between the two sources. I want for destination: /export/distros/images/redhat/3.0WS/en/os/i386 /export/distros/1.0/images/redhat/3.0WS/en/os/i386 In other

I'm sorry if this is not the correct place for suggestions, but I didn't see any other place. I'm sure everyone has realized how massive the distro list is when submitting test data. My proposed solution is to add two drop down menus, one will contain disto names e.g., "Ubuntu" and "Fedora", the second box will contain release/version e.g., "10.04"

Am a newbee to Linux and am trying to evaluate various distros to see how they fit my needs. For this purpose I now have six trial Linux partitions on the same machine. My other criterions to replace XP as my main system have been passed by all the distros, but remains the last one: to be able to handle Lotus wk4-files. That is where I have my history. First tried installing Lotus 123 from