Re: No image from analog cameras with TW6816 video capture card.

First of all thanks to Dan Ritter that replied to my original post but yet I can't find his reply in the debian-user list. On Mon, Jun 03, 2024 at 10:32:27PM -0400, A. F. Cano wrote: > > I'm trying to get these Lorex SR AIS color cameras, that are supposedly > capable of 1024 x 768 max and 728 x

Re: no space left on device

t one entry in the MFT for every file on an NTFS file system > volume, including the MFT itself. All information about a file, including its > size, time and date stamps, permissions, and data content, is stored either > in MFT entries, or in space outside the MFT that is described by MFT

Re: no space left on device

:22 Stefan Monnier wrote: > >> Jan 13 19:46:06 eagle ntfs-3g[4262]: No free mft record for $MFT: No > >> space left on device > > Hmm, MFT too small? A quick search showed me this (from a forum): > > AFAIK the MFT is implemented as a "normal" file; it can gr

Re: no space left on device

>> Jan 13 19:46:06 eagle ntfs-3g[4262]: No free mft record for $MFT: No >> space left on device > Hmm, MFT too small? A quick search showed me this (from a forum): AFAIK the MFT is implemented as a "normal" file; it can grow as needed like any other file. So, as long as

Re: no space left on device

A big thank you to everybody for all the hints and support. Unfortunately I was pressured to wipe the drive and use elsewhere. Therefore I couldn't continue with any further experiments :-(

Re: no space left on device

On 1/20/25 11:15, Adam Weremczuk wrote: > Also: > > sudo mount -t exfat /dev/nvme0n1 /mnt/nvme0n1 > mount: /mnt/nvme0n1: wrong fs type, bad option, bad superblock on /dev/ > nvme0n1, missing codepage or helper program, or other error. > > makes no difference. If it thinks ex

Re: no space left on device

On 20/01/2025 23:37, Max Nikulin wrote: On 20/01/2025 23:29, Hans wrote: Am Montag, 20. Januar 2025, 17:15:40 CET schrieb Adam Weremczuk: Try "chkdsk /F /R C:" in windows, this should help. Perhaps some tool already "repaired" the drive and some filesystem structure is really corrupted by e.g

Re: no space left on device

On 1/20/25 05:37, Adam Weremczuk wrote: I don't think it's fake but it's the lack of partition being the main issue. I've just reconnected it to the previous system and found this in history: sudo mkfs.exfat /dev/nvme0n1 sudo mkdir /mnt/nvme0n1 sudo mount /dev/nvme0n1 /mnt/nvme0n1 I think the

Re: no space left on device

Am Montag, 20. Januar 2025, 17:39:19 CET schrieb Adam Weremczuk: > I'm unable to mount the disk in Windows without formatting to assigne a > letter, so can't do "chkdsk ... C:" No, you do NOT have to mount the drive. Just boot windows into rescue mode and then got to t

Re: no space left on device

n a windows computer, then you can use any windows-live-cd for that, like Falcon4, HirensBootCD or UBCD4Win. Hans Also: sudo mount -t exfat /dev/nvme0n1 /mnt/nvme0n1 mount: /mnt/nvme0n1: wrong fs type, bad option, bad superblock on /dev/nvme0n1, missing codepage or helper program, or other error. makes no difference.

Re: no space left on device

On 20/01/2025 23:29, Hans wrote: Am Montag, 20. Januar 2025, 17:15:40 CET schrieb Adam Weremczuk: Try "chkdsk /F /R C:" in windows, this should help. Perhaps some tool already "repaired" the drive and some filesystem structure is really corrupted by e.g. mbr code. You may try to get somethin

Re: no space left on device

On Mon, Jan 20, 2025 at 16:15:40 +, Adam Weremczuk wrote: > Also: > > sudo mount -t exfat /dev/nvme0n1 /mnt/nvme0n1 > mount: /mnt/nvme0n1: wrong fs type, bad option, bad superblock on > /dev/nvme0n1, missing codepage or helper program, or other error. > > makes no

