tumbleweed-cli
snapper
tumbleweed-cli | snapper | |
---|---|---|
13 | 33 | |
80 | 828 | |
- | 1.4% | |
2.6 | 9.0 | |
6 months ago | 8 days ago | |
Shell | C++ | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
tumbleweed-cli
-
OpenSuse:TumbleWeed Update Broken?
There is a third controversial option: tumbleweed-cli which is helping to move from snapshot to snapshot. To be honest I'm not aware of the status.
-
Can I install the last week image?
Would this work? https://github.com/boombatower/tumbleweed-cli
-
From Fedora to Tumbleweed: looking for guidance
There is also https://github.com/boombatower/tumbleweed-cli which i like very much when using tumbleweed
-
Is there any love for Gnome on Leap?
If the persistent updates or update notifications are the only problem for a switch to TW, then there's always the installable package 'tumbleweed-cli' (you can find it in the repos) more infos. https://github.com/boombatower/tumbleweed-cli With this you can set a specific opensuse snapshot. This should only be used for updates, not for rollbacks, that's what snapper is for. As far as I know monthly updating is recommended (at least).
- Question on Tumbleweed updates, and checking before updating
-
The resilience of Tumbleweed (or why you can trust it as much as Leap/Debian) -- 227 days between updates
A certain number of older snapshots is kept on the mirrors and can be chosen with tumbleweed-cli.
-
(Help) Not exactly sure what has happened to my install but I've somehow broke it.
Jesus. It's not that zypper isn't a good tool, it's that tumbleweed-cli uses the snapshot versions, and is actually designed for this exact use case. See this thread and the comment by u/bommbatower for more information.
-
Opensuse Tumbleweed - Need clarifications before deciding to switch
I use tumbleweed-cli to upgrade from a solid snapshot to the next one, typically once every two weeks or so. This allows rolling as quickly or slowly as is desired, provided the snapshots are still available here: http://download.opensuse.org/history/
-
I am just discovering OpenSUSE and I have some questions !
I'd suggest you to install tumbleweed-cli (zypper in tumbleweed-cli) to target a specific snapshot, so you're not going to upgrade your system all the time, but only when a new snapshot is released (and when you want to switch to it, at your discretion).
-
Tumbleweed cli vs zypper dup vs KDE discover
I do believe you're right! My mistake. That's good to know. It looks like it's just the scoring system that's done by a third party - unless I'm wrong again :) Please let me know if I am. I'm still hesitant to use it with respect to the scoring system as an ordinary user. I was under the misconception that the github repo at https://github.com/boombatower/tumbleweed-cli would have been under the official opensuse github repo.
snapper
-
Bcachefs Merged into the Linux 6.7 Kernel
I left SUSE close to the end of 2021, and I had had to reinstall my work laptop twice that year alone. I consider that recent enough to call it current.
> df is not lying
To me, that reads as "df isn't lying because $EXCUSES."
I disagree. I don't care about excuses. I want a 100% accurate accounting of free space at all times via the standard xNix free-disk-space reporting command, and the same from the APIs that command uses so that applications can also get an accurate report of free space.
If a filesystem cannot report free space reliably and accurately, then that filesystem is IMHO broken. Excuses do not exonerate the FS, and having other FS-specific commands that can report free space do not exonerate it. The `df` command must work, or the FS is broken.
The primary point of Btrfs is that it is the only GPL snapshot-capable FS. The other stuff is gravy: it's a bonus. There are distros that use Btrfs that don't use snapshots, such as Fedora.
Some Btrfs advocates use this to claim that the problems are not problematic. If the filesystem is of interest on the basis of feature $FOO, then "product $BAR does not exhibit this problem" is not an endorsement or a refutation if $BAR does not use feature $FOO.
Btrfs RAID is broken in important ways, but that is not a deal-breaker because there are other perfectly good ways of obtaining that functionality using other parts of the Linux stack. If no feature or functionality is lost considering the OS and stack as a whole, then that isn't a problem. However, this remains serious and an issue.
Additional problems include:
• Poor integration into the overall industry-wide OS stack.
Examples:
- Existing commands do not work or give inconsistent results.
- Duplication of functionality (e.g. overlap with `mdraid`)
• Poor integration into specific vendors' OS stacks.
Examples:
- SUSE uses Btrfs heavily.
But SUSE's `zypper` package manager is not integrated with its `snapper` tool. Zypper doesn't include snapshot space used by Snapper in its space estimation.
Snapper is integrated with Btrfs; licence restrictions notwithstanding, I would be much reassured if Snapper supported other COW filesystems.
(This has been attempted but I don't think anything shipped -- https://github.com/openSUSE/snapper/issues/145 . I welcome correction on this!)
The transactional features of SUSE's MicroOS family of distros rely heavily on it. This lack of awareness of snapshot space utilization deeply worries me. I have raised this with SUSE management, but my concerns were dismissed. That worries me.
Red Hat removed Btrfs support from RHEL. As a result it has had to bodge transactional package management together by grafting Git-like functionality into OStree, then building two entirely new packaging systems around OStree, one for the OS itself and a different one for GUI-level packages. The latter is Flatpak, of course.
This strikes me as prime evidence that:
1. Btrfs isn't ready.
-
Desktop Linux Hardening
Very useful. One practical thing to add: enabling automatic snapshots (e.g. with https://github.com/openSUSE/snapper), ideally backing them up separately (e.g., with borg) might help recovery.
-
best practice to keeping Linux environment 'clean'?
I like btrfs snapshots, e.g. with snapper (http://snapper.io/), but that needs a bit of setup (and is out of the box with some distros, e.g. opensuse).
-
New user: some small issues
Use snapper, it's very good and it can be integrated with grub so that you can boot into an snapshot (not sure you can do that with timeshift).
-
Snapper: Trouble setting up /.snapshots mountpoint for custom subvol location
The other big difference, is that I would like to have "flat" hierarchy (at least within the nested distro-specific subvol) for my snapshots. Meaning that I do not like the nested structure of /.snapshots that snapper seems to assume by default and would prefer something like /fedora/snapshots/rootfs instead. It seems this is a somewhat popular request that has been opened for over 8 years... but since it hasn't been implemented in snapper itself, most people just use workarounds.
-
New high-end gaming PC build, need distro suggestion
If, for some reason, anything goes wrong with your system, it is also trivial to return it to a working state, using snapper. This is preconfigured by default, no manual work required.
-
Best configuration for bare hypervisor distro FOR DESKTOP VMs
Are you sure you need a full on virtual machine, rather than a system snapshotting tool like Snapper or Timeshift?
-
snapper list -show-items-about-to-be-deleted, have anyone done it?
I never said it did. Please read. It was meant to demonstrate that the health of the project is questionable, since after thatf ater that change was submitted, the official tests for the project is broken (see the current status on their github page https://github.com/openSUSE/snapper).
- How do you prefer to backup and restore your Fedora system?
-
Just try it, it's glorious
The amazing tooling: - YaST, the best configuration tool out there. I think its fair to say that nothing comes close to the number of things you can configure with Yast. - Open Build Service (OBS), a tool that automatically builds binaries for software and sets up repositories to add to your favorite package manager. Supports every major linux distro but intergrates especially well with the openSUSE software store, and OPI (openSUSE equivelant to something like paru or yay) to be like the AUR but (imo) better. - openQA, Automated testing for any package or operating system, making sure that even on leading edge software, you're still stable. - snapper, out of the box btrfs snapshots that make sure you can (almost) always boot into a useable system, even after a bumpy update.
What are some alternatives?
opi - OBS Package Installer (CLI)
TimeShift - System restore tool for Linux. Creates filesystem snapshots using rsync+hardlinks, or BTRFS snapshots. Supports scheduled snapshots, multiple backup levels, and exclude filters. Snapshots can be restored while system is running or from Live CD/USB.
openQA - openQA web-frontend, scheduler and tools.
btrbk - Tool for creating snapshots and remote backups of btrfs subvolumes
Bumblebee - Bumblebee daemon and client rewritten in C
zfs - OpenZFS on Linux and FreeBSD
snapper-gui - GUI for snapper, a tool for Linux filesystem snapshot management, works with btrfs, ext4 and thin-provisioned LVM volumes
Rsnapshot - a tool for backing up your data using rsync (if you want to get help, use https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss)
snap-sync - Use snapper snapshots to backup to external drive
rsync-time-backup - Time Machine style backup with rsync.
BorgBackup - Deduplicating archiver with compression and authenticated encryption.
linux-timemachine - Rsync-based OSX-like time machine for Linux, MacOS and BSD for atomic and resumable local and remote backups