Re: [CentOS] Security Updates not properly flagged

2021-06-21 Thread Lange, Markus
Hi,

freely does not imply free to redistribute. Of course these
informations are available from various sources which allow
redistribution, but it takes time to aggregate them - time that someone
need to spend doing the necessary research.

best regards,
Markus

On Mon, 2021-06-21 at 13:53 +0200, Gionatan Danti wrote:
> Il 2021-06-21 13:34 Pete Biggs ha scritto:
> > CentOS does not provide the metadata to allow the --security flag
> > to
> > work.
> 
> Right.
> 
> > It doesn't provide it because that information from Redhat is
> > proprietary and not open source.
> 
> This is not my understanding. From what I can see, updates which
> patches 
> CVEs are freely readable on Red Has site. For example:
> CVE: https://access.redhat.com/security/cve/cve-2021-3156
> UPDATE: https://access.redhat.com/errata/RHSA-2021:0221
> 
> Historically the CentOS team refused to provide such metadata due to
> the 
> added work required. Now with Stream, and the demise of classic
> CentOS, 
> security updates are even less probable (ie: a rolling release is
> often 
> wholly updated).
> 
> Regards.
> 
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] https://blog.centos.org/2020/12/future-is-centos-stream/

2020-12-08 Thread Lange, Markus
Hi,

this is really bad news.

Back in 2014 [1], sadly no one at RH seems to remember...

"Some of the things that are not changing:
- - The CentOS Linux platform isn't changing. The process and methods
built up around the platform however are going to become more open,
more inclusive and transparent.
- - The sponsor driven content network that has been central to the
success of the CentOS efforts over the years stays intact.
- - The bugs, issues, and incident handling process stays as it has
been
with more opportunities for community members to get involved at
various stages of the process.
- - The Red Hat Enterprise Linux to CentOS firewall will also remain.
Members and contributors to the CentOS efforts are still isolated from
the RHEL Groups inside Red Hat, with the only interface being srpm /
source path tracking, no sooner than is considered released. In
summary:  we retain an upstream.

Feel free to reach out if you have specific concerns about how this
change impacts your CentOS story. URLs mentioned at the bottom of this
email should be a good starting point."

Crossing fingers that alternatives emerge soon.

Best regards,
Markus

[1] 
https://lists.centos.org/pipermail/centos-announce/2014-January/020100.html


On Tue, 2020-12-08 at 09:06 -0500, Rich Bowen wrote:
> The future of the CentOS Project is CentOS Stream, and over the next 
> year we’ll be shifting focus from CentOS Linux, the rebuild of Red
> Hat 
> Enterprise Linux (RHEL), to CentOS Stream, which tracks just ahead of
> a 
> current RHEL release. CentOS Linux 8, as a rebuild of RHEL 8, will
> end 
> at the end of 2021. CentOS Stream continues after that date, serving
> as 
> the upstream (development) branch of Red Hat Enterprise Linux.
> 
> Meanwhile, we understand many of you are deeply invested in CentOS
> Linux 
> 7, and we’ll continue to produce that version through the remainder
> of 
> the RHEL 7 life cycle. 
> https://access.redhat.com/support/policy/updates/errata/#Life_Cycle_Dates
> 
> CentOS Stream will also be the centerpiece of a major shift in 
> collaboration among the CentOS Special Interest Groups (SIGs). This 
> ensures SIGs are developing and testing against what becomes the
> next 
> version of RHEL. This also provides SIGs a clear single goal, rather 
> than having to build and test for two releases. It gives the CentOS 
> contributor community a great deal of influence in the future of
> RHEL. 
> And it removes confusion around what “CentOS” means in the Linux 
> distribution ecosystem.
> 
> When CentOS Linux 8 (the rebuild of RHEL8) ends, your best option
> will 
> be to migrate to CentOS Stream 8, which is a small delta from CentOS 
> Linux 8, and has regular updates like traditional CentOS Linux
> releases. 
> If you are using CentOS Linux 8 in a production environment, and are 
> concerned that CentOS Stream will not meet your needs, we encourage
> you 
> to contact Red Hat about options.
> 
> We have an FAQ - https://centos.org/distro-faq/ - to help with your 
> information and planning needs, as you figure out how this shift of 
> project focus might affect you.
> 
> [See also: Red Hat's perspective on this. 
> https://www.redhat.com/en/blog/centos-stream-building-innovative-future-enterprise-linux]
> 
> ___
> 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] systemd syslog.target

2020-08-11 Thread Lange, Markus
Hi,

if I get it correctly [1] it is not recommended to use After=syslog but
it's not forbidden. But as the syslog.service should not be enabled it
is not running anyway. As the man page states:

"If a unit foo.service contains a setting Before=bar.service and both
units are being started, bar.service's start-up is delayed until
foo.service is started up. Note that this setting is independent of and
orthogonal to the requirement dependencies as configured by Requires="
[2]

it should have no effect including this after even if it's not
necessary.

I Would recommend not including the After as it's somehow deprecated
since systemd v38 (January 2012!).

The only effect you may observe is that if syslog.service is started
through socket activation your service might be delayed starting up
resulting in an non-optimal startup time. However, this might take some
ms barely anyone would notice that.

best regards
Markus

[1] https://www.freedesktop.org/wiki/Software/systemd/syslog/
[2] https://www.freedesktop.org/software/systemd/man/systemd.unit.html

On Tue, 2020-08-11 at 09:15 +0100, ctcard wrote:
> 
> Thanks Simon,I think my question got a bit lost amongst all the grub
> issues - does anyone else have information about whether any
> references to syslog.target in systemd unit files can be
> removed?ChrisSent from Samsung Mobile on O2
> 
>  Original message 
> From: Simon Matter via CentOS  
> Date: 31/07/2020  10:02  (GMT+00:00) 
> To: CentOS mailing list  
> Subject: Re: [CentOS] systemd syslog.target 
> 
> Hi,>> I've noticed that there are several systemd unit files in
> CentOS 7 and 8> with the optionAfter=syslog.targetin the [Unit]
> section, but since systemd> version 198 syslog.target has not
> existed.I deduce from this that> "After=syslog.target" is ignored by
> systemd and can therefore be removed.> Is this correct? I am writing
> some systemd unit files for our own services> which previously used
> init.d scripts, so I want to ensure I'm not causing> problems by
> omitting "After=syslog.target"ChrisSent from Samsung Mobile on>
> O2Interesting, there is really no syslog.target on either CentOS 7 or
> 8. Butif a service needs classic syslog, shouldn't it have another
> After=instead?Simon___Cen
> tOS mailing listcen...@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] Slightly OT : where is Cipherli.st ?

2020-03-16 Thread Lange, Markus
Hi,

not exactly your question but it might help you anyway.

Mozilla provides an great config generator for many commonly used
applications for multiple application and openssl versions [1].

You can choose between 3 security levels. They reflect how old/out-
dated your clients you need to support are.

best regards,
Markus

[1] https://ssl-config.mozilla.org/
-- 
IT 2.3
Tel: +49 69 1525 - 1786

On Mon, 2020-03-16 at 14:53 +0100, Nicolas Kovacs wrote:
> Hi,
> 
> Up until recently, I've been using the excellent https://cipherli.st
> resource
> to configure SSL on my servers.
> 
> I tried to take a look again today, but the site seems to have
> vanished.
> 
> Anybody knows what's happened ? Has it moved ?
> 
> Cheers,
> 
> Niki
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] About license at redistribution

2019-11-14 Thread Lange, Markus
Hi,

at first I'm not part of the CentOS Project nor I'm a lawyer.

But may I can answer your questions.
According to the CentOS About page "CentOS Linux is no-cost and free to
redistribute." [1]. So as you are planning to redistribute it should be
fine to do. While redistributing you also need to consider the legal
section [2]. However as you are planning a business you should involve
a lawyer to make it clear to you in your special legal situation!

To your second question: Yes you definitely should do that, as you make
profit from the great work the maintainers do and can't make profit if
they discontinue doing this great work. But no one can force you to,
it's up to you to take what the community provides without giving
anything back.

