Bonjour,
Le dimanche 25 février 2024, Hugues MORIN-TRENEULE a écrit...
> Néanmoins, il me reste un espace non utilisé en fin de disque.
> Quand j'aurai un moment, je rajouterai quelques giga sur / afin de ne plus
> me retrouver en difficulté par manque d'espace.
Je ne sais pas si
Bonjour
Désolé pour ce retour tardif.
Je vous confirme que tout est OK, mon système fonctionne normalement et je
n'ai pour l'heure rencontré aucun probleme.
Oui effectivement, les partitions sont complètement entremêlées et
réparties sur 3 partitions.
sda1 qui contient /
sda2 qui contient sda5
m. I've never used btrfs filesystem df
Would it matter if you're not running your filesystem close to full?
Cheers,
David.
On Mon 19 Feb 2024 at 10:26:05 (+1100), Keith Bainbridge wrote:
> On 18/2/24 14:49, Keith Bainbridge wrote:
> > On 18/2/24 07:34, debian-u...@howorth.org.uk wrote:
> > > Keith Bainbridge wrote:
> > > > Yes the / partitions are btrfs
> > >
> > > So the apparently missing space is perhaps taken up
On Wed, Feb 21, 2024 at 12:21:05PM +1100, Keith Bainbridge wrote:
>
> On 21/2/24 10:47, Felix Miata wrote:
> > I didn't think so, which begs the question why OP Keith is using it. :p
> > --
>
> I read somewhere about 2 years ago, that it automagically de-duped data
> when it detected I was
On 21/2/24 10:47, Felix Miata wrote:
I didn't think so, which begs the question why OP Keith is using it. :p
--
I read somewhere about 2 years ago, that it automagically de-duped data
when it detected I was copying the same file to different directories.
It's not deliberate, but I have
Keith Bainbridge composed on 2024-02-21 11:57 (UTC+1100):
> Felix Miata wrote:
>> A current thread from elsewhere that should be helpful:
>> <https://forums.opensuse.org/t/btrfs-disk-full-how-to-fix-it-is-that-
>> really-the-solution/172576>
>> btrfs f
On 21/2/24 11:38, Felix Miata wrote:
A current thread from elsewhere that should be helpful:
<https://forums.opensuse.org/t/btrfs-disk-full-how-to-fix-it-is-that-
really-the-solution/172576>
btrfs filesystem usage /
snapper list
btrfs qgroup show /
at should be helpful:
<https://forums.opensuse.org/t/btrfs-disk-full-how-to-fix-it-is-that-really-the-solution/172576>
btrfs filesystem usage /
snapper list
btrfs qgroup show /
Was requested by a btrfs expert.
--
Evolution as taught in public schools is, like relig
Greg Wooledge composed on 2024-02-20 14:56 (UTC-0500):
> On Tue, Feb 20, 2024 at 02:47:26PM -0500, Felix Miata wrote:
>> Surely somewhere on debian.org such things must be addressed if Bookworm's
>> default
>> has also been changed to btrfs.
> That has not happened. The default file system is
On Tue, Feb 20, 2024 at 02:47:26PM -0500, Felix Miata wrote:
> Surely somewhere on debian.org such things must be addressed if Bookworm's
> default
> has also been changed to btrfs.
That has not happened. The default file system is still ext4.
to...@tuxteam.de composed on 2024-02-20 09:38 (UTC+0100):
> On Tue, Feb 20, 2024 at 02:42:18AM -0500, Felix Miata wrote:
>> Keith Bainbridge composed on 2024-02-20 17:45 (UTC+1100):
>> > I just removed 3 snapshots from my daily driver with no change in used
>> > space reported by df
>> df
Felix Miata wrote:
> Keith Bainbridge composed on 2024-02-20 17:45 (UTC+1100):
>
> > I just removed 3 snapshots from my daily driver with no change in
> > used space reported by df
>
> df doesn't know how to calculate freespace on btrfs. You need to be
> typing
>
> btrfs filesystem df
Hi,
> when cfdisk reports:
> Device Start End Sectors Size Type
> /dev/sda2 1785522176 1786245119 722944 353M EFI System
> /dev/sda3 1786245120 1933045759 146800640 70G EFI System
> I don't understand the 'EFI System' note /dev/sda3 is /
The partition type
On Tue, Feb 20, 2024 at 09:21:15PM +1100, Keith Bainbridge wrote:
>
> On 20/2/24 19:38, to...@tuxteam.de wrote:
[...]
> Tomas, the upgrade failure was earlier than these notes. It has now worked
I see.
> Sorry, but I don't know how to assess the snapshot space usage.
Nor do I -- my question
On 20/2/24 19:38, to...@tuxteam.de wrote:
On Tue, Feb 20, 2024 at 02:42:18AM -0500, Felix Miata wrote:
Keith Bainbridge composed on 2024-02-20 17:45 (UTC+1100):
I just removed 3 snapshots from my daily driver with no change in used
space reported by df
df doesn't know how to calculate
On 20/2/24 18:42, Felix Miata wrote:
btrfs filesystem df
OK, so please interpret:
>> btrfs filesystem df -h /
Data, single: total=32.80GiB, used=31.94GiB
System, DUP: total=8.00MiB, used=16.00KiB
Metadata, DUP: total=1.50GiB, used=1.10GiB
GlobalReserve, single: total=71.69MiB, used=0.00B
On Tue, Feb 20, 2024 at 02:42:18AM -0500, Felix Miata wrote:
> Keith Bainbridge composed on 2024-02-20 17:45 (UTC+1100):
>
> > I just removed 3 snapshots from my daily driver with no change in used
> > space reported by df
>
> df doesn't know how to calculate freespace on btrfs. You need to be
On 20/2/24 18:11, Keith Bainbridge wrote:
On 19/2/24 14:20, Keith Bainbridge wrote:
On 19/2/24 10:26, Keith Bainbridge wrote:
On 18/2/24 14:49, Keith Bainbridge wrote:
On 18/2/24 07:34, debian-u...@howorth.org.uk wrote:
Keith Bainbridge wrote:
Yes the / partitions are btrfs
So the
Keith Bainbridge composed on 2024-02-20 17:45 (UTC+1100):
> I just removed 3 snapshots from my daily driver with no change in used
> space reported by df
df doesn't know how to calculate freespace on btrfs. You need to be typing
btrfs filesystem df
if you have not aliased df to btrfs
On 19/2/24 14:20, Keith Bainbridge wrote:
On 19/2/24 10:26, Keith Bainbridge wrote:
On 18/2/24 14:49, Keith Bainbridge wrote:
On 18/2/24 07:34, debian-u...@howorth.org.uk wrote:
Keith Bainbridge wrote:
Yes the / partitions are btrfs
So the apparently missing space is perhaps taken up
On 19/2/24 13:00, Max Nikulin wrote:
On 19/02/2024 06:26, Keith Bainbridge wrote:
So later yesterday afternoon I created a new snapshot with no obvious
change is free space.
Effect of snapshots is delayed. When you remove a file that does not
belong to any snapshot, some disk space is
David Christensen wrote:
> On 2/18/24 19:20, Keith Bainbridge wrote:
> > I am convinced that the missing space is used by btrfs snapshot
> > process.
>
>
> Perhaps. But, are you re-balancing your btrfs file systems regularly?
>
>
hot hardlinks ;-) )
Once, some older filesystem state is snapshotted, its space is taken
until the snapshot gets destroyed/removed. This can lead to situations,
where a device is full, but in order to free some space, deleting files
will NOT help, because in order to do so, a change in the directory
nee
On 2/18/24 19:20, Keith Bainbridge wrote:
I am convinced that the missing space is used by btrfs snapshot process.
Perhaps. But, are you re-balancing your btrfs file systems regularly?
https://manpages.debian.org/bookworm/btrfs-progs/btrfs-balance.8.en.html
Doing it by hand was not
On Mon, Feb 19, 2024 at 02:20:20PM +1100, Keith Bainbridge wrote:
[...]
> I am convinced that the missing space is used by btrfs snapshot process. But
> WHY is the used space reporting on my daily driver LESS than that on the
> spare machine 29G vs 35G? The original install was the same .iso
On 19/2/24 10:26, Keith Bainbridge wrote:
On 18/2/24 14:49, Keith Bainbridge wrote:
On 18/2/24 07:34, debian-u...@howorth.org.uk wrote:
Keith Bainbridge wrote:
Yes the / partitions are btrfs
So the apparently missing space is perhaps taken up by btrfs snapshots.
Seems to be the
On 19/2/24 13:41, Felix Miata wrote:
would be some places to start. Didn't you do your
https://btrfs.readthedocs.io/en/latest/btrfs-filesystem.html
reading yet? ?_?
My eyes have glazed over too often, already. I know I have to get back,
but that NEED to do it is making it harder.
--
All
Keith Bainbridge composed on 2024-02-18 14:49 (UTC+1100):
> debian-u...@howorth.org.uk wrote:
>> So the apparently missing space is perhaps taken up by btrfs snapshots.
> Seems to be the prime suspect.
While snapshotting is obviously a consumer, until you use the right tool for the
job, you
On 19/02/2024 06:26, Keith Bainbridge wrote:
So later yesterday afternoon I created a new snapshot with no obvious
change is free space.
Effect of snapshots is delayed. When you remove a file that does not
belong to any snapshot, some disk space is reclaimed. However to restore
a file
On 18/2/24 14:49, Keith Bainbridge wrote:
On 18/2/24 07:34, debian-u...@howorth.org.uk wrote:
Keith Bainbridge wrote:
Yes the / partitions are btrfs
So the apparently missing space is perhaps taken up by btrfs snapshots.
Seems to be the prime suspect. If that's the case, btrfs is
On 18/2/24 14:08, Max Nikulin wrote:
On 17/02/2024 09:52, Greg Wooledge wrote:
If so, you *could* have data inside the /home directory
of the root file system, which is hidden by the /home file system that's
mounted over it. You'd need to unmount /home to check.
A less intrusive way to
Keith Bainbridge composed on 2024-02-17 15:44 (UTC+1100):
Yes the / partitions are btrfs
Several years ago, I installed Debian (9?) using btrfs for root (and
boot?). I failed to understand that btrfs required regular maintenance
and/or I was too lazy to figure it out and do it. After a
On 18/2/24 09:19, Cindy Sue Causey wrote:
I only know to say this because it just happened a few days ago. Rsync
left some semi-permanent remnants when I was having problems with the
wireless capable hard drive docking station repeatedly cutting out. I
was offloading videos and images from a
On 18/2/24 07:34, debian-u...@howorth.org.uk wrote:
Keith Bainbridge wrote:
Yes the / partitions are btrfs
So the apparently missing space is perhaps taken up by btrfs snapshots.
Seems to be the prime suspect. If that's the case, btrfs is NOT
hard-linking the snapshots as
On 17/02/2024 09:52, Greg Wooledge wrote:
If so, you *could* have data inside the /home directory
of the root file system, which is hidden by the /home file system that's
mounted over it. You'd need to unmount /home to check.
A less intrusive way to inspect shadowed directories is bind
Le 17 février 2024 Alban Vidal a écrit :
> Pour éviter des soucis d'espace disque à l'avenir, je pense qu'il serait
> judicieux de redimensionner un peu les partitions, en en retirant un peu dans
> le /opt ou /home pour en mettre un peu plus sur la racine (/), 2 ou 3G par
> exemple.
Je pense que
On 2/17/24, Greg Wooledge wrote:
> On Sat, Feb 17, 2024 at 04:00:14PM -0500, Stefan Monnier wrote:
>> > So the apparently missing space is perhaps taken up by btrfs snapshots.
>>
>> Another possibility is a (few) large file(s) that is/are still open for
>> some process(es) but have been `rm`
On Sat, Feb 17, 2024 at 04:00:14PM -0500, Stefan Monnier wrote:
> > So the apparently missing space is perhaps taken up by btrfs snapshots.
>
> Another possibility is a (few) large file(s) that is/are still open for
> some process(es) but have been `rm` (`unlink`) so they don't have a name
> any
> So the apparently missing space is perhaps taken up by btrfs snapshots.
Another possibility is a (few) large file(s) that is/are still open for
some process(es) but have been `rm` (`unlink`) so they don't have a name
any more.
Stefan
Keith Bainbridge wrote:
> Yes the / partitions are btrfs
So the apparently missing space is perhaps taken up by btrfs snapshots.
, Hugues MORIN-TRENEULE
a écrit :
>Re bonjour
>
>Je viens d'exécuter le apt full-upgrade.
>Je pensais que ça allait prendre un peu de temps mais ça a été rapide, tous
>les paquets étaient déjà à jour :)
>
>J'ai redémarré et tout semble fonctionner.
>J'ai effectué quelques
Re bonjour
Je viens d'exécuter le apt full-upgrade.
Je pensais que ça allait prendre un peu de temps mais ça a été rapide, tous
les paquets étaient déjà à jour :)
J'ai redémarré et tout semble fonctionner.
J'ai effectué quelques mises a jour et preparé l'upgrade a la version
suivante comme
l, qui semble s'être déroulé
> > sans incident.
> >
> > - J'ai RE-exécuté apt upgrade --without-new-pkgs qui m'a listé les
> paquets
> > qui ne sont plus nécessaires.
> > Je les ai retirés avec apt autoremove comme le conseille la commande
> > précédente.
> >
Keith Bainbridge wrote:
...
> No nfs mounts
any swap partition or swap space?
but other than that sharing /home with / is likely your
issue and you mention snapshots and backintime and i do
recall that needing plenty of space.
as for btrfs, i have no clue, i've never touched it.
On 17/2/24 17:08, Felix Miata wrote:
Keith Bainbridge composed on 2024-02-17 15:44 (UTC+1100):
Yes the / partitions are btrfs
df was not designed for the task you gave it. You need to use
btrfs filesystem
commands:
https://btrfs.readthedocs.io/en/latest/btrfs-filesystem.html
On Sat, Feb 17, 2024 at 03:44:49PM +1100, Keith Bainbridge wrote:
[...]
> df -h
> Filesystem Size Used Avail Use% Mounted on
> udev7.2G 0 7.2G 0% /dev
> tmpfs 1.5G 1.9M 1.5G 1% /run
> /dev/nvme0n1p2 63G 27G 35G 44% /
> tmpfs 7.3G 84M
Keith Bainbridge composed on 2024-02-17 15:44 (UTC+1100):
> Yes the / partitions are btrfs
df was not designed for the task you gave it. You need to use
btrfs filesystem
commands:
https://btrfs.readthedocs.io/en/latest/btrfs-filesystem.html
--
Evolution as taught in public schools
On Fri, Feb 16, 2024 at 09:52:22PM -0500, Greg Wooledge wrote:
> On Sat, Feb 17, 2024 at 01:38:56PM +1100, Keith Bainbridge wrote:
> > >> sudo df -h /
> > Filesystem Size Used Avail Use% Mounted on
> > /dev/sda336G 35G 100M 100% /
>
> First off: you don't need sudo for this,
On 17/2/24 13:55, Gremlin wrote:
On 2/16/24 21:38, Keith Bainbridge wrote:
Good afternoon All
I have just rebooted this laptop to ensure it is 'fresh'
/ is reporting full.
Trying to locate where I ran
sudo du -hPx --max-depth=1 /
0 /mnt
181M /boot
15M /etc
0 /media
236M
On 17/2/24 13:52, Greg Wooledge wrote:
On Sat, Feb 17, 2024 at 01:38:56PM +1100, Keith Bainbridge wrote:
>> sudo df -h /
Filesystem Size Used Avail Use% Mounted on
/dev/sda336G 35G 100M 100% /
First off: you don't need sudo for this, ever.
Second: what kind of file
On 2/16/24 21:38, Keith Bainbridge wrote:
Good afternoon All
I have just rebooted this laptop to ensure it is 'fresh'
/ is reporting full.
Trying to locate where I ran
sudo du -hPx --max-depth=1 /
0 /mnt
181M /boot
15M /etc
0 /media
236M /opt
336K /root
0 /srv
4.0K
On Sat, Feb 17, 2024 at 01:38:56PM +1100, Keith Bainbridge wrote:
> >> sudo df -h /
> Filesystem Size Used Avail Use% Mounted on
> /dev/sda336G 35G 100M 100% /
First off: you don't need sudo for this, ever.
Second: what kind of file system is this?
> sudo du -hPx
On Sat 17 Feb 2024 at 13:38:56 (+1100), Keith Bainbridge wrote:
> I have just rebooted this laptop to ensure it is 'fresh'
>
> / is reporting full.
>
> Trying to locate where I ran
>
> sudo du -hPx --max-depth=1 /
> 0 /mnt
> 181M /boot
> 15M /etc
> 0
Good afternoon All
I have just rebooted this laptop to ensure it is 'fresh'
/ is reporting full.
Trying to locate where I ran
sudo du -hPx --max-depth=1 /
0 /mnt
181M/boot
15M /etc
0 /media
236M/opt
336K/root
0 /srv
4.0K/tmp
8.1G/usr
726M/var
9.2G
s'être déroulé
> sans incident.
>
> - J'ai RE-exécuté apt upgrade --without-new-pkgs qui m'a listé les paquets
> qui ne sont plus nécessaires.
> Je les ai retirés avec apt autoremove comme le conseille la commande
> précédente.
>
> Jusque là, tout semble OK :)
En effet !
>
la commande
précédente.
Jusque là, tout semble OK :)
Normalement afin de finir mon upgrade il ne manque plus que le apt
full-upgrade à exécuter.
Je me suis arrêté là pour l'instant, par manque de temps pour aller plus
loin
Je n'ai pas encore éteint (ou rebooter) la machine.
Est ce que mon oubli
la place, il faut
> que je relance la commande apt full-upgrade
> Mais avant cela, je dois killer le pid de apt et faire un dpkg-reconfigure.
>
> Pour trouver le pid d'apt, c'est à l'aide de la commande ps?
> Et apres kill "n° de pid"
>
> Est ce qu'il y a autre
d'apt - killall -9 "PID d'apt" - dpkg-reconfigure - apt
upgrade --without-new-pkgs (=> Cette commande met à niveau les
paquets qui peuvent l'être sans entraîner l'installation ou la
suppression d'autres paquets. ) - apt full-upgrade
Ça vous semble correct ?
Oui ça devrait aller,
t-new-pkgs (=> Cette commande met à niveau les
paquets qui peuvent l'être sans entraîner l'installation ou la suppression
d'autres paquets. )
- apt full-upgrade
Ça vous semble correct ?
Très cordialement
Hugues
Le mar. 13 févr. 2024 à 09:34, Michel Verdier a écrit :
> Le 12 février 2
Le 12 février 2024 Hugues MORIN-TRENEULE a écrit :
> Avec le recul, aujourd'hui, je ne ferai que des partitions pour /home, /var
> et /opt.
/home et /opt il faut voir selon tes applis. Mais si /var est saturé ça
bloque tout le système à cause des logs qui ne peuvent plus se faire.
> Est ce que
t; comment faire en pratique.
> >
> > Donc si je comprends bien, maintenant que j'ai fait de la place, il faut
> > que je relance la commande apt full-upgrade
> > Mais avant cela, je dois killer le pid de apt et faire un dpkg-reconfigure.
> >
> > Pour trouver
On 12 Feb 2024 08:00, Hugues MORIN-TRENEULE wrote:
Bonjour a tous
Je reviens vers vous car je ne sais pas comment m'y prendre pour réparer un
crash lors d'un apt full-upgrade lors d'un passage de Stretch a Bullseye.
Ca fonctionne peut-être, mais ce n'est pas la manière recommandée
On 12/02/2024 19:23:39, Hugues MORIN-TRENEULE wrote:
> Pour trouver le pid d'apt, c'est à l'aide de la commande ps?
> Et apres kill "n° de pid"
> Est ce qu'il y a autre chose a faire pour killer le processus d'apt?
Tu peux tuer un processus en utilisant son nom avec la commande killall, qui
Salut
Merci pour l'info
Malheureusement même si j'entrevois de quoi tu parles, je ne sais pas trop
comment faire en pratique.
Donc si je comprends bien, maintenant que j'ai fait de la place, il faut
que je relance la commande apt full-upgrade
Mais avant cela, je dois killer le pid de apt et
Salut
C'est un système qui à l'origine avait été installé en Wheezy ou Jessie et
que j'ai upgradé.
Je n'avais pas autant de connaissance que maintenant et il m'avait semblé
plus judicieux de faire une partition par montage.
Je me disais que ca serait surement plus simple de restaurer le système
Le 12 février 2024 Hugues MORIN-TRENEULE a écrit :
> J'ai effectivement vu ce message mais je n'en avais pas compris la raison.
> Néanmoins, au vue de df -TPh, je m’aperçois que ma partition racine et
> /boot son bien "chargées".
> Est ce que le problème pourrait provenir de la?
Le message
rdialement,
> Alban
>
>
> Le 12 février 2024 08:00:00 GMT+01:00, Hugues MORIN-TRENEULE <
> mor...@gmail.com> a écrit :
>
>> Bonjour a tous
>>
>>
>> Je reviens vers vous car je ne sais pas comment m'y prendre pour réparer
>> un crash lors d'
gues MORIN-TRENEULE
a écrit :
>Bonjour a tous
>
>
>Je reviens vers vous car je ne sais pas comment m'y prendre pour réparer un
>crash lors d'un apt full-upgrade lors d'un passage de Stretch a Bullseye.
>
>Il y a quelques temps vos conseils et explications mon permis de de mettre
Bonjour a tous
Je reviens vers vous car je ne sais pas comment m'y prendre pour réparer un
crash lors d'un apt full-upgrade lors d'un passage de Stretch a Bullseye.
Il y a quelques temps vos conseils et explications mon permis de de mettre
a jours mon Stretch afin de le préparer à l'upgrade
On 1/30/24 1:43 PM, Michael Kjörling wrote:
https://www.debian.org/releases/bullseye/amd64/release-notes/ch-upgrading.en.html#file-conflicts
should help.
Sure. Thanks!
-themes-more (possibly with
apt, possibly directly with dpkg), then try the '--fix-broken' step
again.
Assuming that works, I'd then follow it up by repeating the full-upgrade
step just to make sure, and then after that - if I really wanted
gnome-themes-more - try to reinstall it (preferably using
On 1/30/24 1:41 PM, Greg Wooledge wrote:
On Tue, Jan 30, 2024 at 01:19:09PM +0100, Miroslav Skoric wrote:
Unpacking marco-common (1.24.1-3) over (1.20.3-1) ...
.[1mdpkg:.[0m error processing archive
/tmp/apt-dpkg-install-S65GMD/8-marco-common_1.24.1-3_all.deb (--unpack):
trying to overwrite
On 30 Jan 2024 13:19 +0100, from sko...@uns.ac.rs (Miroslav Skoric):
> Preparing to unpack .../8-marco-common_1.24.1-3_all.deb ...
> Unpacking marco-common (1.24.1-3) over (1.20.3-1) ...
> .[1mdpkg:.[0m error processing archive
> /tmp/apt-dpkg-install-S65GMD/8-marco-common_1.24.1-3_all.deb
On Tue, Jan 30, 2024 at 01:19:09PM +0100, Miroslav Skoric wrote:
> Unpacking marco-common (1.24.1-3) over (1.20.3-1) ...
> .[1mdpkg:.[0m error processing archive
> /tmp/apt-dpkg-install-S65GMD/8-marco-common_1.24.1-3_all.deb (--unpack):
> trying to overwrite
>
nimal system upgrade" (# apt upgrade --without-new-pkgs). That
> part performed without any issue, and cat /etc/debian_version reported
> 11.8 (previously it was 10.x).
>
> "4.4.5 Upgrading the system" (# apt full-upgrade) ran also fine until
> some 20% or so, and then
t any issue, and cat /etc/debian_version reported
11.8 (previously it was 10.x).
"4.4.5 Upgrading the system" (# apt full-upgrade) ran also fine until
some 20% or so, and then failed when handled marco-common package. Here
are the few last lines of that session:
...
Preparing to unp
On 12/5/23 03:54, Andrew M.A. Cater wrote:
Just a heads up for Gene: for when you upgrade one of your machines
(or replace disks). Linuxcnc is now a full package in Debian at least
on amd64 (and possibly on arm64).
It pulls in large amounts of dependencies, so I didn't install it myself
but apt
Just a heads up for Gene: for when you upgrade one of your machines
(or replace disks). Linuxcnc is now a full package in Debian at least
on amd64 (and possibly on arm64).
It pulls in large amounts of dependencies, so I didn't install it myself
but apt-cache show linuxcnc should give you
Am 23.10.2023 um 12:04:35 Uhr schrieb Michael Kjörling:
> Encrypted /boot has been supported with GRUB 2 for a while. That
> leaves only a minimal portion of GRUB in plaintext on storage.
Although it is not default, so users should be aware that they need to
do additional steps to encrypt /boot.
On 23 Oct 2023 13:59 +0200, from m...@dorfdsl.de (Marco M.):
> Be aware that the boot loader and the /boot aren't encrypted by default
> and they can be attacked (e.g. simply place a tainted kernel inside) by
> anybody who has access to the harddisk.
Encrypted /boot has been supported with GRUB 2
Am 23.10.2023 um 12:53:14 Uhr schrieb lester29:
> 1. Does an encryption key on the USB protect against rubber-hose
> cryptanalysis?
No, the LUKS headers are viewable. You need another layer around that
supports hidden containers.
> 2. Is it true that key on pendrive is more risky than
On 23 Oct 2023 12:53 +0200, from leste...@gazeta.pl (lester29):
> 1. Does an encryption key on the USB protect against rubber-hose
> cryptanalysis?
I don't see how it would. Presumably you would have access to it;
therefore that access could potentially be exploited through coercion
or torture.
Hi
I need to set up full disk encryption of the linux in my laptop.
Questions:
1. Does an encryption key on the USB protect against rubber-hose
cryptanalysis?
2. Is it true that key on pendrive is more risky than password because
someone can steal the usb key and access data without the need
On Fri 20 Oct 2023 at 11:51:35 (+0200), Gertjan Klein wrote:
> Op 20-10-2023 om 05:10 schreef David Wright:
> > On Thu 19 Oct 2023 at 13:30:53 (+0200), Gertjan Klein wrote:
> > > I don't intend to send mail from this machine myself, I want mail from
> > > the system (e.g. unattended-upgrades)
Op 19-10-2023 om 21:50 schreef Greg Wooledge:
Once the spam stops coming from your system, then you can try to get your
IP address removed from all of the DNS spammer lists. Usually there's a
web form you can fill out. Or the listing may expire after a while.
I've seen many postings over the
Op 20-10-2023 om 05:10 schreef David Wright:
On Thu 19 Oct 2023 at 13:30:53 (+0200), Gertjan Klein wrote:
I don't intend to send mail from this machine myself, I want mail from
the system (e.g. unattended-upgrades) delivered to my personal
mailbox.
I wouldn't expect /then/ to see my name, or
n,,,:/home/gklein:/bin/bash
> >
> > On my (bullseye) system, that field is what is used to get my full
> > name.
>
> It's what I'd expect to be used, unless configured otherwise.
Yes, in emails that you and I send. (Both our tests were carried out
from our bash prompts.)
> &g
On Thu, Oct 19, 2023 at 09:10:50PM +0200, Gertjan Klein wrote:
> Op 19-10-2023 om 15:00 schreef Greg Wooledge:
> > Traditional Unix terminal- or command-line-based MUAs inject new messages
> > into the outgoing mail queue by piping them to /usr/sbin/sendmail.
>
> That means, as I believe Stefan
Op 19-10-2023 om 15:00 schreef Greg Wooledge:
Traditional Unix terminal- or command-line-based MUAs inject new messages
into the outgoing mail queue by piping them to /usr/sbin/sendmail.
That means, as I believe Stefan pointed out, that they leave
authorization to this single program, for all
> Traditional Unix terminal- or command-line-based MUAs inject new messages
> into the outgoing mail queue by piping them to /usr/sbin/sendmail.
>
> Fancy GUI MUAs like Thunderbird are often written to work on either
> Windows or Unix, so they don't always offer the ability to inject through
>
On Thu, Oct 19, 2023 at 01:10:22PM +0200, Gertjan Klein wrote:
> Op 17-10-2023 om 23:20 schreef Greg Wooledge:
> > [...] This is different
> > from when an MTA accepts a message directly from a MUA. That's usually
> > called a "submission", and can use either SMTP or /usr/sbin/sendmail.
>
> So
Op 18-10-2023 om 18:30 schreef David Wright:
On Tue 17 Oct 2023 at 19:41:43 (+0200), Gertjan Klein wrote:
gklein@parvos:~$ cat /etc/passwd | grep gklein
gklein:x:1000:1000:Gertjan Klein,,,:/home/gklein:/bin/bash
On my (bullseye) system, that field is what is used to get my full
name.
It's
Op 17-10-2023 om 23:20 schreef Greg Wooledge:
On Tue, Oct 17, 2023 at 09:50:13PM +0200, Gertjan Klein wrote:
I do appreciate it. If I switch to bsd-mailx I have something that should
work. Although I'm concerned by the statement (on the Debian package page)
that it doesn't speak SMTP. This is
On Wed, 2023-10-18 at 13:56 -0400, Greg Wooledge wrote:
[...]
> Before stretch, if you had heirloom-mailx installed, both "mail -a file"
> and "mailx -a file" worked. After upgrading to stretch, you'd have an
> s-nail program, but *not* a mail or mailx program, so all your scripts
> would break.
On Wed, Oct 18, 2023 at 06:04:30PM +0100, Tixy wrote:
> On Wed, 2023-10-18 at 11:28 -0500, David Wright wrote:
> > (Aside: does anyone know what "heirloom-mailx" is?)
>
> I remember it being the mailx compatible program that got installed by
> default many releases ago, and it was replaced by
On Wed, 2023-10-18 at 11:28 -0500, David Wright wrote:
> (Aside: does anyone know what "heirloom-mailx" is?)
I remember it being the mailx compatible program that got installed by
default many releases ago, and it was replaced by s-nail in
2016. (Possibly as a fork of that orphaned project?)
I
don't want to receive mail on the VPS, I just want the mail the system
> > > generates to end up in my mailbox elsewhere. This works, but the mail
> > > from address looks like this: "gklein ". This irks me.
> > > My account has my full name configured;
> >
> &
On Tue, Oct 17, 2023 at 09:50:13PM +0200, Gertjan Klein wrote:
> Op 17-10-2023 om 20:40 schreef Greg Wooledge:
> > On my system, mailx points to bsd-mailx:
>
> On Geert's as well. I wonder why. I installed nullmailer, and it
> automatically pulled in mailutils. I stayed with it because I don't
Op 17-10-2023 om 20:40 schreef Greg Wooledge:
On Tue, Oct 17, 2023 at 05:43:55PM +0200, Gertjan Klein wrote:
While this is more an annoyance than a showstopper for me, I would like
the From address to look like "My name ". Does anyone here
know which program to persuade, and how to persuade it?
1 - 100 of 1785 matches
Mail list logo
