Posts by alexkemp

alexkemp · Other Issues

golinux wrote:

Devuan only forks a few hundered packages.

Love the "only"; yikes!

alexkemp · Off-topic

OK, dd has finally finished & I can get a first look at both images.

(Life with this desktop is not as easy at this moment as it should be: the 1TB hdd is 97% full, which means that there is some serious clear-out to be done, and as I work HandBreak is ripping an ancient Blu-ray to disc which means 100% on the CPU, 6 hours to rip it, 2% swap, and as soon as swap initiates I notice that the performance of the whole system falls through the floor.)

part1.img seems to be composed entirely of null-bytes:

:~/TMP$ hexdump -C part1.img | head
00000000  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
01000000

part2.img is NOT an exFAT fs:

$ mdir -i part2.img -a
Unknown media type f5
$ hexdump -C part2.img | head
00000000  98 56 46 c4 a3 02 69 13  da 93 4f 6a fc 9b 87 72  |.VF...i...Oj...r|
00000010  0e 17 d8 67 56 d6 1f 53  1b 0f f4 b7 cd 4d c4 c1  |...gV..S.....M..|
00000020  75 27 9c a0 10 c7 43 3a  a5 be 2a 08 63 5d 51 48  |u'....C:..*.c]QH|
00000030  24 37 00 54 38 66 ca 64  4f 9a 61 e7 e3 8c 63 9c  |$7.T8f.dO.a...c.|
00000040  9b ca 08 17 86 78 f4 61  07 ae 54 9f ce da 2e 66  |.....x.a..T....f|
00000050  89 fe dd 59 27 fb c8 ad  d4 11 1f 8d 31 3c 17 a7  |...Y'.......1<..|
00000060  1b bb 51 b8 74 8a b8 21  9f ec cc f4 32 74 2b 9a  |..Q.t..!....2t+.|
00000070  c8 e1 e4 4d 16 e3 dd 88  6e e0 63 c7 3e 48 7c f9  |...M....n.c.>H|.|
00000080  db ce 24 6f 97 5a b9 62  8b 2e e4 e3 2a dd 95 c2  |..$o.Z.b....*...|
00000090  24 1d 8e a0 a2 15 f7 51  d9 4e 38 2f 92 a4 5c 17  |$......Q.N8/..\.|

alexkemp · Off-topic

A little extra:

Checking the disk-image ‘sdc64gb.img’ that I took using dd at 02:59 this morning shows the reason that testdisk reports it as an EFI partition (look at 00000200):–

$ la
total 62367844
-rw-r--r-- 1 alexk alexk 63864569856 Jun 11 02:59 sdc64gb.img
alexk@ng3:~/TMP$ hexdump -C sdc64gb.img | less
00000000  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
000001c0  02 00 ee ff ff ff 01 00  00 00 ff 4f 6f 07 00 00  |...........Oo...|
000001d0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
000001f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..............U.|
00000200  45 46 49 20 50 41 52 54  00 00 01 00 5c 00 00 00  |EFI PART....\...|
00000210  cb cc 43 cd 00 00 00 00  01 00 00 00 00 00 00 00  |..C.............|
00000220  ff 4f 6f 07 00 00 00 00  22 00 00 00 00 00 00 00  |.Oo.....".......|
00000230  de 4f 6f 07 00 00 00 00  82 13 4b 1d 39 c6 3d 44  |.Oo.......K.9.=D|
00000240  9d 04 e4 c1 d8 ad b9 0b  02 00 00 00 00 00 00 00  |................|
00000250  80 00 00 00 80 00 00 00  98 a4 38 f4 00 00 00 00  |..........8.....|
00000260  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
00000400  a2 10 a7 19 ca b3 e4 11  b0 26 10 60 4b 88 9d cf  |.........&.`K...|
00000410  fb c6 93 19 db 24 c6 4f  94 52 35 21 39 17 8b d0  |.....$.O.R5!9...|
00000420  00 08 00 00 00 00 00 00  ff 87 00 00 00 00 00 00  |................|
00000430  00 00 00 00 00 00 00 00  61 00 6e 00 64 00 72 00  |........a.n.d.r.|
00000440  6f 00 69 00 64 00 5f 00  6d 00 65 00 74 00 61 00  |o.i.d._.m.e.t.a.|
00000450  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
00000480  a4 1e 3d 19 ca b3 e4 11  b0 75 10 60 4b 88 9d cf  |..=......u.`K...|
00000490  6a 46 de cf 74 a0 c9 7a  0a 48 a7 66 19 2a d9 4a  |jF..t..z.H.f.*.J|
000004a0  00 88 00 00 00 00 00 00  de 4f 6f 07 00 00 00 00  |.........Oo.....|
000004b0  00 00 00 00 00 00 00 00  61 00 6e 00 64 00 72 00  |........a.n.d.r.|
000004c0  6f 00 69 00 64 00 5f 00  65 00 78 00 70 00 61 00  |o.i.d._.e.x.p.a.|
000004d0  6e 00 64 00 00 00 00 00  00 00 00 00 00 00 00 00  |n.d.............|
000004e0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|

It's a damn shame that it could not detect the fstype.

alexkemp · Off-topic

Now tried selecting FAT32 for both partitions, leading to this screen:

TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org

Disk /dev/sdc - 63 GB / 59 GiB - CHS 60906 64 32
     Partition               Start        End    Size in sectors
 P EFI System                  2048      34815      32768
>P EFI System                 34816  124735454  124700639

Structure: Ok.  Use Up/Down Arrow keys to select partition.
Use Left/Right Arrow keys to CHANGE partition characteristics:
                P=Primary  D=Deleted
Keys A: add partition, L: load backup, T: change type, P: list files,
     Enter: to continue
63 GB / 59 GiB

… but no joy. Choosing P to list files gave the following screen:–

TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org
   P EFI System                  2048      34815      32768
Directory /

No file found, filesystem may be damaged.

Use Right to change directory, h to hide deleted files
    q to quit, : to select the current file, a to select all files
    C to copy the selected files, c to copy the current file

I'm going to leave this now. testdisk cannot find the fstype, and there are too many options to try to guess.

alexkemp · Off-topic

This post is about using testdisk

When launched all by itself, testdisk launches into it’s own text-window with highlit-options to choose from. We select Create:–

TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org

