similar to: synthesizing yum transactions

I've been making my own custom RHEL / CentOS boot CDs for years, and all of the instructions for such work call out to take a distro's CD, and copy key files from it. Among those files are those that I think are associated with the the SYSLINUX/ISOLINUX project; e.g.: http://mirror.centos.org/centos/6/os/x86_64/images/ http://mirror.centos.org/centos/6/os/x86_64/isolinux/ Two

On Tue, Oct 13, 2015 at 03:18:16PM -0500, Johnny Hughes wrote: > On 10/13/2015 01:40 PM, Brian Reichert wrote: > > On Tue, Oct 13, 2015 at 12:51:07PM -0400, Brian Reichert wrote: > >> On Tue, Oct 13, 2015 at 11:42:08AM -0500, Johnny Hughes wrote: > >>> The info you are looking at there is for CentOS-7 .. the syslinux for > >>> CentOS-6 is here: >

On Tue, Oct 13, 2015 at 12:03:00PM -0400, Jonathan Billings wrote: > On Tue, Oct 13, 2015 at 11:38:06AM -0400, Brian Reichert wrote: > > Does anyone have any insight on these topics, or, at the very least, > > a better forum to pursue them? > > The patches used to build the latest syslinux package for CentOS7 are > here: > >

On Tue, Oct 13, 2015 at 11:42:08AM -0500, Johnny Hughes wrote: > The info you are looking at there is for CentOS-7 .. the syslinux for > CentOS-6 is here: > > http://vault.centos.org/6.7/os/Source/SPackages/syslinux-4.04-3.el6.src.rpm > > The CentOS team did not modify that source code, we just built it as is. > > That source code produces the syslinux binary used by

First off, I have to admit that I'm uncertain if this is the appropriate forum; I'd be happy for suggestions about where else to look. I'm doing this work on a stock install of CentOS-7-x86_64-Minimal-1810.iso, with no updates. I'm trying to create an RPM database from a custom set of RPMs. One RPM ('openldap-ltb' from the LDAP Tool Box project (ltb-project.org) has a

On 10/13/2015 01:40 PM, Brian Reichert wrote: > On Tue, Oct 13, 2015 at 12:51:07PM -0400, Brian Reichert wrote: >> On Tue, Oct 13, 2015 at 11:42:08AM -0500, Johnny Hughes wrote: >>> The info you are looking at there is for CentOS-7 .. the syslinux for >>> CentOS-6 is here: >>> >>>

Back in February, I opened two bugs, that seem to have had no activity: https://bugs.centos.org/view.php?id=15850 https://bugs.centos.org/view.php?id=15846 Is there some step I skipped when creating these? Or am I being impatient? :) -- Brian Reichert <reichert at numachi.com> BSD admin/developer at large

All temporary files are kept in a single directory. At the end of the autotests that one directory is deleted. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- autotest.sh | 20 +++++++++++--------- 1 files changed, 11 insertions(+), 9 deletions(-) diff --git a/autotest.sh b/autotest.sh index c9f8a2d..d658cf3 100755 --- a/autotest.sh +++ b/autotest.sh @@ -40,6 +40,7 @@ # an

Hi all. I have currently a server: cat /etc/redhat-release CentOS release 5.7 (Final) uname -a Linux host.domain.com 2.6.18-274.18.1.el5 #1 SMP Thu Feb 9 12:45:44 EST 2012 x86_64 x86_64 x86_64 GNU/Linux I have there a filesystem mounted: /dev/vg0/paczki /home/paczki-workdir ext4 defaults,noatime 0 0 on which df gives strange output: LANG=C df -h

Autobuild has to be updated to call make in the recipe directory and move the resulting iso to the main build directory. Importing the existing autotest.sh script from ovirt-node-image Signed-off-by: Mike Burns <mburns at redhat.com> --- autobuild.sh | 7 + autotest.sh | 764 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 771 insertions(+), 0 deletions(-)

When the user runs o-c-networking then it ensures that all features of networking that we configure are reset and only those settings touched are applied. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- scripts/ovirt-config-networking | 46 +++++++++++++++++++++++++------------- 1 files changed, 30 insertions(+), 16 deletions(-) diff --git a/scripts/ovirt-config-networking

Hello. I once read somewhere that it's possible to limit SSH pubkeys to 'tunnel-only'. I can't seem to find any information about this in any of the usual places. I'm going to be deploying a few servers in a couple of days and I'd like them to log to a central server over an SSH tunnel (using syslog-ng) however I'd like to prevent actual logins (hence

I'm forwarding this to security@, as I'm getting no replies on ipfw@. Hope it's relevant enough for you :( ---Original Message----- From: owner-freebsd-ipfw@freebsd.org [mailto:owner-freebsd-ipfw@freebsd.org] On Behalf Of Erik Paulsen Skålerud Sent: Wednesday, May 28, 2003 1:02 AM To: ipfw@freebsd.org Subject: Question about logging. Sorry for asking this, It's probably been

I'm almost finished with the BuildBot validation config, but I'm having trouble convincing it to compiler llvm-gcc-4.2. Here's the relevant portion of the config: f.addStep(SVN(workdir="llvm-gcc-4.2/src", mode='clobber', baseURL='http://llvm.org/svn/llvm-project/llvm-gcc-4.2/', defaultBranch='trunk')) checking="" if optimized ==

On Tue, Oct 13, 2015 at 12:51:07PM -0400, Brian Reichert wrote: > On Tue, Oct 13, 2015 at 11:42:08AM -0500, Johnny Hughes wrote: > > The info you are looking at there is for CentOS-7 .. the syslinux for > > CentOS-6 is here: > > > > http://vault.centos.org/6.7/os/Source/SPackages/syslinux-4.04-3.el6.src.rpm Related question; where do these files come from?

All, I currently have 2 bricks running Gluster 3.10.1. This is a Centos installation. On Friday last week, I enabled the trashcan feature on one of my volumes: gluster volume set date01 features.trash on I also limited the max file size to 500MB: gluster volume set data01 features.trash-max-filesize 500MB 3 hours after that I enabled this, this specific gluster volume went down: [2017-06-16

On Tue, 2017-06-20 at 08:52 -0400, Ludwig Gamache wrote: > All, > > I currently have 2 bricks running Gluster 3.10.1. This is a Centos installation. On Friday last > week, I enabled the trashcan feature on one of my volumes: > gluster volume set date01 features.trash on I think you misspelled the volume name. Is it data01 or date01? > I also limited the max file size to 500MB:

I have asked this before in -questions but due to a odd security requirement, I need the option to auto lock a normal user's account (root and those in the wheel group must be excluded) after let say, 3, login failures. I know this can cause a DoS issue but I HAVE to have the option of doing it in FreeBSD. Any info is appreciated Thanks. Mike C carlson39@llnl.gov

Yes it is. Example from my program: workdir <- "S:\\Stat\\C03202\\R-output\\" ... sink(file=paste(workdir, assayname, "-1.txt", sep="")) ... win.metafile(filename = paste(workdir, assayname, "-2%02d.wmf", sep="")) You get the idea! Kind regards, Jesper Frickmann Statistician, Quality Control Novozymes North America Inc. Tel. +1 919 494

Instead, the script lets libvirt determine which emulator to use. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- autotest.sh | 6 ++---- 1 files changed, 2 insertions(+), 4 deletions(-) diff --git a/autotest.sh b/autotest.sh index c9f8a2d..96a15b5 100755 --- a/autotest.sh +++ b/autotest.sh @@ -270,7 +270,6 @@ define_node () { # flexible options # define defaults,