OpenBox Re-spin

[manyroads]

Pieces like communication (network) seems sporadic and unpredictable with the repo versions of OB.

As an aside, I m becoming something of a fan of iceWm... after I add a few tweaks and a decent set of themes and icons. Fluxbox themes is a bit too 'retro', for me (clunky looking). jwm is not bad but seems a bit unstable, especially with networking from Virtualbox. Actually antiX in general seems not to like VirtualBox very much. I can make it work but getting privs to work so that Guest Additions installs and allows 'seamless' shared file access is much harder than it ought to be.

I have not tried installing OB on antiX yet...

[anticapitalista]

Actually antiX in general seems not to like VirtualBox very much. I can make it work but getting privs to work so that Guest Additions installs and allows 'seamless' shared file access is much harder than it ought to be.

I have not tried installing OB on antiX yet...

You must use VB 6 version.
Also, do remember that this antiX version is an alpha release and will have lots of issues.

[dolphin_oracle]

Pieces like communication (network) seems sporadic and unpredictable with the repo versions of OB.

As an aside, I m becoming something of a fan of iceWm... after I add a few tweaks and a decent set of themes and icons. Fluxbox themes is a bit too 'retro', for me (clunky looking). jwm is not bad but seems a bit unstable, especially with networking from Virtualbox. Actually antiX in general seems not to like VirtualBox very much. I can make it work but getting privs to work so that Guest Additions installs and allows 'seamless' shared file access is much harder than it ought to be.

I have not tried installing OB on antiX yet...

add your user to the "vboxsf" user group (login/logout) to use shared file access

[Jerry3904]

Easiest with User Manager

[manyroads]

[...]
You must use VB 6 version.
Also, do remember that this antiX version is an alpha release and will have lots of issues.

I will make certain that v 6 is what is installed... I think it is actually defaulting to a version 5.whatever

It's not a problem though. I'm awaiting the next release for further tests.

[manyroads]

add your user to the "vboxsf" user group (login/logout) to use shared file access

Did that. I get a different problem when I miss on that error/setting. The version I have works (sort of), I simply need to do everything using the root verison of SpaceFM. Access from non-root to the shared drive is not happy unless its from root. I do think it may have something to do with the version 5 vs. 6 of VB issue mentioned by @anticapitalista. I'll test that specifically in the next iteration.

[dolphin_oracle]

add your user to the "vboxsf" user group (login/logout) to use shared file access

Did that. I get a different problem when I miss on that error/setting. The version I have works (sort of), I simply need to do everything using the root verison of SpaceFM. Access from non-root to the shared drive is not happy unless its from root. I do think it may have something to do with the version 5 vs. 6 of VB issue mentioned by @anticapitalista. I'll test that specifically in the next iteration.

FWIW I'm using VB 5.2.24 with the latest antiX alpha 19a1 as a guest (VB 6 guest additions preinstalled) and not having any problems with shared folder access, either reading or writing.

[manyroads]

FWIW I'm using VB 5.2.24 with the latest antiX alpha 19a1 as a guest (VB 6 guest additions preinstalled) and not having any problems with shared folder access, either reading or writing.

When I get home (I have a 2000 mile drive this weekend)... I'll give things another try. I have been having fun with the new antiX and learned a LOT! I will keep at things. I look forward to the journey... (in MX/antiX) as well as on the road.

[Head_on_a_Stick]

Pieces like communication (network) seems sporadic and unpredictable with the repo versions of OB.

I don't understand, openbox doesn't have anything to do with networking, can you be more specific?

Also, if this is to be used as a respin then how are users supposed to update openbox if it has been installed from source?

The openbox project is not being developed any more but new vulnerabilities could yet be discovered in the code.

[manyroads]

Actually it is others who have told me the current version does not communicate. I have no problem with the issue. You'll find mention of the problem somewhere in this stream.

As for the update issue... I had not thought any of that through since this was being done for me and I was sharing what I'd done thus far. I certainly agree with yoour point about updates and usability. What I have done in the past is share my final scripts and let people do with them as they will. In that sense my work is more a 'working proof of concept' rather than a respin.

As for OB being abandoned or 'functionally stabilized', I was not aware. That actually seems reason enough to move on to another wm (like iceWM which is still alive, so far as I can tell.).