TestDisk is free data recovery software designed to help recover lost
partitions and/or make non-booting disks bootable again when these symptoms
are caused by faulty software, certain types of viruses or human error.
It can also be used to repair some filesystem errors.

Information gathered during TestDisk use can be recorded for later
review. If you choose to create the text file, testdisk.log , it
will contain TestDisk options, technical information and various
outputs; including any folder/file names TestDisk was used to find and
list onscreen.

Use arrow keys to select, then press Enter key:
>[ Create ] Create a new log file
 [ Append ] Append information to log file
 [ No Log ] Don't record anything

Now /dev/sdc is chosen …

!!! REMEMBER !!! This is running as root. This is the perfect opportunity to shaft a working system. Be very careful!

:–

TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org

  TestDisk is free software, and
comes with ABSOLUTELY NO WARRANTY.

Select a media (use Arrow keys, then press Enter):
 Disk /dev/sda - 1000 GB / 931 GiB - WDC WD10EZEX-08Y20A0
>Disk /dev/sdc - 63 GB / 59 GiB - Generic- SD/MMC

>[Proceed ]  [  Quit  ]

Note: Disk capacity must be correctly detected for a successful recovery.
If a disk listed above has an incorrect size, check HD jumper settings and BIOS
detection, and install the latest OS patches and disk drivers.

Now to select the partition (fingers crossed):–

TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org

Disk /dev/sdc - 63 GB / 59 GiB - Generic- SD/MMC

Please select the partition table type, press Enter when done.
 [Intel  ] Intel/PC partition
>[EFI GPT] EFI GPT partition map (Mac i386, some x86_64...)
 [Humax  ] Humax partition table
 [Mac    ] Apple partition map (legacy)
 [None   ] Non partitioned media
 [Sun    ] Sun Solaris partition
 [XBox   ] XBox partition
 [Return ] Return to disk selection

Hint: EFI GPT partition table type has been detected.
Note: Do NOT select 'None' for media with only a single partition. It's very
rare for a disk to be 'Non-partitioned'.

Now Analyse to try to check stuff
([ Advanced ] Filesystem Utils is used to undelete files, and is *very* effective) (no use here since files cannot be detected):–

TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org

Disk /dev/sdc - 63 GB / 59 GiB - Generic- SD/MMC
     CHS 60906 64 32 - sector size=512

>[ Analyse  ] Analyse current partition structure and search for lost partitions
 [ Advanced ] Filesystem Utils
 [ Geometry ] Change disk geometry
 [ Options  ] Modify options
 [ Quit     ] Return to disk selection

Note: Correct disk geometry is required for a successful recovery. 'Analyse'
process may give some warnings if it thinks the logical geometry is mismatched.

Choose default option (this takes a heck of a long while as it ploughs through every cylinder) (~1hr for 64G disk):–

TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org

Disk /dev/sdc - 63 GB / 59 GiB - CHS 60906 64 32
Current partition structure:
     Partition                  Start        End    Size in sectors

 1 P Unknown                     2048      34815      32768 [android_meta]
 2 P Unknown                    34816  124735454  124700639 [android_expand]

                P=Primary  D=Deleted
>[Quick Search]  [ Backup ]
                            Try to locate partition

After ~1 hour the next screen is shown:–

TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org

Disk /dev/sdc - 63 GB / 59 GiB - CHS 60906 64 32
     Partition               Start        End    Size in sectors

Keys A: add partition, L: load backup, Enter: to continue

Pressing 'A' then gives this next screen (this is NOT what a successful fix looks like):–

TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org

Disk /dev/sdc - 63 GB / 59 GiB - CHS 60906 64 32

  Unknown                        1  124735487  124735487

>[Sector]  [Sector]  [ Type ]  [ Done ]

                             Change starting sector

I entered two partitions using the former values, each with a fstype of EFI/ext2, but then trying to view files gave a "must be damaged" result. Entering a fstype EFI/unknown gave the following (no files can be viewed):–

TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org

Disk /dev/sdc - 63 GB / 59 GiB - CHS 60906 64 32
     Partition               Start        End    Size in sectors
 P EFI System                  2048      34815      32768
>P EFI System                 34816  124735454  124700639

Structure: Ok.  Use Up/Down Arrow keys to select partition.
Use Left/Right Arrow keys to CHANGE partition characteristics:
                P=Primary  D=Deleted
Keys A: add partition, L: load backup, T: change type,
     Enter: to continue
63 GB / 59 GiB

Pressing Enter now gave:

TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org

Disk /dev/sdc - 63 GB / 59 GiB - CHS 60906 64 32

     Partition                  Start        End    Size in sectors

 1 P EFI System                  2048      34815      32768
 2 P EFI System                 34816  124735454  124700639

 [  Quit  ] >[ Return ]  [ Write  ]
                         Return to partition selection

Choosing Write gave:

TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org

Write partition table, confirm ? (Y/N)

Ah well, the disk is toast anyway, so I said 'Y':

TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org

You will have to reboot for the change to take effect.

>[Ok]

Chose Quit

TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org

Disk /dev/sdc - 63 GB / 59 GiB - Generic- SD/MMC
     CHS 60906 64 32 - sector size=512

 [ Analyse  ] Analyse current partition structure and search for lost partitions
 [ Advanced ] Filesystem Utils
 [ Geometry ] Change disk geometry
 [ Options  ] Modify options
>[ Quit     ] Return to disk selection

Note: Correct disk geometry is required for a successful recovery. 'Analyse'
process may give some warnings if it thinks the logical geometry is mismatched.

and Quit:

TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org

  TestDisk is free software, and
comes with ABSOLUTELY NO WARRANTY.

Select a media (use Arrow keys, then press Enter):
 Disk /dev/sda - 1000 GB / 931 GiB - WDC WD10EZEX-08Y20A0
>Disk /dev/sdc - 63 GB / 59 GiB - Generic- SD/MMC

 [Proceed ] >[  Quit  ]
                                  Quit program
Note: Disk capacity must be correctly detected for a successful recovery.
If a disk listed above has an incorrect size, check HD jumper settings and BIOS
detection, and install the latest OS patches and disk drivers.

alexkemp · Off-topic

Hi Ralph.

Yup, did that before starting! It is a 59.5 GiB file called "sdc64gb.img". It is also worth pointing out that testdisk can also save an image of the partition(s) to disk before trying to rewrite.

ralph.ronnquist wrote:

