Andreas Kähäri writes:
i'm not sure why you're addressing this to me, as i'm not the
OP.
It's addressed to the thread in general.
Your response quoted me, then made use of the word 'you'. Which
you - and yes, i mean you, Andreas, specifically - have again done
below:
That said, yes,
On Sun, May 12, 2024 at 11:51:32AM -0700, Chris Bennett wrote:
> I found a YouTube channel LowLevelLearning that covers various
> programming languages in a manner that I find particularly helpful and
> clear. For example comparing C and assembly on the same code is superb.
>
> In a short, he
On 13/5/24 04:40, Chris Bennett wrote:
I saw a news bit yesterday that in one town, all of the school children
are buying old fashioned typewriters to break their link to computers
and do things the old fashioned way. +1 to them.
I prefer real text on paper myself. I learn things much better
On Sun May 12 21:50:12 2024 Martin Schröder wrote:
>
> If a line begins with "- " (dash, space) or "+ " (plus, space),
> then the type of rule is being explicitly specified as an exclude
> or an include (respectively). Any rules without such a prefix are
> taken to be an include.
I'd
> I suspect that it is because a web service might change its root
> directory to /var/www using chroot(2),
> Can anyone confirm or deny my assumption?
right, www is chrooted.
-Dan
On May 12 11:51:32, cpb_m...@bennettconstruction.us wrote:
> In a short, he recommended valgrind to help finding memory leaks.
man malloc
Otto Moerbeek thought me this:
First compile your program with debug symbols (and, conveniently, without
optimization settings.)
$ DEBUG="-g -O0" make
Then:
$ MALLOC_OPTIONS=D ktrace -tu
$ kdump -u malloc
kdump will though you lines like this:
0x34f10a4b153 20480 1 20480
Am So., 12. Mai 2024 um 21:18 Uhr schrieb Walter Alejandro Iglesias
:
> On Sun May 12 20:58:43 2024 Andreas Kähäri wrote
> > With rsync(1):
> >
> > rsync -n -aim --delete-excluded \
> > --include-from=list \
> > --include='*/' \
> > --exclude='*' \
>
On Sun May 12 20:58:43 2024 Andreas Kähäri wrote
> With rsync(1):
>
> rsync -n -aim --delete-excluded \
> --include-from=list \
> --include='*/' \
> --exclude='*' \
> source/ target
>
I don't understand what your command does exactly.
I found a YouTube channel LowLevelLearning that covers various
programming languages in a manner that I find particularly helpful and
clear. For example comparing C and assembly on the same code is superb.
In a short, he recommended valgrind to help finding memory leaks.
Other than splint and
On Sun, May 12, 2024 at 09:53:00AM +, Rubén Llorente wrote:
>
> I think it is worth mentioning I know of a number of small operations that
> have announced their complete withdrawal from social media - Twitter,
> Facebook, Instagram, the Fediverse - because the benefit they get from
> social
On Sun, May 12, 2024 at 01:40:25PM +0200, Walter Alejandro Iglesias wrote:
> > Unix development. Given that i've been using computers for a few
> > decades, i still instinctively don't use spaces in filenames, even
> > though they're very much allowed. But of course, that's not what
> > most of
Hi everyone,
I hope all of you had a great weekend so far!
I was wondering why OpenBSD web services like httpd write their PID file
to /var/www/run instead of /var/run.
I suspect that it is because a web service might change its root
directory to /var/www using chroot(2), making everything
Andreas Kähäri writes:
The external env(1) utility will only ever list environment
variables.
The IFS variable does not need to be exported as an environment
variable
as it's only ever used by the current shell (and any new shell
would
reset it).
To list all variables in a shell, use the
Страхиња Радић writes:
Дана 24/05/12 07:31PM, Alexis написа:
Omitting -r as a parameter to read would make it interpret
backscape
sequences, which would make the directory name in the filesystem
different than the one command/script operates on, which is most
likely undesired (unless the
Дана 24/05/12 07:31PM, Alexis написа:
> i wondered about that in this context. If people putting odd / inappropriate
> things in directory names are a concern ("weird characters", as you wrote
> upthread), what do we do about the possibility of someone having consciously
> put e.g. a \t in a
On Sun, May 12, 2024 at 08:08:17PM +1000, Alexis wrote:
> Andreas Kähäri writes:
>
> > Well, that's one way to control this trainwreck of a script; just say
> > that any name containing "inappropriate" characters aren't allowed!
> >
> > May I ask why you don't simply use rsync(1) (or even
On Sun, May 12, 2024 at 07:56:55PM +1000, Alexis wrote:
> Andreas Kähäri writes:
>
> > The ksh(1) shell sets IFS by default to a space, tab and a newline
> > character.
>
> Those are the defaults used when IFS is not set _as a variable_. If you log
> in, and run env(1), in the absence of any
On Sun May 12 13:22:13 2024 Alexis wrote:
> Andreas Kähäri writes:
> > Well, that's one way to control this trainwreck of a script;
> > just say
> > that any name containing "inappropriate" characters aren't
> > allowed!
> >
> > May I ask why you don't simply use rsync(1) (or even
> >
On Sun, May 12, 2024 at 07:31:41PM +1000, Alexis wrote:
> Страхиња Радић writes:
>
> > When `while ... read ...` idiom is used, it is advisable to clear IFS to
> > turn off field splitting
>
> *nod* Fair point; it's not set by default, so i didn't think to note that
> any manual setting of it
On Sun May 12 11:40:05 2024 tux2bsd wrote
> Hi Walter
>
> mktemp makes temporary unique filenames like this:
>
> delete_list=$(mktemp)
> source_list=$(mktemp)
> target_list=$(mktemp)
> # Do your code. If you want to keep something you do
> # that appropriately then:
> rm $delete_list
Andreas Kähäri writes:
Well, that's one way to control this trainwreck of a script;
just say
that any name containing "inappropriate" characters aren't
allowed!
May I ask why you don't simply use rsync(1) (or even
openrsync(1) from
the OpenBSD base system)?
i'm not sure why you're
Andreas Kähäri writes:
The ksh(1) shell sets IFS by default to a space, tab and a
newline
character.
Those are the defaults used when IFS is not set _as a
variable_. If you log in, and run env(1), in the absence of any
manual setting of IFS in .kshrc or whatever, you'll see that IFS
is
Stuart Longland wrote:
It's also dead because how how things are being run there. It's a site
for misinformation. "OpenBSD 7.5 is released" isn't misinformation,
it's fact, so has no place on twitter.com or x.com. It's also news
about an open-source free-software project, something that
Страхиња Радић writes:
When `while ... read ...` idiom is used, it is advisable to
clear IFS
to turn off field splitting
*nod* Fair point; it's not set by default, so i didn't think to
note that any manual setting of it should be overridden for this.
and use -r to avoid interpretation of
> What about the following, better?
>
> -
> # Remove files from target directory
> date=$(date +%H%M%S)
> delete_list=/tmp/delete_$date
> source_list=/tmp/source_$date
> target_list=/tmp/target_$date
Hi Walter
mktemp makes temporary unique filenames
Дана 24/05/12 06:17PM, Alexis написа:
> To deal with spaces etc., one could possibly use something along the lines
> of the following kludge; it assumes that \n is relatively unlikely to be
> found in a directory name, and that the directories in $dirs can be
> separated by \n.
>
> cd "$target"
On Sun May 12 10:07:30 2024 Страхиња Радић wrote:
> A few notes:
>
> - You don't need a backslash after a pipe (|) or a list operator (||
> and &&) - a line ending with a pipe is an incomplete pipeline. So
> (with added quoting):
>
> diff "$source_list" "$target_list" |
> awk '/^> /
Страхиња Радић writes:
Lapsus: the variable dirs should not be quoted here if it
contains more
than one directory to be passed to find. It is vulnerable to
directory
names containing spaces and weird characters, however.
So:
cd "$target" &&
find $dirs | sort | uniq >
29 matches
Mail list logo