Best Regards
Markus


[1] https://www.centos.org/about/
[2] https://www.centos.org/legal/

On Thu, 2019-11-14 at 18:08 +0900, sensor make wrote:
>  Hello.
> 
> I'd like to ask about license issue.
> Now I'm planning to make and sell some measurement system controlled
> by PC.
> There is no technical issue but I don't have enough information about
> license.
> 
> I will do the following,
> 
>  1) Install CentOS and my applications on the PC.
>  2) Sell the PC as a measurement device.
>  3) Distribute DVD made from CentOS iso image file to the user if
> he/she
> needs.
> 
>  Question 1.
>  Is there no problem from the view point of CentOS license ?
> 
>  Question 2.
>  Should I donate to CentOS community ?
> 
> 
> Best Regards.
> ___
> 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] XRDP idle disconnect

2019-09-27 Thread Lange, Markus
Hi,

there is an option in sesman.ini called KillDisconnected. This could be
what you are looking for [1]. There is also an option called
DisconnectTimeLimit to set your custom timeout [2]. But I haven't
tested this method.

A more graceful method should be letting your desktop environment
terminate idle sessions. Once the desktop session is terminated sesman
will notice and clean up what ever it still keeps. For GNOME you may
take a look at [3].

But! be aware of data loss due to unsaved data in any programms in the
sessions and all the other ugly things that probably happen on an
ungraceful session/application termination and the amount of support
requests you might get.

best regards,
Markus

[1] ;; KillDisconnected - kill disconnected sessions
; Type: boolean
; Default: false
; if 1, true, or yes, kill session after 60 seconds
KillDisconnected=false

[2] ;; DisconnectedTimeLimit - when to kill idle sessions
; Type: integer
; Default: 0
; if not zero, the seconds before a disconnected session is killed
; min 60 seconds
DisconnectedTimeLimit=0

[3] 
https://people.gnome.org/~pmkovar/system-admin-guide/automatic-logout.html

On Fri, 2019-09-27 at 16:47 +0300, Todor Petkov wrote:
> Hello,
> 
> I have a machine with Centos7, Plasma desktop and XRDP. Many people
> log in the machine, and then press 'X' of the rdp window, instead of
> logging off. Is there a way to automatically log off their sessions,
> similar to MS Windows setting?
> 
> Thanks,
> ___
> 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] Why is the branch c6 empty for every rpm packages?

2019-08-27 Thread Lange, Markus
Hi,

I can't tell you why CentOS 6 isn't available an git.centos.org anymore
but I think your assumption is right.
You may find what you need on http://vault.centos.org/ .

Best regards
Markus

On Tue, 2019-08-27 at 16:31 +0800, Qiying Wang wrote:
> Hi,
> 
> I wan't to find the sqlite & python rpm packaging files in
> git.centos.org,
> but I found that the branch c6 for centos 6 are all empty.
> 
> Is that because centos 6 reached its end? Or where can I find the
> packaging
> files?
> 
> Best regards,
> 
> WqyJh
> ___
> 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] systemd

2019-02-08 Thread Lange, Markus
Hi,

for compiling Kernel Modules it might be worth looking at DKMS.
DKMS is available through EPEL and is designed to compile Kernel
Modules in an automated way when ever Kernel Updates are made.

For more Informations on DKMS see [1, 2, 3].

best regards,
Markus

[1] https://github.com/dell/dkms
[2] https://linux.die.net/man/8/dkms
[3] https://wiki.archlinux.org/index.php/Dynamic_Kernel_Module_Support

On Thu, 2019-02-07 at 09:40 -0500, Jerry Geis wrote:
> Hi All -  I have a systemd service file to start my application.
> 
> Part of my service file is:
> [Service]
> Type=forking
> ExecStart=/path to start
> ExecStop=/path to stop
> RemainAfterExit=yes
> 
> This works fine "normally".
> 
> However - when I do a "yum update; and reboot"  my script detects a
> kernel
> change and now does a number of "recompiling" steps for drivers and
> such
> before starting my application. Somewhere along the way that just
> stops.
> I'm half way into recompiling those drivers and it just stops.
> 
> Is there something else I need in the service file ?
> 
> Thanks
> 
> Jerry
> ___
> 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] looking for a tool to convert my running system into a installation dvd

2019-02-04 Thread Lange, Markus
Hi,

probably you are looking for Anacondas kickstart feature.
A kickstart installation can be used to install all your packages and
provide basic system configuration. It is possible, but not meant to be
used as, to even configure the system as you have it currently running
using post-install scripts. [1] seems to be a quite good resource to
get started with kickstart installations.

This is meant to be used if you plan a roll-out on multiple (many)
machines where an manual installation is not applicable (in this case
some kind of configuration management should be used to keep track of
the configurations deployed).
If you just want a single (or just some few) system(s) as hole clone of
your system (including full configuration), backup and restore seems
better.

best regards
Markus Lange

[1] https://people.centos.org/jperrin/Kickstart2.html

On Mon, 2019-02-04 at 17:44 +0100, Ralf Prengel wrote:
> Hallo,
> I m looking for a tool to convert my running system into a
> installation dvd.
> Thanks for hint.
> I found some tools working more or less for debian.
> 
> Thank for hints
> Ralf
> 
> Von meinem iPad gesendet
> ___
> 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] [Marketing Mail] Re: [Marketing Mail] Re: Cups freeze when remote server is unavailable

2018-10-30 Thread Lange, Markus
Hi Patrick,

you can install your lab printers using the lp* / cups* commands in
your ks file or using scripts, see centos / redhat / arch / cups docu
for more informations on that (arch wiki got some examples).
For the home printers you can use what ever method available, for ease
the web interface / GUI configuration tool should be a good choice.

Markus

On Mon, 2018-10-29 at 19:58 +0100, Patrick Bégou wrote:
> Hi Lange,
> 
> thanks for these links. Following John reply I goes back and deeper
> in
> looking for documentation. Using the web interface is not an option
> as I
> have many laptops to set up and they are all automatically
> (re)installable from a PXE boot + kickstart in case of trouble. So
> all
> must be setup automatically (using command lines in the kickstart
> file)
> and user must be allowed to add their own home printer.
> 
> I understand some things this afternoon, discover cups-browsed that
> was
> not available in 1.4 version (CentOS6), understand why it was not
> working (the laboratory cups version was 1.4 on a debian server and
> CentOS7 has 1.6.x now) discover also that ppd files are deprecated in
> newer cups version (> 2.x ?)
> 
> Time is to go deeper in all these documentations and build a scenario
> to
> set up cups in these automatic installations process. I agree, it was
> not a bug, just misunderstanding new cups software behaviour.
> 
> Patrick
> 
> Le 29/10/2018 à 17:15, Lange, Markus a écrit :
> > Hi,
> > 
> > John tries to tell you:
> > Revert your configuration changes to the config file and use the
> > local
> > web interface / lp* / GUI Print Server Configuration tool to setup
> > all
> > printers at work and / or at home using these tools.
> > 
> > This method needs a local cups instance that works if your OS is
> > running (if a printer is not reachable for printing cups can still
> > keep
> > the job in it's queue until the printer is reachable).
> > You can find an linux.com article on Printer Setups in [1] (mainly
> > selected for its screenshots of cups web interface and not for its
> > actuality) which should give you all information's to get it work.
> > 
> > At least for desktop setups cups should be running by default, see
> > "systemctl status cups" to check if it's running.
> > 
> > For a more in-depth view on cups I can recommend reading the
> > archwiki
> > [2].
> > 
> > best regards
> > Markus
> > 
> > [1] https://www.linux.com/learn/linux-101-printing
> > [2] https://wiki.archlinux.org/index.php/CUPS
> > 
> > 
> > On Mon, 2018-10-29 at 15:35 +0100, Patrick Bégou wrote:
> > > Hi John
> > > 
> > > thanks for your quick reply. If it is not a bug, as I was reading
> > > on
> > > the
> > > web, it is some misunderstanding from me.
> > > Running cups 1.4.2 (CentOS6) I was using the "BrowsePoll"
> > > directive
> > > in
> > > cupsd.conf. So the printers were automatically known from the
> > > central
> > > server of the lab. And home printers were working fine with this
> > > setup too.
> > > In CentOS7, with cups 1.6.3, this directive does not exist any
> > > more
> > > and
> > > reading the doc I had understood that it was replaced by the
> > > client.conf
> > > file. Reading your answer suggest it is not true.
> > > 
> > > So could you tell me or suggest reading on the right manner to
> > > reproduce
> > > my previous centos6 setup ?
> > > 
> > > Sorry for this newbie question, I'm not very familiar with cups
> > > setup.
> > > 
> > > Patrick
> > > 
> > > 
> > > Le 29/10/2018 à 14:45, John Hodrien a écrit :
> > > > On Mon, 29 Oct 2018, Patrick Bégou wrote:
> > > > 
> > > > > Any idea ?
> > > > 
> > > > I don't see that this is a bug.
> > > > 
> > > > In client.conf you're telling it which server to use,
> > > > exclusively. 
> > > > You're not
> > > > adding remote printers, you're telling it which CUPS server to
> > > > talk
> > > > to
> > > > everytime you use CUPS clients commands.  You don't even need
> > > > to
> > > > run a
> > > > local
> > > > CUPS server if you configure it like this.
> > > > 
> > > > If you want a machine to work at both ends, I'd suggest you
> > > > don't
> > > > do
> > > > this, and
>

Re: [CentOS] [Marketing Mail] Re: Cups freeze when remote server is unavailable

2018-10-29 Thread Lange, Markus
Hi,

John tries to tell you:
Revert your configuration changes to the config file and use the local
web interface / lp* / GUI Print Server Configuration tool to setup all
printers at work and / or at home using these tools.

This method needs a local cups instance that works if your OS is
running (if a printer is not reachable for printing cups can still keep
the job in it's queue until the printer is reachable).
You can find an linux.com article on Printer Setups in [1] (mainly
selected for its screenshots of cups web interface and not for its
actuality) which should give you all information's to get it work.

At least for desktop setups cups should be running by default, see
"systemctl status cups" to check if it's running.

For a more in-depth view on cups I can recommend reading the archwiki
[2].

best regards
Markus

[1] https://www.linux.com/learn/linux-101-printing
[2] https://wiki.archlinux.org/index.php/CUPS


On Mon, 2018-10-29 at 15:35 +0100, Patrick Bégou wrote:
> Hi John
> 
> thanks for your quick reply. If it is not a bug, as I was reading on
> the
> web, it is some misunderstanding from me.
> Running cups 1.4.2 (CentOS6) I was using the "BrowsePoll" directive
> in
> cupsd.conf. So the printers were automatically known from the central
> server of the lab. And home printers were working fine with this
> setup too.
> In CentOS7, with cups 1.6.3, this directive does not exist any more
> and
> reading the doc I had understood that it was replaced by the
> client.conf
> file. Reading your answer suggest it is not true.
> 
> So could you tell me or suggest reading on the right manner to
> reproduce
> my previous centos6 setup ?
> 
> Sorry for this newbie question, I'm not very familiar with cups
> setup.
> 
> Patrick
> 
> 
> Le 29/10/2018 à 14:45, John Hodrien a écrit :
> > On Mon, 29 Oct 2018, Patrick Bégou wrote:
> > 
> > > Any idea ?
> > 
> > I don't see that this is a bug.
> > 
> > In client.conf you're telling it which server to use, exclusively. 
> > You're not
> > adding remote printers, you're telling it which CUPS server to talk
> > to
> > everytime you use CUPS clients commands.  You don't even need to
> > run a
> > local
> > CUPS server if you configure it like this.
> > 
> > If you want a machine to work at both ends, I'd suggest you don't
> > do
> > this, and
> > instead run a local CUPS server, and add remote printers to that
> > local
> > server.
> > 
> > jh
> > ___
> > 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] [Marketing Mail] Re: LVM and Backups

2018-09-19 Thread Lange, Markus
On Wed, 2018-09-19 at 08:55 +0200, Alessandro Baggi wrote:
> Il 18/09/2018 17:14, Gordon Messmer ha scritto:
> > On 9/17/18 11:38 PM, Alessandro Baggi wrote:
> > > Il 17/09/2018 22:12, Gordon Messmer ha scritto:
> > > > That doesn't look right.  It should look more like 1) stop or
> > > > freeze 
> > > > all of the services (httpd and database), 2) make the snapshot,
> > > > 3) 
> > > > start or thaw all of the services, 4) mount the snapshot, 5)
> > > > back up 
> > > > the data, 6) remove the snapshot.
> > > 
> > > About database setup I perform backups via pg_dump so how the
> > > snapshot 
> > > affects pgsql database? What your suggestion I must perform
> > > database 
> > > backup copying only filesystem file and not pgsql.sql database
> > > dump?
> > 
> > 
> > If you want a plain-text dump of the DB, you can do that before the
> > LVM 
> > snapshot sequence: 1) pg_dump, 2) stop or freeze all of the
> > services 
> > (httpd and database), 3) make the snapshot, 4) start or thaw all of
> > the 
> > services, 5) mount the snapshot, 6) back up the data, 7) remove
> > the 
> > snapshot.
> > 
> > Typically, the reason you want to use snapshots for the backup is
> > that 
> > you don't need to do pg_dump to get a consistent DB backup,
> > though. 
> > pg_dump style backups are extremely slow to restore.  If you freeze
> > the 
> > DB, make a snapshot, and thaw, you can make a safe, consistent
> > backup of 
> > the DB files directly, and restore in minimal time.
> > 
> > 
> > > > Are you using bacula's built-in snapshot support, or are you
> > > > rolling 
> > > > your own?
> > > 
> > > No I'm using pre/post job script where I have lvm commands to
> > > create 
> > > and destroy snapshot volume.
> > > 
> > 
> > I really recommend using a ready-made process rather than rolling
> > your 
> > own.  Bacula has snapshot support.  Alternately, my project can
> > manage 
> > snapshots and handle freezing / thawing PostgreSQL services.  I
> > think 
> > it's a better option than Bacula's, but either is better than 
> > reinventing this wheel.
> > 
> > https://bitbucket.org/gordonmessmer/dragonsdawn-snapshot
> > 
> > ___
> > CentOS mailing list
> > CentOS@centos.org
> > https://lists.centos.org/mailman/listinfo/centos
> 
> Thank you for the suggestion.
> 
> I don't know why I considered pg_dump better then filesystem backup.
> At 
> this moment I prefer pg_dump because in this mode I can restore data
> on 
> different version of postgresql. With filesystem dump I can restore
> only 
> for a specific version. Is right?
> 
> I will give a try.
> 
> Thank you again for suggestions.
> 
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos

Hi,

an restore may need additional attention while restoring database files
to a different version of postgres. However, while the versions does
not differ that much (an official upgrade path exists, or no layout
change was made between the versions) the files work just as if you
updated the database using yum (check out spec file from source pkg to
find out what happens on package upgrades, you may need to do upgrade
steps manually).

This should only be a problem when you try to restore to a new major
version of postgres. But in that case I would recommend an additional
pg_dump backup to have a save fallback.

best regards

ps: I do not use postgres, please understand my testimony as not tested
practically.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] [Marketing Mail] Centos7 update: epel no route to host

2018-05-11 Thread Lange, Markus
Hi,

there seem to be some problems with the epel. I'm not sure if your
problem (have the same on my systems) relate to this, however see epel-
devel Mailinglist [1] for more information on current epel problems.

Best regards
Markus

[1] https://lists.fedoraproject.org/archives/list/epel-de...@lists.fedo
raproject.org/thread/WC7T2SOTX2LDC2X3FKSBLZQR3LB2PUDP/

On Fri, 2018-05-11 at 12:35 +0200, johan.vermeul...@telenet.be wrote:
> Hello All, 
> 
> I' have a laptop who's not booting to graphical screen today. 
> Actualy I had several the last few days, related to cr repo. 
> 
> This one won't update, EM: 
> 
> updates | 3.4 kB 00:00:00 
> epel/x86_64/updateinfo FAILED 
> https://mirror.ynet.sk/epel/7/x86_64/repodata/3ada5bcbccaa9772074a773
> b15bd01dd48e753a184ebecfed590de6c389ada03-updateinfo.xml.bz2: [Errno
> 14] curl#7 - "Failed connect to mirror.ynet.sk:443; No route to
> host" 
> 
> I reinstalled epel-release package, same issue remains. 
> 
> I guess I could update without epel, but maybe this will make things
> worse. 
> 
> Any advise would be appreciated. 
> 
> Greetings, J 
> ___
> 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] [Marketing Mail] Re: [External] Re: [Marketing Mail] Create CentOS 6 system as "clone" of another - with LVM and different disk sizes