partitions might be FAT32 (or vfat?) with an ext2 (or perhaps ext4) within

I'm spending yet another hour analysing the wretched cylinders to try that one. I previously set the fstype to 'ext2' & tried to view files & it said "none … damaged".

I'm pretty sure that I'm going to have to let the A52 reformat it & forget any existing files. I've got a very old backup on disk, but that is all.

alexkemp · Off-topic

This is a report on my attempts to recover info from a sd-card before I re-format it. Here is how the story begins:

A 64GB SD-Card was used within a SmartPrime7 (VFD-600) Android-6 mobile phone
June 08: The (non-replaceable) battery in that SmartPrime7 died
June 09: A Blackview A52 Android-12 mobile phone was obtained as a replacement
June 10: Vodaphone transferred both SIMM + SD-Card to the A52 for me
The A52 Contact list was easily populated from the SIMM during setup
The A52 wanted to re-format the SD-Card; could any data be extracted first?
The Card was plugged into a SD/MMC cardreader and then into a USB socket in my Desktop computer running Chimaera 4

The reader LED lit-up, but it did not auto-mount. I now entered into a blizzard of DDG-searches to discover how-to mount these partitions (and why they did not auto-mount).

Consulting man mount, the process at it’s simplest is the command “sudo mount device mountpoint”, where:–

‘sudo’ == in most cases this admin command must be performed as root
‘mount’ == the Devuan command to mount the device
‘device’ == the name given by Devuan to the physical device that contains a filesystem (fs)
‘mountpoint’ == a directory that pre-exists within the existing Devuan fs

There are 3 wrinkles to this command in this case:–

It usually is able to auto-detect the fs type (but not here), so a `-t fstype` will be required
‘device’ can often change on restart, meaning that a `-L Label` or `-U UUID` would be required if repetitively loaded
Any existing files within ‘mountpoint’ will no longer be accessible when a device is mounted there.

Discovering the Device

dmesg is normally the first port of call if it has just been inserted/attached, and fdisk is next, with two levels of detail available (both below). Neither helps, and an attempt at mount simply underlines the error. The fs can be found using fsck -N (no-action, and it simply reports the fs). That is fsck.ext2 which means that the fs is ‘ext2’. We try a mount with that & it fails. So, try to find alternate superblocks with mke2fs -n /dev/sdc1, and try to use an alternate superblock to fix the fs, but nothing works (the disk is in the toilet).

We need to try more desperate measures, and turn to testdisk (available from the standard distribution) (see next post).

$ sudo dmesg | tail
[  832.195604] scsi host3: usb-storage 1-1.3:1.0
[  833.219061] scsi 3:0:0:0: Direct-Access     Generic- SD/MMC           1.00 PQ: 0 ANSI: 0 CCS
[  833.219877] sd 3:0:0:0: Attached scsi generic sg3 type 0
[  834.000163] sd 3:0:0:0: [sdc] 124735488 512-byte logical blocks: (63.9 GB/59.5 GiB)
[  834.001152] sd 3:0:0:0: [sdc] Write Protect is off
[  834.001164] sd 3:0:0:0: [sdc] Mode Sense: 03 00 00 00
[  834.002150] sd 3:0:0:0: [sdc] No Caching mode page found
[  834.002160] sd 3:0:0:0: [sdc] Assuming drive cache: write through
[  834.020198]  sdc: sdc1 sdc2
[  834.020700] sd 3:0:0:0: [sdc] Attached SCSI removable disk

$ sudo fdisk -l
[sudo] password for alexk: 
…
Disk /dev/sdc: 59.48 GiB, 63864569856 bytes, 124735488 sectors
Disk model: SD/MMC          
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 1D4B1382-C639-443D-9D04-E4C1D8ADB90B

Device     Start       End   Sectors  Size Type
/dev/sdc1   2048     34815     32768   16M unknown
/dev/sdc2  34816 124735454 124700639 59.5G unknown

$ sudo fdisk -x
…
Disk /dev/sdc: 59.48 GiB, 63864569856 bytes, 124735488 sectors
Disk model: SD/MMC          
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 1D4B1382-C639-443D-9D04-E4C1D8ADB90B
First LBA: 34
Last LBA: 124735454
Alternative LBA: 124735487
Partition entries LBA: 2
Allocated partition entries: 128

Device     Start       End   Sectors Type-UUID                            UUID                                 Name           Attrs
/dev/sdc1   2048     34815     32768 19A710A2-B3CA-11E4-B026-10604B889DCF 1993C6FB-24DB-4FC6-9452-352139178BD0 android_meta   
/dev/sdc2  34816 124735454 124700639 193D1EA4-B3CA-11E4-B075-10604B889DCF CFDE466A-A074-7AC9-0A48-A766192AD94A android_expand

$ sudo fsck -N /dev/sdc1
fsck from util-linux 2.36.1
[/sbin/fsck.ext2 (1) -- /dev/sdc1] fsck.ext2 /dev/sdc1 
$ sudo fsck -N /dev/sdc2
fsck from util-linux 2.36.1
[/sbin/fsck.ext2 (1) -- /dev/sdc2] fsck.ext2 /dev/sdc2

$ mkdir -p ~/TMP/SDC1
$ mkdir -p ~/TMP/SDC2
$ sudo mount /dev/sdc1 ~/TMP/SDC1
[sudo] password for alexk: 
mount: /home/alexk/TMP/SDC1: wrong fs type, bad option, bad superblock on /dev/sdc1, missing codepage or helper program, or other error.
$ sudo mount -t ext2 /dev/sdc1 ~/TMP/SDC1
mount: /home/alexk/TMP/SDC1: wrong fs type, bad option, bad superblock on /dev/sdc1, missing codepage or helper program, or other error.

$ sudo fsck.ext2 /dev/sdc1 -v
e2fsck 1.46.2 (28-Feb-2021)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sdc1

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>

$ sudo mke2fs -n /dev/sdc1
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 16384 1k blocks and 4096 inodes
Filesystem UUID: 4fce5c0e-d330-4406-b7bf-3935e5161dac
Superblock backups stored on blocks: 
	8193

$ sudo e2fsck -b 8193 /dev/sdc1
e2fsck 1.46.2 (28-Feb-2021)
e2fsck: Invalid argument while trying to open /dev/sdc1

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>

