similar to: strange email from cron regarding "rear"

There is some interest lately in making a self-contained grub2 boot image - call it pvgrub2, used for booting paravirtual domU in xen where a grub2 config is installed. First attempt------------------ I first tried using the grub2*.src.rpm from the C7 vault. I configured as shown belowhttps://blog.xenproject.org/2015/01/07/using-grub-2-as-a-bootloader-for-xen-pv-guests/ for headers, I used

Hi Debian Grub maintainer, In december, Xen PVH support has been committed in grub master: https://www.mail-archive.com/grub-devel at gnu.org/msg28125.html The last pieces needed in the Linux kernel to boot PVH with grub2 landed in Linux 4.20. I asked our kernel team to carry those patches on top of the Linux 4.19 kernel that is going to ship in Buster, and that wish was granted:

CentOS Errata and Bugfix Advisory 2019:2475 Upstream details at : https://access.redhat.com/errata/RHBA-2019:2475 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: b91b489b63c529df80ddd6358f27c09a9921a016bc160a0601cc3628eaa95342 rear-1.17.2-8.el6_10.i686.rpm x86_64:

Every now and then I get an alert like this one. I have no clue what this "rear" subsystem is, or why madam would be trying to write to its log file. Can anyone enlighten me? thanks in advance! ------------------------- SELinux is preventing /usr/sbin/mdadm from write access on the file /var/log/rear/rear-fcshome.log.lockless. ***** Plugin restorecon (93.9 confidence) suggests

CentOS Errata and Bugfix Advisory 2017:0090 Upstream details at : https://rhn.redhat.com/errata/RHBA-2017-0090.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: ae747914fe9f29dfa149793a47c4eafa900cd1fca69120b32eeba2b8398a1c27 rear-1.17.2-7.el7_3.x86_64.rpm Source:

CentOS Errata and Bugfix Advisory 2017:1316 Upstream details at : https://rhn.redhat.com/errata/RHBA-2017-1316.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 8b3831f700576199b652a5573233754e30a6a161b3de65a7b666cda0d022ee57 rear-1.17.2-9.el7_3.x86_64.rpm Source:

CentOS Errata and Bugfix Advisory 2017:2937 Upstream details at : https://access.redhat.com/errata/RHBA-2017:2937 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 024be5510699ff2696ac06e63ebfe8147bd76abd7235834986752b4d81584873 rear-2.00-3.el7_4.x86_64.rpm Source:

CentOS Errata and Bugfix Advisory 2018:0168 Upstream details at : https://access.redhat.com/errata/RHBA-2018:0168 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 0e16bbcadc843b56a882374fdea3021125e041d6d791be83bf34895fc126385b rear-2.00-4.el7_4.x86_64.rpm Source:

CentOS Errata and Bugfix Advisory 2018:0419 Upstream details at : https://access.redhat.com/errata/RHBA-2018:0419 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 30a83520f2cd54903fbea41f84c74d206aa5ff468d8d09fd85d3c1cb9ae0b402 rear-2.00-5.el7_4.x86_64.rpm Source:

CentOS Errata and Bugfix Advisory 2019:0498 Upstream details at : https://access.redhat.com/errata/RHBA-2019:0498 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 460b753777046b5da6c8839289eb11607f48b9624a78b1a5df33e07ef97b21ad rear-2.4-4.el7_6.x86_64.rpm Source:

CentOS Errata and Bugfix Advisory 2019:1876 Upstream details at : https://access.redhat.com/errata/RHBA-2019:1876 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: e0b00ed45de32d7cec4c24f9b0832206b495b7a132edaf5c9213e08ac437943a rear-2.4-5.el7_6.x86_64.rpm Source:

CentOS Errata and Bugfix Advisory 2019:2603 Upstream details at : https://access.redhat.com/errata/RHBA-2019:2603 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 3d2ffc86df0d4e4645a73e97f6ed4efcdc6d859cfa8a2ac003bf7bcd2fd1fe57 rear-2.4-9.el7_7.x86_64.rpm Source:

CentOS Errata and Bugfix Advisory 2019:3069 Upstream details at : https://access.redhat.com/errata/RHBA-2019:3069 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: c4700ea98f087e2852e04889b61cb7b227769e0e88b84e13f76eb10e376dacab rear-2.4-10.el7_7.x86_64.rpm Source:

Hi all, I've had this error rear it's ugly head again and I'm not exactly sure why. The output in /var/log/message is: crond[14764]: pam_loginuid(crond:session): set_loginuid failed opening loginuid crond[14765]: pam_loginuid(crond:session): set_loginuid failed opening loginuid crond[14811]: pam_loginuid(crond:session): set_loginuid failed opening loginuid

Hey all, I'am able to use pxelinux to successfully boot a particular kernel and image on various IBM PC's ex. 6287-41U and 6591-34U. However, using the same setup (ie. dhcp, tftp, pxelinux.0, pxelinux.cfg, networkcard, bootrom, ram memory) on an IBM 6282-73U my kernel and image decompress fine but I'am getting a... Kernel Panic: VFS: Unable to mount root fs on 01:01 I realize

--- helper/init.c | 4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/helper/init.c b/helper/init.c index 0ca3135..2b5dacf 100644 --- a/helper/init.c +++ b/helper/init.c @@ -163,8 +163,10 @@ main () chdir ("/"); - /* Run /init from ext2 filesystem. */ + mount_proc (); print_uptime (); + + /* Run /init from ext2 filesystem. */ execl

CentOS Errata and Bugfix Advisory 2018:2458 Upstream details at : https://access.redhat.com/errata/RHBA-2018:2458 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 6f703578ac65e4aad512f78328bdf01c0aeb932b299fe92562678d079622fa92 rear-2.00-7.el7_5.x86_64.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ }

I'd agree with you John. I'm trying to get away from Amanda's unpredictability and go back to using scripts to drive dump (for ext2/3/4) and xfsdump (for xfs). Is there any easy way to tell rear to include xfsdump and dump capability? If the commands are there then its trivial to restore data. What I've done in the past is before the nightly backup write a small file to the

On 25/01/15 18:07, Stefan Kania wrote: > Or you try this: > http://relax-and-recover.org/ > With Rear it ist possible to do a P2V migration. Hello Stefan Oh wow, amazing piece of software... the YouTube video sold it to me. REAR could be very useful. List - I'll take all your comments under my wing, and return with a full report. Many thanks. :) Paul Littlefield

Hey everyone, I've added Ogg Opus support to my Adobe Premiere plug-in here: http://github.com/fnordware/AdobeOgg Now I'll add Opus support to me WebM plug-in too. I've got this Opus stuff mostly figured out, but I have a few questions. Here's one: What do the numbers in mapping mean? I see that opus.h refers to the Vorbis channel mapping order, so does mapping in Opus take