2018-04-13 Thread Lange, Markus
Hi,

I could be wrong, but afaik clonezilla makes bit-accurate copies of the file
system like dd does. Therefore, no configurations should be adapted. Usually
Linux doesn't care where it runs, as long as the underlying 'hardware' (or
virtual hardware) architecture matches.

However, there are a number of configuration files that need to be modified for
such clones, including network settings (local or on your dhcp server),
{crypt,fs}tab (if no bit-accurate copy of the filesystem was used),
/etc/host{s,name} depending on your network setup.

best regards,
 - MarkusOn Fr, 2018-04-13 at 15:45 +0200, Toralf Lund wrote:
> On 13/04/18 15:32, Lange, Markus wrote:
> > 
> > Hi,
> > 
> > You can simply boot a live system to create your partition layout and copy
> > it
> > over the existing system with rsync. Once your system is copied, you will
> > need
> > to customize all hardware-dependent configuration files such as
> > {crypt,fs}tab,
> > network configurations, bootloader and so on depending on your setup.
> > 
> > Don't forget to install the bootloader afterwards!
> > 
> > You can also install a minimal system and use a live system to copy the
> > files
> > from the existing server to the new one (e.g. with rsync -a). This way you
> > do
> > not have to create the partition layout and bootloader manually.
> > 
> > Using clonezilla would only replace the part of copying the files and
> > installing
> > the bootloader, all other settings still have to be made.
> Actually, I don't believe that's quite true. I've "cloned" to dissimilar 
> hardware in the same manner before, and found that there was special 
> handling of various hardware dependent config files, so that I didn't 
> get set-up  for the "wrong" type.
> 
> - Toralf
> 
> > 
> >   Rsync should be much
> > faster for data transfer.
> > 
> > Best regards,
> >   - Markus
> > On Fr, 2018-04-13 at 14:46 +0200, Toralf Lund wrote:
> > > 
> > > Hi,
> > > 
> > > I just found myself having to set up a new CentOS 6 system with a nearly
> > > identical configuration to an existing host, so I thought I would just
> > > 
> > >   1. Do a minimal install to set up partitions etc. on the new system.
> > >   2. Create an image of the existing system using Clonezilla
> > >  (https://urldefense.proofpoint.com/v2/url?u=http-3A__www.clonezilla.o
> > > rg=DwIGaQ=KV_I7O14pmwRcmAVyJ1eg4Jwb8Y2JAxuL5YgMGHpjcQ=Q0oqxzgUp3xCCI
> > > iJDwS-RbNDndQ-KZDhj8wwveNoqU4=LuCuhEh29vlP9l-
> > > Vakjf6lKeZVlmfp_AaqPakYDOV1c=7DzBbYmBU7fUsxgvVL-
> > > 59HG_y2uuwR1jxcbXX5skfGM= )
> > >   3. Run a Clonezilla restore on the new system.
> > > 
> > > - as I though it would be a lot simpler than replicating the exact
> > > package selection, installing the same users, doing the same manual
> > > config edits (which are required) etc.
> > > 
> > > It turns out that it wasn't quite as easy, though. The problem is that
> > > the system use LVM2 volumes for the filesystems, and the new host has a
> > > slightly smaller disk than the other, and Clonezilla seems unable to
> > > restore to a volume that's smaller than the one that was cloned - even
> > > if the actual data fits.
> > > 
> > > I guess I could temporarily reduce the LVM volume sizes on the existing
> > > units and clone again, but I'd rather not if I can avoid it. Just
> > > copying file-by-file could be an option, too, but I somehow feel less
> > > comfortable doing that than the above; there is something about the way
> > > I could end up with a mixture of my "minimal install" and the "cloned"
> > > data, I suppose.
> > > 
> > > Does anyone have any other ideas about how I might achieve what I want?
> > > 
> > > - Toralf
> > > 
> > > ___
> > > CentOS mailing list
> > > CentOS@centos.org
> > > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.centos.org_mail
> > > man_listinfo_centos=DwIGaQ=KV_I7O14pmwRcmAVyJ1eg4Jwb8Y2JAxuL5YgMGHpjcQ
> > > =Q0oqxzgUp3xCCIiJDwS-RbNDndQ-KZDhj8wwveNoqU4=LuCuhEh29vlP9l-
> > > Vakjf6lKeZVlmfp_AaqPakYDOV1c=qjiIy57nu_S3OjTO1LYJjQmDFY6GkzLkKvn2F5IrUqo
> > > =
> > ___
> > CentOS mailing list
> > CentOS@centos.org
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.centos.org_mailma
> > n_listinfo_centos=DwIGaQ=KV_I7O14pmwRcmAVyJ1eg4Jwb8Y2JAxuL5YgMGHpjcQ=Q
> > 0oqxzgUp3xCCIiJDwS-RbNDndQ-KZDhj8wwveNoqU4=LuCuhEh29vlP9l-
> > Vakjf6lKeZVlmfp_AaqPakYDOV1c=qjiIy57nu_S3OjTO1LYJjQmDFY6GkzLkKvn2F5IrUqo
> > =
> 
> ___
> 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] [Marketing Mail] Create CentOS 6 system as "clone" of another - with LVM and different disk sizes

