Activity for alx
| Type | On... | Excerpt | Status | Date |
|---|---|---|---|---|
| Edit | Post #290224 |
Post edited: |
— | 6 months ago |
| Edit | Post #290224 |
Post edited: |
— | 6 months ago |
| Edit | Post #290224 |
Post edited: |
— | 6 months ago |
| Edit | Post #290224 | Initial revision | — | 6 months ago |
| Answer | — |
A: How to RTFM well to get a CLI command The pager less(1) less(1) is the usual pager nowadays; you would do well learning to use it. It's also used for paging the manual pages, in most systems. The most common operation is searching, which is done by pressing `/`. Press `h` within the pager, or run `less --help` to read its help f... (more) |
— | 6 months ago |
| Comment | Post #290221 |
Most shells don't provide manual pages for their built-ins like exit, but exit(1) is defined by POSIX (The Portable Operating System Interface), and there are POSIX manual pages.
On Debian:
```
$ apt-file find /exit.1;
fish-common: /usr/share/fish/man/man1/exit.1
manpages-posix: /usr/share/m... (more) |
— | 6 months ago |
| Comment | Post #290204 |
Here are the drives I own:
- USB: <https://www.amazon.es/gp/product/B08H8GNGCZ>
```sh
$ time (sudo dd if=/dev/zero of=/dev/sdb bs=1MiB status=progress; sync)
33303822336 bytes (33 GB, 31 GiB) copied, 156 s, 213 MB/s
dd: error writing '/dev/sdb': No space left on device
31785+0 records in
... (more) |
— | 6 months ago |
| Comment | Post #290204 |
I'm very happy about it! Thanks for the question! :) (more) |
— | 6 months ago |
| Comment | Post #290201 |
Yes, as @Canina pointed out, I was trying to keep the Fixed font. I didn't check that other fonts had more sizes. It is indeed the simplest solution. (more) |
— | 6 months ago |
| Comment | Post #290203 |
The winner to my taste has been `Lat15-Terminus32x16.psf.gz`.
Heh, only caveat is I prefer the Fixed font. But size matters! I wish there was a large version of it. :)
As you said, I don't trust passing the kernel a different resolution. (more) |
— | 6 months ago |
| Edit | Post #290204 |
Post edited: |
— | 6 months ago |
| Edit | Post #290204 |
Post edited: |
— | 6 months ago |
| Edit | Post #290204 |
Post edited: |
— | 6 months ago |
| Edit | Post #290204 |
Post edited: |
— | 6 months ago |
| Edit | Post #290204 | Initial revision | — | 6 months ago |
| Answer | — |
A: Looking for a way to sync dotfile content between different machines without introducing security issues It depends on how much sensitive they are. I have three classes. 1) Very sensitive directories Partitions For my `/.ssh/`, `/.password-store/`, `/.gnupg/`, and `/.abook/`, I have a drive with 4 partitions, one for each directory, each of them encrypted with LUKS2. The relevant fs... (more) |
— | 6 months ago |
| Comment | Post #290201 |
My default font is 8x16, and the largest one I can choose is 8x18. which I don't think will make much of a difference. Also, will it change the rectangle size, or will it just have less space between letters? That might even be negative to readability. (more) |
— | 6 months ago |
| Edit | Post #290199 |
Post edited: |
— | 6 months ago |
| Edit | Post #290199 | Initial revision | — | 6 months ago |
| Question | — |
How to change resolution of virtual terminal? How can I rescale the Linux virtual terminals (ctrl + alt + {f1, f2, f3, f4, f5, f6}), so that a high-resolution display doesn't make the letters too small? I'd like to use 1080 or even 720 resolution in virtual terminals (and only there; I want native resolution in ctrl + alt + f7). If that ... (more) |
— | 6 months ago |
| Comment | Post #290119 |
Re: `\` and `|`: I agree that the `\` is a bit ugly. However, I find it less readable if the pipe symbol goes to the right. It's usually something very important, so I prefer it as the first symbol. I wish sh(1) had mandatory semicolons like C, so that escaping newlines wouldn't have been necessar... (more) |
— | 6 months ago |
| Comment | Post #290009 |
@#57088 No problem. Nitpicking helps get even better answers, or just random useful info. :)
You may find it interesting that find(1), because of the library it uses for name filtering, is very slow, and grep(1), even with the overhead of a new fork(2), outperforms find(1) very easily. You can ... (more) |
— | 6 months ago |
| Comment | Post #290119 |
It is a standalone program (actually, a shell script) that is designed to search through C code.
Here's the source code: <https://www.alejandro-colomar.es/src/alx/alx/grepc.git/tree/bin/grepc>
I would love to see it being used by other people and get bug reports! :-)
Feel free to email me for... (more) |
— | 6 months ago |
| Comment | Post #290136 |
Since you write the code, you can tell your kernel that no program can create such files. Or maybe you can program it so that only root can create such files. Or maybe programs that have some capability (read <https://man7.org/linux/man-pages/man7/capabilities.7.html>).
Regarding the question of... (more) |
— | 6 months ago |
| Comment | Post #290136 |
If you fear that attackers may create files by physically writing 0s and 1s into your drive, you can encrypt the drive. If it's encrypted, you can remain sure that the only way to add files to your drive is via software, and only if you know the key.
This also removes the possibility that someone... (more) |
— | 6 months ago |
| Comment | Post #290136 |
While a kernel could theoretically have backdoors creating such files anywhere in the millions of lines of code, it usually only has one (or a few at most) place where filenames are validated.
We assume you trust the code in your kernel, because otherwise why would you use it? If you don't trust ... (more) |
— | 6 months ago |
| Comment | Post #290136 |
If you modify gnome, an attacker could create files by calling system calls directly.
You need to modify the kernel if you really want to block any software from creating files with certain characters. (more) |
— | 6 months ago |
| Comment | Post #290119 |
If you make it configurable, so that it is disabled by default and can be enabled for users that want it, maybe you could convince kernel maintainers to merge the feature. (more) |
— | 6 months ago |
| Edit | Post #290119 |
Post edited: |
— | 6 months ago |
| Edit | Post #290119 |
Post edited: |
— | 6 months ago |
| Edit | Post #290119 | Initial revision | — | 6 months ago |
| Answer | — |
A: How can I restrict filename characters? You could try and convince Linux kernel maintainers, but they are reticent to that. I wonder what they'll do after POSIX.1-202x (Issue 8) possibly will forbid those. Maybe you could patch your kernel. It would be an interesting thing to do, even if just for fun. I've never done such a thing, so... (more) |
— | 6 months ago |
| Comment | Post #290113 |
@#8049
Maybe a safe assumption is that it would be on Linux, given the name of the server. :) (more) |
— | 6 months ago |
| Comment | Post #290009 |
> All *nix systems accept everything except / and \0 in file names.
And great news, POSIX may outlaw `\n` (and a few more) soon: <https://www.austingroupbugs.net/view.php?id=251>. (more) |
— | 7 months ago |
| Comment | Post #288401 |
To add a bit more to this:
POSIX.1-202x (Issue 8) is considering outlawing `\n` (actually, characters 1 through 31) in filenames.
See <https://www.austingroupbugs.net/view.php?id=251>.
And the POSIX portable filename character set already limits the characters that one should want to use in ... (more) |
— | 7 months ago |
| Comment | Post #290009 |
> Why not `find . -type f -name '*-min.jpg-*' -print0` to avoid the `grep`?
Because the grep(1) is so much simpler conceptually. I don't need to remember of all the options from find(1) that can be used for file names (`-ilname`, `-iname`, `-ipath`, `-iregex`, `-iwholename`, `-lname`, `-name`, `-... (more) |
— | 7 months ago |
| Comment | Post #290009 |
> All *nix systems accept everything except `/` and `\0` in file names.
That's true for the kernels. Individual programs may or may not. When writing scripts like this one (which I do often), it helps not having to consider such insane file names. Usual *nix filters do not like non-portable fil... (more) |
— | 7 months ago |
| Comment | Post #290009 |
> And there is no reason to assume the random string will only have alphanumerical values.
That was my inductive guess from the small sample. If it's different, the regex could be adjusted to fit. The good thing of using `[[:alnum:]]` is that it self-documents, so any mismatches will be easily d... (more) |
— | 7 months ago |
| Edit | Post #289999 |
Post edited: Hardened versions |
— | 7 months ago |
| Edit | Post #290009 |
Post edited: |
— | 7 months ago |
| Edit | Post #290009 |
Post edited: reorder, to put the safe version first |
— | 7 months ago |
| Edit | Post #290009 |
Post edited: fix grep |
— | 7 months ago |
| Edit | Post #290009 |
Post edited: |
— | 7 months ago |
| Edit | Post #290009 |
Post edited: |
— | 7 months ago |
| Edit | Post #290009 |
Post edited: |
— | 7 months ago |
| Edit | Post #290009 |
Post edited: |
— | 7 months ago |
| Edit | Post #290009 |
Post edited: Add safe version |
— | 7 months ago |
| Edit | Post #290009 |
Post edited: |
— | 7 months ago |
| Edit | Post #290009 |
Post edited: |
— | 7 months ago |
| Edit | Post #290009 |
Post edited: |
— | 7 months ago |
- ← Previous
- 1
- 2
- 3
- 4
- Next →