Timeshift 2

[Tonja Witcraft]

HeyoHoudini wizards,

I am trying to run a timeshift inside a for-loop and timeshift one specific iteration of the for loop but I am having some issues. It only seems to work when I run the for-loop in single pass. When I run it without the single pass the timeshift seems like it is ignored.

I am trying to make an HDA where a user can transfer multiple different attributes and also have a time offset control making it so that attribute "b" is transferred 10 frames after "a", or vise versa.

I am including my hip-file (its from houdini 17.5). Sorry about the mess, I tried cleaning it up to the best of my ability. The "problem area" can be found here: "/obj/Tests/Test_Soft_Constraints/curve_constraint_breaker5/", put the display-flag on "visualize1" inside "curve_constraint_breaker5" and try to toggle "repeat_end1" "single pass" option to see the issue. The for-loop is driven by the different entries in the "Set Attribute Values" list on "curve_constraint_breaker5". There might be some fracturing that has to cook at startup. I'm including some pictures as well but I am not sure if they are saying much (the screenshots show a visualization of the attribute transfer, havent moved timeline scrubber, only turned on or off the single pass option).

Thank you so much for the read!

As I have said before, if you ask me to do something, I will evaluate the thing in good faith, and I may choose to do as requested. If you try to force me, the odds are strong that I will commit to never doing the thing you are trying to force me to do. This is one such instance; I simply refuse to set up a redundant Timeshift when I know I have a superior image backup already.

Navigate to /usr/bin, and open the file mintupgrade as root in the text editor. If it asks what you want to do with the file, select Display. Scroll down to line 223, and find and comment out or delete these lines:

Again, I am not sure why the site hamburgered my formatting in the code section. The whole point of code tags is to retain the existing formatting, and what does it do? Strips it all out. Copy and paste it, and the formatting is back!

If it is installed but never used, it would still complain about not being set up. That was how my Mint 19.3 was. The Mint updater looks for the presence of the file /etc/timeshift.json, which is the Timeshift settings file. It creates this at the time you first set up Timeshift, whether for manual or automatic creation of snapshots.

Mint 19.3 uses the Ubuntu 18.04 HWE (hardware enablement) kernel stack, which has been on 5.3 for some time now, but it has just moved to 5.4, so it was offered to you as a result. That does mean that the 5.3 Ubuntu kernel (which is the one Mint uses too) is EOL. Not to worry; 5.4 is a solid kernel and it works well.

When a new Ubuntu version is released, it will come with a newer kernel, and in time that kernel will usually be offered first in HWE Edge, tested to make sure everything works as expected, then released to HWE, for the current LTS versions of Ubuntu. The HWE Edge versions of 5.4 are what you were seeing in the Mint kernel dialog before as an option.

People who are using Mint versions older than 19.3 can optionally install the HWE stack to get newer kernels or xserver versions, while still ensuring that they have been tested and verified by Ubuntu. The same applies to people using the actual Ubuntu versions that came with the original, standard kernel and xserverd stacks. I do prefer to use newer kernels where possible, as they often have some nice improvements in power management, performance, and other things.

I am also on Linux Mint 19.3 and have the Timeshift configured for automatic backup every week. So I was curious, why the mintupgrade check stops with an error like this. When I checked the /usr/bin/mintupgrade file I realized, that the used path is wrong! The correct path is: /etc/timeshift/timeshift.json (instead of /etc/timeshift.json). After correcting the path the error gone.

Hi, I am new in this system and I can not find the time shift tool, and I can not understand the answer, Could someone explain it how I could use the timeshift?, Please explain me as I was a dummy

thanks in advance

One benefit of the missing time shift tool was a vertical line that would appear along all the tracks. This was helpful to me for aligning tracks as it would let me easily see which tracks were misaligned.

What I would do is to drop a temporary point label at the line-up position. Then when you move tracks with the drag-bars you will see the yello snap-line appear when the edge of the moved clip lines up with the label.