2018-04-13 Thread Lange, Markus
Hi,

You can simply boot a live system to create your partition layout and copy it
over the existing system with rsync. Once your system is copied, you will need
to customize all hardware-dependent configuration files such as {crypt,fs}tab,
network configurations, bootloader and so on depending on your setup.

Don't forget to install the bootloader afterwards!

You can also install a minimal system and use a live system to copy the files
from the existing server to the new one (e.g. with rsync -a). This way you do
not have to create the partition layout and bootloader manually.

Using clonezilla would only replace the part of copying the files and installing
the bootloader, all other settings still have to be made. Rsync should be much
faster for data transfer.

Best regards,
 - Markus
On Fr, 2018-04-13 at 14:46 +0200, Toralf Lund wrote:
> Hi,
> 
> I just found myself having to set up a new CentOS 6 system with a nearly 
> identical configuration to an existing host, so I thought I would just
> 
>  1. Do a minimal install to set up partitions etc. on the new system.
>  2. Create an image of the existing system using Clonezilla
> (http://www.clonezilla.org)
>  3. Run a Clonezilla restore on the new system.
> 
> - as I though it would be a lot simpler than replicating the exact 
> package selection, installing the same users, doing the same manual 
> config edits (which are required) etc.
> 
> It turns out that it wasn't quite as easy, though. The problem is that 
> the system use LVM2 volumes for the filesystems, and the new host has a 
> slightly smaller disk than the other, and Clonezilla seems unable to 
> restore to a volume that's smaller than the one that was cloned - even 
> if the actual data fits.
> 
> I guess I could temporarily reduce the LVM volume sizes on the existing 
> units and clone again, but I'd rather not if I can avoid it. Just 
> copying file-by-file could be an option, too, but I somehow feel less 
> comfortable doing that than the above; there is something about the way 
> I could end up with a mixture of my "minimal install" and the "cloned" 
> data, I suppose.
> 
> Does anyone have any other ideas about how I might achieve what I want?
> 
> - Toralf
> 
> ___
> 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