| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Incredible! |
Hello mark! 04 Aug 16 15:17, you wrote to me: AL>> Technically, you don't need to keep two copies. The INSTALL AL>> instructions, AAMOF, suggest unpacking the tarball to /tmp as the AL>> root user, running the SETUP.sh script to create the MBSE users AL>> and home directories, and then logging in as the mbse user to AL>> unpack and build the software. ml> that sounds more like what i'd expect... i'll have to dig in a li'l ml> deeper as i'm pretty sure that the permissions and ownership likely ml> need to be adjusted so the mbse user can get to them... That's the main reason for logging in as mbse before the final build of the software. Unpacking the source archive (or cloning the code from a repository) as mbse sets the owner/group of all the source files to mbse:bbs. The initial build is also done as user mbse. Then you run make install as root to install the files to the proper places and adjust ownership/permissions as needed. Andrew --- GoldED+/LNX 1.1.5-b20160322* Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219) SEEN-BY: 203/0 633/267 280 640/384 1384 690/682 712/620 848 770/1 @PATH: 320/219 203/0 640/384 712/848 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.