$ sudo e2fsck -b 32768 /dev/sdc1
e2fsck 1.46.2 (28-Feb-2021)
e2fsck: Invalid argument while trying to open /dev/sdc1

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>

cd ~/TMP
$ sudo testdisk /list
[sudo] password for alexk: 
TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org
Please wait...
Disk /dev/sda - 1000 GB / 931 GiB - CHS 121601 255 63
Sector size:512
Model: WDC WD10EZEX-08Y20A0, S/N:WD-WCC3F1TLE7XN, FW:02.01A02

Disk /dev/sdc - 63 GB / 59 GiB - CHS 60906 64 32
Sector size:512
Model: Generic- SD/MMC, FW:1.00

Disk /dev/sda - 1000 GB / 931 GiB - CHS 121601 255 63
     Partition			Start        End    Size in sectors
 1 P EFI System                  2048    1050623    1048576
 2 P Linux filesys. data      1050624 1937960959 1936910336
 3 P Linux Swap            1937960960 1953523711   15562752

Disk /dev/sdc - 63 GB / 59 GiB - CHS 60906 64 32
     Partition			Start        End    Size in sectors
 1 P Unknown                     2048      34815      32768 [android_meta]
 2 P Unknown                    34816  124735454  124700639 [android_expand]

The next post will run through how-to use testdisk (and I hope that it works).

alexkemp · Other Issues

There is now a chromium-l10n update & this one is SOLVED.

