Subj : Re: G.3 compileriler warnings on CentOS 8
To : Vincent Coen
From : James Digriz
Date : Fri Sep 04 2020 02:21 pm
Vincent Coen wrote to James Digriz:
<cut>
VC>
VC> > Yes, and thanks to all who replied! Now I just have to write a *$#%!
VC> > systemd unit file to get it running. ;-)
VC>
VC> No you don't.
VC>
VC> In my system and in relation to reading the manual I have in directory
VC> xinetd.d a file called mbsebbs and the content is :
VC>
<cut file>
VC>
VC> I have a lot of files for doing different tasks so you might have 2 - 5
VC> etc.
VC>
VC> Now my home directory for mbse, is at /home and NOT /opt
VC>
VC> This can be set up using ./configure --prefix=/home
VC>
Yes, I'm using the same setup. For some reason, though, the start script
didn't
work at first. Of course, after I made my comment, it now works. <shrug>.
Something called systemd-sysv-generator apparently lets the mbsed init scripts
operate correctly.
VC>
VC> The reason is that if I decide to load up another distro held on my system
VC> drives which can be a DASD or a SSD I do not have to reinstall and copy
VC> over
VC> the content of mbse which in my case is over 16Gb - well over.
VC> { Also my system has links to a IBM m/f environment etc so it starts
VC> adding up
VC> as to all of the changes required for each distro - bit of a pain ! }
VC>
VC> Then checking the end of that pass to ensure it will load it all up in
VC> /home/mbse before moving forwards in the build.
VC>
Kewl. Are you running Hercules or are you on real iron?
jbdigriz
Greetings, James Digriz
email:
[email protected]
--- MBSE BBS v1.0.7.18 (GNU/Linux-x86_64)
* Origin: DragonsWeb Labs BBS 1:123/755 (1:123/755)
