Output of *file* command for a given odt file gives me Composite Document File V2 Document, Cannot read section info. By searching on Google I found it a doc document and I installed *unoconv* to read it on linux(fedora). But when I run the command: unoconv -d document --format=odt file.doc I get the following error: unoconv: RuntimeException during import phase:Office probably died. Unsupported URL Thumb.doc: "type detection failed"**. I am having all packages of libreoffice writer. So how do I open these kind of files on fedora?

I am trying to create a matrix of plant traits and plant species. There are 2,912,746 rows in the data and 3 columns. There are different numbers of traits for each species, and not every species has every trait. The data format is tab delimited. Current format-- Species Trait Value Species_1 SLA 4 Species_1 Photopath C3 Species_1 Mycorrhiza AMF Species_2 SLA 3 Species_2 Growth 10 Desired format-- SLA Photopath Mycorrhiza Growth Species_1 4 C3 AMF Species_2 3 10 Any help with this would be OH SO appreciated. It has been a quite the challenge, and I'm not sure where to begin. Thank you!!!! ~Mark Anthony

I have a gzip archive with trailing data. If I unpack it using gzip -d it tells me: "*decompression OK, trailing garbage ignored*" (same goes for gzip -t which can be used as a method of detecting that there is such data). Now I would like to get to know this garbage, but strangely enough I couldn't find any way to extract it. gzip -l --verbose tells me that the "compressed" size of the archive is the size of the file (i.e. with the trailing data), that's wrong and not helpful. file is also of no help, so what can I do?

