> Anyway, the context is big enough to play around with for
> now then.
Yes, this method works, I think?
I used it again with CONTEXT / QUERY and, as context, had the
5 first parts of this:
http://www.scifiscripts.com/scripts/starship_troopers.txt
then query: What sentence is the most origina
Executing this script halts it after the tar with the following message.
--
#!/bin/sh
tar -zcvf bak.tar.gz /home/user/Documents &&
gpg -r backup@user.local -e bak.tar.gz &&
rm -rf bak.tar.gz &&
rsync -vac --delete /home/user/Documents/bak.tar.gz.gpg /media/user/6548-2136
&&rm -rf bak.tar.gz.gpg
Richard Bostrom (12024-07-14):
> tar -zcvf bak.tar.gz /home/user/Documents &&
Information missing: what is the current directory.
> gpg -r backup@user.local -e bak.tar.gz &&
> rm -rf bak.tar.gz &&
> rsync -vac --delete /home/user/Documents/bak.tar.gz.gpg /media/user/6548-2136
> &&rm -rf bak.tar
On 7/14/24 00:57, Richard Bostrom wrote:
Executing this script halts it after the tar with the following message.
--
#!/bin/sh
tar -zcvf bak.tar.gz /home/user/Documents &&
gpg -r backup@user.local -e bak.tar.gz &&
rm -rf bak.tar.gz &&
rsync -vac --delete /home/user/Documents/bak.tar.gz.gpg /medi
Hi.
In case you are running unstable or testing and it recently started
blocking at boot waiting for encrypted swap or something to do with
encrypted disks:
Check if systemd-cryptsetup is installed.
HtH
--
Nicolas George
Le 14/07/2024 à 11:00, Nicolas George a écrit :
Hi.
In case you are running unstable or testing and it recently started
blocking at boot waiting for encrypted swap or something to do with
encrypted disks:
Check if systemd-cryptsetup is installed.
HtH
You are a bit cryptic here : should it be
Erwan David (12024-07-14):
> You are a bit cryptic here : should it be installed or should it be removed
Sorry. For me it was not installed and installing it fixed the problem.
> ? I am running testing without problem and systemd-cryptsetup is not
> installed. If I should install it I'd prefer to
Le 14/07/2024 à 11:44, Nicolas George a écrit :
Erwan David (12024-07-14):
You are a bit cryptic here : should it be installed or should it be removed
Sorry. For me it was not installed and installing it fixed the problem.
? I am running testing without problem and systemd-cryptsetup is not
i
On 07/14/2024 01:28 AM, Brad Rogers wrote:
On Sat, 13 Jul 2024 15:31:59 -0400
"Stephen P. Molnar" wrote:
Hello Stephen,
I downloaded a new copy of Miniconda3-latest-Linux-x89_64.s
You say nothing about where you got this from but, assuming it's
https://docs.anaconda.com/miniconda/
your pr
On 2024-07-14 11:00, Nicolas George wrote:
Hi.
In case you are running unstable or testing and it recently started
blocking at boot waiting for encrypted swap or something to do with
encrypted disks:
Check if systemd-cryptsetup is installed.
HtH
Thanks for the confirmation!
I downloaded deb
On 07/14/2024 07:15 AM, Stephen P. Molnar wrote:
On 07/14/2024 01:28 AM, Brad Rogers wrote:
On Sat, 13 Jul 2024 15:31:59 -0400
"Stephen P. Molnar" wrote:
Hello Stephen,
I downloaded a new copy of Miniconda3-latest-Linux-x89_64.s
You say nothing about where you got this from but, assumi
Here is the AI script!
It is all CLI/TUI, all FOSS, and all local execution/storage
as well.
#! /bin/zsh
#
# Find the most original sentence in a text file.
#
# uses:
# mistral-7b-instruct-v0.2.Q5_K_M.llamafile
# llamafile v0.8.5
#
# usage:
# $ ori input.txt # outputs to input-ori.txt
src=
Dear list,
I am wondering, why on a multiuser system like debian the rights for a normal
user are "rw- r-- r--", (owner: user and ownergroup: usergroup)
Of course there is a reason for this, but it is not understandable for me.
First two are clear: rw for myself, and readable for all users, i
On Sun, Jul 14, 2024 at 19:09:54 +0200, Hans wrote:
> I am wondering, why on a multiuser system like debian the rights for a normal
> user are "rw- r-- r--", (owner: user and ownergroup: usergroup)
Tradition, and a culture based around sharing.
The Unix culture of openness and freedom (specifica
Hi Greg,
yes, did already change it. However, this looks like a security hole for me,
as I believe, not many people or admins are changing this.
IMO debian should change this in the next release, but I doubt it.
I will ask the security team for it, they will decide.
Have fun!
Hans
Am Sonntag
On 2024-07-14 19:18, Greg Wooledge wrote:
On Sun, Jul 14, 2024 at 19:09:54 +0200, Hans wrote:
I am wondering, why on a multiuser system like debian the rights for a normal
user are "rw- r-- r--", (owner: user and ownergroup: usergroup)
Tradition, and a culture based around sharing.
The Unix c
On Sun, Jul 14, 2024 at 19:38:26 +0200, Hans wrote:
> Hi Greg,
>
> yes, did already change it. However, this looks like a security hole for me,
> as I believe, not many people or admins are changing this.
>
> IMO debian should change this in the next release, but I doubt it.
>
> I will ask the
On Sun, Jul 14, 2024 at 19:44:35 +0200, Lists wrote:
> Setting umask in your shell profile isn't that hard indeed. I've doing that
> for years. However, that does not mean your DE will honour that setting. I
> have tried to do so for KDE (more specifically Krusader), but I ended up
> nowhere. I hav
On Sun, Jul 14, 2024 at 07:44:35PM +0200, Lists wrote:
> On 2024-07-14 19:18, Greg Wooledge wrote:
> > On Sun, Jul 14, 2024 at 19:09:54 +0200, Hans wrote:
> > > I am wondering, why on a multiuser system like debian the rights for a
> > > normal
> > > user are "rw- r-- r--", (owner: user and ownerg
Hi,
Hans wrote:
> I am wondering, why on a multiuser system like debian the rights for a
> normal user are "rw- r-- r--", (owner: user and ownergroup: usergroup)
Because the usual umask of 0022 keeps the more credulous programs from
giving w-permission to everybody.
Any program is free to hand ou
Greg, I do not agree. If I am writing a document with private content, then I
do not want to let it be read by someone else except me.
No one has to read any letters or cv's or maybe documents for my lawyer, my
medic, my friends or whatever.
And after years there are a lot of documents one is
Hans (12024-07-14):
> Greg, I do not agree. If I am writing a document with private content, then I
If you are writing something confidential, it is your responsibility to
lock the door of your office.
Regards,
--
Nicolas George
On Sun, Jul 14, 2024 at 19:57:45 +0200, to...@tuxteam.de wrote:
> On Sun, Jul 14, 2024 at 07:44:35PM +0200, Lists wrote:
> > Setting umask in your shell profile isn't that hard indeed. I've doing that
> > for years. However, that does not mean your DE will honour that setting.
> The place to do th
I see itthe other way round. No, if you are in the secure area, it is the
responsibility of the owner to make it secure by design i.e with dself closing
doors where you can not look into or windows with curtains.
However, I presume, debian wants to be secure. If no one cares and all agree
with
* 2024-07-14 19:44:35+0200, li...@nodatagrabbing.com wrote:
> Setting umask in your shell profile isn't that hard indeed. I've doing
> that for years. However, that does not mean your DE will honour that
> setting. I have tried to do so for KDE (more specifically Krusader), but
> I ended up now
On 2024-07-14 19:18, Greg Wooledge wrote:
On Sun, Jul 14, 2024 at 19:09:54 +0200, Hans wrote:
I am wondering, why on a multiuser system like debian the rights for a normal
user are "rw- r-- r--", (owner: user and ownergroup: usergroup)
Tradition, and a culture based around sharing.
The Unix c
On Sun, Jul 14, 2024 at 02:10:46PM -0400, Greg Wooledge wrote:
> On Sun, Jul 14, 2024 at 19:57:45 +0200, to...@tuxteam.de wrote:
[...]
> Does that work in KDE?
At least The Internet (TM) (from some cursory poking) seems to
say so. I stay away from DEs for... reasons, so I can't test
it.
>
On 2024-07-14 19:43, Me wrote:
Setting umask in your shell profile isn't that hard indeed. I've doing
that for years. However, that does not mean your DE will honour that
setting. I have tried to do so for KDE (more specifically Krusader), but
I ended up nowhere. I haven't found a setting that
On 2024-07-14 19:57, to...@tuxteam.de wrote:
On Sun, Jul 14, 2024 at 07:44:35PM +0200, Lists wrote:
On 2024-07-14 19:18, Greg Wooledge wrote:
On Sun, Jul 14, 2024 at 19:09:54 +0200, Hans wrote:
I am wondering, why on a multiuser system like debian the rights for a normal
user are "rw- r-- r--"
On Sun, Jul 14, 2024 at 08:31:23PM +0200, Me wrote:
> On 2024-07-14 19:57, to...@tuxteam.de wrote:
[...]
> > [1] https://wiki.debian.org/Xsession
>
> Did you actually try this? I did and it did not what I was expecting it to
> do. But maybe I should try again, maybe things have improved in the
On 15/07/2024 01:32, Hans wrote:
I see itthe other way round. No, if you are in the secure area, it is the
responsibility of the owner to make it secure by design i.e with dself closing
doors where you can not look into or windows with curtains.
The door is closed by default in bookworm. User h
On 2024-07-14 19:38:26, Hans spake thus:
Hi Greg,
yes, did already change it. However, this looks like a security hole for me,
as I believe, not many people or admins are changing this.
I suspect that most people /do/ change it, once they become aware of
it, for the very reason stated in th
On Sun, Jul 14, 2024 at 22:15:34 -0400, Alan D. Salewski wrote:
> As it is, it
> looks[1] like default perms for $HOME are 0755.
If home directories are created with adduser, then the contents of
/etc/adduser.conf are relevant:
# The permissions mode for home directories of non-system users.
# D
On 2024-07-14 22:15:34, "Alan D. Salewski" spake thus:
[...]
The user's umask value would matter less if the default perms of
user $HOME directories were 077
s/were/were from a umask of/
Here is some cool ascii art to illustrate permissions
after mount.
The (x)_b notation indicates that x is in base b.
# permissions
# rwxr-xr-x dirs
local dmask=022 # (22)_8 = (10010)_2
local fmask=133 # (133)_8 = ( 1011011)_2
> Here is the AI script!
>
> It is all CLI/TUI, all FOSS, and all local execution/storage
> as well. [...]
I have stored it here:
https://dataswamp.org/~incal/ai/ori
I'm very happy with this solution and would like to thank
everyone for helping me out and making me aware of new
concepts and t
36 matches
Mail list logo
