This is the instruction for the install in the download -
sudo chown myusername:myusergroup /mystic
./install

So I think I would type

sudo chown david:adm /mystic

...then...

./install

Not working for me. Suggestions?

Perhaps "myusergroup" isn't adm, but I thought it was. I'm new at this and am uncertain.

Many thanks.

David, aka Centinel (if I'm on your bbs)

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

On 05/31/17, David Holden pondered and said...

This is the instruction for the install in the download -
sudo chown myusername:myusergroup /mystic
./install

So I think I would type

sudo chown david:adm /mystic

I think the idea is to run sudo ./install if you wish to install to a
directory outside your home dir. Then run the sudo chown line you mention to set the correct user name and group there after...

I may be wrong.. but that's kinda what I thought was the go.

David, aka Centinel (if I'm on your bbs)

Welcome to the BBS Scene David :)

Best, Paul

--- Mystic BBS v1.12 A33 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (3:770/100)

Hello David,

This is the instruction for the install in the download -
sudo chown myusername:myusergroup /mystic
./install
So I think I would type
sudo chown david:adm /mystic
...then...
./install

I have Mystic A33 installed on a Ubuntu 16.10 machine and it installed and runs
fine. I created a user and group named "bbs". Logged in as that user and created a temp install directory of "myst". So... In linux that would actually
be "/home/bbs/myst". I uncompressed the Mystic install files to the "myst" directory and ran "./install" from the "myst" directory. When the installer asks for a base Mystic directory. I then specified "/home/bbs/mystic" for the first directory specification. Upon hitting enter. The remaining directory paths were changed from "/mystic/" to "/home/bbs/mystic/" automatically. I then
simply proceeded with the install which took all of a couple seconds.

Not working for me. Suggestions?
Perhaps "myusergroup" isn't adm, but I thought it was. I'm new at this and >am uncertain.

Here the user that Mystic was installed and is run under is "bbs" and the group is also "bbs". When the various servers here are loaded they will load initially as root in order bind to the specified ports <1024 but actually run as user "bbs".


Jeff

--- BBBS/Li6 v4.10 Toy-3
* Origin: The OuijaBoard - Anoka, MN (1:282/1031)

This is the instruction for the install in the download -
sudo chown myusername:myusergroup /mystic
./install

So I think I would type

sudo chown david:adm /mystic

...then...

./install

You can do:

sudo ./install

Then once you install it you would CHOWN the directory you've installed to to the user and group you want the BBS to run under. So if you install to
/mystic then you'd:

chown -R me:group /mystic

Make sure you don't forget the -R though, so it recusively owns everything under the mystic directory.

--- Mystic BBS v1.12 A34 (Windows/64)
* Origin: Sector 7 [Mystic BBS WHQ] (1:129/215)

David Holden wrote to All <=-

@MSGID: <592F7B4B.3112.fido-mystic@freeway.apana.org.au>
This is the instruction for the install in the download -
sudo chown myusername:myusergroup /mystic
./install

So I think I would type

sudo chown david:adm /mystic

...then...

./install

Actually, I'd do the chown after installation

chown -R david:adm /mystic

Though I've always used a period instead of a colon between user and group.

chown -R david.adm /mystic

Not working for me. Suggestions?

See above.


... Oh - ah, I'm going to blow it up.
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (3:633/410)

Jeff Smith wrote to David Holden <=-

I have Mystic A33 installed on a Ubuntu 16.10 machine and it installed
and runs fine. I created a user and group named "bbs". Logged in as
that user and created a temp install directory of "myst". So... In
linux that would actually be "/home/bbs/myst". I uncompressed the
Mystic install files to the "myst" directory and ran "./install" from
the "myst" directory. When the installer asks for a base Mystic
directory. I then specified "/home/bbs/mystic" for the first directory specification. Upon hitting enter. The remaining directory paths were changed from "/mystic/" to "/home/bbs/mystic/" automatically. I then simply proceeded with the install which took all of a couple seconds.

I run Mystic on a R-Pi, but the theory is essentially the same. If I was installing from scratch again, I'd do (while logged in as root):

1. Create a user (I use mystic). On the Pi, by default, the user gets its own group, also "mystic".

Run the Mystic installer. Install to /mystic (default)

After installation

chown -R mystic.mystic /mystic

At this point, log in as the mystic user and run ./mystic -cfg

Finally, log in as root and get the startup scripts working. :)

Not working for me. Suggestions?
Perhaps "myusergroup" isn't adm, but I thought it was. I'm new at this and
am uncertain.

Here the user that Mystic was installed and is run under is "bbs" and
the group is also "bbs". When the various servers here are loaded they will load initially as root in order bind to the specified ports <1024
but actually run as user "bbs".

Same here, except my user is "mystic" rather than "bbs" (personal choice, nothing more), but the principle is the same.


... Brecht's Hierarchy of Needs: Grub first, then ethics.
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (3:633/410)

On Wednesday, May 31, 2017 at 8:47:48 PM UTC-5, David Holden wrote:

This is the instruction for the install in the download -
sudo chown myusername:myusergroup /mystic
./install