Which format (Mac or DOS) should I use on Linux PCs/Clusters? [I know the difference](https://stackoverflow.com/questions/28617814/difference-between-dos-format-and-mac-format) : - DOS format uses "carriage return" (CR or \r) then "line feed" (LF or \n). - Mac format uses "carriage return" (CR or \r) - Unix uses "line feed" (LF or \n) I also know [how to select the option](https://stackoverflow.com/questions/13368223/nano-2-0-6-saving-a-file-in-mac-format) : - AltM for Mac format - AltD for DOS format But there is no UNIX format. Then save the file with Enter.

Let's assume that I want to run a shell script named test.sh at 1 AM every day. I could either use: 0 1 * * * /home/user/test.sh Or I could use: 0 01 * * * /home/user/test.sh For the above example, which is technically the correct answer - should a leading 0 be used in the shedule, or should just the number of the hour be entered?

Please confirm if .DAT extension files are the same as compressed format files (.zip ) in Unix. As I try to use gzip filename.DAT then is the original 2 GB file size the same after compression? Is there any alternative to reduce the size of .DAT extension files?

An Example of Unified Format :

-none
--- lao	2002-02-21 23:30:39.942229878 -0800
+++ tzu	2002-02-21 23:30:50.442260588 -0800
@@ -1,7 +1,6 @@
-The Way that can be told of is not the eternal Way;
-The name that can be named is not the eternal name.
 The Nameless is the origin of Heaven and Earth;
-The Named is the mother of all things.
+The named is the mother of all things.
+
 Therefore let there always be non-being,
   so we may see their subtlety,
 And let there always be being,
@@ -9,3 +8,6 @@
 The two are the same,
 But after they are produced,
   they have different names.
+They both may be called deep and profound.
+Deeper and more profound,
+The door of all subtleties!

What is the purpose of the timestamps (e.g. 2002-02-21 23:30:39.942229878 -0800) that appear after the file names? Are they mandatory? Can I safely remove them? What are the consequences of faking the time (e.g. using a future time)?

It is on debian on x86_64

me@debian:~/bin$ chmod a+x helix-23.03-aarch64.AppImage
me@debian:~/bin$ ./helix-23.03-aarch64.AppImage
/tmp/.mount_helix-RyzFyw/AppRun: 4: exec: /tmp/.mount_helix-RyzFyw/usr/bin/hx: Exec format error

It is known that there are self-healing file systems like e.g. ZFS, Btrfs, bcachefs and self-healing RAM, like e.g. ECC RAM or corresponding software implementations, which can correct single or multiple erroneous bits. What are there for self-healing file formats or projects to self-healing file formats for standard programs ? What does a file format mean? P.e: * .txt, .doc, tar.lz4, .mp4

I am currently working on a program converting mailbox files from an old, tenex based mail format to mbox. The tenex mailbox format has separator lines like the mbox format (the latter is called the From_ line), tenex: 7-Feb-86 21:41:21-EST,1925;000000000000 mbox: From mail@example.com Fri Feb 07 14:20:00 1986 but due to a lack of documentation, the origin of the datetime stamp in the separator line of a "tenex formatted" file is obscure. Hence, when transforming a message from the tenex to mbox format, I used the datetime stamp from date-header field for constructing the From_ line for the mbox formatted message, not the one in the separator line of the tenex formatted file. But RFC4155 , an attempt to describe "the" mbox format (there are actually several different formats) and supply a kind of standard for this file format, states: > Each message begins with a separator line that identifies the message > sender, and also identifies the date and time at which the message was > received by the final recipient (either the last-hop system in the > transfer path, or the system which serves as the recipient's > mailstore). Hence, I am in doubt that my approach using the datetime stamp from the date header field is correct. But, without having the transport envelope, from where can I get the actual datetime stamp of the final recipient receiving the message? Is this the datetime stamp in the last entry of the of Received header field(s)?

When I grep for phan in my hunspell-dic file /usr/share/hunspell/de_DE_frami.dic, I get list of words including

/Sm
cellophan/Sozm
cellophan/hke
cellophan/ozm
glaukophan/EPSozm

Where do I find documentation, what the suffixes mean? I looked for a manpage for hunspell but only found a non helpful one to update-dictcommon-hunspell. man dict? didn't help either.

On Linux, each software can decide the configuration format he wishes to use. Some uses TOML, INI, JSON, XML, CSV, YAML, JS, CSS, scripts, and so on. However, some configuration files use kind of INI-like text formats, which seem non-standard, e.g. : A text file in which each line is composed of a key and a value separated by one or many white space characters, line beginning by "#" are comments, and sometime it has some kind of "blocs" (e.g. in SSH) :

Include /etc/ssh/ssh_config.d/*.conf

Host *
#   ForwardAgent no
    SendEnv LANG LC_*

A variant is used (e.g. in Nginx) in which "blocs" are defined by {} :

server {
    listen 127.0.0.1:80;
}

Is there any name/group of words used to designate this type/family/kind of formats ?

I am looking for extensions of files and cut simply gives the filename if the file has no extension so I am looking to make cut give a "extensionless" when no '.' is found I am using this as a refrence: https://stackoverflow.com/questions/1842254/how-can-i-find-all-of-the-distinct-file-extensions-in-a-folder-hierarchy the answers that ignore the files without extensions were no good as I needed to find those too

Is there any command line tool available on Linux to check a PDF file version?

Modem Manager GUI creates a database named sms.gdbm to store all the SMS details. Currently Modem Manager GUI is not providing a feature to simply delete all received/sent messages. So I'm trying to create a program to remove those records from its database (sms.gdbm). But first I want to know the structure of the sms.gdbm database. What are the databases it contains, also table and their column names. So are there any CLI or GUI programs to display the structure of a *.gdbm file?

I have this SanDisk Cruzer Edge where it's a write-protected NTFS partition that I got from my dad as I needed a flash drive. I tried using GParted, didn't work, I saw something online that used the terminal, which didn't work. I use Ubuntu Unity 22.04, which might be problematic but it does have most if not all GNOME utilities. List of what has been attempted: - formatting via GParted - formatting via terminal What the drive contains is basically a bootleg installer for either Windows XP or Windows 7 that is Legacy-only. Which is in Russian. What do I do? thanks very much. please I beg for help I have only used Linux for about a year properly and I am very much lost

epubcat book.epub 1 3 # outputs plain text of pages 1 through 3 I don’t know if epubs have the concept of “pages.” If not, perhaps we can say each 400 chars are a page? A general solution that works for other ebook formats is better (mobi, azw3, etc). My own thoughts are currently on first converting the book to text via ebook-convert or pandoc and then extracting the needed amount, but this seems awfully inefficient as I intend to only get a little of the beginning of the content. You can download an example file that can be used for testing [here](http://82.102.11.148:8080//tmp/Time%20to%20Put%20Your%20Galleons%20Where%20Your%20Mouth%20Is%20-%20Tsume%20Yuki.epub) .

How can I convert (or open) .ost file (Microsoft Outlook email folder) on linux ? Ideally, I would like to read it with Mutt. But mutt does not seem to understand this format. Therefore I would like to convert it into something readable such as mbox or mdir format. Are there such conversion tools on linux ?

While browsing through the Kernel Makefiles, I found these terms. So I would like to know what is the difference between vmlinux, vmlinuz, vmlinux.bin, zimage & bzimage?

I ran this code to filter out biallelic variants from my vcf file: bcftools view --max-alleles 2 --exclude-types indels merged.ecDNA.vcf.gz>merged.ecDNA2.vcf.gz However, I got an error message: [E::vcf_parse_format] Number of columns at 1:219048632 does not match the number of samples (111 vs 231) Error: VCF parse error The thing is, merged.ecDNA2.vcf.gz still appeared in my directory and it seems to be a working vcf file. So I was wondering, if my code actually produced a vcf file that appears to be normally functioning, would the above error still have any effect on my output file? What should the number 1:219048632 refer to? I tried this code too: bcftools view -m2 -M2 -v snps merged.ecDNA.vcf.gz>merged.ecDNA3.vcf.gz And I got the same error message for the above code. If anyone could give a general explanation of what that error message means, it would be super helpful.