/.local/sbin/update
Hit:1 http://deb.devuan.org/merged chimaera InRelease
Hit:2 http://deb.devuan.org/merged chimaera-security InRelease
Hit:3 http://deb.devuan.org/merged chimaera-updates InRelease                
Hit:4 http://deb.devuan.org/merged chimaera-proposed-updates InRelease       
Hit:5 http://deb.devuan.org/merged chimaera-backports InRelease
Hit:6 https://josm.openstreetmap.de/apt alldist InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
5 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 5 not upgraded.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  chromium chromium-common chromium-l10n chromium-sandbox josm-latest
5 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 95.5 MB of archives.
After this operation, 2,050 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://deb.devuan.org/merged chimaera-security/main amd64 chromium-l10n all 114.0.5735.90-2~deb11u1 [6,184 kB]
Get:5 https://josm.openstreetmap.de/apt alldist/universe amd64 josm-latest all 1.5.svn18746 [15.7 MB]
Get:2 http://deb.devuan.org/merged chimaera-security/main amd64 chromium amd64 114.0.5735.90-2~deb11u1 [68.5 MB]
Get:3 http://deb.devuan.org/merged chimaera-security/main amd64 chromium-common amd64 114.0.5735.90-2~deb11u1 [4,970 kB]             
Get:4 http://deb.devuan.org/merged chimaera-security/main amd64 chromium-sandbox amd64 114.0.5735.90-2~deb11u1 [134 kB]              
Fetched 95.5 MB in 9s (10.1 MB/s)                                                                                                    
Reading changelogs... Done
(Reading database ... 201190 files and directories currently installed.)
Preparing to unpack .../chromium-l10n_114.0.5735.90-2~deb11u1_all.deb ...
Unpacking chromium-l10n (114.0.5735.90-2~deb11u1) over (113.0.5672.126-1~deb11u1) ...
Preparing to unpack .../chromium_114.0.5735.90-2~deb11u1_amd64.deb ...
Unpacking chromium (114.0.5735.90-2~deb11u1) over (113.0.5672.126-1~deb11u1) ...
Preparing to unpack .../chromium-common_114.0.5735.90-2~deb11u1_amd64.deb ...
Unpacking chromium-common (114.0.5735.90-2~deb11u1) over (113.0.5672.126-1~deb11u1) ...
Preparing to unpack .../chromium-sandbox_114.0.5735.90-2~deb11u1_amd64.deb ...
Unpacking chromium-sandbox (114.0.5735.90-2~deb11u1) over (113.0.5672.126-1~deb11u1) ...
Preparing to unpack .../josm-latest_1.5.svn18746_all.deb ...
Unpacking josm-latest (1.5.svn18746) over (1.5.svn18744) ...
Setting up chromium-sandbox (114.0.5735.90-2~deb11u1) ...
Setting up chromium-common (114.0.5735.90-2~deb11u1) ...
Setting up chromium (114.0.5735.90-2~deb11u1) ...
Setting up josm-latest (1.5.svn18746) ...
Setting up chromium-l10n (114.0.5735.90-2~deb11u1) ...
Processing triggers for mailcap (3.69) ...
Processing triggers for desktop-file-utils (0.26-1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for shared-mime-info (2.0-1) ...
Processing triggers for menu (2.1.48) ...

alexkemp · Other Issues

soren wrote:

Hi,
Just use the command as so without packages

Nope (but thanks for trying).

$ sudo apt --fix-broken install
[sudo] password for alexk: 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.

boughtonp wrote:

The page also mentions a bug in the chromium-l10n package, which is about this issue:
https://bugs.debian.org/cgi-bin/bugrepo … ug=1037087

Clearly that is the issue; it is the precise error previously reported by me above. The bug report was made today (I was searching for such a report yesterday but of course, could find nothing

alexkemp · Other Issues

soren wrote:

Have you tried the following command?
sudo apt --fix-broken install

Essentially, I got the same as the previous attempts:

$ sudo apt --fix-broken install chromium-l10n chromium-shell chromium-driver chromium chromium-common chromium-sandbox josm-latest
[sudo] password for alexk: 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
chromium-l10n is already the newest version (113.0.5672.126-1~deb11u1).
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 chromium-l10n : Depends: chromium (< 113.0.5672.126-1~deb11u1.1~) but 114.0.5735.90-2~deb11u1 is to be installed
E: Unable to correct problems, you have held broken packages.

im on unstable and its still only at 113?

The latest version (albeit Windows) is 116.0.5812.0 (Sunday, June 4, 2023 Revision: 1152969).

alexkemp · Other Issues

A one-line script is run every day under my Chimaera 4 system:

sudo apt update && sudo apt install -f && sudo apt upgrade

No problems until today, when it reports that 3 of 4 available packages will be held back:

$ ~/.local/sbin/update
Hit:1 https://josm.openstreetmap.de/apt alldist InRelease
Hit:2 http://deb.devuan.org/merged chimaera InRelease
Get:3 http://deb.devuan.org/merged chimaera-security InRelease [26.2 kB]
Get:4 http://deb.devuan.org/merged chimaera-updates InRelease [26.1 kB]
Get:5 http://deb.devuan.org/merged chimaera-proposed-updates InRelease [26.6 kB]
Hit:6 http://deb.devuan.org/merged chimaera-backports InRelease
Fetched 78.9 kB in 3s (28.9 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
4 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  chromium chromium-common chromium-sandbox
The following packages will be upgraded:
  josm-latest
1 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
Need to get 15.7 MB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] n
Abort.

Cue frantic DDG searches.

A 12-year old question has good suggestions:

$ sudo apt-get --with-new-pkgs upgrade chromium chromium-common chromium-sandbox josm-latest
[sudo] password for alexk: 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 chromium-l10n : Depends: chromium (< 113.0.5672.126-1~deb11u1.1~) but 114.0.5735.90-2~deb11u1 is to be installed
E: Broken packages

$ sudo apt-get install chromium chromium-common chromium-sandbox josm-latest
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Suggested packages:
  chromium-l10n chromium-shell chromium-driver
The following packages will be REMOVED:
  chromium-l10n
The following packages will be upgraded:
  chromium chromium-common chromium-sandbox josm-latest
4 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Need to get 89.3 MB of archives.
After this operation, 80.6 MB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.

Nope; not ready for it to be removed yet.

These are the problematic packages waiting to be upgraded:

$ apt list --upgradable
Listing... Done
chromium-common/stable-security 114.0.5735.90-2~deb11u1 amd64 [upgradable from: 113.0.5672.126-1~deb11u1]
chromium-sandbox/stable-security 114.0.5735.90-2~deb11u1 amd64 [upgradable from: 113.0.5672.126-1~deb11u1]
chromium/stable-security 114.0.5735.90-2~deb11u1 amd64 [upgradable from: 113.0.5672.126-1~deb11u1]
josm-latest/unknown 1.5.svn18746 all [upgradable from: 1.5.svn18744]

So, after that blizzard of code, what to do? Is it likely that chromium-l10n may finally get updated if I am patient, or is there any other solution?

alexkemp · Other Issues

steve_v wrote:

Setting the immutable bit in extended attributes should also work - chattr +i [filename] as root.

Works perfect. Perhaps, a touch too perfect for some scenarios. But perfect to stop ALL deletions.

~$ man chattr
NAME
       chattr - change file attributes on a Linux file system
…
ATTRIBUTES
…
       i      A  file  with  the 'i' attribute cannot be modified: it cannot be deleted or renamed, no link can be created to this
              file, most of the file's metadata can not be modified, and the file can not be opened in write mode.  Only the supe‐
              ruser or a process possessing the CAP_LINUX_IMMUTABLE capability can set or clear this attribute.

~$ mkdir TMP
~$ cd TMP
~/TMP$ echo "a" > tmp.txt
~/TMP$ la tmp.txt
-rw-r--r-- 1 alexk alexk    2 Jun  3 00:04 tmp.txt
~/TMP$ sudo chown root.root tmp.txt
[sudo] password for alexk: 
~/TMP$ sudo chattr +i tmp.txt
~/TMP$ la tmp.txt
-rw-r--r-- 1 root root 2 Jun  3 00:04 tmp.txt
~/TMP$ chmod 0700 tmp.txt
chmod: changing permissions of 'tmp.txt': Operation not permitted
~/TMP$ sudo chmod 0700 tmp.txt
chmod: changing permissions of 'tmp.txt': Operation not permitted
~/TMP$ rm tmp.txt
rm: cannot remove 'tmp.txt': Operation not permitted
~/TMP$ sudo chattr -i tmp.txt
~/TMP$ sudo chmod 0700 tmp.txt
~/TMP$ la tmp.txt
-rwx------ 1 root root 2 Jun  3 00:04 tmp.txt
~/TMP$ rm tmp.txt
rm: remove write-protected regular file 'tmp.txt'? y
~/TMP$ cd -
/home/alexk
~$ rmdir TMP

alexkemp · Other Issues

I was astonished that an ordinary user can delete a file owned by root, but yes it can (if the dir is owned by the user):

$ echo "a" > tmp.txt
$ la tmp.txt
-rw-r--r-- 1 alexk alexk     2 Jun  2 17:48 tmp.txt
$ chmod 0700 tmp.txt
$ la tmp.txt
-rwx------ 1 alexk alexk 2 Jun  2 17:48 tmp.txt
$ sudo chown root.root tmp.txt
[sudo] password for alexk: 
$ la tmp.txt
-rwx------ 1 root root 2 Jun  2 17:48 tmp.txt
$ rm tmp.txt
rm: remove write-protected regular file 'tmp.txt'? y
$ la tmp.txt
ls: cannot access 'tmp.txt': No such file or directory

alexkemp · Desktop and Multimedia

I've uploaded 2 scripts to Github:

Get-Chrome-Cache

In that Repository, getCC is a PERL script that extracts all accessible files from the Chromium cache. Once they are all extracted, browseCC is a BASH script that accesses text-files dropped into the extract dir & uses YAD to display summaries & specifics on those files, including thumbnails for image files.

alexkemp · Desktop and Multimedia

Note Before:

DVD & Blu-Ray discs are problematic under Linux for many reasons, and special steps need to be taken before Linux apps can play them.

I thought that it might be useful to expand this post to serve as a reference, since at first I could not remember myself all the steps I took.

delgado wrote:

encrypted with "css" and decryption libraries are needed to play them … don't think this will ever make it into debian officially.

References:

Wiki: libdvdcss: Content Scramble System (CSS) software decryption library for accessing DVDs
VLC: Videolan (VLC): help on installing libdvdcss
HowTo Geek: Play DVDs and Blu-rays on Linux

Narrative:

CDs were first issued in 1982 and mostly held music files. The digital files on the media were NOT scrambled & quickly everyone learned to ‘rip’ the music from the disc and load it onto other electronic players. That became a nightmare for the Music Industry when the Internet got going in the 1990s.

DVDs were first released in 1996 and were designed to store larger files than Music required. The industry was determined NOT to make the same mistake as with CDs, and introduced both Regions (to try to restrict distribution regionally) and encryption (CSS) to restrict playing to officially-endorsed machines. The media became popular for both entertainment- (films, games) and software-distribution. CSS was brain-dead and easy to decrypt, but the combo of both endemic disc-players that contained zero hardware-decryption + industry-sponsored law (DMCA (Digital Millennium Copyright Act)), threatening fines and/or incarceration, was a nightmare for Linux users.

Blu-Ray was originated in 2002 & became a standard in 2008. It was designed to store very much larger digital files (required by larger domestic TV screens). In every way it is DVDs with knobs-on.

DVDs:

The modern advice from both Windows & Linux is “Install VLC”.

VLC states “VLC media player binaries are distributed with the libdvdcss library included” (that library is the one that decrypts the DVD-stream). That should mean that, once VLC is installed under Devuan, that other apps in the system should also be able to access the same library & decrypt the same streams. However, life is often not perfect, so here is what to do if glitches appear (it looks like the libdvdcss binary may be pre-installed under Windows but not Linux):–

With more ancient Debian/Ubuntu 15.04 it was sudo apt-get install libdvdread4 then sudo /usr/share/doc/libdvdread4/install-css.sh. My Chimaera still has /usr/share/doc/libdvdread4/README.css within it. However, the current advice is a little different:–

sudo apt install libdvd-pkg
sudo dpkg-reconfigure libdvd-pkg

The second step will download, build and install the latest libdvdcss source on your machine. At that point *all* libdvdcss-aware apps in your system — such as MPlayer, MPV + Handbrake — will be able to play DVDs.

$ apt search libdvd-pkg
Sorting... Done
Full Text Search... Done
libdvd-pkg/stable,now 1.4.2-1-1 all [installed]
  DVD-Video playing library - installer

$ apt search libdvdcss
Sorting... Done
Full Text Search... Done
…
libdvdcss-dev/now 1.4.2-1~local amd64 [installed,local]
  library for accessing encrypted DVDs - development files

libdvdcss2/now 1.4.2-1~local amd64 [installed,local]
  library for accessing encrypted DVDs

libdvdcss2-dbgsym/now 1.4.2-1~local amd64 [installed,local]
  debug symbols for libdvdcss2

libdvdread4/now 6.0.1-1 amd64 [installed,local]
  library for reading DVDs

libdvdread8/stable,now 6.1.1-2 amd64 [installed,automatic]
  library for reading DVDs

Blu-Ray

Blue-Ray presents yet more problems. Once again, refer to How to Play DVDs and Blu-rays on Linux:

sudo apt-get install vlc libaacs0 libbluray-bdj libbluray1
mkdir -p ~/.config/aacs/
cd ~/.config/aacs/ && wget http://vlc-bluray.whoknowsmy.name/files/KEYDB.cfg

$ apt search libbluray
Sorting... Done
Full Text Search... Done
libbluray-bdj/stable,now 1:1.2.1-4+deb11u2 all [installed]
  Blu-ray Disc Java support library (BD-J library)

libbluray-bin/stable 1:1.2.1-4+deb11u2 amd64
  Blu-ray disc playback support library (tools)

libbluray-dev/stable 1:1.2.1-4+deb11u2 amd64
  Blu-ray disc playback support library (development files)

libbluray-doc/stable 1:1.2.1-4+deb11u2 all
  Blu-ray disc playback support library (documentation)

libbluray2/stable,now 1:1.2.1-4+deb11u2 amd64 [installed]
  Blu-ray disc playback support library (shared library)

All the above works fine in my Chimaera system.

Updated:
May 23: Added a fuller narrative on installing libdvdcss.
Added info on the command (libdvd-pkg) to install libdvdcss in order to be able to play DVDs.

alexkemp · Desktop and Multimedia

I'm using updated Chimaera & VLC Media Player gives me the best results. The one thing that I need to settle to is very little in terms of the interactive DVD menu.

(there are a staggering number of VLC-Plugins; perhaps one of those will fix the bad dvd-menu):

$ apt search vlc
Sorting... Done
Full Text Search... Done
…
vlc/stable,stable-security,now 3.0.18-0+deb11u1 amd64 [installed]
  multimedia player and streamer

vlc-bin/stable,stable-security,now 3.0.18-0+deb11u1 amd64 [installed]
  binaries from VLC

vlc-data/stable,stable-security,now 3.0.18-0+deb11u1 all [installed,automatic]
  common data for VLC

alexkemp · Other Issues

You have not included the full command for hexdump to get the correct result (it is hexdump -C). However, to make life simple for yourself use the shortcut hd (I only just discovered that just now - it is also hexdump).

If you look at this Wiki page for File Signatures you will find that the magic signature for ttf is 00 01 00 00 00. Therefore:

$ hd /usr/lib/firefox-esr/fonts/TwemojiMozilla.ttf | head
00000000  00 01 00 00 00 11 01 00  00 04 00 10 43 4f 4c 52  |............COLR|
00000010  9b 59 1b ad 00 13 22 f8  00 02 51 6c 43 50 41 4c  |.Y...."...QlCPAL|
00000020  99 fd 98 85 00 15 74 64  00 00 0f ea 46 46 54 4d  |......td....FFTM|
00000030  94 98 f7 41 00 15 84 50  00 00 00 1c 47 44 45 46  |...A...P....GDEF|
00000040  00 27 34 59 00 15 84 6c  00 00 00 1e 47 53 55 42  |.'4Y...l....GSUB|
00000050  71 92 ee f7 00 15 84 8c  00 00 6c 80 4f 53 2f 32  |q.........l.OS/2|
00000060  34 c3 0a 83 00 00 01 98  00 00 00 60 63 6d 61 70  |4..........`cmap|
00000070  25 3d b7 6c 00 00 6a a8  00 00 0b fa 63 76 74 20  |%=.l..j.....cvt |
00000080  00 11 01 44 00 00 76 a4  00 00 00 04 67 61 73 70  |...D..v.....gasp|
00000090  ff ff 00 03 00 13 22 f0  00 00 00 08 67 6c 79 66  |......".....glyf|

and you will spot the magic signature starting at '00000000'. If *your* ttf files do not start with this signature (which AHA6.ttf does not), then they will not be recognised by the system as TTF font files. My best guess then is that something within the way that you are processing them is shafting them.

There is a helpful Step-by-Step install TTF fonts on Linux page if you need help on that.

Update: spel-check

alexkemp · Other Issues

Please use [ code ] ... [/ code] tags to quote terminal-results (as below) (keeps the text in this window small). You would also be well advised to use your computer as an ordinary user rather than the root user. Switch to the root user only when you have some extensive admin to do that actually *requires* root to work (updating the system is such a requirement).

sivaprema wrote:

# file /usr/lib/firefox-esr/fonts/TwemojiMozilla.ttf
/usr/lib/firefox-esr/fonts/TwemojiMozilla.ttf: TrueType Font data, 17 tables, 1st "COLR", 12 names, Macintosh, type 1 string

That is a proper ttf font …

# file /usr/share/fonts/truetype/aha/AHA6.ttf
/usr/share/fonts/truetype/aha/AHA6.ttf: data

… and that is most unlikely to be such a font. Here is one way to check:–

$ strings /usr/lib/firefox-esr/fonts/TwemojiMozilla.ttf | wc -l
28319

(28,319 lines of text-strings - that is what a ttf font should look like)

Here is what the top of the file looks like (you can also change the 'head' to 'less' (no quotes) to examine the whole file):–

$ strings /usr/lib/firefox-esr/fonts/TwemojiMozilla.ttf | head
COLR
QlCPAL
FFTM
GDEF
GSUBq
OS/24
`cmap%=
cvt 
gasp
glyf

Now an examination using a hex-viewer; look at the first 12-bytes to see the magic-signature for a ttf font (ALL ttf-fonts should look something like this in the 1st 12 bytes):

$ hexdump -C /usr/lib/firefox-esr/fonts/TwemojiMozilla.ttf | head
00000000  00 01 00 00 00 11 01 00  00 04 00 10 43 4f 4c 52  |............COLR|
00000010  9b 59 1b ad 00 13 22 f8  00 02 51 6c 43 50 41 4c  |.Y...."...QlCPAL|
00000020  99 fd 98 85 00 15 74 64  00 00 0f ea 46 46 54 4d  |......td....FFTM|
00000030  94 98 f7 41 00 15 84 50  00 00 00 1c 47 44 45 46  |...A...P....GDEF|
00000040  00 27 34 59 00 15 84 6c  00 00 00 1e 47 53 55 42  |.'4Y...l....GSUB|
00000050  71 92 ee f7 00 15 84 8c  00 00 6c 80 4f 53 2f 32  |q.........l.OS/2|
00000060  34 c3 0a 83 00 00 01 98  00 00 00 60 63 6d 61 70  |4..........`cmap|
00000070  25 3d b7 6c 00 00 6a a8  00 00 0b fa 63 76 74 20  |%=.l..j.....cvt |
00000080  00 11 01 44 00 00 76 a4  00 00 00 04 67 61 73 70  |...D..v.....gasp|
00000090  ff ff 00 03 00 13 22 f0  00 00 00 08 67 6c 79 66  |......".....glyf|

You can now examine both TwemojiMozilla.ttf & AHA6.ttf on your own machine to discover whether these rogue fonts are actually fonts at all.

(if you do not yet have hexdump then install bsdextrautils (part of chimaera-stable)):–

$ apt search hexdump
Sorting... Done
Full Text Search... Done
bsdextrautils/stable,now 2.36.1-8+devuan2 amd64 [installed]
  extra utilities from 4.4BSD-Lite

alexkemp · Other Issues

sivaprema wrote:

in fontforge ".._ttf is not a known format

The use of an underscore (“_”) concerns me there. In general Linux uses mime (or file) to discover what a file actually is, rather than the Window$-inspired “.tld” convention.

I do not have fontforge installed.

Possibly one way to begin to diagnose your situation is from the command-line. If you have mlocate installed (to quickly locate files) and either FireFox and/or Thunderbird installed then you will be able to locate this specific TTF font:

$ file /usr/lib/firefox-esr/fonts/TwemojiMozilla.ttf
/usr/lib/firefox-esr/fonts/TwemojiMozilla.ttf: TrueType Font data, 17 tables, 1st "COLR", 12 names, Macintosh, type 1 string

That should help to begin to help discover exactly what your system thinks any particular ttf file is.

One final other common source is mscorefonts and/or fonts-liberation:

$ apt search fonts-liberation
Sorting... Done
Full Text Search... Done
fonts-liberation/stable,now 1:1.07.4-11 all [installed]
  Fonts with the same metrics as Times, Arial and Courier

fonts-liberation2/stable,now 2.1.3-1 all [installed]
  Fonts with the same metrics as Times, Arial and Courier (v2)

ttf-mscorefonts-installer/stable,now 3.8 all [installed]
  Installer for Microsoft TrueType core fonts

$ file /usr/share/fonts/truetype/msttcorefonts/Arial.ttf
/usr/share/fonts/truetype/msttcorefonts/Arial.ttf: TrueType Font data, digitally signed, 23 tables, 1st "DSIG", 70 names, Unicode, Typeface \251 The Monotype Corporation plc. Data \251 The Monotype Corporation plc/Type Solution

HTH

alexkemp · Hardware & System Configuration

Hi amc252.

Every electronic component within your computer has a driver associated with it that allows that component to "play along". Monitors are no different to anything else. Therefore, your first search can involve finding a Chimaera driver for the digital TV.

The miracle of modern electronic equipment was made far easier with the introduction of PnP ("Plug 'n' Play"). That relies on a digital connection & various subsystems, and is what allows something like a monitor to be plugged in, auto-detected by the computer, recognised, the driver auto-located via the internet, auto-downloaded & auto-installed. Now, a USB connection is certainly digital but is more used for modems or HDD & little used for connecting monitors - HDMI connections are the standard for that.

Check your computer: does it have a HDMI port?
Check your digital monitor: does it have a HDMI port?

If the answer to the two questions above are both "yes" then you may be in business very quickly; just make sure that both ports are switched "on" in the setup for both machines, and that your computer is connected via an Ethernet port to the internet before you make the HDMI connection (Ethernet is 'old school' & thus provides few problems cf WLAN).

If the above is not possible & you are determined to go ahead with RCA & such-like then bring your will up-to-date so that afterwards others can realise the reasons for your suicide.

Good luck.

alexkemp · Other Issues

I've got two drives that are USB-connected HDD:

Seagate 2TB portable
(this is formatted using standard Linux utilities to (so-called) FAT64 (HPFS/NTFS/exFAT: max 2TB))
WD (Western Digital) 4TB portable ("My Passport")
(this is native M$ format ("Microsoft basic data") and I cannot find a linux utility that can format and/or repair it to it's current state)

The advantage of the former is that it is ubiquitous across many different OS. As an example, my ancient Samsung TV can read & play movies from (1), but not (2).

The advantage of (2) is that it can store above the 2TB threshold. Also, astonishing that I may need it to. I left the disk in it's supplied format since that can be read by more OS than a native Linux format.

As long as you have a 64-bit cpu then (as I understand it) either disk can be read up to the max of the cpu (which I cannot recall as I sit here, but much, much more than 4TB).

alexkemp · Installation

OK. Thanks to admin (although the OP has been further edited).

alexkemp · Installation

Well, now that you have edited it, it reads "daedalus" although when first posted it read "deadalus".

I was attempting to both be light-hearted in my response, and also warning other folks not to blindly copy your [ code ]'ed config since it contained a spelling mistake. Also, I personally only ever 'code' actual results without editing them so that others can trust that what I code is actually what I got as a result.

You need to address your remarks on the absence of non-free to fsmithred, since he states that yes, that does work whereas security & updates will not. I have no personal experience to be able to comment.

alexkemp · Installation

For those that realise that daedalus is *not* dead, do not copy brday's code.

The Devuan package information is here, and the sole Default configuration shown for daedalus is as follows on that page:

Devuan Daedalus (testing) wrote:

deb http://deb.devuan.org/merged daedalus main

@brday:
If your code was copied from the terminal then you likely have a reason (speling), otherwise non-free & contrib are not available for deadalus, though they may be for daedalus.

alexkemp · Devuan Derivatives

prospero wrote:

a new Chimaera live iso from two days ago

Possibly due to a recent kernel upgrade to 6.1.12-1 (available from backports):

$ uname -a
Linux ng3 6.1.0-0.deb11.5-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.12-1~bpo11+1 (2023-03-05) x86_64 GNU/Linux
$ la /boot/initrd* /boot/vmlinuz*
-rw-r--r-- 1 root root 68062772 Mar 28 22:35 /boot/initrd.img-6.0.0-0.deb11.6-amd64
-rw-r--r-- 1 root root 68913767 Mar 31 17:35 /boot/initrd.img-6.1.0-0.deb11.5-amd64
-rw-r--r-- 1 root root  7730784 Dec 19 14:14 /boot/vmlinuz-6.0.0-0.deb11.6-amd64
-rw-r--r-- 1 root root  7866720 Mar  5 18:27 /boot/vmlinuz-6.1.0-0.deb11.5-amd64

My actual update was March 31 (I update daily):

$ la -clt /boot/initrd* /boot/vmlinuz*
-rw-r--r-- 1 root root 68913767 Mar 31 17:35 /boot/initrd.img-6.1.0-0.deb11.5-amd64
-rw-r--r-- 1 root root  7866720 Mar 31 17:35 /boot/vmlinuz-6.1.0-0.deb11.5-amd64
-rw-r--r-- 1 root root 68062772 Mar 28 22:35 /boot/initrd.img-6.0.0-0.deb11.6-amd64
-rw-r--r-- 1 root root  7730784 Jan  4 10:14 /boot/vmlinuz-6.0.0-0.deb11.6-amd64

The officially official Devuan Forum!

#226 Re: Other Issues » Update nginx > 1.19.4 » 2023-06-19 16:18:54

#227 Re: Off-topic » Obtaining data from an Android-formatted SD/MMC Card » 2023-06-12 10:45:20

#228 Re: Off-topic » Obtaining data from an Android-formatted SD/MMC Card » 2023-06-11 22:49:21

#229 Re: Off-topic » Obtaining data from an Android-formatted SD/MMC Card » 2023-06-11 22:01:20

#230 Re: Off-topic » Obtaining data from an Android-formatted SD/MMC Card » 2023-06-11 21:20:58

#231 Re: Off-topic » Obtaining data from an Android-formatted SD/MMC Card » 2023-06-11 20:59:59

#232 Off-topic » Obtaining data from an Android-formatted SD/MMC Card » 2023-06-11 13:16:26

Discovering the Device

#233 Re: Other Issues » [SOLVED] Chromium Upgrade: 3 Packages have been Kept Back » 2023-06-06 01:04:36

#234 Re: Other Issues » [SOLVED] Chromium Upgrade: 3 Packages have been Kept Back » 2023-06-04 15:59:44

#235 Re: Other Issues » [SOLVED] Chromium Upgrade: 3 Packages have been Kept Back » 2023-06-04 09:57:16

#236 Other Issues » [SOLVED] Chromium Upgrade: 3 Packages have been Kept Back » 2023-06-03 20:54:35

#237 Re: Other Issues » [SOLVED] File "recently-used.xbel" » 2023-06-02 23:18:05

#238 Re: Other Issues » [SOLVED] File "recently-used.xbel" » 2023-06-02 17:00:01

#239 Re: Desktop and Multimedia » [SOLVED] Help requested with WINE setup and/or Chromium Cache Searching » 2023-05-31 23:12:23

#240 Re: Desktop and Multimedia » [SOLVED] Can't figure out how to play DVDs » 2023-05-22 13:48:26

Note Before:

References:

Narrative:

DVDs:

Blu-Ray

#241 Re: Desktop and Multimedia » [SOLVED] Can't figure out how to play DVDs » 2023-05-22 01:08:10

#242 Re: Other Issues » [SOLVED] TTF True Type Fonts » 2023-05-20 00:15:07

#243 Re: Other Issues » [SOLVED] TTF True Type Fonts » 2023-05-19 20:05:41

#244 Re: Other Issues » [SOLVED] TTF True Type Fonts » 2023-05-19 09:19:58

#245 Re: Hardware & System Configuration » How do I get USB to RCA connection to work? » 2023-04-29 09:29:53

#246 Re: Other Issues » What is the maximum USB capacity Devuan can use? » 2023-04-28 08:12:52

#247 Re: Installation » Add repositoy to daedalus? » 2023-04-26 23:53:09

#248 Re: Installation » Add repositoy to daedalus? » 2023-04-26 14:30:16

#249 Re: Installation » Add repositoy to daedalus? » 2023-04-26 11:19:15

#250 Re: Devuan Derivatives » GNUinOS - Libre » 2023-04-04 10:48:16

Board footer