Re: no space left on device

exfat /dev/nvme0n1 /mnt/nvme0n1 > mount: /mnt/nvme0n1: wrong fs type, bad option, bad superblock on > /dev/nvme0n1, missing codepage or helper program, or other error. > > makes no difference. >

Re: no space left on device

file -s /dev/sdb1 > > /dev/sdb1: DOS/MBR boot sector > > > > Perhaps it is due to "AA55h" signature in 510 and 511 bytes just like in > > MBR partition table > > <https://learn.microsoft.com/en-gb/windows/win32/fileio/exfat-specificatio > > n#3120-bootsignature-field> So tools unaware of filesystem name in 3-10 > > bytes may be confused. Maybe they do not expect a "superfloppy" and take > > MBR with no partitions hypothesis first.

Re: no space left on device

Also: sudo mount -t exfat /dev/nvme0n1 /mnt/nvme0n1 mount: /mnt/nvme0n1: wrong fs type, bad option, bad superblock on /dev/nvme0n1, missing codepage or helper program, or other error. makes no difference. On 20/01/2025 16:04, Adam Weremczuk wrote: Yes, /dev/nvme0n1 comes from the onboard M2

Re: no space left on device

t a "superfloppy" and take MBR with no partitions hypothesis first.

Re: no space left on device

. Maybe they do not expect a "superfloppy" and take MBR with no partitions hypothesis first.

Re: no space left on device

e are some tools available for checking this (I believe, in Debian there is a tool called "f3" or similar. If there are no important data on the drive, you might reformat the drive to ext2/3/4 and then use "resize2fs" to corect the settings of your drive. In the past I used to

Re: no space left on device

On Mon, Jan 20, 2025 at 13:01:35 +, Adam Weremczuk wrote: > Please see the attached illustrating that, no destructive steps taken yet. > > On 20/01/2025 12:55, Adam Weremczuk wrote: > > Gparted seems to recognise the fact that 53% of space has data written > > to it. It

Re: no space left on device

There are fake 4TB drives in the market. Maybe you got one? There are some tools available for checking this (I believe, in Debian there is a tool called "f3" or similar. If there are no important data on the drive, you might reformat the drive to ext2/3/4 and then use "resiz

Re: no space left on device

Please see the attached illustrating that, no destructive steps taken yet. On 20/01/2025 12:55, Adam Weremczuk wrote: Gparted seems to recognise the fact that 53% of space has data written to it. It also knows about the extfat system. This morning, when I viewed the drive through gparted on a

Re: no space left on device

an entire disk, but that disk has an msdos partition table with*no* partitions. There are several problems here: 1) An msdos partition table only supports disks up to 2 TB and yours is 4 TB. 2) You didn't create any partitions. 3) You didn't create an exfat file syste

Re: no space left on device

al/physical): 512B/512B > Partition Table: msdos > Disk Flags: > > Number Start End Size Type File system Flags > > (parted) You're trying to mount an entire disk, but that disk has an msdos partition table with *no* partitions. There are several problems here: 1)

Re: no space left on device

On Jan 20, 2025, Adam Weremczuk wrote: > Hi all, > > An update on my struggle. > > I followed the extfat path but I likely somehow make a noobish mistake > and a partition was not created... > > Despite that, I was able to mount it an copy all the data across to it! > > Now when I try to mount

Re: no space left on device