So I think I would type

sudo chown david:adm /mystic

...then...

./install

Not working for me. Suggestions?

Perhaps "myusergroup" isn't adm, but I thought it was. I'm new at this and

am uncertain.

Many thanks.

David, aka Centinel (if I'm on your bbs)

I am curious to know why a couple of you have a user created to run the BBS?

By the way, from previous attempts I'm stumbling over the fact that somehow I made a "mystic" folder in the home directory. I noticed it won't just let me delete it. So when I hit F2 in the instructions to install from the Mystic screen I get an error, '
that folder already exists'.

David/Centinel

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

Hello David,

On Wednesday, May 31, 2017 at 8:47:48 PM UTC-5, David Holden wrote:

Perhaps "myusergroup" isn't adm, but I thought it was. I'm new at this and

am uncertain.

I am curious to know why a couple of you have a user created to run the BBS?

By the way, from previous attempts I'm stumbling over the fact that somehow I made a "mystic" folder in the home directory.

As in /home/Mystic? Or /home/<user>/Mystic? For ease of installation I installed Mystic using a preexisting user. In my case the user was "bbs". So I then already had a /home/bbs directory and let the Mystic installer create /home/bbs/Mystic

I noticed it won't just let me delete it.

What ownership and permissions exist for the "Mystic directory that you created? Was the directory creation done as a different user? If it is /home/Mystic that you created then I believe that you would need to delete
that directory as "root". But that is the "rub" as Mystic needs to create the base Mystic directory itself. Hence the reason I installed Mystic in the manner
in which I did.

So when I hit F2 in the instructions to install from the Mystic
screen I get an error, that folder already exists'.

The Mystic installer needs to create the specified Mystic directory itself. That is why I install/update Mystic from a separate location (Temp install directory) and let the installer do the directory creation.


Jeff

--- BBBS/Li6 v4.10 Toy-3
* Origin: The OuijaBoard - Anoka, MN (1:282/1031)

On Friday, June 2, 2017 at 2:45:30 AM UTC-5, Jeff Smith wrote:

As in /home/Mystic? Or /home/<user>/Mystic? For ease of installation I installed Mystic using a preexisting user. In my case the user was "bbs". So

I

then already had a /home/bbs directory and let the Mystic installer create /home/bbs/Mystic

I noticed it won't just let me delete it.

What ownership and permissions exist for the "Mystic directory that you created? Was the directory creation done as a different user? If it is /home/Mystic that you created then I believe that you would need to delete that directory as "root". But that is the "rub" as Mystic needs to create the base Mystic directory itself. Hence the reason I installed Mystic in the

manner

in which I did.

So when I hit F2 in the instructions to install from the Mystic
screen I get an error, that folder already exists'.

The Mystic installer needs to create the specified Mystic directory itself. That is why I install/update Mystic from a separate location (Temp install directory) and let the installer do the directory creation.

New to Ubuntu here. So I think the ownership is the super-user sudo. Originally
I attempted the commands in the unix instruction and I think the directory was created then, not sure. But now it's created and I have to get rid of it to let
the installer
do it.

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

On 05/31/17, David Holden pondered and said...

This is the instruction for the install in the download -
sudo chown myusername:myusergroup /mystic
./install

So I think I would type

sudo chown david:adm /mystic

...then...

./install

Not working for me. Suggestions?

Perhaps "myusergroup" isn't adm, but I thought it was. I'm new at this and am uncertain.

Is the ./install file executable? Do you have the correct install archive? Make sure you aren't using the PI version on the x86 install. I think that Mystic linux is for 32bit and not 64bit. You may need to install compat drivers.

- ++ - .
++-+-+++|+++-+ ++| +-++|+++-+--- cyberia.darktech.org
+|- +||+--++-- +++ +-+|+++-- -+- San Jose, CA.
++ ++ +

--- Mystic BBS v1.12 A33 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (3:770/100)

chmod 755 *

In the area where you extract the install.

Make sure you have permissions wherever you install
Mystic

On 11:36 16/06 , Darryl Perry wrote:

On 05/31/17, David Holden pondered and said...

This is the instruction for the install in the download -
sudo chown myusername:myusergroup /mystic
./install

So I think I would type

sudo chown david:adm /mystic

...then...

./install

Not working for me. Suggestions?

Perhaps "myusergroup" isn't adm, but I thought it was. I'm new at this and am uncertain.

Is the ./install file executable? Do you have the correct install archive? >Make sure you aren't using the PI version on the x86 install. I think that >Mystic linux is for 32bit and not 64bit. You may need to install compat >drivers.

N++ ++ N++ .
++-+N++++|+++-+ ++N++ N++N++|+++-+N++N++cyberia.darktech.org +|N+++||+N++++N++ ++N++ N+++|++N++N++N++N++San Jose, CA.
++ N++N++ N++

--- Mystic BBS v1.12 A33 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (3:770/100)

--
yrNews Usenet Reader for iOS
http://appstore.com/yrNewsUsenetReader

--- Mystic BBS/NNTP v1.12 A33 (Linux/64)
* Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (1:130/210)