Message Area
Casually read the BBS message area using an easy to use interface. Messages are categorized exactly like they are on the BBS. You may post new messages or reply to existing messages!

You are not logged in. Login here for full access privileges.

Previous Message | Next Message | Back to The Linux/FreeBSD MBSE BBS Suppo...  <--  <--- Return to Home Page
   Networked Database  The Linux/FreeBSD MBSE BBS Suppo...   [531 / 554] RSS
 From   To   Subject   Date/Time 
Message   Vince Coen    Deon George   Disable creation of softlinks   March 17, 2019
 11:20 PM *  

Hello Deon!

Saturday March 16 2019 11:44, you wrote to All:

 > Howdy,

 > When MBSE tosses incoming files, is there a setting to stop it
 > creating a symlink? I was going to look through the code, but I
 > thought I'd ask here too, in case this route provides a quicker answer
 > ;)

Why ?

Symlinks take up next to no spaces on ext4 etc.


In any event we must maintain the dos 8.3 standard just on case,
1. Downlinks use a dos based BBS - it is possible.
2. When tossing we have to allow for (1.)
3. We should consider enforcing the 8.3 max. rule and not up the name size to 
go to 11
chars as that is not compilying with the DOS standard.



Now all that said,  even with old versions of Windows and the latest OS 
versions of dos
there is support for extended file names as FAT has been replaced for all.

The issue is will it break other systems and I suspect that it could.


1. Another possible upgrade is to go through all of the code base creating new 
coding to
support access to the current Data bases where said code is called as required 
to open,
close, read, write etc each DB (file).

2. Create same again but this time supporting a rdb - MySQL.

This is one of the reasons for (1) but the obvious is to upgrade any system 
from flat
files to rdb.

Now with that done we can create a simple (or not) editor to edit/change etc 
the file
descriptions database.

Next is to be able to produce extra stats during normal ops.

Make it easier to run multi copies of mbse on more than one platform - I do 
find it
annoying to have to run rsync often to keep them in sync as I also have mbse 
on a
Raspberry Pi3B+ and (at one point) a Mac Pro but will be selling it off on 
Ebay soo as it
is not being used at all.
Also a Laptop or two is in the mix as well as my media system which is 24/7 
just to record
on-air programming so it has more than enough space and can also have a 
instance of mbse
the media stuff uses MySql already.

Hopefully this will start cutting down of systems in 24/7 ops and therefore 
the Electricity
bill.

The Pi come on does a rsync then shuts down if needed just as a back up system 
JIC.
It does have a 1Tb drive for boot and data etc.

Vince

--- Mageia Linux v6 X64/Mbse v1.0.7.11/GoldED+/LNX 1.1.501-b20150715
 * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)
  Show ANSI Codes | Hide BBCodes | Show Color Codes | Hide Encoding | Hide HTML Tags | Show Routing
Previous Message | Next Message | Back to The Linux/FreeBSD MBSE BBS Suppo...  <--  <--- Return to Home Page

VADV-PHP
Execution Time: 0.0926 seconds

If you experience any problems with this website or need help, contact the webmaster.
VADV-PHP Copyright © 2002-2024 Steve Winn, Aspect Technologies. All Rights Reserved.
Virtual Advanced Copyright © 1995-1997 Roland De Graaf.
v2.0.140505

Warning: Unknown: open(c:\Sessions\sess_vukj7g1nn900q3ie64enr11677, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0 PHP Warning: session_start(): open(c:\Sessions\sess_vukj7g1nn900q3ie64enr11677, O_RDWR) failed: No such file or directory (2) in D:\wc5\http\public\VADV\include\common.inc.php on line 45 PHP Warning: Unknown: open(c:\Sessions\sess_vukj7g1nn900q3ie64enr11677, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 PHP Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0