Hi all, An update on my struggle. I followed the extfat path but I likely somehow make a noobish mistake and a partition was not created... Despite that, I was able to mount it an copy all the data across to it! Now when I try to mount the NVMe on a different Ubuntu system (through USB adap

Re: no space left on device

On Wed, Jan 15, 2025 at 10:43:57AM -0500, Michael Stone wrote: > On Wed, Jan 15, 2025 at 05:53:18AM +0100, to...@tuxteam.de wrote: [...] > > It is most probably that the NTFS is running out of mft records, a > > resource you set up when making the ntfs file system [...] > I'm skeptical of this a

Re: no space left on device

ate (HDD -> NVMe). > > That's significantly faster than before. > > Partially because I'm using "rsync -avh --no-perms --no-group --no-owner > ..." this time. fuse is slow in general and that applies to ntfs-3g. There's a kernel exfat module which wi

Re: about output from mount (was: no space left on device)

Felix Miata writes: > I have the following in ~/.bashrc for making that easier: > > alias Mnt='mount | egrep -v "cgroup|rpc|ramfs|tmpfs|^sys|on /dev|on /proc|on > /sys|on /var" | sort ' mount | fgrep -vf <(awk '/^nodev/{print $2}' /proc/filesystems) urs

Re: no space left on device

ipedia.org/wiki/SandForce#Technology I have no idea whether modern NVME drives do this or not.

Re: no space left on device

On Wed, Jan 15, 2025 at 5:51 AM Nicolas George wrote: > > Jeffrey Walton (12025-01-15): > > Using compression to minimize writes is part of a write leveling > > strategy to extend drive life. > > . > > So you say, and all you have to quo

Re: no space left on device

Jeffrey Walton (12025-01-15): > Using compression to minimize writes is part of a write leveling > strategy to extend drive life. > . So you say, and all you have to quote for it is a Google search result page. This is how far I am willi

Re: no space left on device

Using a random stream during zeroization due to write compression has > > been a security control for at least 15 years. This should be no > > surprise to anyone nowadays. > > I am not denying that. You made a different statement, that I leave > quoted, and you have nothing to

Re: no space left on device

security control for at least 15 years. This should be no > surprise to anyone nowadays. I am not denying that. You made a different statement, that I leave quoted, and you have nothing to support that statement. -- Nicolas George

Re: no space left on device

ncritical quote from a drive manufacturer. > Furthermore, it does not support your precise claim: > > > > > Probably better since disk controllers often use compression to > > > > minimize writes and blocks written during a write cycle. Using a random stream during zeroiza

Re: no space left on device

Jeffrey Walton (12025-01-15): > Reliably Erasing Data from Flash-Based Solid State Drives, > , The word compression does not appear in this document. Would you be so kind as to explain why you considered it relevant? > Practical Eras

Re: no space left on device

On Wed, Jan 15, 2025 at 3:58 AM Nicolas George wrote: > > Jeffrey Walton (12025-01-15): > > Probably better since disk controllers often use compression to > > minimize writes and blocks written during a write cycle. > > I find that statement highly dubious. Do you have a source? Reliably Erasing

Re: no space left on device

Jeffrey Walton (12025-01-15): > Probably better since disk controllers often use compression to > minimize writes and blocks written during a write cycle. I find that statement highly dubious. Do you have a source? Regards, -- Nicolas George

Re: no space left on device

harddrive. Doing so, there should be no problems with MFT or similar. Another idea, which came in my mind, to pack the whole source folder into one single file (i.e. with tar or 7z or zip whatever) and then transfer this to the NVME. Yes, I know, transferring very large

Re: no space left on device

; > 4B2QJXD7 > > > > The firmware seems to be the latest version: https:// > > semiconductor.samsung.com/consumer-storage/support/tools/ > > > > I'm giving exfat a shot and so far I'm impressed with 160 MB/s average > > transfer rate (HDD -> NVMe). &

Re: no space left on device

That's significantly faster than before. > > > > Partially because I'm using "rsync -avh --no-perms --no-group --no-owner > > ..." this time. > > fuse is slow in general and that applies to ntfs-3g. There's a kernel exfat > module which will offer perform

Re: no space left on device

On 1/14/25 19:42, Andy Smith wrote: Hi David, On Tue, Jan 14, 2025 at 07:28:28PM -0800, David Christensen wrote: I suggest that you unmount any filesystems on the SSD and then fill the SSD with random bytes using dd(1). If the purpose of this is to check that the full capacity of the NVMe is

Re: no space left on device

hat is already packaged in Debian makes this job much more straightforward. But OP's problem is more likely to be some issue with the ntfs-3g driver or the NTFS filesystem on the NVMe. Thanks, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting

Re: no space left on device

Partially because I'm using "rsync -avh --no-perms --no-group --no- owner ..." this time. I suggest that you unmount any filesystems on the SSD and then fill the SSD with random bytes using dd(1). Something like: # time dd if=/dev/randome of=/dev/nvme0n1 bs=1m status=pr

Re: no space left on device

On 1/14/25 12:03, Michael Stone wrote: On Tue, Jan 14, 2025 at 03:30:17PM +, Adam Weremczuk wrote: I need NTFS to connect it to a WS 2019 machine later. Have you considered exfat? Support for that on linux is much better than ntfs. At the very least I'd format the drive as anything ot

Re: no space left on device

On Tue, Jan 14, 2025 at 06:13:44PM +, Adam Weremczuk wrote: I'm giving exfat a shot and so far I'm impressed with 160 MB/s average transfer rate (HDD -> NVMe). That's significantly faster than before. Partially because I'm using "rsync -avh --no-perms --no-grou

Re: no space left on device

://semiconductor.samsung.com/consumer-storage/support/tools/ I'm giving exfat a shot and so far I'm impressed with 160 MB/s average transfer rate (HDD -> NVMe). That's significantly faster than before. Partially because I'm using "rsync -avh --no-perms --no-group --no-owner ..."

Re: no space left on device

On Tue, Jan 14, 2025 at 04:40:12PM +0100, Hans wrote: > Am Dienstag, 14. Januar 2025, 16:25:02 CET schrieb Adam Weremczuk: > > > Syslog reveals this: > > > > Jan 13 19:46:06 eagle ntfs-3g[4262]: No free mft record for $MFT: No > > space left on device > >

Re: no space left on device

On Tue, Jan 14, 2025 at 03:25:02PM +, Adam Weremczuk wrote: > All files copied were under 500 MB in size each, guaranteed. > > No dmesg entries from around the copy failure time. > > Syslog reveals this: > > Jan 13 19:46:06 eagle ntfs-3g[4262]: No free mft record for

Re: no space left on device

On Tue, Jan 14, 2025 at 03:30:17PM +, Adam Weremczuk wrote: I need NTFS to connect it to a WS 2019 machine later. Have you considered exfat? Support for that on linux is much better than ntfs. At the very least I'd format the drive as anything other than ntfs and retry as suggested elsewh

Re: no space left on device

>> Is it some kind of NVMe temp garbage overhead? No, it's a problem at the ntfs-3g level, not the NVMe level. > Possibly. I haven't been following the thread very attentively and have no > particular expertise, but maybe you are running to an issue similar to > the

Re: no space left on device

On 1/14/25 10:30, Adam Weremczuk wrote: > On 14/01/2025 15:14, Hans wrote: >> >> It looks like Adam wants to copy a Windows system to another drive. Maybe he >> could delete hyberfile.sys, pagefile.sys and swapfile.sys before rsyncing. >> >> These are not necessary and will be recreated at boot fro

Re: no space left on device

Greg Wooledge wrote: > On Tue, Jan 14, 2025 at 15:25:02 +, Adam Weremczuk wrote: > > Jan 13 19:46:06 eagle ntfs-3g[4262]: No free mft record for $MFT: No space > > left on device > > Jan 13 19:46:15 eagle ntfs-3g[4262]: message repeated 3154 times: [ No free > > mf

Re: no space left on device

On Tue, Jan 14, 2025 at 15:25:02 +, Adam Weremczuk wrote: > Jan 13 19:46:06 eagle ntfs-3g[4262]: No free mft record for $MFT: No space > left on device > Jan 13 19:46:15 eagle ntfs-3g[4262]: message repeated 3154 times: [ No free > mft record for $MFT: No space left on device

Re: no space left on device

Hi Adam, Adam Weremczuk writes: > All files copied were under 500 MB in size each, guaranteed. > > No dmesg entries from around the copy failure time. > > Syslog reveals this: > > Jan 13 19:46:06 eagle ntfs-3g[4262]: No free mft record for $MFT: No > space left on device

Re: no space left on device

On Tue, Jan 14, 2025 at 10:15 AM Hans wrote: > > Good idea, Klaus! > > It looks like Adam wants to copy a Windows system to another drive. Maybe he > could delete hyberfile.sys, pagefile.sys and swapfile.sys before rsyncing. Wow! That's a bit drastic, how about "rsync ... --exclude-from=FILENAME

Re: no space left on device

Am 14.01.25 um 16:30 schrieb Adam Weremczuk: I need NTFS to connect it to a WS 2019 machine later. I thought it would be easier than fiddling with WSL or pay for something like: https://www.paragon-software.com/home/linuxfs-windows/ (which seems decent) Why do you connect the HD to 2019

Re: no space left on device

of data to that drive (26+ > million files, tens of thousands of folders, about 2TB in total). > > I copied from an internal 8TB SATA HDD formatted with ext4. > > After running for several hours, it refused to continue due to "no space > left on device". > > I

Re: no space left on device

Am Dienstag, 14. Januar 2025, 16:25:02 CET schrieb Adam Weremczuk: > Syslog reveals this: > > Jan 13 19:46:06 eagle ntfs-3g[4262]: No free mft record for $MFT: No > space left on device Hmm, MFT too small? A quick search showed me this (from a forum): No

Re: no space left on device

I need NTFS to connect it to a WS 2019 machine later. I thought it would be easier than fiddling with WSL or pay for something like: https://www.paragon-software.com/home/linuxfs-windows/ (which seems decent) On 14/01/2025 15:14, Hans wrote: Good idea, Klaus! It looks like Adam wants to cop

Re: no space left on device

All files copied were under 500 MB in size each, guaranteed. No dmesg entries from around the copy failure time. Syslog reveals this: Jan 13 19:46:06 eagle ntfs-3g[4262]: No free mft record for $MFT: No space left on device Jan 13 19:46:06 eagle ntfs-3g[4262]: message repeated 40 times: [ No

Re: no space left on device

ere is a tool called "f3" for checking this. It is packaged in Debian so probably is in Ubuntu also. Thanks, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting

Re: no space left on device

Good idea, Klaus! It looks like Adam wants to copy a Windows system to another drive. Maybe he could delete hyberfile.sys, pagefile.sys and swapfile.sys before rsyncing. These are not necessary and will be recreated at boot from Windows next time. Just an idea Hans > My assumption is: thi

Re: no space left on device

On Tue, Jan 14, 2025 at 03:58:50PM +0100, Klaus Singvogel wrote: > Adam Weremczuk wrote: > > > > The command was: > > > > rsync -av /mnt/sdb1/data-mirror/ /mnt/nvme0n1p1/data-mirror/ --progress > > --delete > > If you're running out of disk space, use option "--delete-before" instead of > "--d

Re: no space left on device

Adam Weremczuk wrote: > > The command was: > > rsync -av /mnt/sdb1/data-mirror/ /mnt/nvme0n1p1/data-mirror/ --progress > --delete If you're running out of disk space, use option "--delete-before" instead of "--delete" But the option --delete-before is more dangerous, as you might loose files,

Re: no space left on device

On Tue, Jan 14, 2025 at 09:48:36AM -0500, Stefan Monnier wrote: > > After running for several hours, it refused to continue due to "no space > > left on device". > > I've confirmed the problem trying to save a text file there, same error. > > Hmm... I d

Re: no space left on device

Adam Weremczuk wrote: > The last few line before termination were: > > 47,997 100%2.29MB/s0:00:00 (xfr#19403697, to-chk=0/25525501) > rsync: [receiver] mkstemp > "/mnt/nvme0n1p1/data-mirror/20241231/.task_id.OyhQxa" failed: No space left > on device (28) &g

Re: about output from mount (was: no space left on device)

Greg Wooledge composed on 2025-01-14 07:30 (UTC-0500): > Finally, please show the mount options of whatever file system is > full. This means grepping something out of the output of "mount". > It can be difficult to get the right line sometimes. I have the following in ~/.bashrc for making that

Re: no space left on device

> After running for several hours, it refused to continue due to "no space > left on device". > I've confirmed the problem trying to save a text file there, same error. Hmm... I don't see anything amiss in the data you sent, so I'm afraid I don't know wha

Re: no space left on device

Hi Hans, You are incorrect, the source (directory) is 2TB in size: root@eagle:~# du -sh /mnt/sdb1/data-mirror 2.0T/mnt/sdb1/data-mirror and the destination drive (started blank and empty) reported 3.7 TB capacity. The question is why rsync and disk space tools disagree whether there sho

Re: no space left on device

Am 14.01.25 um 15:12 schrieb Greg Wooledge: ntfs partition is reported via the "mount" command, among others. So this is an NTFS file system that you're writing to? I think that's got to be related to your problems somehow. Maybe you're exceeding some limit in the Linux NTFS driver (singl

Re: no space left on device

Google says: When an NTFS partition is reported as "FUSEBLK", it means that the partition is being mounted with the FUSE file system in userspace. This is normal and allows non-root users to read and write to the partition. "FUSEBLK" is just how an NTFS partition is reported via the "mount"

Re: no space left on device

Source is sdb1, target is nvme0n1p1 > rsync -av /mnt/sdb1/data-mirror/ /mnt/nvme0n1p1/data-mirror/ --progress > --delete > root@eagle:~# df -h /mnt/nvme0n1p1 > Filesystem Size Used Avail Use% Mounted on > /dev/nvme0n1p1 3.7T 1.1T 2.6T 30% /mnt/nvme0n1p1 Your target has 1,1 TB free. >

Re: no space left on device

On Tue, Jan 14, 2025 at 14:05:46 +, Adam Weremczuk wrote: > Mount options of the destination as requested: > > root@eagle:~# mount | grep /mnt/nvme0n1p1 > /dev/nvme0n1p1 on /mnt/nvme0n1p1 type fuseblk > (rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096) What on earth is a fuseblk? G

Re: no space left on device

Hi Greg, The last few line before termination were: 47,997 100%2.29MB/s0:00:00 (xfr#19403697, to-chk=0/25525501) rsync: [receiver] mkstemp "/mnt/nvme0n1p1/data-mirror/20241231/.task_id.OyhQxa" failed: No space left on device (28) sent 1,889,449,185,360 bytes received 3

Re: no space left on device

On Tue, Jan 14, 2025 at 11:49:25 +, Adam Weremczuk wrote: > After running for several hours, it refused to continue due to "no space > left on device". > > I've confirmed the problem trying to save a text file there, same error. Please show us all of the details, *

Re: no space left on device

On Tue, Jan 14, 2025 at 11:49:25AM +, Adam Weremczuk wrote: > I started copying (with rsync) a large chunk of data to that drive (26+ > million files, tens of thousands of folders, about 2TB in total). > That much has been copied so far: > > find /mnt/nvme0n1p1 -type f | wc -l > 19868844 Th

no space left on device

about 2TB in total). I copied from an internal 8TB SATA HDD formatted with ext4. After running for several hours, it refused to continue due to "no space left on device". I've confirmed the problem trying to save a text file there, same error. That much has been copied so far:

Re: SSL error:FFFFFFFF80000002:system library::No such file or directory: ../crypto/bio/bss_file.c:67 when I'm trying to sign the nvidia driver on Debian 12.

On 11/26/24 12:59, Mario Marietto wrote: 2) # apt install nvidia-detect nvidia-driver You first did an `update`. Also the wiki at [1] suggest to install other PKGs. [1] https://www.reddit.com/r/debian/comments/1h08w9v/ssl_error8002system_libraryno_such/?rdt=41730 -- John Doe

SSL error:FFFFFFFF80000002:system library::No such file or directory: ../crypto/bio/bss_file.c:67 when I'm trying to sign the nvidia driver on Debian 12.

/sign-file sha512 /var/lib/shim-signed/mok/MOK.priv /var/lib/shim-signed/mok/MOK.der /lib/modules/5.19.0-23-generic/updates/dkms/nvidia.ko At main.c:298: - SSL error:8002:system library::No such file or directory: ../crypto/bio/bss_file.c:67 - SSL error:1080:BIO routines::no suc

Re: needrestart no longer depends on libmodule-scandeps-perl?

On Tue, Nov 19, 2024 at 1:39 PM Mike Kupfer wrote: > > I noticed that after updating 'needrestart' to 3.6-4+deb12u2, the > 'libmodule-scandeps-perl' package now shows up in the autoremove list. > (In a VM that still has the 3.6-4+deb12u1 'needrestart', trying to > remove 'libmodule-scandeps-perl'

Re: apt-get changelog [was: needrestart no longer depends on libmodule-scandeps-perl?]

Charles Curley wrote: > On Wed, 20 Nov 2024 06:22:50 +0100 > wrote: > > > Hm. "apt-get changelog needrestart" works for me? Since apt delegates > > to apt-get, it should do the same... in fact, it works, too. > > > > What's missing? > > Possibly trixie v. bookworm. Specifically, I think it ha

No display found with Nvidia RTX 4060 Ti

lxserver_nvidia" [   149.799] (II) Unloading glxserver_nvidia [   149.799] (II) UnloadSubModule: "wfb" [   149.799] (EE) Screen(s) found, but none have a usable configuration. [   149.799] (EE) Fatal server error: [   149.799] (EE) no screens found(EE) [   149.799] (EE) Please consult th

needrestart no longer depends on libmodule-scandeps-perl?

I noticed that after updating 'needrestart' to 3.6-4+deb12u2, the 'libmodule-scandeps-perl' package now shows up in the autoremove list. (In a VM that still has the 3.6-4+deb12u1 'needrestart', trying to remove 'libmodule-scandeps-perl' will also remove 'needrestart'.) Can someone confirm that thi

Re: apt-get changelog [was: needrestart no longer depends on libmodule-scandeps-perl?]

On Wed, Nov 20, 2024 at 06:36:08AM -0700, Charles Curley wrote: > On Wed, 20 Nov 2024 06:22:50 +0100 > wrote: > > > Hm. "apt-get changelog needrestart" works for me? Since apt delegates > > to apt-get, it should do the same... in fact, it works, too. > > > > What's missing? > > Possibly trixie

Re: apt-get changelog [was: needrestart no longer depends on libmodule-scandeps-perl?]

On Wed, 20 Nov 2024 06:22:50 +0100 wrote: > Hm. "apt-get changelog needrestart" works for me? Since apt delegates > to apt-get, it should do the same... in fact, it works, too. > > What's missing? Possibly trixie v. bookworm. Bookworm: charles@issola:~$ apt-get changelog needrestart Err:1 htt

apt-get changelog [was: needrestart no longer depends on libmodule-scandeps-perl?]

On Tue, Nov 19, 2024 at 11:39:53AM -0800, Mike Kupfer wrote: > Christian Britz wrote: > > > See the changelog: > > * debian/control: Drop Depends on libmodule-scandeps-perl > > Thanks. I had tried looking at the changelog, but Synaptic and apt were > unable to find it. Hm. "apt-get changelog ne

Re: needrestart no longer depends on libmodule-scandeps-perl?

Erwan David wrote: > However the depency is back for 3.7-3 in testing The dependency was removed for 3.7-3.1, which is in unstable at the moment. mike

Re: needrestart no longer depends on libmodule-scandeps-perl?

Le 19/11/2024 à 20:39, Mike Kupfer a écrit : Christian Britz wrote: See the changelog: * debian/control: Drop Depends on libmodule-scandeps-perl Thanks. I had tried looking at the changelog, but Synaptic and apt were unable to find it. Okay. After some poking around, I now see a couple ways

Re: needrestart no longer depends on libmodule-scandeps-perl?

Christian Britz wrote: > See the changelog: > * debian/control: Drop Depends on libmodule-scandeps-perl Thanks. I had tried looking at the changelog, but Synaptic and apt were unable to find it. Okay. After some poking around, I now see a couple ways to get at the changelog. One is the copy i

Re: needrestart no longer depends on libmodule-scandeps-perl?

Am 19.11.24 um 19:16 schrieb Mike Kupfer: > I noticed that after updating 'needrestart' to 3.6-4+deb12u2, the > 'libmodule-scandeps-perl' package now shows up in the autoremove list. > (In a VM that still has the 3.6-4+deb12u1 'needrestart', trying to > remove 'libmodule-scandeps-perl' will also

Re: No sound after migrate to Bookworm

i386 version: apt install pipewire-bin pipewire-bin:i386- apt autoremove Now pipewire start correctly on login. Le 13/11/2024 à 15:00, Martin a écrit : Hi I have no sound anymore since I upgrade from Debian Bullseye to Bookworm. I use Gnome desktop environement. pipewire, pipewire-pulse and

No sound after migrate to Bookworm

Hi I have no sound anymore since I upgrade from Debian Bullseye to Bookworm. I use Gnome desktop environement. pipewire, pipewire-pulse and wireplumber are installed and enabled for users by systemd like on a fresh bookworm install. If I exec pipewire, pipewire-pulse and wireplumber

Re: No kernel

On Wed, 2024-11-06 at 15:01 -0500, Dan Ritter wrote: > Van Snyder wrote: > > I tried to use the netinst to install Debian 12.5 onto a Dell > > Inspiron > > 15. Eventually, after the usual things, it said there was no > > kernel. So > > I tried the 12.1.0 neti

Re: No kernel

On Wed, 06 Nov 2024 10:57:56 -0800 Van Snyder wrote: > I tried to use the netinst to install Debian 12.5 onto a Dell Inspiron > 15. Eventually, after the usual things, it said there was no kernel. > So I tried the 12.1.0 netinst and it also said there was no kernel. > What happene

Re: No kernel

Van Snyder wrote: > I tried to use the netinst to install Debian 12.5 onto a Dell Inspiron > 15. Eventually, after the usual things, it said there was no kernel. So > I tried the 12.1.0 netinst and it also said there was no kernel. What > happened? How can I install? "no kernel

No kernel

I tried to use the netinst to install Debian 12.5 onto a Dell Inspiron 15. Eventually, after the usual things, it said there was no kernel. So I tried the 12.1.0 netinst and it also said there was no kernel. What happened? How can I install?

Re: If one sets 'Defaults rootpw' in sudoers but no root password is it disaster?

ng root? Would the only way > > > out be to boot into single user mode to mend things? > > > > Mostly, yes. > > > > > > > ... or is visudo clever enough to spot this? > > > > No. > > > > How about this: > > > > Create a second user

Re: If one sets 'Defaults rootpw' in sudoers but no root password is it disaster?

mend things? > > Mostly, yes. > > > > ... or is visudo clever enough to spot this? > > No. > > How about this: > > Create a second user -- we'll call it foo. Give foo sudo > privileges. Take away sudo privileges from your normal account. > > No

Re: If one sets 'Defaults rootpw' in sudoers but no root password is it disaster?

reate a root password. (This is on systems where, > previously, I've never had a root password). > > Would this totally lock me out from becoming root? Would the only way > out be to boot into single user mode to mend things? Mostly, yes. > ... or is visudo clever en

Re: If one sets 'Defaults rootpw' in sudoers but no root password is it disaster?

I am to tired to test this now - but I guess as prerequisite you should then give the root user a password.  A long time ago I was "providing" root with a password in some Debian or Ubuntu system using 'passwd'. sudo should not cope with an undefined root password, and visudo is just a wrapper

  1   2   3   4   5   6   7   8   9   10   >