Re: [DNG] rm not freeing space (SOLVED)
Quoting Marc Shapiro via Dng (dng@lists.dyne.org):
> On 3/19/21 8:31 PM, tempforever via Dng wrote:
> >
> >To find files last modified in January:
> >(adjust the dates as needed; on Mar. 19 this should locate files dated
> >Jan 1 - 31 but it could be off a day or so)
> >
> >cd /media/archives
> >find -type f -mtime -78 -mtime +46 -ls
>
> Thank you!
>
> That found the files. They were in a hidden directory
> '/media/archives/.Trash-0'.
Aha! For your future convenience, here is a Perl script I get a lot of
use from, when looking for the (individually) largest files within $PWD
and its subtrees:
:r /usr/local/bin/largest20
#!/usr/bin/perl -w
# You can alternatively just do:
# find . -xdev -type f -print0 | xargs -r0 ls -l | sort -rn -k +5 | head -20
# Sometimes also handy: du -cks * | sort -rn
use File::Find;
@ARGV = $ENV{ PWD } unless @ARGV;
find ( sub { $size{ $File::Find::name } = -s if -f; }, @ARGV );
@sorted = sort { $size{ $b } <=> $size{ $a } } keys %size;
splice @sorted, 20 if @sorted > 20;
printf "%10d %s\n", $size{$_}, $_ for @sorted
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Strange behaviour with last version of grub
In der Nachricht vom Tuesday, 9 March 2021 18:40:22 CET schrieb Adrian Zaugg: > In der Nachricht vom Saturday, 6 March 2021 19:16:13 CET schrieb fsmithred > via > Dng: > > I could not reproduce the problem on a system that boots legacy bios and > > uses grub-pc. > > ...my machine where it happened is a Legacy-BIOS-MBR-Installation. The problem I encountered was something different, but maybe related. My machine booted into the grub menu, loaded initrd, stayed blank, changed screen resolution and still did not show any boot message. It did answer pings but sshd did not come up, keyboard strokes ignored. Inspecting the machine with a live distro I found the linux image installed is from the package linux-image-4.19.0-14-amd64, which is ...signed. I never realized before this image to be signed. I installed linux-image-4.19.0-14- amd64-unsigned and the machine came back up as usual. Since when is the standard stock kernel signed? Regards, Adrian. signature.asc Description: This is a digitally signed message part. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Netiquette
On Wed, 17 Mar 2021, Florian Zieboll via Dng wrote: > On Wed, 17 Mar 2021 12:53:58 + (GMT) > Jim Jackson wrote: > > > for the record alpine is broken in that area. As far as I can make > > out it just uses the subject line to "thread" emails (modulo the > > various "re:"s etc) > > > It's a while ago that I used (al)pine (in fact, it was still pine back > then, IIRC in combination with fetchmail). Nevertheless, I'd bet that > you can make alpine sort threads by the "References" header. Just out > of curiosity, I did a quick websearch and found the following document: > > http://www.chiark.greenend.org.uk/doc/alpine-doc/tech-notes/config.html#show-sort well well well. Many thanks for that. And I thought I knew my way around alpine :-( As they say: Familiarity breeds contempt! > > libre Gr??e, > Florian > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] rm not freeing space (SOLVED)
On 3/19/21 8:31 PM, tempforever via Dng wrote: To find files last modified in January: (adjust the dates as needed; on Mar. 19 this should locate files dated Jan 1 - 31 but it could be off a day or so) cd /media/archives find -type f -mtime -78 -mtime +46 -ls Thank you! That found the files. They were in a hidden directory '/media/archives/.Trash-0'. I had seen this before and I really thought that I had checked this directory. Possibly, I checked it as myself and not as root. That would have given me a 'permissions denied' error. Although I would normally try again as root, perhaps I missed that step. I have seen posts that suggest this directory is created when deleting files with a file manager, not from the command line. Even so, despite the fact that I usually do my file management from the command line that is not always the case, it seems odd that this is the ONLY such directory that I can find anywhere in my directory tree. If I look at 'Trash' in my file manager (caja) it shows some other files, but not the ones in question. In any case, deleting the files under '/media/archive/.Trash-0/files' and '/media/archive/.Trash-0/info' freed up about 618 GB of space (some files when back to October). Now, '/media/archives' is about 46% used, instead of 84%, and I am much happier. Thank you to all who have responded to my request for help. We can now put this issue to rest. Marc ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] No future?
On Sat, 20 Mar 2021 17:21:43 +0100 Florian Zieboll via Dng wrote: > It's still about leaves hanging on the same ol' tree. s/hanging/growing/ :-) Cheerio, Florian ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Upgrade from buster to beowulf, runlevels are goofed
‐‐‐ Original Message ‐‐‐ On Sunday, March 21, 2021 10:07 AM, Antony Stone wrote: > On Sunday 21 March 2021 at 10:57:46, Erich Minderlein via Dng wrote: > > > In the times of SuSE 7.0 to 7.3 I used runlevels to control a server with > > attached thin clients. The users on the system got a wall message and had > > to save their work. After a few minutes the runlevel was reduced from 5 to > > 3. > > That's a long time ago. > > > Now I find that the runlevels are identical from 2 to 5 as opposed to the > > old times, when they were substantially differentiated. (root only, +local > > multi-user, +network, +Xserver) Is this a heritage of the debian > > distribution crippled by the poeystemd? > > No, Debian has had identical runlevels 2-5 for many releases, nothing to do > with systemd. > > > Can I obtain a devuan different more clever system with update-rc.d ? > > I'm not quite sure what you're looking for - I've never tried Debian Buster, > but Devuan Beowulf works fine for me, and I happened yesterday to have to > install a sysvinit startup file (for zoneminder, which no longer comes with > one > by default), which got installed using update-rc.d without any problem. > > > https://en.wikipedia.org/wiki/Runlevel#Linux_Standard_Base_specification > > devuan (beowulf standard installation with some cruft maybe) as I have it > > on my notebooks does not conform to the LSB. > > Devuan is based on Debian, and that project dropped LSB support in 2015: > https://wiki.debian.org/LSB > > You can have LSB, or you can have Debian/Devuan, but it's not easy to have > both. > The only change that I can recall since the very very early days is that the runlevels used to step either incrementally or decrementally through all states between the current runlevel and the target runlevel e.g. 2>3>4>5 and 4>3>2>1 instead of jumping straight to 5 or straight to 1. The sysvinit scripts require LSB headers on Debian/Devuan. The drop of LSB by Debian refers to not complying with the whole LSB specification which dictates far more than just the init scripts. There is nothing to prevent from defining different states at different runlevels. There is no practical way of determining what will be required at system build time by a generic installation utility, it is up to the system administrator to customise the install appropriately after. man update-rc.d publickey - g4sra@protonmail.com - 0x42E94623.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Upgrade from buster to beowulf, runlevels are goofed
On Sunday 21 March 2021 at 10:57:46, Erich Minderlein via Dng wrote: > In the times of SuSE 7.0 to 7.3 I used runlevels to control a server with > attached thin clients. The users on the system got a wall message and had > to save their work. After a few minutes the runlevel was reduced from 5 to > 3. That's a long time ago. > Now I find that the runlevels are identical from 2 to 5 as opposed to the > old times, when they were substantially differentiated. (root only, +local > multi-user, +network, +Xserver) Is this a heritage of the debian > distribution crippled by the poeystemd? No, Debian has had identical runlevels 2-5 for many releases, nothing to do with systemd. > Can I obtain a devuan different more clever system with update-rc.d ? I'm not quite sure what you're looking for - I've never tried Debian Buster, but Devuan Beowulf works fine for me, and I happened yesterday to have to install a sysvinit startup file (for zoneminder, which no longer comes with one by default), which got installed using update-rc.d without any problem. > https://en.wikipedia.org/wiki/Runlevel#Linux_Standard_Base_specification > devuan (beowulf standard installation with some cruft maybe) as I have it > on my notebooks does not conform to the LSB. Devuan is based on Debian, and that project dropped LSB support in 2015: https://wiki.debian.org/LSB You can have LSB, or you can have Debian/Devuan, but it's not easy to have both. Antony. -- Wanted: telepath. You know where to apply. Please reply to the list; please *don't* CC me. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Upgrade from buster to beowulf, runlevels are goofed
Hi Now I upgraded my other notebook from buster to beowulf. No more debian systems chez moi. I followed the advice from the website. However, the upgrades of the notebooks were not smooth. On the 2nd NB when I started the system after the dist-upgrade, it went straight into the Xserver. Only the xserver keyboard driver was lost in the process of upgrading. Only the power button on the NB could save, no, delete the situation. After changing /etc/rc2.d/S04lightdm to /etc/rc2.d/_S04lightdm I could safely boot and do the missing work. In the times of SuSE 7.0 to 7.3 I used runlevels to control a server with attached thin clients. The users on the system got a wall message and had to save their work. After a few minutes the runlevel was reduced from 5 to 3. This stopped the x client on the server, while maintaining the network connection. A backup was made, and when finished, the runlevel was increased to 5 and the thin clients (with a blank screen) obtained their login screen automagically again. It was extremely simple to accomplish. Since the times of SuSE7.3, after with I switched to debian in 2003, I did not observe the sysvinit/runlevels, there was no need to, until I obtained the systemd message: A service required was not available at start. Now I find that the runlevels are identical from 2 to 5 as opposed to the old times, when they were substantially differentiated. (root only, +local multi-user, +network, +Xserver) Is this a heritage of the debian distribution crippled by the poeystemd? Can I obtain a devuan different more clever system with update-rc.d ? https://debianforum.de/forum/viewtopic.php?t=173006 https://de.wikipedia.org/wiki/Runlevel#Beispiel_Linux https://en.wikipedia.org/wiki/Runlevel#Linux_Standard_Base_specification devuan (beowulf standard installation with some cruft maybe) as I have it on my notebooks does not conform to the LSB. Before filing a bug, I ask for the opinion here in the forum. -- mit freundlichen Grüßen with the beste regards cordialement Erich |\/|inderlei|\| -- ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