It works, but I ended up rolling back to Audacity 3.0.5. I even noticed that the missing vertical line shows along all tracks regardless of which tool is selected.

Vertical line along all tracks.png982897 212 KB

Clip handles are the rounded corners above the clip which feature the clip title. You can move clips around by simply clicking and dragging the clip handle, and you can rename clips by double-clicking the clip handle.

If the timeshift is -410 seconds, then privacyIDEA assumes, that the clock of the TOTP token is off by 410 seconds. Thus privacyIDEA will check otp values in a timewindow of 180 seconds of by 410 seconds.

If the time of the smartphone is then corrected again, then privacyIDEA will check the OTP value in a timewindow of by 410 secs. But the smartphone calculated the otp value based on the correct time.

This way it will fail.

I have both the server and my client using the same public time server, both are completely in sync. However when I sync my token, I get a timeshift value (7.74954390526). I would think it wold be almost nonexistent since they are based off the exact same clock values.

After installing my current system Linux Lite 6.2 on Jan 18, and after updating the system I let timeshift run for the first time.

After that I let it do a weekly snapshot and set it to keep two ones of them.

Later I decided to abandon weekly snaphots and perform them manually.

In general, the initial system snapshot created by Timeshift is important as it captures the state of your system at the time of installation or initial configuration. It serves as a baseline from which you can restore your system to its original state if needed.

Rollback to the initial state: If you encounter a critical issue or want to revert your system back to its original state, having the initial snapshot readily available can be beneficial. It allows you to roll back your system to the exact state it was in when you first installed it, avoiding any potential issues that might have arisen since then.

Considering these factors, it is generally recommended to keep the initial snapshot, along with the most recent snapshots, for a comprehensive backup strategy. This way, you have a recent snapshot for emergencies and the initial snapshot as a reference point for a complete system restoration.

If storage space is a concern, you may consider deleting older snapshots from the sequence but still retain the initial snapshot. This ensures you have a more recent backup while still maintaining the baseline snapshot.

By default, Timeshift uses the RSYNC algorithm for creating snapshots. This algorithm allows for incremental backups, where subsequent snapshots only capture the changes or differences from the previous snapshots. This approach helps save disk space by avoiding the need to duplicate unchanged files in each snapshot.

On the other hand, if you are using Timeshift with a file system that does not support snapshots, such as ext4 [or ext3], it will still create snapshots, but they will be full snapshots. Each snapshot would contain a complete copy of all the files and directories.

You raise a valid point. If you are using Timeshift with ext3 and have a completely functional system at the time of the first snapshot, you may not necessarily need to retain the very first snapshot if you have subsequent snapshots that capture the system in a stable and updated state.

The primary purpose of keeping the initial snapshot is to have a reference point from which you can restore your system to its original state if needed. However, if you have subsequent snapshots that capture your system after updates and installations, those snapshots can serve as effective restore points as well.

In such a scenario, where you have subsequent snapshots that adequately represent the state of your system with updates and installed programs, you can choose to omit the very first snapshot and retain the most recent snapshots that reflect a stable and up-to-date configuration.

Wow, you got a comprehensive answer

The only issue you have is making sure you keep snapshots of the system when it is in a good state.

Full snapshots are easy to manage. I am glad it turned out that way. Its just like clonezilla, only it does filesystems instead of partitions.

In RSYNC mode, snapshots are taken using rsync and hard-links. Common files are

shared between snapshots which saves disk space. Each snapshot is a full system

backup that can be browsed with a file manager.

I like Timeshift and have used it many times successfully. But for a major / important points of the my OS, like first checkpoint, before major updates, and before release upgrade, I feel a lot more comfortable have a standalone backup / restore procedure. I use CloneZilla for those.

Hi Rosika,

OK, if Timeshift does the delete, it might be capable of leaving behind anything that is hard linked to later snapshots

but

if you simply deleted the files with rm it could be a disaster

3a8082e126