search for: fedoras

This is just a mechanincal change, so that the public documentation[*] refers to the latest release Fedora versions, instead of the EOLed versions. While at it, also update the `virt-cutomize` Makefile.am [*] http://libguestfs.org/virt-builder.1.html Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com> --- Maybe I missed more places. (Me wonders if upstream libguestfs uses a more

Introduce a mandatory arch= key in all the entries of index files, to identify which architecture is each. Adapt the long and JSON list outputs to print also this new field. This introduces an incompatibility with index files created with virt-builder < 1.26, as they will be rejected until entries will have the arch= key added (which is ignored by older virt-builder, so adding it will not

- convert the Fedora 20 examples to Fedora 25 - convert the yum examples to dnf - convert the Debian 7 examples to Debian 8 - mention that --core updates all the installed packages, not "core" ones - convert i386 to i686 for the Fedora 32bit examples - mention that autogenerated root passwords are printed on stdout - mention --get-kernel is deprecated in favour of virt-get-kernel -

https://bugzilla.samba.org/show_bug.cgi?id=4764 Summary: Wrong include/exclude descriptions Product: rsync Version: 2.6.8 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: tps@vr-web.de QAContact:

Hey there everyone! Trying to use virt-builder to download & resize the standard fedora-23 image from libguestfs.org ... ??[rsawhill at jiop 11:50 ~] {0} $ rpm -q libguestfs-tools > libguestfs-tools-1.32.7-1.fc23.noarch > ??[rsawhill at jiop 11:50 ~] {0} $ virt-builder --list | grep fedora-23 > fedora-23 x86_64 Fedora? 23 Server > fedora-23 i686

Create a new directory (builder/template). Integrate all of the scripts into a single program, so that templates are generated more consistently. This also changes how the index file is generated. The script now generates the index file fragment and saves it under version control, and then generates the final index file by concatenating these. (Previously the index was written by hand which was

On 07/28/2017 04:22 PM, Matthew Miller wrote: > On Fri, Jul 28, 2017 at 10:11:53PM +0100, Phil Perry wrote: >> The issue I have here is even if I did file a bug, and the issue >> were fixed, no sooner than it's fixed fedora updates to the next >> version and introduces a whole bunch of new bugs, and so the cycle >> continues. I played that game for a while with

Hi All, The subject says it all. I'm asking because I've found Fedora 9 to be buggy as hell - it is one of the worst Fedora releases I've ever used (and I've been using it since Fedora Core 1). I'm putting up with it for my work laptop, but it's not fun. :( My main home machine is still on Fedora Core 6 and will stay there until CentOS 6 comes out. I don't want to

Hi all- Over the past week or two, I've been trying out asterisk under Fedora 1 Linux (RedHat). In my setup (single and dual Xeon motherboards), I have so far had a very good experience in terms of performance. In doing E1 load testing, I've found that Fedora handles heavy load much better than RedHat9, probably because of its better use of the multi-threading capabilities of the Xeon.

I''m using Fedora 7 with xen''s virt-manager. I''d manage to install a full virtualized WinXp domU after changing the settings in .xml files. Now I would like to try to install the paravirtualize fedora 7 using virt-manager I''m using this install media address > http://download.fedora.redhat.com/pub/fedora/linux/core/6/i386/os/ And the virt-manager console

If the guest uses SELinux, then make sure to run a relabel (or at least schedule one) after the image build: this way the template is relabelled, or at least it will do that at the next boot, without the need for the user to ask for a relabel. This just covers the case of building a new image with no additional operations on it though. --- builder/website/centos.sh | 2 ++

Not to be impatient, but something seems odd. The CRAN repository has nothing for Fedora 9. The RPM of R that comes with Fedora 9 is version 2.6.2. Someone connected with the Fedora project must have built that. R 2.7 is not in the "updates" for Fedora 9, so nobody connected with Fedora has done that. However - and this is the odd thing - the "development" repository of

I am currently (still) running Fedora 17 --- having not managed to screw my courage to the sticking place and upgrade. Even though we are now up to Fedora 20, I think. The traffic on the Fedora mailing list on the upgrading issue is a bit terrifying. I would just like to confirm that: It is ***NOT*** possible to download a binary of R for Fedora 17. Is this correct? My efforts to

Hi I had installed Xen-3.0.4 in Scientific linux 4 (kernel version 2.6.16.33) by following the instructions given in following link project-xen.web.cern.ch/project-xen/xen/howto_slcXen.html I ve created the guest Domain with fedora image of size 2.2GB , disk space as 10GB and the domain started successfully . when i logged into the xm console and checked the disk space its showing only 2.2GB ..

I just landed in Paris, and haven't read backwards in this thread, but I've done 3.2.0 builds for all current Fedora releases, they're all in updates-testing (I think the Fedora 22 builds are in updates stable now). The thing that changed is that R doesn't bundle a number of libraries like it used to. This doesn't affect the official Fedora R package, since we never used the

Is there somewhere a succinct guide to just how much extra crud we need to install on RHEL to make use of EPEL packages? [root at troll-1 noarch]# rpm -ivh R2spec-4.1.0-1.el6.noarch.rpm error: Failed dependencies: fedora-packager is needed by R2spec-4.1.0-1.el6.noarch [root at troll-1 noarch]# wget http://dl.fedoraproject.org/pub/epel/6/x86_64/fedora-packager-0.5.9.4-1.el6.noarch.rpm

On Tue, 27 Oct 2020, Stephen John Smoogen wrote: > On Tue, 27 Oct 2020 at 13:20, Michael Hennebry < > hennebry at web.cs.ndsu.nodak.edu> wrote: > >> I've been trying to move from Centos 7 to fedora. >> My monitor is 1440x900, but fedora only believes it's 640x480. > 1. What kind of video card is this? > 2.How is the video connected to the monitor?

This change involves rewriting make-fedora-img.sh in perl. This allows the flexibility to write mdadm.conf containing whichever uuids where randomly generated when the md devices were created. --- .gitignore | 2 + images/Makefile.am | 18 +++- images/guest-aux/make-fedora-img.pl | 194 +++++++++++++++++++++++++++++++++++

I was able to get login prompt ( commit 7c62209cde5b13b81685e79b2f9e3757e293aef1 ) first time via serial console:- title Xen 3.4.1  Fedora 12 Serial (2.6.31-rc8 ) (/dev/sdb1)   root (hd1,0)   kernel /xen-3.4.1.gz dom0_mem=1024M loglvl=all guest_loglvl=all com1=19200,8n1 console=com1   module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=hvc0 earlyprintk=xen   module

On 07/30/2017 09:41 AM, Walter H. wrote: > On 30.07.2017 14:29, Johnny Hughes wrote: >> I personally have a Fedora machine that I keep updated and do some work >> on all the time learning/testing. I just seamlessly upgraded it from >> Fedora 25 to Fedora 26 using a couple of dnf commands .. awesome >> experience actually. > because of this feature to upgrade from one