On Feb 25, 2015 10:00 PM, "Peter" wrote:
>
> I haven't tried this, but see if it works:
> yum shell
> remove *
> install @minimal
> run
>
>
I've not tried this to see the effect but don't forget in el6 there is the
yum history database...
yum history list will show all yum operations that have h
On Wed, 25 Feb 2015 17:30:30 -0600, Ashley M. Kirchner
wrote:
On Feb 25, 2015 4:19 PM, "Jason Warr" wrote:
It will if you try to configure the now non-existent interface.
That's what I figured, so I can remove it from the kickstart file, no
problem. The question then becomes, if kick
On 02/25/2015 07:48 AM, Leon Fauster wrote:
Am 22.02.2015 um 16:12 schrieb Stephen Harris :
Is the device NFS exported? I've seem that prevent umounting even though
nothing shows up in the process list.
Its a local "virtual" device (raid controller exports it as one device).
I believe that
On Feb 25, 2015 4:19 PM, "Jason Warr" wrote:
> It will if you try to configure the now non-existent interface.
That's what I figured, so I can remove it from the kickstart file, no
problem. The question then becomes, if kickstart doesn't configure it, what
happens when the system reboots after i
On Wed, 25 Feb 2015 17:11:02 -0600, Ashley M. Kirchner
wrote:
Add "rdblacklist=MODULE_NAME" to your append line in pxelinux.conf file.
Trying that next. It'll have to wait till tomorrow as we're under a
serious
blizzard/snow event right now and I'd like to get home before all of hell
f
On Wed, Feb 25, 2015 at 4:14 PM, wrote:
> So, is this a CentOS bug, or upstream's problem?
No idea. Guessing, it's probably missing upstream because at the time
firewalld was stabilizing for RHEL7 it was brand new even on Fedora.
So I'll bet a bunch of service files just aren't created.
--
Ch
Chris Murphy wrote:
> I'm on Fedora 22 Server which has this already:
>
> # cat /usr/lib/firewalld/services/rsyncd.xml
>
>
> Rsync in daemon mode
> Rsync in daemon mode works as a central server, in
> order to house centralized files and keep them
> synchronized.
>
>
>
>
> And also:
>
Add "rdblacklist=MODULE_NAME" to your append line in pxelinux.conf file.
>
Trying that next. It'll have to wait till tomorrow as we're under a serious
blizzard/snow event right now and I'd like to get home before all of hell
freezes over. However, question, if I blacklist the module, that means
du
On Wed, Feb 25, 2015 at 2:39 PM, Earl A Ramirez wrote:
> On Wed, 2015-02-25 at 16:33 -0500, m.r...@5-cent.us wrote:
>> Chris Murphy wrote:
>> > firewall-cmd --add-service=rsyncd
>> >
>> firewall-cmd --add-service=rsyncd
>> Error: INVALID_SERVICE: rsyncd
>>
>> Is there another place that there need
I'm on Fedora 22 Server which has this already:
# cat /usr/lib/firewalld/services/rsyncd.xml
Rsync in daemon mode
Rsync in daemon mode works as a central server, in
order to house centralized files and keep them
synchronized.
And also:
# dnf provides /usr/lib/firewalld/services/rsync
On Wed, 25 Feb 2015 16:45:04 -0600, Ashley M. Kirchner
wrote:
Out of order meaning, it puts the additional ethernet card as eth0, with
the built-in ports as eth1 and eth2 respectively. WITHOUT the additional
card >installed, it puts the built-in ports as eth0 and eth1, which is
what I wa
On Wed, Feb 25, 2015 at 4:45 PM, Ashley M. Kirchner wrote:
> Out of order meaning, it puts the additional ethernet card as eth0, with
> the built-in ports as eth1 and eth2 respectively. WITHOUT the additional
> card installed, it puts the built-in ports as eth0 and eth1, which is what
> I want it
Ashley M. Kirchner wrote:
> Out of order meaning, it puts the additional ethernet card as eth0, with
> the built-in ports as eth1 and eth2 respectively. WITHOUT the additional
> card installed, it puts the built-in ports as eth0 and eth1, which is what
> I want it to do. The additional card should
Out of order meaning, it puts the additional ethernet card as eth0, with
the built-in ports as eth1 and eth2 respectively. WITHOUT the additional
card installed, it puts the built-in ports as eth0 and eth1, which is what
I want it to do. The additional card should be eth2, at least that's what I
wa
Define out of order in this case just so I know for sure what you mean.
What my solution does, or at least does reliably in my case, is make sure
the interfaces are in the same order once installed as the install kernel
saw them. It won't re-order them to be sequential based on bus, mac or
Ok, when I run that, it creates a now "custom" 70-persistent-net.rules, but
the interfaces are still out of order, with the added one listed first, and
the built-ins 2nd and 3rd.
On Wed, Feb 25, 2015 at 2:00 PM, Jason Warr wrote:
> Here is my script for post install if you want to try it.
>
> In
On 02/26/2015 07:23 AM, Niki Kovacs wrote:
> I wonder if there's an easy way to strip down an installation to the
> bare minimum, e. g. the packages you get when you select "minimum
> installation".
I haven't tried this, but see if it works:
yum shell
remove *
install @minimal
run
Peter
On Wed, 2015-02-25 at 16:33 -0500, m.r...@5-cent.us wrote:
> Chris Murphy wrote:
> > firewall-cmd --add-service=rsyncd
> >
> firewall-cmd --add-service=rsyncd
> Error: INVALID_SERVICE: rsyncd
>
> Is there another place that there needs to be an rsyncd service file,
> whatever it's supposed to be n
Chris Murphy wrote:
> firewall-cmd --add-service=rsyncd
>
firewall-cmd --add-service=rsyncd
Error: INVALID_SERVICE: rsyncd
Is there another place that there needs to be an rsyncd service file,
whatever it's supposed to be named, *other* than where systemd wants it?
mark
> To make it perman
firewall-cmd --add-service=rsyncd
To make it permanent, do the above and this:
firewall-cmd --permanent --add-service=rsyncd
Chris Murphy
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Here is my script for post install if you want to try it.
In order for the shuffling to not occur you do need to create the udev
rules file somehow. I am not sure how mangled this will be in email but
it is worth a try. It should run OK with nothing else. I have a better
version in the w
Thanks for that Jason but it didn't solve the problem. The system is still
coming up with the interfaces shuffled. It seems to *always* want to use
the added ethernet card as eth0.
On Wed, Feb 25, 2015 at 1:37 PM, Jason Warr wrote:
> Starting back in RHEL/Cent 5 I found that the only way to make
Le 25/02/2015 20:18, Brian Mathis a écrit :
I don't think there's a single yum command that lets you roll back to the
packages the were installed at a given point in time.
Maybe a good idea would be to find one or a handful of packages that the
whole desktop and/or graphical subsystem depend
On 2/25/2015 12:04 PM, Niki Kovacs wrote:
Le 25/02/2015 19:36, John R Pierce a écrit :
I install from the 'minimum' ISO, and get that off the bat, then just
install the packages I need with yum
I do the same, but my question is: how to do that the other way around?
Let's say you start from th
I'm having issues with an rsyncd. systemctl status rsyncd shows it running
rsyncd.service - fast remote file copy program daemon
Loaded: loaded (/usr/lib/systemd/system/rsyncd.service; enabled)
Active: active (running) since Wed 2015-02-25 10:57:02 EST; 4h 43min ago
Main PID: 31672 (rsync)
Starting back in RHEL/Cent 5 I found that the only way to make sure your
interface enumeration was consistent after install with what you had
during install was to create a udev rules file using the mac addresses as
the key. It is easy to run a short script in postinstall to create it
base
Version 6.6 ...
On Wed, Feb 25, 2015 at 1:17 PM, Jim Perrin wrote:
>
>
> On 02/25/2015 01:56 PM, Ashley M. Kirchner wrote:
> > Ok, so some of this now works, but I'm still having problems. With the
> > bootif option, the system now correctly configures and uses the same
> > interface to get its
On 02/25/2015 01:56 PM, Ashley M. Kirchner wrote:
> Ok, so some of this now works, but I'm still having problems. With the
> bootif option, the system now correctly configures and uses the same
> interface to get its kickstart file. However, when the system is done and
> boots up, the interfaces
Ok, so some of this now works, but I'm still having problems. With the
bootif option, the system now correctly configures and uses the same
interface to get its kickstart file. However, when the system is done and
boots up, the interfaces are still messed up. So this is what I have in the
kickstart
On Wed, 25 Feb 2015 20:04:22 +0100
Niki Kovacs wrote:
> how do you manage from
> there to get back to exactly the base system you had from the start?
My approach would be to create a list of installed rpms for what you're using
as the base system:
rpm -qa --qf "%{NAME}\n" | sort > starting.txt
On Wed, Feb 25, 2015 at 2:04 PM, Niki Kovacs wrote:
>
> Le 25/02/2015 19:36, John R Pierce a écrit :
>
>> I install from the 'minimum' ISO, and get that off the bat, then just
>> install the packages I need with yum
>>
>
> I do the same, but my question is: how to do that the other way around?
>
Le 25/02/2015 19:36, John R Pierce a écrit :
I install from the 'minimum' ISO, and get that off the bat, then just
install the packages I need with yum
I do the same, but my question is: how to do that the other way around?
Let's say you start from the base system, then install a couple doze
On 2/25/2015 10:23 AM, Niki Kovacs wrote:
I wonder if there's an easy way to strip down an installation to the
bare minimum, e. g. the packages you get when you select "minimum
installation".
I install from the 'minimum' ISO, and get that off the bat, then just
install the packages I need wi
Hi,
I wonder if there's an easy way to strip down an installation to the
bare minimum, e. g. the packages you get when you select "minimum
installation".
In Slackware, the bone-headed package manager slackpkg has a few nice
options, among which 'slackpkg clean-system', which removes all
thi
Le 24/02/2015 08:41, Andrew Holway a écrit :
+1 for freeipa. It is an extremely well integrated domain controller with a
functionality similar to Microsoft Active Directory.
I want to thank everybody for their numerous and detailed answer posts
to this thread. Looks like FreeIPA is the way t
On Wed, 25 Feb 2015, Michael Mol wrote:
On Wed, Feb 25, 2015 at 10:27 AM, Michael Mol wrote:
So, I'm seeing a bunch of DHCPv6 traffic coming from my CentOS7
machines. Basically, the machines are trying to send router
solicitations, the packets are blocked at their egress firewalls, and
I get t
On Wed, Feb 25, 2015 at 10:27 AM, Michael Mol wrote:
> So, I'm seeing a bunch of DHCPv6 traffic coming from my CentOS7
> machines. Basically, the machines are trying to send router
> solicitations, the packets are blocked at their egress firewalls, and
> I get to see the logs.
>
> I don't wish to
Am 22.02.2015 um 15:51 schrieb J Martin Rushton
:
>> on an EL5 XEN DOM0 system I have following volume
>>
>> $ df -h /srv FilesystemSize Used Avail Use% Mounted
>> on /dev/sdc1 917G 858G 60G 94% /srv
>>
>> that partition was used by virtual machines but they were all
On 02/24/2015 09:35 AM, lheck...@users.sourceforge.net wrote:
>
>> I will change the instructions on the wiki to say to edit the files
>> that are included in the centos-release rpm.
>
> Thanks, Johnny.
>
> That's not really my problem. My problem is that I now need to track an
> additional
Am 22.02.2015 um 16:12 schrieb Stephen Harris :
>> nothing is using the partition
>> $ lsof |grep srv
>>
>
> Although the prompt is a $, I assume you're actually doing this as root?
Yeah - its a bad behaviour doing tasks with a # prompt and then
making a request in mailinglists with $ as promp
So, I'm seeing a bunch of DHCPv6 traffic coming from my CentOS7
machines. Basically, the machines are trying to send router
solicitations, the packets are blocked at their egress firewalls, and
I get to see the logs.
I don't wish to disable IPv6. I don't wish to statically configure
IPv6 at this t
Send CentOS-announce mailing list submissions to
centos-annou...@centos.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-requ..
Le 24/02/2015 13:51, Jim Perrin a écrit :
Might also be worth mentioning that supposedly around the 7.2 timeframe,
gnome is scheduled to be bumped to a more modern version.
https://bugzilla.redhat.com/show_bug.cgi?id=1174442
In theory this should put transparent terminal support back in
gnome-
43 matches
Mail list logo
