Re: [CentOS] Regarding using CentOS on Commercial Appliance
Thanks for the reply. I had already visited the links mentioned by you. The link https://www.centos.org/legal/trademarks/ talks about non-usage of trademarks in commercial software which is taken care. The link https://www.centos.org/legal/ talks very less about legal terms and condition. Is there some other link which mentions about the License model used by CentOS. Infact, no where it is mentioned that it follows GPL or not. Just in that trademarks link below there is some mentioning of Creative Commons 3.0 but that looks only for trademark. Any idea will be highly helpful? Atleast if I know which license it follows, then I will be able to consult a lawyer for the same to know things in detail. On Tuesday, 9 August 2016 10:40 PM, Gordon Messmer wrote: On 08/08/2016 10:23 PM, Akshat Kakkar wrote: > I know all the CentOS packages, etc. might fall in GPL and as a result I > should be supplying source code of all the packages in CentOS. > > What else is expected from me? Certainly, I'd think you should include the source code for the CentOS distribution. When doing so, pay attention to: https://www.centos.org/legal/trademarks/ and: https://www.centos.org/legal/ ___ 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] Regarding using CentOS on Commercial Appliance
10.8.2016, 10:29, Akshat Kakkar kirjoitti: > Is there some other link which mentions about the License model used by > CentOS. Infact, no where it is mentioned that it follows GPL or not. Just in > that trademarks link below there is some mentioning of Creative Commons 3.0 > but that looks only for trademark. > The EULA file at the root of the distribution discs says: "The Distribution is released as GPLv2. Individual packages in the distribution come with their own licences." http://mirror.centos.org/centos-7/7/os/x86_64/EULA -- Markku Kolkka markku.kol...@iki.fi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Maybe OT - Centos 5 SATA JMicron JMB361 SATA
Hi All,
I know Centos 5 is almost EOL and all this is old but
I'm helping a colleague who has moved a Centos 5 install on an IDE disk
to system with a Foxconn M'board. His idea is to use the SATA interface
that's on the Foxconn.
The thing boots OK and then gets into a loop trying to start the
interfaces to the SATA disks. Oceans of stuff like this in /var/log/messages
Aug 7 04:23:32 filestore kernel: ata1: hard resetting link
Aug 7 04:23:32 filestore kernel: ata1: SATA link up 1.5 Gbps (SStatus
113 SControl 310)
Aug 7 04:23:32 filestore kernel: ata1.00: configured for UDMA/33
Aug 7 04:23:32 filestore kernel: ata1.01: configured for UDMA/33
Aug 7 04:23:32 filestore kernel: ata1: EH complete
Aug 7 04:24:02 filestore kernel: ata1.00: exception Emask 0x0 SAct 0x0
SErr 0x0 action 0x6 frozen
Aug 7 04:24:02 filestore kernel: ata1.00: cmd
25/00:08:00:88:e0/00:00:e8:00:00/e0 tag 0 dma 4096 in
Aug 7 04:24:02 filestore kernel: res
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 7 04:24:02 filestore kernel: ata1.00: status: { DRDY }
I have limited the SATA speed to 1.5G with a kernel param in Grub to see
if that helps.
After a few hours the thing seems to settle down and can see this
cat /proc/partitions | grep sd
8 0 1953514584 sda
816 1953514584 sdb
832 1953514584 sdc
But the devices are non-functional. eg:-
smartctl -a /dev/sda
Smartctl open device: /dev/sda failed: No such device
and
fdisk /dev/sda
Unable to open /dev/sda
So I reckon the JMicron JMB361 controller [02:00.0 SATA controller:
JMicron Technology Corp. JMB361 AHCI/IDE (rev 02)] is not something that
Centos 5 is very keen on.
Its loaded the ahci module for it
uname says
Linux filestore 2.6.18-411.el5 #1 SMP Mon Jul 11 18:16:41 CDT 2016 i686
i686 i386 GNU/Linux
This thread -> https://bugzilla.redhat.com/show_bug.cgi?id=462425 <-
suggests that a fix may have been backported from 2.6.27
Does this look familiar to anyone? And is there a remedy or would I be
best to swap in a better SATA controller in there? Suggestions??
Thanks
Ken
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] C7 Backup problem
Il 09/08/2016 19:15, Valeri Galtsev ha scritto: On Tue, August 9, 2016 11:51 am, Gordon Messmer wrote: On 08/08/2016 11:11 PM, Alessandro Baggi wrote: |78 | backup-fd | 2016-08-08 09:52:57 | B| F | 191,024 | 7,978,295,072 | T | |79 | backup-fd | 2016-08-08 12:10:31 | B| F | 0 | 0 | A | |80 | backup-fd | 2016-08-09 03:05:03 | B| I | 191,024 | 7,978,337,100 | T Job with id 79 was aborted due to disk failure. Why, if I have a job full performed on sunday, on monday I got an incr job with the same size? As far as I know, incremental backups include all changes since the last full backup. You do have a full backup on 8/8 at 9:52, but that isn't the *last* full backup. The last full is 8/8 at 12:10, and it doesn't include anything, so all files are changes since the last full backup. Well, actually incremental is only the difference between current state and last backup (whichever it was: incremental, differential, or full). In other words, to restore the whole thing to today's date you do: 1. restore everything from latest full backup 2. restore everything from latest differential backup, which is difference between latest full backup state and machine state on the day of that differential backup was performed (if you have more than one diff backup since full, you choose latest) 3. restore everything from all incremental backups performed after last differential in chronological order Of course, these are the definitions of full, differential, and incremental that bacula (or bareos) uses. When you are restoring some file or directory on particular day/time bacula (or bareos) does all necessary lookups in database to track full-->differential-->incremental-->...-->incremental history for particular object (file, symlink, directory,...) and only restores relevant copy, the one after which object didn't change till requested day/time. I know the terminology they use is a bit confusing, but I hope the scheme above helps un-confuse it. Valeri Naturally, I could be wrong, but that's what it looks like from here. ___ 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 Hi all, thanks for tips. Reading from bacula.org: "Before doing an Incremental or a Differential backup, Bacula checks to see if there was a prior Full backup of the same Job that terminated successfully. If so, it uses the date that full backup started as the time for comparing if files have changed. If Bacula does not find a successful full backup, it proceeds to do one. Perhaps you canceled the full backup, or it terminated in error. In such cases, the full backup will not be successful. You can check by entering list jobs and look to see if there is a prior Job with the same Name that has Level F and JobStatus T (normal termination). " Now in my env, I've defined a backup jobs and 3 pools (Incr, FULL and Update). In the last case, I've performed a full backup for the job on a different pool (Update pool). This job was canceled by me due to disk failure and at 03:00 incr was perfomed (resulting in a full backup). Now, from bacula.org, if a full backup was stopped/cancelled/geterror (also if the job was runned on another pool), at the next incremental backup (I suppose also differential) a full backup will be performed. It is right? Now if it is right, I will create another job for update backup to remove this issue. Thanks in advance. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS-announce Digest, Vol 138, Issue 4
Send CentOS-announce mailing list submissions to
centos-annou...@centos.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-requ...@centos.org
You can reach the person managing the list at
centos-announce-ow...@centos.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of CentOS-announce digest..."
Today's Topics:
1. CESA-2016:1585 Moderate CentOS 6 qemu-kvm Security Update
(Johnny Hughes)
2. Updated Vagrant Box's are now available : 1607 (Karanbir Singh)
--
Message: 1
Date: Tue, 9 Aug 2016 20:30:28 +
From: Johnny Hughes
To: centos-annou...@centos.org
Subject: [CentOS-announce] CESA-2016:1585 Moderate CentOS 6 qemu-kvm
Security Update
Message-ID: <20160809203028.ga15...@n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii
CentOS Errata and Security Advisory 2016:1585 Moderate
Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-1585.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
e31ec415fe61ba629f3df0854b173a99b106b3c7ce69489fb89d7816e2cbb860
qemu-guest-agent-0.12.1.2-2.491.el6_8.3.i686.rpm
x86_64:
3a2e91869b71112d3ebe89f06175ac1a5faefb95fa9acf4d4f172843875b7a91
qemu-guest-agent-0.12.1.2-2.491.el6_8.3.x86_64.rpm
456d98c996030cf3e9337012b245b9023027d75c8aa65cab07a499b77ddefbe6
qemu-img-0.12.1.2-2.491.el6_8.3.x86_64.rpm
c9916710560c00b92c4efdd82572ec7c494ad873cfbe6ff810f119fced56e06e
qemu-kvm-0.12.1.2-2.491.el6_8.3.x86_64.rpm
f0a8a7e166631410c385a1678542abeaa027a4a7d993368a6ebbca33a734
qemu-kvm-tools-0.12.1.2-2.491.el6_8.3.x86_64.rpm
Source:
90e35bb009e57acb83e6933d8afedac7e04969c5d022ee11462fab0610dd3d3f
qemu-kvm-0.12.1.2-2.491.el6_8.3.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: @JohnnyCentOS
--
Message: 2
Date: Wed, 10 Aug 2016 10:43:34 +0100
From: Karanbir Singh
To: CentOS Announcements List
Subject: [CentOS-announce] Updated Vagrant Box's are now available :
1607
Message-ID: <55ded250-f8c2-d881-9040-1c91b5c20...@centos.org>
Content-Type: text/plain; charset=utf-8
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Updated Vagrant box's are now available for CentOS Linux 7 and CentOS
Linux 6 for x86_64. These are available for the Libvirt and the
VirtualBox providers in Vagrant.
ref: https://atlas.hashicorp.com/centos/boxes/6
https://atlas.hashicorp.com/centos/boxes/7
Release Notes for these images are published at :
https://seven.centos.org/2016/08/updated-centos-vagrant-images-available
- -v1607-01/
We are doing all of our work, including build scripts and build
content for these Vagrant Box's as a part of the CentOS Cloud Instance
SIG. And host the content for contribution and participation at
https://github.com/CentOS/sig-cloud-instance-build/tree/master/vagrant
- - I would like to invite everyone to come join us and help extend the
scope of this work, as well as improve the current results.
regards,
- --
Karanbir Singh, Project Lead, The CentOS Project
+44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS
GnuPG Key : http://www.karan.org/publickey.asc
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)
iQEcBAEBAgAGBQJXqvdGAAoJEI3Oi2Mx7xbtw+sH/2OSI2BJtd4/+lTnpJulQFhM
ogE+dpfHgKvgVpUSm6PPjtmEVjP2x4OC/pALTRiBkQpgk7Mi7DNt9K8qjD7ClDxk
WO/U5rkRTAvIZVFZ5BhXvrN1RzDArxSGdj5oSBnUzKWmc9wGvuX9Rz82FiC173KW
4Am9JeIlrYC5rsFzUqvijyaCG/8MweO6E242/FjfRWe+WTLX59OuVXzuRFVIpcvj
p5WMolJ+j3BzqPYOUWIB8nqaFq+NQ7oHdxo/N/94gSxleT/5uHS+KXLyWeVhhHZE
UgaAztSB/0r/mFmIkHa2ISqtASMGodTVicPKDfF96+5WldRhXLRVCNYtx4+AZLM=
=oBhE
-END PGP SIGNATURE-
--
___
CentOS-announce mailing list
centos-annou...@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce
End of CentOS-announce Digest, Vol 138, Issue 4
***
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Gateway question
On Wed, Aug 10, 2016 at 09:29:15AM +0300, Levente Birta wrote: > I read the document again ... and this talk about accessing this multi-homed > host from the internet... > I have all this configured and working! You say this is working because of the output here? # ip route show default via 192.168.1.1 dev enp3s0 default via 192.168.1.1 dev enp2s0 169.254.0.0/16 dev enp2s0 scope link metric 1002 169.254.0.0/16 dev enp3s0 scope link metric 1003 192.168.1.0/24 dev enp2s0 proto kernel scope link src 192.168.1.12 192.168.1.0/24 dev enp3s0 proto kernel scope link src 192.168.1.13 -- Jonathan Billings ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Gateway question
On 10/08/2016 15:28, Jonathan Billings wrote: On Wed, Aug 10, 2016 at 09:29:15AM +0300, Levente Birta wrote: I read the document again ... and this talk about accessing this multi-homed host from the internet... I have all this configured and working! You say this is working because of the output here? # ip route show default via 192.168.1.1 dev enp3s0 default via 192.168.1.1 dev enp2s0 169.254.0.0/16 dev enp2s0 scope link metric 1002 169.254.0.0/16 dev enp3s0 scope link metric 1003 192.168.1.0/24 dev enp2s0 proto kernel scope link src 192.168.1.12 192.168.1.0/24 dev enp3s0 proto kernel scope link src 192.168.1.13 Yep... default is: # ip route show default via 192.168.1.1 dev enp2s0 169.254.0.0/16 dev enp2s0 scope link metric 1002 169.254.0.0/16 dev enp3s0 scope link metric 1003 192.168.1.0/24 dev enp2s0 proto kernel scope link src 192.168.1.12 192.168.1.0/24 dev enp3s0 proto kernel scope link src 192.168.1.13 and this way not work Then with the following command: #route add default gw 192.168.1.1 dev enp3s0 Hurray ... work :) -- Levi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Gateway question
On 10/08/16 16:29, Levente Birta wrote: And as I said this problem is resolved too ... I asked for another way to achieve this When you add a default gateway with: route add default gw 192.168.1.1 dev enp3s0 you'll note that you now have 2 routes with the same metric of 0 (use route -n to see the metric field - couldn't get ip route to show me the metric). When using ip route command, you need to specify a different metric otherwise it won't take. To me, ip route is doing the right thing as having 2 gateways with the same metric will confuse the routing process. If you need to use ip route to add another default gateway, make sure to use a different metric: ip route add 0/0 via 192.168.1.1 dev enp3s0 metric ak. PS: In my virtual environment *[0]*, the routing tables for tables t2 and t3 appeared incomplete. The route specified in the route files for network 192.168.1.0/24 was missing - most likely cause it was already in the main routing table. Only the default route appeared in the tables $ cat /etc/sysconfig/network-scripts/route-enp0s3 192.168.1.0/24 dev enp0s3 src 192.168.1.12 table t2 default via 192.168.1.1 dev enp0s3 table t2 $ cat /etc/sysconfig/network-scripts/route-enp0s8 192.168.1.0/24 dev enp0s8 src 192.168.1.13 table t3 default via 192.168.1.1 dev enp0s8 table t3 $ ip r l t t2 default via 192.168.1.1 dev enp0s3 $ ip r l t t3 default via 192.168.1.1 dev enp0s8 *[0]* - https://imagebin.ca/v/2r5NJgNEqSgQ ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] XRDB not in our centos6.8 build
I am a bit baffled on this. We recently rebuilt all our servers to CentOS release 6.8 (Final) from a prior 6.x centos release. We ran into a couple of problems such as Java not working (just had to yum install java). It was installed, but unable to create a java machine, until I yum install java solved the problem. But now a user (the big boss) is receiving xrdp errors. And it appears that xrdp is not installed on these newly built servers. I googled xrdp and was unable to decipher if it is needed in our environment (we use sas which does use X11 graphics on the servers to export graphs). If it is needed, wondering why it not included in the groups we have always used for kickstart. When would I need xrdp? or is it one of the leftovers here from a bygone era? Thanks for your response. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] XRDB not in our centos6.8 build
On 2016-08-10, Dan Hyatt wrote: > > I am a bit baffled on this. > > We recently rebuilt all our servers to CentOS release 6.8 (Final) > from a prior 6.x centos release. We ran into a couple of problems > such as Java not working (just had to yum install java). It was > installed, but unable to create a java machine, until I yum install > java solved the problem. > > But now a user (the big boss) is receiving xrdp errors. And it appears > that xrdp is not installed on these newly built servers. > > I googled xrdp and was unable to decipher if it is needed in our > environment (we use sas which does use X11 graphics on the servers to > export graphs). > > If it is needed, wondering why it not included in the groups we have > always used for kickstart. > > When would I need xrdp? or is it one of the leftovers here from a > bygone era? > > > Thanks for your response. The package description (yum info xrdp): "The goal of this project is to provide a fully functional Linux terminal server, capable of accepting connections from rdesktop and Microsoft's own terminal server / remote desktop clients." If you connect to the server(s) using Windows clients, then it's likely that you need this package. I notice that xrdp is in the EPEL repository rather than the standard CentOS repositories. That might explain why it is not installed via kickstart. -- Liam ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
