My question then is there a way or an option in the Mystic installer to permit installation to an existing directory? I realize I could simply install to say /home/bbs/mystic but I would prefer /home/mystic if possible.
On 12-10-19 10:20, Jeff Smith wrote to Mystic People <=-
My question then is there a way or an option in the Mystic installer
to permit
installation to an existing directory? I realize I could simply
install to say
/home/bbs/mystic but I would prefer /home/mystic if possible.
My current install will be to a Raspberry pi3 with a second SD card mounted as /home/mystic. Hence my desire to install Mystic to the
existing /mystic directory.
On 12-10-19 10:20, Jeff Smith wrote to Mystic People <=-
I know it was discussed, but I can't recall if the installer was changed to permit (with warnings) installation into an existing directory.
My current install will be to a Raspberry pi3 with a second SD card
mounted as /home/mystic. Hence my desire to install Mystic to the
existing /mystic directory.
If push comes to shove, you could always install it into /home/mystic/install,
then simply do the following: mv /home/mystic/install/* /home/mystic
On 12-10-19 20:45, Jeff Smith wrote to Vk3jed <=-
Yeah... I seem to recall being one of the people asking that question
:)
I currently have Mystic installed on a Linux PC and I did install
Mystic to a SATA 4TB HD setup/mounted as /home and let the installer create the /home/mystic directory. Then I created the Linux user
"mystic" and both Linux and Mystic were happy.
If push comes to shove, you could always install it intohome/mystic/install,
then simply do the following: mv /home/mystic/install/* /home/mystic
I remember pondering that option but wasn't sure if there would be
paths specified during the install that I couldn't change later. As in Mystic set to look in /home/mystic/install and the path couldn't be changed wherever needed in the configs. I recall one piece of BBS/FTN software where I had to change literally hundreds of paths manually in multiple files if a change was required.
Hello There, I don't seem to remember things as I used to. That
said. I recall that in the past the Mystic installer would not
permit Mystic to be installed IF the destination directory already existed. It seemed that the installer insisted on creating the destination directory itself and would abort if the directory
already existed in Linux. I had to install Mystic and THEN create
the Linux user "mystic". My question then is there a way or an
option in the Mystic installer to permit installation to an
existing directory? I realize I could simply install to say /home/bbs/mystic but I would prefer /home/mystic if possible.
My current install will be to a Raspberry pi3 with a second SD
card mounted as /home/mystic. Hence my desire to install Mystic to
the existing /mystic directory. Jeff --- BBBS/Li6 v4.10 Toy-4 *
Origin: FSXNET: The Ouija Board - bbs.ouijabrd.net (21:1/128)
On 12-10-19 20:45, Jeff Smith wrote to Vk3jed <=-
I currently have Mystic installed on a Linux PC and I did install
Mystic to a SATA 4TB HD setup/mounted as /home and let the installer
create the /home/mystic directory. Then I created the Linux user
"mystic" and both Linux and Mystic were happy.
Yeah that'll work, but you have to use a 2 step process to move it to a volume >mounted on /home/mystic. Or did you decide to mount /home instead? (which is
common configuration in Linux).
changed wherever needed in the configs. I recall one piece of BBS/FTN
software where I had to change literally hundreds of paths manually in
multiple files if a change was required.
Cood point. I think there is a way to simply change all paths at once in Mystic, because it's done for Windows -> Linux and vice versa migrations.
On 12-15-19 18:04, Jeff Smith wrote to Vk3jed <=-
The SATA HD was mounted by the Linux installer as /home. Mystic
installer created /home/mystic. Then Linux created the user "mystic". I then checked and verified that ownership and permissions were correct.
I have also done SBBS installs to say /sbbs and took ownership of the
sbbs directory by the user that SBBS would be run as. I have never been partial to running a BBS as root. Too many potential problems and
security concerns.
On 12-15-19 18:08, Jeff Smith wrote to Vk3jed <=-
It's not that hard to write a script to look in selected file(s) and do
a search and replace based upon specific text strings.
Yeah chown -R is your friend for these situations. ;)
On 12-20-19 07:57, Phoobar wrote to Vk3jed <=-
Yeah chown -R is your friend for these situations. ;)
Tried that right before bed the other night & didn't work...but last night...worked perfectly. Almost fell out of my chair when it did work.
Tried that right before bed the other night & didn't work...but last night...worked perfectly. Almost fell out of my chair when it did worOnly reasons I've had it not work are:
1. Typos ;)
2. I wasn't logged in as root when I issued the command.
On 12-15-19 18:08, Jeff Smith wrote to Vk3jed <=-
It's not that hard to write a script to look in selected file(s) and do
a search and replace based upon specific text strings.
That's assuming text files, but yeah in that instance, sed is your friend. :)
On 12-20-19 11:40, Jeff Smith wrote to Vk3jed <=-)
That's assuming text files, but yeah in that instance, sed is your friend.
Yeah, that is assuming that the installer doesn't write an installation path to a file that can't changed/edited later. I have run into that situation before.
| Sysop: | Eric Oulashin |
|---|---|
| Location: | Beaverton, Oregon, USA |
| Users: | 128 |
| Nodes: | 16 (1 / 15) |
| Uptime: | 03:52:41 |
| Calls: | 1,549 |
| Calls today: | 3 |
| Files: | 2,153 |
| Messages: | 313,476 |
| Posted today: | 1 |