AROS World Exec
Development => AROS Software Development => Topic started by: salass00 on January 14, 2023, 06:29:42 AM
-
Just over seven years after the release of version 53.6 (looks like I never created a binary archive for V53.7 ???) version 54.1 is now available for i386-aros (and also m68k-amigaos) at:
https://github.com/salass00/filesysbox/releases
The V54.0 version which brought the AROS/OS3 back port up to a similar level as the AmigaOS 4 port feature wise was thanks to the work of BSzili.
Changes since the previous release are:
filesysbox.library 53.7 (26.4.2018)
- Got rid of all the GetXxxBase macros.
- Fixed an out of bounds array access in FbxUpdatePaths() which would result
in memory after the FbxFS struct being trashed.
filesysbox.library 54.0 (22.12.2022)
- Added timezone conversion code using locale.library.
- Calculate a path hash for fib_DiskKey unless FBXF_USE_INO flag is set.
- Added FBXF_USE_FILL_DIR_STAT flag to avoid unnecessary getattr() calls for
filesystems like ssh2-handler that already provide all the stat data in
readdir().
- Don't treat ENOSYS return value from FbxSetAmigaProtectionFlags() as an
error.
- Rewrote the FbxFillInfoData() function and made it set id_BytesPerBlock to
512 instead of zero if a volume is not available.
- Modified path handling for Ext2FileSystem which only accepts "/" as path
argument for the file system root directory and not "".
- Rewrote FbxReturnMountMsg() using ReplyPkt() and added a NULL msg safety
check.
- Added some more validity checks when reading FSSM from device node in
FbxSetupFS().
- Added validity checks in code for getting FSSM in FbxQueryMountMsg().
- Changed CHECKVOLUME() macro to return ERROR_NOT_A_DOS_DISK instead of
ERROR_OBJECT_IN_USE when the filesystem is inhibited.
- Added semaphore protection in FbxHandleTimerEvent().
- Added the FbxQueryFS() and FbxQueryFSTags() functions.
- Added the FbxGetSysTime() function.
filesysbox.library 54.1 (14.1.2023)
- A rename operation with exactly the same source and destination is now
treated as a no-op and returns success rather than ERROR_OBJECT_EXISTS.
- Rename operations where the the only change is in letter casing (e.g.
"rename tmp TMP") no longer fail with ERROR_OBJECT_EXISTS on case
insensitive file system implementations.
- Advance the file position in FSWrite() also if write() returns a lower
number of bytes written than was specified.
- Implemented the same charset conversion system that is used in the latest
AmigaOS 4 filesysbox versions. Internally filesysbox still uses UTF-8 for
all strings and conversion only happens when strings are passed to or from
the AmigaDOS API. In order for the conversion to be reversible any UTF-8
characters that do not have an equivalent in the local charset will be
converted into URL-style escape sequences where the character is specified
as a base32 encoded character sequence preceded by a percent symbol.
-
thank you :)
-
filesysbox.library 54.1 (14.1.2023)
- A rename operation with exactly the same source and destination is now
treated as a no-op and returns success rather than ERROR_OBJECT_EXISTS.
On Wanderer this problem has not been solved, it is not possible to rename the same file from lowercase/uppercase or vice versa.
The "move" problem has also not been solved, instead of moving a file/folder, it just makes a copy.
-
@salass00
Thanks for the new release. If you have questions in the future development about AROS specifics, please feel free to contact me. :)
-
@salass00
Thanks for your time and effort. :)
-
Version 54.2 of filesysbox for AROS/OS3 is now available. It is mostly a few bug fixes but a couple of new features are an AVL tree for faster unicode to local charset conversion of non-ASCII characters and ACTION_DIE packet support, which was implemented by BSzili.
@deadwood
Thanks for the offer and I will keep it in mind.
-
thank you :)
-
While working on an AROS port of smb2-handler I found a bug in the OS3/AROS port of filesysbox that resulted in random seek failures (fuse_file_info structures were not cleared when allocated) and a bug in libsmb2 that was only triggered on AROS because of how the AROS libc defines O_RDWR (I've created a pull request on the libsmb2 repo for it).
-
yes we have problems even with the old version of samba at least for a tried to use it at the moment you can not use this protocol, thanks
-
OS3 and AROS ports of smb2-handler are now available at:
https://github.com/salass00/smb2fs/releases
As Zune didn't have an equivalent class that I could use to replace the ClassAct/ReAction requester.class (used for the password requester) I simply disabled this code in the AROS port for now, so on AROS the password will have to be specified in the DOSDriver/Mountlist entry.
-
Thank you, great update !
-
yes great update :D
-
On Aros with Network Manager you usually configure Samba but with the old handler there are problems you can rename the new handler as the old and see if the procedure is successful I do not know about networks :-\
Thank you
-
I tried the handler with no success. :-(
I created a mountlist file called ENNE in DOSdrivers with the suggested lines, using this URL
Startup = "smb://Paolone:mypassword()192.168.xxx.xxx/N$"
I don't get any error message when I try to mount ENNE, however there is no way to access the share. Any help?
-
I connected as a guest I did mount tells me the resource is already there but I do not see the device
Startup = "smb://192.168.1.7/myshare NOPASSWORDREQ"
-
I created a mountlist file called ENNE in DOSdrivers with the suggested lines, using this URL
Startup = "smb://Paolone:mypassword()192.168.xxx.xxx/N$"
I don't get any error message when I try to mount ENNE, however there is no way to access the share. Any help?
The "()" should be an at sign ("@") (see the README in the archive). Annoyingly AROS archives and OS4Depot censors this symbol thinking that it is an e-mail address.
Error messages are written as serial debug output so you have to use sashimi or null-modem cable to capture them.
Also if you didn't add Activate=1 as explained in the readme you have to manually activate the file system by doing something like "dir SMB0:" after it's been mounted.
-
Hi salass00, sorry, but just to better understand the terms used on your string ?
mypc= is it the name of PC-Windows or its IP ?
myuser= is the name of the user of the PC-Windows which "sharing" ?
myshare= is it a volume or folder that the PC-Windows shares ?
Question, SMB can work if AROS is connected to the LAN Network, via a LAN Network Share with the PC
-
Host can be an IPv4 IP address or any host name that can be resolved using the gethostbyname() function. If you can "ping" it using the ping command then it should work with smb2-handler as well.
The username and password should be ones that are recognized by the samba server that you are trying to connect to.
Share is the name of the samba share you want to access, which may or may not be the same as the name of the disk/directory being shared. There is also the possibility to specify a path after the share name (path separator here should be normal slash ("/") not backslash) to only mount a specific sub-directory.
-
I get this error message, where do I go wrong ?
[smb2fs] smb2_connect_share failed. smb2_service failed with : Read from socket failed, errno:104. Closing socket.
-
Errno 104 is ECONNRESET (Connection reset by peer) according to <aros/posixc/errno.h>.
-
How is it resolved ?
-
Googling a little on "ECONNRESET" it could be a sign of a bad network connection. Basically the socket connection was abruptly closed from the other end.
For testing smb2-handler on AROS I've used a 32-bit x86 AROS installation inside VirtualBox to connect to a samba share on the host machine (running Ubuntu 22.04 LTS). The only connection errors I've experienced are that occasionally it times out and I have to restart the samba server ("sudo service smbd restart") to get it working again. I'm assuming that this is because there is no dismount function in AROS so I can't make the file system do a proper disconnect from the samba share (instead I just do a warm or cold reboot when I need to test a new version of the handler).
-
The Connection on my "Fiber" LAN works very well on AROS One x86, I have no problem surfing the Net, also all my PCs connected on the Net have no problem with sharing
Also I noticed that on AROS x86 the Ping works endlessly without stopping and giving the sent/received packets.
I wouldn't want me to do something wrong, could you please attach your example DOSDRiver SMB2 file, maybe others need it too, thanks
-
I created a mountlist file called ENNE in DOSdrivers with the suggested lines, using this URL
Startup = "smb://Paolone:mypassword()192.168.xxx.xxx/N$"
I don't get any error message when I try to mount ENNE, however there is no way to access the share. Any help?
The "()" should be an at sign ("@") (see the README in the archive). Annoyingly AROS archives and OS4Depot censors this symbol thinking that it is an e-mail address.
Error messages are written as serial debug output so you have to use sashimi or null-modem cable to capture them.
Also if you didn't add Activate=1 as explained in the readme you have to manually activate the file system by doing something like "dir SMB0:" after it's been mounted.
I forgot to say I have tried @ as well, but without luck.
-
maybe this string is well
Handler = L:smb2-handler
StackSize = 65536
Priority = 5
GlobVec = -1
Startup = "smb://user:password@nameserver/share directory"
-
Ok, I finally understood why it didn't work for me. I am too much accustomed to Windows' standard volume shares (HOSTNAME/x$ where 'x' is the letter of a volume) and I assumed filesysbox would have supported them, as like as it does for explicit user-made shares. So the current experience I have is
MYHOSTNAME/D$, C$ or N$ are NOT working
while
MYHOSTNAME/SHARE is working
althoug SHARE must be something that I explicitly decided to share with Windows' own commands. So, if I create a MYHOSTNAME/DISK_C share for drive C, it will work with filesysbox.
Any hope to see Windows's standard default shares supported as well?
Moreover:
Also if you didn't add Activate=1 as explained in the readme you have to manually activate the file system by doing something like "dir SMB0:" after it's been mounted.
I have added the line Activate = 1 to the Dosdriver file, but I still need to access the directory some way (either with CLI or placing the volume name in Magellan's apposite field) to have the device actually mounted. Maybe I should try with the icon tooltype?
-
Well I succeeded, AROS One x86 connected to Windows share, it works !!!
The Share Icons automatically appeared on Wanderer !!!
-
SMB2 also works well on OS3, tomorrow I will test with AROS 68k !
-
a friend of mine on another forum has solved the problem soon I will post the problem :)
-
I have already solved it, you have seen the screenshots !
---- Italiano -----
Io ho già risolto, hai visto gli screenshot !
-
yes I know but you have not explained how to solve the problem
-
No one has asked me until now, salass00's Mountlist is also correct for Windows, the problem you encounter is only for sharing on Windows.
With Windows you can share one folder or all folders of the "Public" user.
On Windows what is important is to enable sharing (Network and Sharing Center).
I enclose my Mountlists:
Handler = L:smb2-handler
StackSize = 65536
Priority = 5
GlobVec = -1
Startup =
"smb://UserPC:password@192.168.x.x./Public"
or
"smb://UserPC:password@Name-PC/Public"
"smb://UserPC:password@192.168.x.x/Folder name to share"
or
"smb://UserPC:password@Name-PC/Folder name to share"
At Tooltypes Icon:
ACTIVATE=1
Se vuoi puoi postare il mio commento su Amigapage, se qualcuno ha bisogno di altre info in italiano può contattarmi su Amiganews sulla news dedicata a SMB2
-
ok thank you Carlo :)
-
Excellent "SMB2" on AROS One x86, also works perfectly by VMWare, this I would say is good news and a nice convenience.
As you can see from the screenshot I shared, both a Win10 folder, and the User "Public" with all its folders
(https://ae.amigalife.org/index.php?action=dlattach;topic=1065.0;attach=4178;image)
-
I shared the folder C: on Windows 10 but from Aros does not see it with your settings maybe it's the firewall :-\
-
As I said, you have to enable "all" shares and give all permissions to folders.
-
okay thanks!
-
If I have time and if requested I can add a detailed post in Italian on amiganews, in this way I also please other Italian users who have asked me.
-
After several days of successful use of SMB2 filesystem, I can pinpoint these:
In its startup sequence, Icaros Desktop mounts whatever it finds in DEVS:DOSDrivers with these lines:
Automount >NIL:
Mount >NIL: "DEVS:DOSDrivers/~((.#?)|(#?.info))"
I noticed the syntax slightly changed in recent AROS builds by Deadwood:
Automount >NIL:
Mount >NIL: "DEVS:DOSDrivers/~((.#?)|(#?.info)|(#?.dbg))"
but I guess it only adds the chance to mount something with a .dbg extension.
- If I create a SMB2 dev file with ACTIVATE=1, at next reboot I still need to access the share some way to see it 'mounted' and shown by Wanderer or Magellan. Shouldn't file managers show them automatically? This happens with both ACTIVATE=1 in the file, or in icon's tooltypes, or both.
- If I move the dev file and its icon to WBStartup, as others already pointed out, I effectively get the shares mounted at startup, and correctly shown by Wanderer and Magellan.
- if I DON'T put ACTIVATE=1 anywhere, the smb share can be mounted simply by accessing it, for instance with a DIR command. I guess this should be the correct behavior.
- Although SMB2 shares get mounted correctly almost every time, some times I get some weird result. For instance, shares can get unavailable with no reason after a while. I can access them but no file is shown. It also happened I could save a JPG image TO a share, but couldn't read it aftewrwards (the file didn't get recognized as a JPG and Magellan proposed me to sniff it). This until the next reboot, then the file could be read with no issue.
-
Yes Paolo if you don't use ACTIVATE=1, you have to proceed manually, same thing if you use ACTIVATE=1 but the DosDrivers is located In Storage, here as on Amiga you can mount by typing SMB2: followed by enter, or create the mount buttons on Dopus4.
Regarding the oddity of a failed mount, this may depend on:
- Connection delay, in this case the Mounting through the DOSDriver arrives late and then you will no longer have the share mounting, it could be solved by disassembling/reassembling the DosDriver.
This problem can be avoided if in the Tooltypes of the icon we add a certain delay, better the maximum possible, in this case we will have more time available for assembly.
- Another reason why the Mounting of the DOSDriver fails, is when the shared folder or network drive is used by other app.
- I also add that if the assembly fails, you have to do a cold restart, a hot restart could keep the "assembly error" memorized
For a good sharing with Windows I recommend to create the Network Drive, this way Windows at each reboot will mount the drive automatically available in Windows Explorer, other advice is to have a short name for Windows, otherwise on AROS you will have a volume name too long.
I for example named my PC simply "Win" and the network drive Share, and on AROS I will have the shared volume with the name Wim-Share, see screenshot
See screenshot.
------ Italiano --------
Si Paolo se non utilizzi ACTIVATE=1, bisogna procedere manualmente, stessa cosa se si usa ACTIVATE=1 ma il DosDrivers si trova In Storage, qui come su Amiga si può montare digitando SMB2: seguito da un invio, oppure creare i bottone di montaggio su Dopus4.
Riguardo le stranezze di un montaggio non andato a buon fine, questo può dipendere:
- Ritardo della connessione, in questo caso il Montaggio attraverso il DOSDriver arriva in ritardo e quindi non si avrà più il montaggio della condivisione, si potrebbe risolvere smontando/rimontando il DosDriver.
Questo problema può essere evitato se nel Tooltypes dell'icona aggiungiamo un certo ritardo, meglio il massimo possibile, in questo caso si avrà più tempo disponibile per il montaggio.
- Altro motivo per cui fallisce il Montaggio del DOSDriver, è quando la cartella condivisa o l'unità di rete è utilizzata da altra appicazione.
- Inoltre aggiungo che se il montaggio fallisce, bisogna fare un riavvio a freddo, un riavvio a caldo potremme mantenere memorizzato "l'errore montaggio"
Per una buona condivisione con Windows consiglio di creare l'Unità di Rete, in questo modo Windows ad ogni riavvio monterà l'unità automaticamente disponibile in Explora Risorse, altro consiglio è di avere un nome corto per Windows, altrimenti su AROS si avrà un nome volume troppo lungo.
Io per esempio ho chiamato il mio PC semplicemente "Win" e l'unità di rete Share, e su AROS avrò il volume condiviso con il nome Wim-Share, vedi screenshot
Vedi screenshot
-
Yes Paolo if you don't use ACTIVATE=1, you have to proceed manually, same thing if you use ACTIVATE=1 but the DosDrivers is located In Storage, here as on Amiga you can mount by typing SMB2: followed by enter, or create the mount buttons on Dopus4.
Ok, but this is not coherent with anything else that happens on the system. If I mount a NTFS hard drive partition at startup, I can see it exposed on Wanderer's desktop. Same if I have a CD in the drive. And I am quite confident it also happened with older network shares using the old SMB device. So why should I manually 'enable' it with a command, or placing shares in WBStartup? And what is the difference if ACTIVATE = 1 gives me the exact same result of no ACTIVATE at all?
Maybe this is the exact behavior it should have, but it is not coherent with anything else.
BTW, I am writing a SMB2 shares 'adder' in LUA, which currently supports creating share links on the fly (eg. in RAM when booting AROS from DVD) and also auto mounting shares by moving the device from devs/DosDrivers to WBStartup. But the best solution would be adding SMB2 filesystem support to prefs/Network (and I haven't the skills to do so).
-
But the best solution would be adding SMB2 filesystem support to prefs/Network (and I haven't the skills to do so).
yes where is a best solution
-
But the best solution would be adding SMB2 filesystem support to prefs/Network (and I haven't the skills to do so).
Yes Paolo would be optimal to add SMB2 in Network Prefes, that way the user could add his data and store it in the DOSDrivers.
But beware the DEVS/DOSDRiver the Mountlist is mounted before the connection happens and therefore the mount will fail and never succeed, and consequently you will need to unmount and remount.
Also, those who have a slow connection or network will never be able to connect if started by DEVS/DOSDrivers
With WBstartup you can delay the right amount of time and thus "always" have your Sharing Icon up and running on the Workbench.
Mounting an HD, CD or Floppy does not need a connection, the mounting is immediate, and there is no time to delay.
The difference between ACTIVATE=0 and ACTIVATE=1 has a big difference, with the former you will never have the icon on the Workbench, the latter on the other hand is purposely created to have the device ready right away.
I on OS3 in the DosDrivers do not use any Icon, when I need the peripherals I run the Mountlist from Dopus or from a Shell.
Translated with www.DeepL.com/Translator (free version)
---- Italiano ----
Si Paolo sarebbe ottimale aggiungere SMB2 in Network Prefes, in questo modo l'utente potrebbe aggiungere i suoi dati e memorizzarli nel DOSDrivers.
Ma attenzione il DEVS/DOSDRiver la Mountlist viene montata prima che avvenga la connessione e quindi il montaggio fallirà e non andrà mai a buon fine, e di conseguenza occorrerà smontare e rimontare.
Inoltre chi ha una connessione o una rete lenta non potrà mai connettersi se avviata da DEVS/DOSDRivers
Con WBstartup puoi ritardare il giusto tempo e quindi avere "sempre" la tua Icona della condivisione operativa sul Workbench.
Montare un HD, un CD o un Floppy non ha bisogno di una connessione, il montaggio è immediato, e non ha tempi da rispettare.
La differenza tra ACTIVATE=0 e ACTIVATE=1 ha una grande differenza, con il primo non avrai mai l'icona sul Workbench, il secondo invece è stato creato di proposito per avere da subitio pronta la periferica.
Io su OS3 nei DosDriver non uso nessuna Icona, quand le periferiche mi servono eseguo la Mountlist da Dopus o da una Shell.
-
Ok, this makes sense. Thanks for the explanation.
-
Paolo, for the same reason SMB0 created by Network Prefs did not work, precisely because it does the Mounting from Storage/DOSDrivers "in advance" of the connection.
Network Prefs and native AROS x86 smb-handler work perfectly, if the mount is done "after the connection"
As you can see from the screenshot, I connected to the Windows Network Unit using Network Prefs :)
----- Italiano -------
Paolo, per lo stesso motivo SMB0 creato da Network Prefs non funzionava, proprio perchè effettua il Montaggio da Storage/DOSDrivers "in anticipo" rispetto alla connessione.
Network Prefs e smb-handler nativi AROS x86 funzionano perfettamente, se il montaggio avviene "dopo la connessione"
Come puoi vedere dallo screenshot, mi sono connesso alla Unità di Rete di Windows utilizzando Network Prefs :)
-
I have added some new information here
https://vmwaros.blogspot.com/2023/02/say-welcome-to-simba.html
-
Poalo nice work, if you make it available and allow me to use it, I could put it on AROS One, thank you.
In any case, I don't know if you read my previous post, Network Prefs Works perfectly, if SMB0 you mount it later or move it to WBStartup
-
Poalo nice work, if you make it available and allow me to use it, I could put it on AROS One, thank you.
Ok, let's do a favour each other: would you fix Icaros Desktop themes as well?
-
Paul, you can take as many themes as you want, if you need anything from AROS One, you don't need to ask anything, we are a family and we have to share everything, in the end AROS will be the one to gain.
On AROS One x86 1.9 there are all the Themes listed, only missing are the Gadgets that I ceated lately.
------- Italiano -------
Paolo, puoi prendere tutti i temi che vuoi, se ti serve qualcosa di AROS One, non hai bisogno di chiedere nulla, siamo una famiglia e dobbiamo condividere tutto, alla fine a guadagnare sarà AROS.
Su AROS One x86 1.9 ci sono tutti i Temi elencati, mancano solo i Gadget che ho ceato ultimamente.
-
Paul, you can take as many themes as you want, if you need anything from AROS One, you don't need to ask anything, we are a family and we have to share everything, in the end AROS will be the one to gain.
On AROS One x86 1.9 there are all the Themes listed, only missing are the Gadgets that I ceated lately.
Many thanks. But themes in Icaros Desktop would need a deeper overhaul and I am not sure taking the ones from your distro would be enough. I'd like to have all current themes fixed and ready with the new gadget, but it's definitely a work I haven't the time and the patience to do.
ITA: Grazie mille. Ma le decorazioni di Icaros Desktop avrebbero bisogno di una revisione più approfondita e non sono sicuro che prendere quelle della tua distribuzione sia sufficiente. Mi piacerebbe che i temi già presenti fossero corretti e aggiornati coi nuovi gadget, ma è purtroppo un lavoro che non ho né il tempo di fare, né la pazienza.
-
On Icaros there should be no compatibility problems with my Themes, the only problem is Dopus Magellan does not support any of the Gadgers, they are supported by the GUIs of the applications instead.
On the themes included on Icaros actually needs a lot of work, and that is what I did on the default AROS Themes, on them the Gadgets did not exist.
As mentioned I did not use the Theme Editor, in my opinion too complicated, so I armed myself with a lot of pasience and imagination, and slowly after numerous tests I managed to fix and improve all the ones I had chosen for AROS One.
On this basis always manually I created the variants by capturing the bars from the actual systems.
---- Italiano -----
Su Icaros non ci dovrebbero essere problemi di compatibilità con i miei Temi, l'unico problema è Dopus Magellan che non supporta nessuno dei Gadger, sono invece supportate dalle GUI delle applicazioni.
Sui temi inclusi su Icaros in effetti occorre molto lavoro, ed è quello che ho fatto sui Temi di default di AROS, su di essi i Gadget non esistevano.
Come detto non ho utilizzato l'Editor dei Temi, a mio avviso troppo complicato, per questo motivo mi sono armato di tanta pazienza e fantasia, e piano piano dopo numerosi test sono riuscito a fixare e migliorarli tutti quelli che avevo scelto per AROS One.
Su queste basi sempre manualmente ho creato le varianti catturando le barre dai reali sistemi.
-
@salass00
On AROS x86 the "no password" share Windows works, but I have to make a small change to the mountlist:
This Mountlist "does not work"
Startup = "smb://NamePC/Shared VOLUME=Share-PC NOPASSWORDREQ"
This Mountlist "works fine," however when the request password appears I leave it blank and continue by clicking OK
Startup = "smb://NamePC/Shared VOLUME=Share-PC USER= PASSWORD="
also works well if I set the mountlist like this, when the request password appears I leave it blank and continue by clicking OK
Startup = "smb://NamePC/Shared VOLUME=Share-PC"
As reported HERE (https://eab.abime.net/showthread.php?p=1617122#post1617122) to BSzili, on OS 3.9 e OS3 "mounting with password requester locks Workbench"
Instead on OS 3.1 and AROS no problem entering the password, no locks Workbench, and sharing works fine
-
@salass00
Solved the problem of disabling "on Win7" shared after 15 minutes.
https://learn.microsoft.com/en-us/troubleshoot/windows-client/networking/mapped-drive-connection-to-network-share-lost (https://learn.microsoft.com/en-us/troubleshoot/windows-client/networking/mapped-drive-connection-to-network-share-lost)
Symptoms:
On a computer that runs Windows 7 Service Pack 1, if you map a drive to a network share, the mapped drive may be disconnected after a regular interval of inactivity, and Windows Explorer may display a red X on the icon of the mapped drive. However, if you try to access or browse the mapped drive, it reconnects quickly.
Cause:
This behavior occurs because the systems can drop idle connections after a specified time-out period (by default, 15 minutes) to prevent wasting server resources on unused sessions. The connection can be re-established quickly, if necessary.
-
For those who have difficulty sharing Folders or Wndows Network Drive, with AROS x86 "without using a password," a few weeks ago I created a video Tutorial showing all the steps, and now I offer it here as well:
Link video
https://youtu.be/ZQywYfsE7IA
-
Filesysbox.library compiled from the experimental lockhandler branch now allows shutting down smb2-handler using "assign dismount" on AROS.
https://github.com/salass00/filesysbox/tree/lockhandler
Unfortunately however because "assign dismount" doesn't remove the device node it is not possible to mount the handler again using the same device name. IMO it should not be the responsibility of filesysbox to remove and free the device node as it was not created by it in the first place.
-
Thanks for the development of this magnificent software, you can download the new version of Filesysbox.library, so you can test it !
-
Just tested a new filesystem on AmigaOS 3 (FS-UAE on Ubuntu):
(https://www.dropbox.com/s/i1sao2oap8iztoq/ssh2fs-os3.png?raw=1)
An AROS port should not be too far behind... I just need to get AmiSSL AROS headers so I can compile it (statically linked OpenSSL is not an option).
-
Many thanks for your effort
-
filesysbox.library V54.4 is now out:
https://github.com/salass00/filesysbox/releases
-
many thanks :)
-
filesysbox.library V54.4 is now out:
https://github.com/salass00/filesysbox/releases
Perfect now you can unmount the share on VMware, also found a way to remount "the same volume"
This feature discovered by accident, to unmount and mount, you need to use 2 commands, and only in that sequence, otherwise it will not work.
Basically you have to dismount SMB2 first with Assign dismount and then with UnMount, done that it is possinile to reassemble SMB2.
UnMount I had compiled it on AROS One x86 some time ago !
On AROS One it will create a script that will do automatic dismount but also automatic Dismount and Mount (useful after the 15 minute shutdown with shared Windows)
(https://ae.amigalife.org/index.php?action=dlattach;topic=1065.0;attach=5061;image)
-
Since HERE (https://eab.abime.net/showthread.php?t=113017&page=18) on AEB we were discussing the functionality of "Assign Dismount" on Os3, I wanted to show that even on OS3 "Assign Dismount" works well, in fact better than on AROS, in fact there is no need to use UnMount.
On OS3 to unmount the share, you have to run "Assign Dismount" 2 times, once to unmount the DosDRIVERS and once to unmount the "Volume", see attached video.
https://youtu.be/Ty1Jc4rp4XA
-
On OS3 to unmount the share, you have to run "Assign Dismount" 2 times, once to unmount the DosDRIVERS and once to unmount the "Volume", see attached video.
This only removes the doslist entries, but leaves the file system running in the background. It's basically just pulling the rug out from under the file system...
The correct method is to invoke ACTION_DIE packet (this will remove all volume nodes and hand over any active locks/notifications to the lock handler process) and if this succeeds then remove the device node. "Assign dismount" on AROS does invoke ACTION_DIE but does not remove the device node.
-
ssh2-handler 53.1 is now released for AmigaOS 3 and AROS:
https://github.com/salass00/ssh2fs/releases/tag/V53.1
Not sure why, but it won't show up on the releases page:
https://github.com/salass00/ssh2fs/releases
-
Many Thanks :)
All Best
-
Thanks salass00, for me what was important is to reuse a share "disconnected from Windows after 15 Minutes"
After the 15 Minutes the share was unusable, and you had to mount another DOSDriver with other name example SMB3, SMB4 etc..
Now inceve using the 2 commands mentioned above, the "expired" share after the 15 Minutes can be Mounted again without any problem, see attached video:
https://youtu.be/v0kkvXbY7W0