-
Posts
6,573 -
Joined
-
Days Won
8
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by BRiT
-
-
So, what happened earlier today, where the forums were completely broken? Was it another "nothing was changed" event? 🤣
- 1
-
Isn't that for "Re-add" as in add back in?
- 1
-
Search using Community Apps for "wazuh" and it should find their dockers that are listed at https://hub.docker.com/r/wazuh/wazuh
-
1 hour ago, DeadDevil6210 said:
Looks like you need to install the development tools like GCC (gnu c compiler) and possibly others in that Ubuntu vm.
-
9 hours ago, DeadDevil6210 said:
unzip unRAIDServer-6.12.2-x86_64.zip -d unRAIDServer cd unRAIDServer
That should be 2 separate commands:
unzip unRAIDServer-6.12.2-x86_64.zip -d unRAIDServer
cd unRAIDServer
-
9 hours ago, flinte said:
Just a thought, could nerdtools not install a package manager like apt or yum/dnf (whatever base slackware uses, im not very familiar with slackware).
Slackware does not have one.
-
Or incorrect parameters set in BIOS for the ram.
-
And amazingly they're not all "Have you tried turning it off and on again?". Truly a great resource and help for the community.
- 1
- 2
-
-
Was it specifically on 6.12.2 or any 6.12.x build?
-
The 7z file format does NOT store file permissions. You will always need to use a post process script to set permissions to what you want them to be.
You may be able to adjust the behavior somewhat by setting "umask".
From Wiki:
QuoteThe 7z format does not store filesystem permissions (such as UNIX owner/group permissions or NTFS ACLs), and hence can be inappropriate for backup/archival purposes.
A workaround on UNIX-like systems for this is to convert data to a tar bitstream before compressing with 7z. But it is worth noting that GNU tar (common in many UNIX environments) can also compress with the LZMA2 algorithm ("xz") natively, without the use of 7z, using the "-J" switch. The resulting file extension is ".tar.xz" or ".txz" and not ".tar.7z". This method of compression has been adopted with many distributions for packaging, such as Arch, Debian (deb), Fedora (rpm) and Slackware. (The older "lzma" format is less efficient.)[8] On the other hand, it is important to note, that tar does not save the filesystem encoding, which means that tar compressed filenames can become unreadable if decompressed on a different computer.. -
32 minutes ago, TomB822 said:
This is a "feature" of Samba. The Windows archive bit is mapped to the executable bit on Linux. It drives me crazy at work because people are constantly checking in text files to git as executable.
Taken from here: https://www.samba.org/samba/docs/using_samba/ch08.html
Three Samba options decide whether the bits are mapped: map archive, map system , and map hidden. These options map the archive, system, and hidden attributes to the owner, group, and world execute bits of the file, respectively. You can add these options to the [data] share, setting each of their values as follows:
[data]
map archive = yes
map system = yes
Map hidden = yes
After that, try creating a file in the share under Unix—such as hello.java—and change the permissions of the file to 755. With these Samba options set, you should be able to check the permissions on the Windows side and see that each of the three values has been checked in the Properties dialog box. What about the read-only attribute? By default, Samba sets this whenever a file does not have the Unix owner write permission bit set. In other words, you can set this bit by changing the permissions of the file to 555.
The default value of the map archive option is yes, while the other two options have a default value of no. This is because many programs do not work properly if the archive bit is not stored correctly for DOS and Windows files. The system and hidden attributes, however, are not critical for a program's operation and are left to the discretion of the administrator.
-
Your syslog shows errors of sorts with commands to SDD and SDH.
You probably should wait for someone else to chime in, but I wouldn't do anything at all just yet.
-
Afaik, disks are only marked as disabled (red x) when a write to them fails.
-
3 minutes ago, Thunder7ga said:
So I guess we have to wait for an update to the container to be available....
That or switch over.
I switched over to the other one mentioned. In CA, searching for "speedtest tracker" produces 2 results. The other one being from "ZappyZaps" repository.
Their forum thread is at:
- 1
-
The docker is setup to use version 1.0.0 and the current version is 1.2.0
The version of the file needed is https://install.speedtest.net/app/cli/ookla-speedtest-1.2.0-linux-x86_64.tgz
The /etc/cont-init.d/50-speedtest/ is coded to use a really old one at: https://install.speedtest.net/app/cli/ookla-speedtest-1.0.0-$arch-linux.tgz
-
So, when's the next series, 6.13?
-
It's not needed, but if you want to test the drive to make sure it's trustworthy and not faulty, it is a good idea to run through preclear or smart long test or other extensive workouts.
- 1
-
-
1 hour ago, itimpi said:
I find it easy to spot the orange dot at the start of each entry with unread items in it, so the font does not really matter.Now it's more a matter of "Why did this change when 'no one changed a thing'?" or at least admit to doing a change. It's one of those blasted computer things. 😀
-
So no one has any idea why this changed?
-
Keep in mind that you probably don't want to buy your drives all at once. This is to prevent them failing all at once or from the same issue IF there is a bad batch or a batch has a common issue.
-
27 minutes ago, SpencerJ said:
hey - we have updated the forum recently (5-6 months at least) - did you just notice this or has it been an issue for you for awhile?I only noticed this within the past week.
- 1
-
Strange driver issue with Asus BT-400 dongle. Or maybe it' me ?
in General Support
Posted
There is a lot of posts in this thread: