osinfo-db-export(1)

📦
version 1.12.0 · 13 versions
, in opensuse-leap 16.0

✨ osinfo-db-export ✨

okay bestie, so picture this: you've got an osinfo database on your machine and you wanna share it with the world (or at least with another machine). That's literally what osinfo-db-export does — it's the export tool from the Osinfo DB Tools squad, and it's giving 🎀 pack it up, put it in a tarball, slay 🎀.

🌸 SYNOPSIS 🌸

osinfo-db-export [OPTIONS...] [ARCHIVE-FILE]

💜 DESCRIPTION 💜

The osinfo-db-export tool creates an osinfo database archive file, and it pulls that content from one of the standard local database locations. Which ones? So glad you asked, bestie, because there are exactly three and they're all kind of iconic in their own way:

  • system — the primary system-wide database location. This one is for operating system vendors who are out here distributing database files in the native package format. Very official. Very main character. 👑
  • local — the secondary system-wide database location. This one's for system administrators who want to provide an updated database for all users. The group-chat admin energy, honestly.
  • user — the user private database location. This one's for unprivileged local users who wanna give the applications they use an updated database. It's giving personal stash, and we respect it. 💅

Now for the default behaviour, because this part matters fr fr: if you run it with a privileged account (ie root), the local database location gets used by default. Otherwise? The user location. No cap.

And if you don't hand it an ARCHIVE-FILE path at all, it'll just make up a filename for you using the format osinfo-db-$VERSION.tar.xz. Automatic. Effortless. Obsessed. ✨

🦋 OPTIONS 🦋

  • --user — overrides the default behaviour to force archiving files from the user database location.
  • --local — overrides the default behaviour to force archiving files from the local database location.
  • --system — overrides the default behaviour to force archiving files from the system database location.
  • --dir=PATH — overrides the default behaviour to force archiving files from the custom directory PATH. Your directory, your rules. 🫶
  • --root=PATH — prefixes the database location with the root directory given by "PATH". This is useful when you wanna archive files that live in a chroot environment or equivalent. Sneaky but valid. 🙈
  • --version=VERSION — sets the version string for the files in the archive to VERSION. If you don't pass this argument, the version gets set to the current date in the format YYYYMMDD. (Yes, it timestamps itself. Lowkey self-aware. 😭)
  • --license=LICENSE-FILE — adds "LICENSE-FILE" to the generated archive as an entry named "LICENSE". Paperwork, but make it cute. 🎀
  • -v, --verbose — displays verbose progress information when archiving files. Perfect for when you need to watch the little files go by. ⭐

🌈 EXIT STATUS 🌈

So the exit status will be 0 if all files were packed successfully. Or it'll be 1 if at least one file could not be packed into the archive. That's it, that's the whole vibe check. 💀

🔥 SEE ALSO 🔥

(the whole friend group, honestly — go say hi 🫶)

👑 AUTHORS 👑

Daniel P. Berrange <berrange@redhat.com>

Copyright (C) 2016 Red Hat, Inc.

🧚 LICENSE 🧚

"osinfo-db-export" is distributed under the terms of the GNU LGPL v2+ license. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

bestie I need you to hear me on this one: NO warranty. Not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Like, none. Zero. Nada. So don't come for anyone if it breaks, mkay? 💖

alright that's the whole page 🌸 — this masterpiece is from osinfo-db-tools-1.12.0, dated 2025-05-02, and it's called osinfo-db-export in case you forgot where you were. go export something, you got this 💅✨

📦 where this page comes from