<div dir="auto"><div>See that "flt" in the filename of that rpm?<div dir="auto"><br></div><div dir="auto">Fairlite made it. It turned out that basically the official package is assembled wrong and includes a junk file in place of a library. It happened sometime after Centos 6, Centos 6.x versions of the same package are fine.</div><div dir="auto"><br></div><div dir="auto">He figured out whatever they did wrong and compiled a new rpm that includes the actual library.</div><div dir="auto"><br></div><div dir="auto">I don't know if upstream has incorporated the fix yet but I think he did submit a bug report and patch, so it's possible there is a more official package that works by now. It's been a year or more.</div><div dir="auto"><br></div><div dir="auto">-- </div><div dir="auto">bkw</div><div dir="auto"><br></div><br><div class="gmail_quote"><div dir="ltr">On Mon, Feb 4, 2019, 2:36 PM Scott Walker via Filepro-list <<a href="mailto:filepro-list@lists.celestial.com">filepro-list@lists.celestial.com</a> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Mark,<br>
<br>
Brian White was nice enough to help us out with this last year.<br>
<br>
<br>
This is from my notes:<br>
<br>
<br>
<br>
CentOS Version 7 Installation Issues <br>
----------------------------------------------------------------------------<br>
--------------------------------------------------------------<br>
<br>
<br>
You must have libtermcap.so.2 installed!<br>
<br>
On CentOS 7 you must first install libc.so.6<br>
<br>
yum install libc.so.6<br>
<br>
Then install:<br>
<br>
rpm -ivh compat-libtermcap-2.0.8-50flt.el7.centos.i686.rpm<br>
<br>
The above file was provided by Brian. I can email you a copy if desired.<br>
<br>
<br>
<br>
Regards,<br>
Scott Walker<br>
<a href="mailto:scott.walker@ramsystemscorp.com" target="_blank" rel="noreferrer">scott.walker@ramsystemscorp.com</a><br>
<br>
<br>
<br>
<br>
-----Original Message-----<br>
From: Filepro-list<br>
[mailto:<a href="mailto:filepro-list-bounces%2Bscottwalker" target="_blank" rel="noreferrer">filepro-list-bounces+scottwalker</a>=ramsystemscorp.com@lists.celestial.<br>
com] On Behalf Of Fairlight via Filepro-list<br>
Sent: Monday, February 4, 2019 1:58 PM<br>
To: <a href="mailto:filepro-list@lists.celestial.com" target="_blank" rel="noreferrer">filepro-list@lists.celestial.com</a><br>
Subject: Re: New server migration<br>
<br>
My previous comments about XFS were for 32-bit binaries. The bit depth is<br>
important, as even 6.0.0 comes in both 32-bit and 64-bit. If you're running<br>
64-bit, you can use inode64 on any filesystem size, and it shouldn't cause<br>
issues.<br>
<br>
If you're running 64-bit binaries, compat-libtermcap may still be an issue<br>
(probably is). I'd have to revisit that directly to confirm or deny. I<br>
remember that the i686 architecture build target did not exist in the spec<br>
file I got from the official SRPM, but that's only necessary if you run<br>
32-bit binaries. The package itself likely still needs to be built<br>
properly, so you're not relying on what I remember as being the default<br>
broken configuration.<br>
<br>
m-><br>
<br>
<br>
On Mon, Feb 04, 2019 at 11:02:34AM -0500, scooter6--- via Filepro-list thus<br>
spoke:<br>
> To clarify, this is with fP 5.6.10R4<br>
> <br>
> <br>
> <br>
> On Mon, Feb 4, 2019 at 10:22 AM <a href="mailto:scooter6@gmail.com" target="_blank" rel="noreferrer">scooter6@gmail.com</a> <br>
> <<a href="mailto:scooter6@gmail.com" target="_blank" rel="noreferrer">scooter6@gmail.com</a>><br>
> wrote:<br>
> <br>
> > Just purchased our new Dell PowerEdge server that I have installed <br>
> > CentOS<br>
> > 7 on<br>
> ><br>
> > Am migrating from older Dell PowerEdge that has Centos 5.10 on it<br>
> ><br>
> > Is there a 'recipe book' anyone may have on steps to migrate all data<br>
etc?<br>
> > Can a simple copy of the fp directories etc do the trick or does the <br>
> > new server need to go through fpinstall ?<br>
> ><br>
> > I know there are significant changes in CentOS from 5.10 to 6 and <br>
> > then to<br>
> > 7 but in what I've read I don't think there too much of a concern <br>
> > for purposes of what we do here<br>
> ><br>
> > Curious if anyone has done this similar migration and what to watch <br>
> > out for or best steps in order to make this as seamless as possible<br>
> ><br>
> > Thanks for any insight<br>
> ><br>
> > Scott<br>
> > PDM<br>
> ><br>
> -------------- next part -------------- An HTML attachment was <br>
> scrubbed...<br>
> URL: <br>
> <<a href="http://mailman.celestial.com/pipermail/filepro-list/attachments/20190" rel="noreferrer noreferrer" target="_blank">http://mailman.celestial.com/pipermail/filepro-list/attachments/20190</a><br>
> 204/1b6775da/attachment.html> <br>
> _______________________________________________<br>
> Filepro-list mailing list<br>
> <a href="mailto:Filepro-list@lists.celestial.com" target="_blank" rel="noreferrer">Filepro-list@lists.celestial.com</a><br>
> Subscribe/Unsubscribe/Subscription Changes <br>
> <a href="http://mailman.celestial.com/mailman/listinfo/filepro-list" rel="noreferrer noreferrer" target="_blank">http://mailman.celestial.com/mailman/listinfo/filepro-list</a><br>
> <br>
<br>
--<br>
Audio panton, cogito singularis.<br>
_______________________________________________<br>
Filepro-list mailing list<br>
<a href="mailto:Filepro-list@lists.celestial.com" target="_blank" rel="noreferrer">Filepro-list@lists.celestial.com</a><br>
Subscribe/Unsubscribe/Subscription Changes<br>
<a href="http://mailman.celestial.com/mailman/listinfo/filepro-list" rel="noreferrer noreferrer" target="_blank">http://mailman.celestial.com/mailman/listinfo/filepro-list</a><br>
<br>
_______________________________________________<br>
Filepro-list mailing list<br>
<a href="mailto:Filepro-list@lists.celestial.com" target="_blank" rel="noreferrer">Filepro-list@lists.celestial.com</a><br>
Subscribe/Unsubscribe/Subscription Changes<br>
<a href="http://mailman.celestial.com/mailman/listinfo/filepro-list" rel="noreferrer noreferrer" target="_blank">http://mailman.celestial.com/mailman/listinfo/filepro-list</a><br>
</blockquote></div></div></div>