User:Cpow
UUID
Christopher Pow
3104 East 53rd Street
Minneapolis, MN 55417-2044
M:(612)910-1271
Other pages
Driver Project
Vfile AIO
Vfile /etc
OA Example Test
DVMS Update Notes
zlibdev
vfile sockets
mmap in DVMS
deos-headers package proposal
Loewen Audit Finding Analysis
Driver FP Fixup
kernel-mode vfile user API proposal
dwsockets remaining work
TTE TSN
TODO from team meetings
- 10/7/2025: Add PCR to update CDD for vfile (new libs)
Docker notes
FTP madness
FTP from docker to a target on the farm works but it needs to be in passive mode if any data transfer is to work. I solved this by adding:
alias ftp='ftp -np'
to .bash_aliases
Launching stuff?
Within Docker it might be nice to launch HTM pages (/desk/help, etc.). This is a solution to that, but not to much else, unfortunately.
To get an experience similar to cygstart in Cygwin which uses the system assigned tool to open a file, do the following:
- Add 'xdg-utils' to your build-docker package list.
- xdg-open can then be used to open files with their assigned tool, like FireFox opening .htm files.
To enhance the above experience and make it more cygstart-like, add the following to your .bashrc:
function open() {
xdg-open "$@">/dev/null 2>&1 &
}
Subversion madness
Subversion in docker keeps asking for your login credentials. The only solution I've found is this from https://stackoverflow.com/a/74521736:
Saving plaintext passwords was intentionally disabled in svn starting from version 1.12. There's no configuration key to re-enable this feature. The only way to make Subversion save your password as a plain text is to enable it at the compile time.
However, Subversion is still able to read the plaintext passwords. And there's an official script to manually save your password as a plain text.
Consider removing any edits from ~/.subversion/config and ~/.subversion/servers. Just remove both files if in doubt. Use your svn server at least once (e.g. checkout something). Verify and permanantly accept the server server certificate fingerprint, if asked. This would generate ~/.subversion/auth/svn.simple/xxxxx file (where "xxxxx" is some hash), but there would be no password in it yet. Run svn auth and note the Authentication realm: <https://myserver.mydomain:12345> VisualSVN Server string in the output. Use the official workaround script to store your password as plaintext: wget https://svn.apache.org/repos/asf/subversion/trunk/tools/client-side/store-plaintext-password.py chmod +x store-plaintext-password.py ./store-plaintext-password.py -u your_username "<https://myserver.mydomain:12345> VisualSVN Server" doublecheck that ~/.subversion/auth/svn.simple/xxxxx now actually contains your password chmod 700 ~/.subversion/auth/svn.simple/xxxxx chmod 700 ~/.subversion/auth/svn.simple try using your svn server again (e.g. svn update). Just tested on svn version 1.14.1 (r1886195), installed with simply apt install subversion, on Ubuntu 22.
Hash collision checking
The following strings have the same CRC value:
b5a7b602ab754d7ab30fb42c4fb28d82
d19f2e9e82d14b96be4fa12b8a27ee9f
This is useful for testing hash collisions.
