Re: [CentOS] CentOS 7, NSF, "feature"
On 2 Feb 2016 20:19, "Ricardo J. Barberis" wrote: > because the interface wasn't yet up, so I had to make a new unit and put this > inside (/etc/systemd/system/nginx.service): > > > .include /usr/lib/systemd/system/nginx.service > > [Unit] > After=network.target remote-fs.target nss-lookup.target network-online.target > > > > The After line is the important one, I copied it from > /usr/lib/systemd/system/nginx.service and added "network-online.target" > at the end. > > After making your changes, be sure to reenable the service so it takes your > new unit, e.g.: > > # systemctl reenable nginx.service > > 1) Don't use .include as that's not recommended and deprecated behaviour. Make an override snippet in /etc/systemd/system/nginx.service.d called custom.conf or network.conf or something. This has the benefit as well of working nicely with systemctl cat and systemd-delta. 2) You just need a systemctl daemon-reload after this not reenable. 3) The network targets situation is detailed (and the whys of it) in the systemd.special man page. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] I am not understanding the size of the iso
On 03/02/16 19:15, Ramaseshan wrote: > Yep, This is true, > If I look at Fedora Gnome for example, which also ships all > these(browser,libre, gnome etc), the final DVD version is just about 1.2 GB. > That is what surprises me. You're comparing apples to oranges. The Fedora images are live DVD, please note that CentOS also offers live DVD images which are 1.2 and 1.7G for GNOME and KDE respectively (for CentOS 7). The installation DVD not only contains *both* GNOME and KDE (each live DVD image only contains one of these), but also other programs that are not on the live DVD. Peter ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Python hashlib and ripemd160
Hi - I think the patent monster has struck again.
rmd = hashlib.new('ripemd160',binascii.unhexlify(someString)).hexdigest()
That fails - ValueError: unsupported hash type
From some googling, it appears that the supported hash types are from
OpenSSL and that means the OpenSSL in CentOS doesn't support ripemd160.
I've worked around other stuff missing from CentOS OpenSSL by building
LibreSSL and linking against that but python is central to the operation
of CentOS and I do not want to mess with replacing the CentOS packaging
of python.
Is there an alternate way to get a ripemd160 hash in python on CentOS ?
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Python hashlib and ripemd160
well, how about compiling instance to another directory like
/opt/python-alternative?
usually works like ./configure --prefix=/opt/python-alternative and then
other normal stuff..
--
Eero
2016-02-03 12:52 GMT+02:00 Alice Wonder :
> Hi - I think the patent monster has struck again.
>
> rmd = hashlib.new('ripemd160',binascii.unhexlify(someString)).hexdigest()
>
> That fails - ValueError: unsupported hash type
>
> From some googling, it appears that the supported hash types are from
> OpenSSL and that means the OpenSSL in CentOS doesn't support ripemd160.
>
> I've worked around other stuff missing from CentOS OpenSSL by building
> LibreSSL and linking against that but python is central to the operation of
> CentOS and I do not want to mess with replacing the CentOS packaging of
> python.
>
> Is there an alternate way to get a ripemd160 hash in python on CentOS ?
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Python hashlib and ripemd160
okay it appears there are no suspect patent issues with ripemd160 so
either they just didn't include it for some other reason or the issue is
elsewhere.
On 02/03/2016 03:00 AM, Eero Volotinen wrote:
well, how about compiling instance to another directory like
/opt/python-alternative?
usually works like ./configure --prefix=/opt/python-alternative and then
other normal stuff..
--
Eero
2016-02-03 12:52 GMT+02:00 Alice Wonder :
Hi - I think the patent monster has struck again.
rmd = hashlib.new('ripemd160',binascii.unhexlify(someString)).hexdigest()
That fails - ValueError: unsupported hash type
From some googling, it appears that the supported hash types are from
OpenSSL and that means the OpenSSL in CentOS doesn't support ripemd160.
I've worked around other stuff missing from CentOS OpenSSL by building
LibreSSL and linking against that but python is central to the operation of
CentOS and I do not want to mess with replacing the CentOS packaging of
python.
Is there an alternate way to get a ripemd160 hash in python on CentOS ?
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
[CentOS] [solved] Re: Python hashlib and ripemd160
from Crypto.Hash import RIPEMD
That lets me do a ripemd-160
On 02/03/2016 03:18 AM, Alice Wonder wrote:
okay it appears there are no suspect patent issues with ripemd160 so
either they just didn't include it for some other reason or the issue is
elsewhere.
On 02/03/2016 03:00 AM, Eero Volotinen wrote:
well, how about compiling instance to another directory like
/opt/python-alternative?
usually works like ./configure --prefix=/opt/python-alternative and then
other normal stuff..
--
Eero
2016-02-03 12:52 GMT+02:00 Alice Wonder :
Hi - I think the patent monster has struck again.
rmd =
hashlib.new('ripemd160',binascii.unhexlify(someString)).hexdigest()
That fails - ValueError: unsupported hash type
From some googling, it appears that the supported hash types are from
OpenSSL and that means the OpenSSL in CentOS doesn't support ripemd160.
I've worked around other stuff missing from CentOS OpenSSL by building
LibreSSL and linking against that but python is central to the
operation of
CentOS and I do not want to mess with replacing the CentOS packaging of
python.
Is there an alternate way to get a ripemd160 hash in python on CentOS ?
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] [solved] CentOS 7 - DNAT with firewalld
HI, Am 26.01.2016 um 15:56 schrieb Django [BOfH]: > So I think destination NAT (DNAT) isn't working on my CentOS 7 host. As > I seaid on my CentOS6 host DNAT is working very well. > > So where's my error? in my configuration or in my head? ;) The problem was a fault in destination hosts routing table. So I can say: "yes, the error was in my brain". ;P cu Django -- "Bonnie & Clyde der Postmaster-Szene!" approved by Postfix-God http://wetterstation-pliening.info http://dokuwiki.nausch.org http://wiki.piratenpartei.de/Benutzer:Django ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] strange behavior of firewalld and port-forwarding
HI, me and firewalld won't have a good start, but I hope we'll be good friends. One of my hosts must rerote traffic from one to another host. It isn't a big problem. I've a host witch must do: 1) forwarding port 25 tcp to a second host Here I've a special mail-relay. My external.xml look like this one: External For use on external networks. You do not trust the other computers on networks to not harm your computer. Only selected incoming connections are accepted. Every thing works expected, incomming traffic on port 25 is forwarded to 10.0.0.87 port 25. 2) traffic from 80.80.80.80 and destination-port 25 should be forwarded to port 22 tcp on 10.0.0.17 and not to 10.0.0.87 on port 25 So I made a new rule with: firewall-cmd --zone=external --add-rich-rule='rule forward-port port="25" to-port="22" to-addr="10.0.0.17" protocol="tcp" family="ipv4" source address="80.80.80.80"' If I try to connect on host 80.80.80.80 my system with: "telnet 10.0.0.17 25" I can connect the final host 10.0.0.17 on port 22 and open-ssh will greet me "SSH-2.0-oPENssh_6.6.1". It is working like I've expected. If I made my new firewall-rule permanent I use: "firewall-cmd --runtime-to-permanent" an the zone-file has now this content: External For use on external networks. You do not trust the other computers on networks to not harm your computer. Only selected incoming connections are accepted. O.K. That isn't a miracle. BUT, every is working right till I restart the server or reload the firewalld with: "firewall-cmd --reload" Now I can't access my host 10.0.0.17 via ssh over my transit-host! I'll reach destination-host 10.0.0.87 on port 25. It looks like, my rich rule were'nt definied. :/ Any idea, how to make it reboot-save? Thanx for help ttyl, Django -- "Bonnie & Clyde der Postmaster-Szene!" approved by Postfix-God http://wetterstation-pliening.info http://dokuwiki.nausch.org http://wiki.piratenpartei.de/Benutzer:Django ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Latest version of kate editor
On Tue, February 2, 2016 12:02, H wrote: > > What do people use as a programming editor on CentOS 6? My first > impression of kate was favorable, not only did it support the usual > programming and scripting languages but also markdown which I have > recently discovered... > > I use vim/gvim together with numerous add-ons from Tim Pope. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail James B. Byrnemailto:byrn...@harte-lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Latest version of kate editor
James B. Byrne wrote: > On Tue, February 2, 2016 12:02, H wrote: >> >> What do people use as a programming editor on CentOS 6? My first >> impression of kate was favorable, not only did it support the usual >> programming and scripting languages but also markdown which I have >> recently discovered... > > I use vim/gvim together with numerous add-ons from Tim Pope. Y'all now have me looking for one that does Brief emulation (the best text editor ever) mark "or should we move this thread to alt.religion.editors?" ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] hot do use iscsi loopback
hi everybody I've looked it up on the net but info is scarce. Could please someone explain how to use loopback and what is purpose? many thanks ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7, NSF, "feature" [SOLVED]
The issue: NFS fails to start in CentOS 7 if it cannot resolve any of a list of hosts. Well, my manager had to google to find the *truly* obscure solution that uses a deeply oddball syntax. In /usr/lib/systemd/system/nfs-server.service, you edit the following line so that it looks like this: ExecStartPre=-/usr/sbin/exportfs -r Notice the *deeply* weird syntax of "=-". This apparently tells it that "a nonzero exit code" should be ignored and considered "success". And, I read in the manpage for systemd.service that if you precede it with an @, it will pass arguments. Why it does not use the used-everywhere-else of *post*fixing those parms, I have no data. And, speaking specifically about nfs-server.service, I also don't understand why you'd set as an out-of-the-box default that it should fail to come up if it can't resolve any export host, rather than default to coming up. mark, discovering new reasons to dislike systemd ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7, NSF, "feature"
El Miércoles 03/02/2016, James Hogarth escribió: > On 2 Feb 2016 20:19, "Ricardo J. Barberis" wrote: > > because the interface wasn't yet up, so I had to make a new unit and put > > this > > > inside (/etc/systemd/system/nginx.service): > > > > > > .include /usr/lib/systemd/system/nginx.service > > > > [Unit] > > After=network.target remote-fs.target nss-lookup.target > > network-online.target > > > > > > > > > The After line is the important one, I copied it from > > /usr/lib/systemd/system/nginx.service and added "network-online.target" > > at the end. > > > > After making your changes, be sure to reenable the service so it takes > > your > > > new unit, e.g.: > > > > # systemctl reenable nginx.service > > 1) Don't use .include as that's not recommended and deprecated behaviour. > Make an override snippet in /etc/systemd/system/nginx.service.d called > custom.conf or network.conf or something. This has the benefit as well of > working nicely with systemctl cat and systemd-delta. Nice to know, I've only used systemd with CentOS 7 so I'm not terribly familiar with it, though I read a lot about it on Lennarts's blog. The .include trick was from systemd 208 IIRC (from CentOS 7.0) but now we have systemd 219 (CentOS 7.2) so there's a lot of little new things to learn :) > 2) You just need a systemctl daemon-reload after this not reenable. > > 3) The network targets situation is detailed (and the whys of it) in the > systemd.special man page. Cheers, -- Ricardo J. Barberis Usuario Linux Nº 250625: http://counter.li.org/ Usuario LFS Nº 5121: http://www.linuxfromscratch.org/ Senior SysAdmin / IT Architect - www.DonWeb.com ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] How to install packages from git.centos.org
Hi all, how can I install rpms from git.centos.org? I'd like to install and test the realtime-kernel. It seems to me that https://wiki.centos.org/Sources only means to build srpms. What I ned is an rt-kernel with headers for further compiling. Purpose: I'd like to build a digital audio workstation and for this I'd like to try out CentOS with the following packages first: - kernel-rt - ardour - calf-plugins BTW: Is there an audio SIG? Thanks in advance Tim ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] hot do use iscsi loopback
On 03/02/16 15:56, lejeczek wrote: hi everybody I've looked it up on the net but info is scarce. Could please someone explain how to use loopback and what is purpose? many thanks ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos huh, silly me, never mind. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7, NSF, "feature" [SOLVED]
> On Feb 3, 2016, at 10:57 AM, m.r...@5-cent.us wrote: > > The issue: NFS fails to start in CentOS 7 if it cannot resolve any of a > list of hosts. > > Well, my manager had to google to find the *truly* obscure solution that > uses a deeply oddball syntax. > > In /usr/lib/systemd/system/nfs-server.service, you edit the following line > so that it looks like this: > ExecStartPre=-/usr/sbin/exportfs -r > > Notice the *deeply* weird syntax of "=-". This apparently tells it > that "a nonzero exit code" should be ignored and considered "success”. Deeply weird or not, this is standard make (or at least gnu make) syntax. I wouldn’t be surprised if the developers thought it was completely normal. > > And, I read in the manpage for systemd.service that if you precede it with > an @, it will pass arguments. Why it does not use the used-everywhere-else > of *post*fixing those parms, I have no data. My reading of the man page is that arguments are always passed, and @ just means that the first “argument” (i.e. 1st token after the executable name) is passed as argv[0] (which would normally the path of the executable itself). But that’s entirely based on the man page, no actual experience. Noam ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7, NSF, "feature" [SOLVED]
On Feb 3, 2016, at 8:57 AM, m.r...@5-cent.us wrote: > > Notice the *deeply* weird syntax of "=-”. That syntax comes from make(1), where it means the same thing. make(1) has been with us since 1977, so I’d think “old and familiar” is a better description than “deeply weird.” > And, I read in the manpage for systemd.service that if you precede it with > an @, it will pass arguments. Why it does not use the used-everywhere-else > of *post*fixing those parms, I have no data. You’ve misread the page. All this option does is lets you run one command but tell the command itself that it was called by a different name. I’m not sure why the systemd creators added this, since you normally get this behavior with links: $ sudo yum install unzip $ ls -li /bin/unzip /bin/infozip 135096149 -rwxr-xr-x. 2 root root 181248 Mar 18 2015 unzip 135096149 -rwxr-xr-x. 2 root root 181248 Mar 18 2015 zipinfo That is, we have a single program binary with two different names. Invoking the program as “zipinfo” makes it behave differently than if you invoke it as “unzip”. All this systemd feature does is lets you say something like: ExecStart=@/bin/unzip zipinfo ... That is, you can run the unzip binary but *call it* zipinfo. Again, I don’t know why they couldn’t just do it with links. However, I will point out that the C programming interfaces on your system (execv() and friends) also support this feature, and have since back before 1977, so that this, too, is not some fresh new weirdness. > I also don't > understand why you'd set as an out-of-the-box default that it should fail > to come up if it can't resolve any export host, rather than default to > coming up. You do it for the same reason you’d fail when mounting any other filesystem. It may be critical to operation, as with shared /usr. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7, NSF, "feature" [SOLVED]
On 02/03/2016 08:59 AM, Warren Young wrote: Again, I don’t know why they couldn’t just do it with links. Probably because they want to support a read-only root filesystem, working toward "stateless" systems. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7, NSF, "feature" [SOLVED]
El Miércoles 03/02/2016, Warren Young escribió: > On Feb 3, 2016, at 8:57 AM, m.r...@5-cent.us wrote: > > Notice the *deeply* weird syntax of "=-”. > > That syntax comes from make(1), where it means the same thing. make(1) has > been with us since 1977, so I’d think “old and familiar” is a better > description than “deeply weird.” > > > And, I read in the manpage for systemd.service that if you precede it > > with an @, it will pass arguments. Why it does not use the > > used-everywhere-else of *post*fixing those parms, I have no data. > > You’ve misread the page. > > All this option does is lets you run one command but tell the command > itself that it was called by a different name. I’m not sure why the > systemd creators added this, since you normally get this behavior with > links: > > $ sudo yum install unzip > $ ls -li /bin/unzip /bin/infozip > 135096149 -rwxr-xr-x. 2 root root 181248 Mar 18 2015 unzip > 135096149 -rwxr-xr-x. 2 root root 181248 Mar 18 2015 zipinfo > > That is, we have a single program binary with two different names. > Invoking the program as “zipinfo” makes it behave differently than if you > invoke it as “unzip”. > > All this systemd feature does is lets you say something like: > > ExecStart=@/bin/unzip zipinfo ... > > That is, you can run the unzip binary but *call it* zipinfo. > > Again, I don’t know why they couldn’t just do it with links. However, I > will point out that the C programming interfaces on your system (execv() > and friends) also support this feature, and have since back before 1977, so > that this, too, is not some fresh new weirdness. I guess that's probably to execute scripts and "hide" the name of the interpreter, e.g.: ExecStart=@/usr/bin/python my_cool_service --my_args > > I also don't > > understand why you'd set as an out-of-the-box default that it should fail > > to come up if it can't resolve any export host, rather than default to > > coming up. > > You do it for the same reason you’d fail when mounting any other > filesystem. It may be critical to operation, as with shared /usr. -- Ricardo J. Barberis Usuario Linux Nº 250625: http://counter.li.org/ Usuario LFS Nº 5121: http://www.linuxfromscratch.org/ Senior SysAdmin / IT Architect - www.DonWeb.com ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] delete directories with find and exclude other directories
Hi all, I'm attempting to delete some directories and I want to be able to exclude a directory called 'logs' from being deleted. This is my basic find operation (without the exclusion) # find . -type d |tail -10 ./d20160124-1120-df8mfb/deployments ./d20160124-1120-df8mfb/releases ./d20160131-16993-vazqg5 ./d20160131-16993-vazqg5/metadata ./d20160131-16993-vazqg5/deployments ./d20160131-16993-vazqg5/releases ./logs ./d20160203-27735-1tqbjh6 ./d20160125-1120-1yccr9p ./d20160131-16993-1yf9lnc I'm just tailing the output so that you have an idea of what's going on without taking up the whole page. :) If I try to exlclude the logs directory with the prune command I get back no results. root@ops-manager:/tmp/tmp# find . -type d -prune -o -name 'logs' -print root@ops-manager:/tmp# What am I doing wrong? Thanks, Tim -- GPG me!! gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] nfs stuck, don't know what processes to kill
Thanks. How did I miss that -l switch? Unfortunately, I went into panic
mode and just rebooted, but I'll know next time.
Dave
On Tue, Feb 2, 2016 at 9:00 AM, Phelps, Matthew
wrote:
> Try "umount -fl"('eff el')
>
> On Tue, Feb 2, 2016 at 1:58 PM, Dave Burns wrote:
>
> > My NFS server is up and other clients can access x. One particular client
> > can't. I tried to unmount the NFS share:
> >
> > [root@nfsclient ~]# umount -f /disk/x
> > umount2: Device or resource busy
> > umount.nfs: /disk/x: device is busy
> > umount2: Device or resource busy
> > umount.nfs: /disk/x: device is busy
> >
> > If I use df or lsof to try to figure out what process to kill, they
> hang. I
> > am reluctant to just reboot, as many other users are getting stuff done.
> > dmesg doesn't show anything useful.
> >
> > How to get unstuck?
> >
> > thanks,
> > Dave
> > ___
> > CentOS mailing list
> > CentOS@centos.org
> > https://lists.centos.org/mailman/listinfo/centos
> >
>
>
>
> --
> Matt Phelps
> System Administrator, Computation Facility
> Harvard - Smithsonian Center for Astrophysics
> mphe...@cfa.harvard.edu, http://www.cfa.harvard.edu
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
--
This email is:[ ] request action [ ] request info [x] fyi[ ]
social
Response needed: [ ] yes [x] up to you [ ] no
Time-sensitive: [ ] immediate[ ] soon [x] none
http://www.43folders.com/2005/09/19/writing-sensible-email-messages
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] delete directories with find and exclude other directories
On Wed, February 3, 2016 11:37 am, Tim Dunphy wrote: > Hi all, > > I'm attempting to delete some directories and I want to be able to exclude > a directory called 'logs' from being deleted. > > This is my basic find operation (without the exclusion) > > # find . -type d |tail -10 > ./d20160124-1120-df8mfb/deployments > ./d20160124-1120-df8mfb/releases > ./d20160131-16993-vazqg5 > ./d20160131-16993-vazqg5/metadata > ./d20160131-16993-vazqg5/deployments > ./d20160131-16993-vazqg5/releases > ./logs > ./d20160203-27735-1tqbjh6 > ./d20160125-1120-1yccr9p > ./d20160131-16993-1yf9lnc crude thing I would do is: find . -type d | grep -v logs , but that will also exclude other names containing "logs" it is like: Semilogs2 logs4me Thanks. Valeri > > I'm just tailing the output so that you have an idea of what's going on > without taking up the whole page. :) > > If I try to exlclude the logs directory with the prune command I get back > no results. > > root@ops-manager:/tmp/tmp# find . -type d -prune -o -name 'logs' -print > root@ops-manager:/tmp# > > What am I doing wrong? > > Thanks, > Tim > > -- > GPG me!! > > gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] I am not understanding the size of the iso
Sorry, I understand the size of the ISO. I overlooked the installation options. Now its all clear. On Wednesday 03 February 2016 04:02 PM, Peter wrote: > On 03/02/16 19:15, Ramaseshan wrote: >> Yep, This is true, >> If I look at Fedora Gnome for example, which also ships all >> these(browser,libre, gnome etc), the final DVD version is just about 1.2 GB. >> That is what surprises me. > You're comparing apples to oranges. The Fedora images are live DVD, > please note that CentOS also offers live DVD images which are 1.2 and > 1.7G for GNOME and KDE respectively (for CentOS 7). The installation > DVD not only contains *both* GNOME and KDE (each live DVD image only > contains one of these), but also other programs that are not on the live > DVD. > > > Peter > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos -- Cheers -- S.Ramaseshan Engineer Fractalio Data Pvt Ltd email : ramases...@fractalio.com Web : www.fractalio.com ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] nfs stuck, don't know what processes to kill
On Tue, Feb 2, 2016 at 9:23 AM, wrote: > Dave Burns wrote: > > My NFS server is up and other clients can access x. One particular client > > can't. I tried to unmount the NFS share: > > > > [root@nfsclient ~]# umount -f /disk/x > > umount2: Device or resource busy > > umount.nfs: /disk/x: device is busy > > umount2: Device or resource busy > > umount.nfs: /disk/x: device is busy > > > > If I use df or lsof to try to figure out what process to kill, they hang. > > I > > am reluctant to just reboot, as many other users are getting stuff done. > > dmesg doesn't show anything useful. > > > > How to get unstuck? > > *IF* I understand what you're saying, on that one client, you're trying to > umount the nfs share. Is that the case? > > IF that is the case... is autofs running? If so, service autofs stop, and > you should be able to umount it. > >mark > > # service autofs stop results in fail. Maybe need #rm /var/run/autofs.pid? Dave ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7, NSF, "feature" [SOLVED]
Warren Young wrote: > On Feb 3, 2016, at 8:57 AM, m.r...@5-cent.us wrote: >> >> I also don't understand why you'd set as an out-of-the-box default >> that it should fail to come up if it can't resolve any export host, >> rather than default to coming up. > > You do it for the same reason you’d fail when mounting any other > filesystem. It may be critical to operation, as with shared /usr. Beg pardon? The NFS server is offering it out, not requiring the f/s in. How could it be considered critical, as mounting / is? I can see it if *networking's* not up, but when it's only members of a list to whom it is available? mark ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] nfs stuck, don't know what processes to kill
Dave Burns wrote: > On Tue, Feb 2, 2016 at 9:23 AM, wrote: > >> Dave Burns wrote: >> > My NFS server is up and other clients can access x. One particular >> client >> > can't. I tried to unmount the NFS share: >> > >> > [root@nfsclient ~]# umount -f /disk/x >> > umount2: Device or resource busy >> > umount.nfs: /disk/x: device is busy >> > umount2: Device or resource busy >> > umount.nfs: /disk/x: device is busy >> > >> > If I use df or lsof to try to figure out what process to kill, they >> > hang.I am reluctant to just reboot, as many other users are getting >> > stuff done. dmesg doesn't show anything useful. >> > >> > How to get unstuck? >> >> *IF* I understand what you're saying, on that one client, you're trying >> to umount the nfs share. Is that the case? >> >> IF that is the case... is autofs running? If so, service autofs stop, >> and you should be able to umount it. >> >> # service autofs stop results in fail. Maybe need #rm >> /var/run/autofs.pid? Ok, ps -ef | grep auto, and see if it's running; or are you saying it *said* shutting it down failed? Oh, and is this CentOS 6 or 6 (service, or systemctl)? If it's already shut off, and lsof doesn't help, does doing a df help? Perhaps it might show someone's workspace, or home directory mounted, so you know who to kill? mark ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] delete directories with find and exclude other directories
Tim Dunphy wrote: > Hi all, > > I'm attempting to delete some directories and I want to be able to exclude > a directory called 'logs' from being deleted. > > This is my basic find operation (without the exclusion) > > # find . -type d |tail -10 > ./d20160124-1120-df8mfb/deployments > ./d20160124-1120-df8mfb/releases > ./d20160131-16993-vazqg5 > ./d20160131-16993-vazqg5/metadata > ./d20160131-16993-vazqg5/deployments > ./d20160131-16993-vazqg5/releases > ./logs > ./d20160203-27735-1tqbjh6 > ./d20160125-1120-1yccr9p > ./d20160131-16993-1yf9lnc > > I'm just tailing the output so that you have an idea of what's going on > without taking up the whole page. :) > > If I try to exlclude the logs directory with the prune command I get back > no results. > > root@ops-manager:/tmp/tmp# find . -type d -prune -o -name 'logs' -print > root@ops-manager:/tmp# > > What am I doing wrong? > find . -type d ! -name logs -prune (and -print has been a default for a long time). mark ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] delete directories with find and exclude other directories
On 02/03/2016 09:37 AM, Tim Dunphy wrote: If I try to exlclude the logs directory with the prune command I get back no results. root@ops-manager:/tmp/tmp# find . -type d -prune -o -name 'logs' -print What am I doing wrong? You're not applying the prune command to items named logs, for one. :) find . -name logs -prune -o -type d -print find will crawl the directory. Items named logs will not be examined further. Otherwise, if the item is a directory, its name will be printed. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] delete directories with find and exclude other directories
On 02/03/2016 10:11 AM, m.r...@5-cent.us wrote: find . -type d ! -name logs -prune That will prune all of the directories whose name is not "logs", starting with "." So... not terribly useful. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] delete directories with find and exclude other directories
Gordon Messmer wrote: > On 02/03/2016 10:11 AM, m.r...@5-cent.us wrote: >> find . -type d ! -name logs -prune > > That will prune all of the directories whose name is not "logs", > starting with "." > > So... not terribly useful. Right, but a) I think I tried using prune 20 years ago... and b) I thought the o/p wanted to not deal with any directory whose name was logs. leaving off prune would get everything, which is perhaps a bit more useful. mark ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] delete directories with find and exclude other directories
On 2/3/2016 12:37 PM, Tim Dunphy wrote: > I'm attempting to delete some directories and I want to be able to exclude > a directory called 'logs' from being deleted. Since you can't have a file and a directory named "logs" in the same directory at the same time (that I know of), you could turn on bash's extended globbing. $ shopt -s extglob $ rm -rf !(logs) That will only preserve the top-level entity named logs, though. If there's a "logs" in a subdirectory, it'll get deleted. -- -Chris ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7, NSF, "feature"
> De: "Ricardo J. Barberis"
> [Unit]
> After=network.target remote-fs.target nss-lookup.target network-online.target
>
>
>
> The After line is the important one, I copied it from
> /usr/lib/systemd/system/nginx.service and added "network-online.target"
> at the end.
>
> After making your changes, be sure to reenable the service so it takes your
> new unit, e.g.:
>
> # systemctl reenable nginx.service
>
>
> It worked for me, maybe it works for you?
On my systems, I saw that network.target was not started, because no service
required it ("After=foo" is totally useless if there isn't any "Require=foo"
too... Mwokay, why not...). I just added a symlink to force network.target to
start, and the ordering problem is solved :
/etc/systemd/system/multi-user.target.wants/network.target ->
/usr/lib/systemd/system/network.target
That link avoids modifying the configuration of _all_ the services needing a
fully working network (ssh, web, mail, snmp, and so on) with a crappy, but
easy-to-deploy, one-liner like this (no, I'm not ashamed) :
# for fic in $(grep -rl "After=.*network.target" /lib/systemd/system | cut -d/
-f5 | grep -v "network-online.target") ; do [ ! -d
"/etc/systemd/system/${fic}.d" ] && mkdir "/etc/systemd/system/${fic}.d" ; echo
-e "[Unit]\nAfter=network-online.target" >
"/etc/systemd/system/${fic}.d/local-network-online.conf" ; done && systemctl
daemon-reload
By the way, congratulations to the genius who decided to name one of the files
"-.slice"... Yes, a filename beginning by a hyphen. I suppose anybody here
understands why it's probably one of the worst ideas he never had.
Sylvain.
Pensez ENVIRONNEMENT : n'imprimer que si ncessaire
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
[CentOS] Kernel Panic post kernel-2.6.32-504.23.4.el6.x86_64
Greetings, Today, I decided to reboot one of my CentOS machines after it had been running for 219 days. In this time, I had done yum updates several times. When I tried rebooting the machine, none of the kernels would work except for the oldest one. Here are the installed kernels: kernel-2.6.32-504.23.4.el6.x86_64 kernel-2.6.32-573.3.1.el6.x86_64 kernel-2.6.32-573.7.1.el6.x86_64 kernel-2.6.32-573.8.1.el6.x86_64 kernel-2.6.32-573.12.1.el6.x86_64 Here is a uname -a: Linux onavenuea 2.6.32-504.23.4.el6.x86_64 #1 SMP Tue Jun 9 20:57:37 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux The CPU is a Intel Core 2 @2400 GHz; there is 6GB of RAM. Much thanks for any advice in this regard. Max Pyziur p...@brama.com ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] delete directories with find and exclude other directories
On 02/03/2016 10:51 AM, m.r...@5-cent.us wrote: Right, but a) I think I tried using prune 20 years ago... and b) I thought the o/p wanted to not deal with any directory whose name was logs. leaving off prune would get everything, which is perhaps a bit more useful. I think you don't understand. I was pointing out that the command you specified would print the name '.' and that is all. It won't descend through '.' because you told it to prune all directories not named "logs". That is, I'm trying to point out that it's your *logic* that's flawed. OP was right in his thinking. The correct way to approach the problem is to ignore (prune) the logs dir, and then to do something with the remaining directories. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Strange performance issue on CentOS 6.7 server
I’m running CentOS 6.7 on my build servers, and on one of the servers the builds are taking almost an order of magnitude longer than usual. There are no runaway processes and there is plenty of free memory. So I suspected that file I/O might be slow, and sure enough, that appears to be the case. I ran a simple dd test and compared the results to a “normal” build server (412 MB/s vs. 31.7 MB/s). Both are on similarly configured VGs on identical hardware. What could cause this performance degradation and are there any other tests I can run before I reboot the server to see if things improve? There is nothing in /var/log messages - are there other logs I should check? Alfred ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7, NSF, "feature" [SOLVED]
On Feb 3, 2016, at 10:18 AM, Gordon Messmer wrote: > > On 02/03/2016 08:59 AM, Warren Young wrote: >> Again, I don’t know why they couldn’t just do it with links. > > Probably because they want to support a read-only root filesystem, working > toward "stateless" systems. How does that explain anything? The same RPM that installed the service file can create a hard link or symlink giving the command an alternate name. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7, NSF, "feature" [SOLVED]
On Feb 3, 2016, at 10:30 AM, Ricardo J. Barberis wrote: > > El Miércoles 03/02/2016, Warren Young escribió: >> >> Again, I don’t know why they couldn’t just do it with links. > > I guess that's probably to execute scripts and "hide" the name of the > interpreter, e.g.: I get why second-rate programmers would care to do that, but what I don’t get is why systemd would need a feature to support that wish. No, I suspect the real reason systemd needs to support this is to work around someone’s broken argv[0] parsing. For instance, there may be a program that assumes it is always started through the PATH, so argv[0] never contains slashes. But, systemd only works with absolute paths for security, so rather than fix the broken program, they added a feature to systemd that lets it lie to the broken program, supplying the program’s basename in argv[0] even though it was started via an absolute path. Just a guess, of course. I notice that none of the service files on my main EL7 box use this leading-@ feature. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Kernel Panic post kernel-2.6.32-504.23.4.el6.x86_64
On Feb 3, 2016, at 12:24 PM, Max Pyziur wrote: > > When I tried rebooting the machine, none of the kernels would work except for > the oldest one. Define “would not work”. Post a photo of the error message somewhere if you can’t describe it better than that. You might have to turn off rhgb mode to get a useful error message. > Here are the installed kernels: > > kernel-2.6.32-504.23.4.el6.x86_64 > kernel-2.6.32-573.3.1.el6.x86_64 > kernel-2.6.32-573.7.1.el6.x86_64 > kernel-2.6.32-573.8.1.el6.x86_64 > kernel-2.6.32-573.12.1.el6.x86_64 Post the contents of /etc/grub.conf. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Strange performance issue on CentOS 6.7 server
On Feb 3, 2016, at 1:30 PM, Alfred von Campe wrote: > > I suspected that file I/O might be slow, and sure enough, that appears to be > the case….What could cause this A dying hard disk can do it. HDDs try to silently paper over I/O errors, but what they can’t hide is the time it takes to do this. If your HDD is constantly correcting errors at the oxide layer, it will be reallly sow. You can try running SMART tests on it, though that’s not guaranteed to show the problem. Got tested backups? :) ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Strange performance issue on CentOS 6.7 server
On Feb 3, 2016, at 16:13, Warren Young wrote: > A dying hard disk can do it. HDDs try to silently paper over I/O errors, but > what they can’t hide is the time it takes to do this. If your HDD is > constantly correcting errors at the oxide layer, it will be reallly > sow. > > You can try running SMART tests on it, though that’s not guaranteed to show > the problem. Well, it’s not “a” disk: it’s a HW RAID of about dozen (server grade) drives, with a VG/LV on top of that. Are there any log files I can check that test the underlying VG/LV health status? Alfred ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Strange performance issue on CentOS 6.7 server
Alfred von Campe wrote: > On Feb 3, 2016, at 16:13, Warren Young wrote: > >> A dying hard disk can do it. HDDs try to silently paper over I/O >> errors, but what they can’t hide is the time it takes to do this. If >> your HDD is constantly correcting errors at the oxide layer, it will be >> reallly sow. >> >> You can try running SMART tests on it, though that’s not guaranteed to >> show the problem. > > Well, it’s not “a” disk: it’s a HW RAID of about dozen (server grade) > drives, with a VG/LV on top of that. Are there any log files I can check > that test the underlying VG/LV health status? > You don't mention what kind of h/w RAID. LSI-based controller, and HP-based ones, both have utilities to check out the drives (MegaRAID and hpacli, respectively); AC&NC JetStors have a web interface. mark ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7, NSF, "feature" [SOLVED]
On 02/03/2016 12:52 PM, Warren Young wrote: Probably because they want to support a read-only root filesystem, working toward "stateless" systems. How does that explain anything? The same RPM that installed the service file can create a hard link or symlink giving the command an alternate name. It might not be the package that includes the symlink. It may be the admin who wants it. Where the root fs is read-only, this feature is an alternative to creating a symlink. It seems to be a thing that people want, in any case: http://comments.gmane.org/gmane.comp.sysutils.systemd.devel/7759 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Strange performance issue on CentOS 6.7 server
On Feb 3, 2016, at 2:26 PM, Alfred von Campe wrote: > > On Feb 3, 2016, at 16:13, Warren Young wrote: > >> A dying hard disk can do it. HDDs try to silently paper over I/O errors, >> but what they can’t hide is the time it takes to do this. If your HDD is >> constantly correcting errors at the oxide layer, it will be reallly >> sow. >> >> You can try running SMART tests on it, though that’s not guaranteed to show >> the problem. > > Well, it’s not “a” disk: it’s a HW RAID of about dozen (server grade) drives smartctl can see through several different types of RAID controller to the underlying physical disks via its -d option. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Strange performance issue on CentOS 6.7 server
On Feb 3, 2016, at 17:10, Warren Young wrote: > smartctl can see through several different types of RAID controller to the > underlying physical disks via its -d option. This is what I have: # smartctl --all /dev/sda smartctl 5.43 2012-06-30 r3573 [i686-linux-2.6.32-573.12.1.el6.i686] (local build) Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net Vendor: IBM Product: ServeRAID M5110e Revision: 3.19 User Capacity:1,494,996,746,240 bytes [1.49 TB] Logical block size: 512 bytes Logical Unit id: 0x60050760408e81b018be601809efd11c Serial number:001cd1ef091860be18b0818e40600705 Device type: disk Local Time is:Wed Feb 3 17:13:34 2016 EST Device does not support SMART Error Counter logging not supported Device does not support Self Test logging I guess I am stuck since it says it doesn’t support SMART. Or is there some way to get some status from this “disk” to see if it’s really the root cause of my performance issues. I think I would have seen something in /var/log/messages if there was a critical issue. Alfred ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Kernel Panic post kernel-2.6.32-504.23.4.el6.x86_64
On Wed, 3 Feb 2016, Warren Young wrote: On Feb 3, 2016, at 12:24 PM, Max Pyziur wrote: When I tried rebooting the machine, none of the kernels would work except for the oldest one. Define “would not work”. Post a photo of the error message somewhere if you can’t describe it better than that. You might have to turn off rhgb mode to get a useful error message. Here's a photo of the screen once the booting froze: http://www.brama.com/~deckard/P1010308.JPG Here are the installed kernels: kernel-2.6.32-504.23.4.el6.x86_64 kernel-2.6.32-573.3.1.el6.x86_64 kernel-2.6.32-573.7.1.el6.x86_64 kernel-2.6.32-573.8.1.el6.x86_64 kernel-2.6.32-573.12.1.el6.x86_64 Post the contents of /etc/grub.conf. I removed most of the non-working kernels 2.6.32-573-*, except for the latest one; here's /etc/grub.conf root@onavenuea ~> more /etc/grub.conf # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/sda3 # initrd /initrd-[generic-]version.img #boot=/dev/sda default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.32-573.12.1.el6.x86_64) root (hd0,0) kernel /vmlinuz-2.6.32-573.12.1.el6.x86_64 ro root=UUID=1d8767bf-b3a6-439a-b359-ba6b0a4f20cf nomodeset rd_NO_LUKS KEYBOARDTYPE=pc KEYTABLE=us LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto rd_NO_LVM rd_NO_DM rhgb quiet initrd /initramfs-2.6.32-573.12.1.el6.x86_64.img title CentOS (2.6.32-504.23.4.el6.x86_64) root (hd0,0) kernel /vmlinuz-2.6.32-504.23.4.el6.x86_64 ro root=UUID=1d8767bf-b3a6-439a-b359-ba6b0a4f20cf nomodeset rd_NO_LUKS KEYBOARDTYPE=pc KEYTABLE=us LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto rd_NO_LVM rd_NO_DM rhgb quiet initrd /initramfs-2.6.32-504.23.4.el6.x86_64.img Thank you. Max Pyziur p...@brama.com___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Kernel Panic post kernel-2.6.32-504.23.4.el6.x86_64
probably open bug https://bugs.centos.org/view.php?id=9374 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Strange performance issue on CentOS 6.7 server
On 3 Feb 2016 22:24, "Alfred von Campe" wrote: > > On Feb 3, 2016, at 17:10, Warren Young wrote: > > > smartctl can see through several different types of RAID controller to the underlying physical disks via its -d option. > > This is what I have: > > # smartctl --all /dev/sda > smartctl 5.43 2012-06-30 r3573 [i686-linux-2.6.32-573.12.1.el6.i686] (local build) > Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net > > Vendor: IBM > Product: ServeRAID M5110e > Revision: 3.19 > User Capacity:1,494,996,746,240 bytes [1.49 TB] > Logical block size: 512 bytes > Logical Unit id: 0x60050760408e81b018be601809efd11c > Serial number:001cd1ef091860be18b0818e40600705 > Device type: disk > Local Time is:Wed Feb 3 17:13:34 2016 EST > Device does not support SMART > > Error Counter logging not supported > Device does not support Self Test logging > > I guess I am stuck since it says it doesn’t support SMART. Or is there some way to get some status from this “disk” to see if it’s really the root cause of my performance issues. I think I would have seen something in /var/log/messages if there was a critical issue. > Severely degraded hardware RAID performance can often be caused by things like a failed cache battery. There is usually some sort of tool to interrogate the device to check things like cache behaviour. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS 7 regression, can not take a KVM qcow2, convert it and boot it on ESXi...
Guys, I have a Packer build procedure, that works like a charm, when with CentOS 6.7. Exemplifying: 1- Packer (with virtio disk) + QEmu + CentOS 6.7 ISO; 2- Create a RAW image; 3- Convert the RAW image into QCOW2 for KVM hypervisors (okay); 4- Convert the RAW image into VMDK for ESXi hypervisors (okay). However, when doing the very same procedure, with CentOS 7.2 ISO, it does not boot on ESXi! After research, I realized that it is not auto-loading the sd_mod on ESXi. I'm seeing errors like this: dracut-initqueue timeout dracut-initqueue timeout And it drops to "dracut#" shell, where I can see that there is no /dev/sda listed on /proc/partitions. I think I tried everything! My last try was, during Packer build, to append "add_drivers+=" sd_mod" to /etc/dracut.conf and re-building initramdisk by running "dracut -f". However, it does not boot either (on ESXi)! I can still boot using Rescue mode on VMWare, then, I can see that sd_mod is inside of initramfs as expected (lsinitrd FTW) but, dracut does not load it! I tried "force_drivers+=" sd_mod", doesn't work too... Weird is that, while during Rescue, if I run "dracut -f" again, then, it works! Normal boot proceeds... But this is unacceptable, because I can not ship a half-broken VMDK and tell customers to first boot on Rescue, run "dracut -f" and then, use the system. So, why the heck the "dracut -f" executed when as a KVM guest have no effect for later ESXi usage? What am I missing? I really appreciate any help! Thanks! Thiago ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 regression, can not take a KVM qcow2, convert it and boot it on ESXi...
On 02/03/2016 06:33 PM, Martinx - ジェームズ wrote: What am I missing? Use lsinitrd to compare the two initrds. Direct each output to two files and then use "diff -u" to see the difference. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7, NSF, "feature" [SOLVED]
On Wed, 2016-02-03 at 13:57 -0700, Warren Young wrote: > On Feb 3, 2016, at 10:30 AM, Ricardo J. Barberis > wrote: > > > > El Miércoles 03/02/2016, Warren Young escribió: > >> > >> Again, I don’t know why they couldn’t just do it with links. > > > > I guess that's probably to execute scripts and "hide" the name of the > > interpreter, e.g.: > > I get why second-rate programmers would care to do that, but what I don’t get > is why systemd would need a feature to support that wish. Perhaps the Systemd are all 'second-rate' programmers ? Good programmers always try to avoid the crap. -- Regards, Paul. England, EU. England's place is in the European Union. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 regression, can not take a KVM qcow2, convert it and boot it on ESXi...
On 4 February 2016 at 00:58, Gordon Messmer wrote: > On 02/03/2016 06:33 PM, Martinx - ジェームズ wrote: >> >> What am I missing? > > > Use lsinitrd to compare the two initrds. Direct each output to two files > and then use "diff -u" to see the difference. Mmm... Nice tip! Thanks! :-D ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] I am not understanding the size of the iso
The whole confusion was, instead of downloading the Live DVD install, I downloaded the DVD version, and made the default installation option (overlooking it) and it gave me only a minimal install by default. So it was nothing but a silly mistake, I am sorry about it. Didnt quite realize it. On Wednesday 03 February 2016 04:02 PM, Peter wrote: > On 03/02/16 19:15, Ramaseshan wrote: >> Yep, This is true, >> If I look at Fedora Gnome for example, which also ships all >> these(browser,libre, gnome etc), the final DVD version is just about 1.2 GB. >> That is what surprises me. > You're comparing apples to oranges. The Fedora images are live DVD, > please note that CentOS also offers live DVD images which are 1.2 and > 1.7G for GNOME and KDE respectively (for CentOS 7). The installation > DVD not only contains *both* GNOME and KDE (each live DVD image only > contains one of these), but also other programs that are not on the live > DVD. > > > Peter > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos -- Cheers -- S.Ramaseshan Engineer Fractalio Data Pvt Ltd email : ramases...@fractalio.com Web : www.fractalio.com ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
