You are not logged in.
New versions of refractasnapshot and refractainstaller are available in Ceres and also on sourceforge. The ones on sf are signed with my key and have ~fsr in the version. Other than that, they are the same as the ones in the repo.
https://sourceforge.net/projects/refracta/files/tools/
refractainstaller-base (9.5.0)
* Set root path to include sbin directories. (for Buster/Beowulf)
* Eliminate sudo/su question in wrapper script. Try sudo first.
* Shorten log name to refractainstaller.log
* Changed yad version test to 0.27 or newer needed. (This is a guess.)
* Changed wording for sshd_config (s/without-password/prohibit-password)refractasnapshot-base (10.2.0)
* Set root path to include sbin directories. (for Buster/Beowulf)
* Fixed missing grub splash in uefi boot.
* Choose task first, get disk report only with full snapshot.
* Put report in text-info window so it has scroll bars and fits on screen.
* Merge grub-efi warning into main report.
* Automate the encryption confusion:
* Test initrd for cryptsetup. Rebuild with CRYPTSETUP=y if needed.
* Test initrd for conf.d/resume and cryptroot. Remove if present.
* Update ssh_config wording.
* Replaced dysfunctional progress bar in check_space() with info window.
* Test for config file after command-line options.
* Changed name of log to refractasnapshot.log
* Make help screen available within program.
* Added '-iso-level 3' to xorriso command for isos larger than 4GB.
I didn't put refractsnapshot-gui in the ascii repo because it wasn't working well with gtk3. You might get off-screen buttons in some of the windows. If so, just use the cli version. They are the same. The latest version (10.2.0) at sourceforge (and soon to be in unstable repo) doesn't have this problem. That version also has the fix for isos larger than 4GB. Nevertheless, you should exclude your data if there's any significant amount and use a different method for the data backup.
If you want to make a bootable backup of a non-uefi system, you can ignore the warnings about grub-efi. If you want your iso to be bootable on bios or uefi (in case you want to install on a uefi system) you need to do a few simple things:
- install grub-efi-amd64 and grub-efi-amd64-bin but don't let grub install the bootloader. Tell it NO when it asks.
- include the grub-pc package in the iso. Put it in the root of your filesystem before you make the snapshot. When you get around to installing the system, if you boot on bios, the installer will find the grub-pc iso and install the package. It will also ask if you want the bootloader installed. Most likely, you will want to say YES here.
Note: It's also possible to do the opposite of the above. Keep grub-pc installed, include grub-efi-amd64 and grub-efi-amd64-bin packages, set force_efi=yes in the config file, and make the snapshot. If you boot on a uefi system, the installer will find the grub-efi packages and install them.
If you know you will only install on a bios system, you can do nothing and just ignore the warning. Your iso will not boot on uefi systems.
grub-efi-amd64 2.02+dfsg1-8 seems to be working correctly here. I rebooted into my ceres install, checked that the grub version was right and ran grub-install --bootloader-id=nodbus && update-grub.
This installation is on a single partition. No raid, lvm or encryption.
I haven't tried that yet, but I will let my ceres install take over the boot on this machine. Meanwhile, can you tell me how your grub directory got into the efi partition? The only file I have in any of the efi directories is grubx64.efi. My grub directory is a subdir of /boot, as it has always been.
Installing the second system should be as easy as running the installer for that system and choosing (or creating) another partition - unless you didn't leave a spare partition or extra space on the drive to create one.
If you want help with partition layouts, describe what you currently have and what you want to accomplish. (output of 'fdisk -l' would help.)
Good one to know. I never heard of multipath-tools and don't have it installed. Also never used dmsetup commands. Thanks for that!
I think I'm confused about what you want to do. If you want to include refractainstaller in your no-gui system, you won't be able to use the gui version. If you want gui, you have to install xorg and whatever else you want for a desktop.
apt-get install refractainstaller-base refractasnapshot-base
apt-get install refractainstaller-gui
apt-get -f installThat last command will add all the dependencies, including yad (if you're in ascii, but not if you're in jessie.)
If you want refractasnapshot-gui, it's not in the repo, but you could download it here -
https://sourceforge.net/projects/refracta/files/tools/
Warning: the first screen might not display properly (with buttons off-screen). That's why it's not in the repo. There's no advantage over the cli version.
Now that I looked at the versions on sourceforge, I suggest you download the latest versions and install wtih:
dpkg -i refracta*.deb
apt-get -f installIf I misunderstood your question, try again.
Here's a video showing how to do what you want to do, except not on a logical partition. It's very easy to get it wrong. (the '4' in the file name means it was my fourth attempt, and I've done it many times before.)
http://distro.ibiblio.org/refracta/misc … rypt-4.ogv
Are you sure you're using a live iso? The output you posted looks like it's from the debian installer, which is only in the installer isos.
Some thoughts - I seem to recall that for a root partition inside an extended partition, you need to mark it with the boot flag. I guess that assumes that /boot is in the root partition.
If you encrypted the root partition without a separate boot partition, then you need to have a line in /etc/default/grub that will tell grub to ask you for the pass phrase.
GRUB_ENABLE_CRYPTODISK=yIf you installed from a usb, the bios may have switched the drive numbers when you tried to boot without the usb. Check what your grub.cfg says.
Sorry about that, but we didn't get to choose who left and who didn't. If we did have that power, we would have taken a few more. But it turns out that would not have been necessary - they're coming around eventually. First year, we got all people who didn't want systemd, but as time goes by, we keep getting more people who thought they did want systemd and changed their minds after they got it.
Welcome to devuan.
P.S. Also sorry I didn't see your post a year ago. I don't think I've ever had two installs come out exactly the same with debian-installer.
Doh! You need to rebuild the initramfs without lvm support. I'm not sure if disabling it in all runlevels before running update-initramfs -u is enough. There may be a config file with a setting something like the one for mdadm. Another way to do it would be to remove lvm2 and mdadm, and the initramfs will be rebuilt automatically without those items.
.
I don't know how that could happen. Are you making new snapshots or doing this on a persistent partition after making changes? Either of those ways should work.
I've seen the same issue with mdadm and raid. To avoid having to manually unmount and close the volume group, you could disable the lvm2 service before making a snapshot. That can be done with update-rc.d or sysv-rc-conf. If you want to get fancy, you could have lvm enabled or disabled in different runlevels, and then make boot menu entries for the different levels. (There's already one for runlevel 3 as text mode in the stock refractasnapshot menu..) That way, it would be available if you need to boot live and access files in the lvm.
I don't know the answer. You should be able to make a backup of the whole mmc device if you can read it while windows is not running. You would need to either boot a live-usb or pull out the card and connect it to another computer. Then dd if=/dev/mmcblk0 of=some-file
If you install devuan to the hdd instead, the grub bootloader will go into the efi partition, and it should include the windows system in the boot menu. That is what normally happens. No guarantees with this. Check your bios to make sure you can turn off secure boot.
Do you know which packages from backports are causing the problem? Get the list of bpo packages that are to be upgraded, and run 'apt-cache policy' on them to see what versions are in ascii and bpo. That might identify the naming problem you suspect. It might also be possible to find the problem by upgrading one bpo package at a time. (one or a few if necessary.)
One solution would be to force eudev to use the new naming scheme. Add 'net.ifnames=1' to the boot command, and you'll get interface names that will not change.
See if the drive shows up in 'fdisk -l' after eject vs. unmount. I have a feeling it might be different.
Maybe the .desktop file is missing. Here's what mine looks like in jessie (for an older version)
/usr/share/applications/gtk-youtube-viewer.desktop
[Desktop Entry]
Name=GTK Youtube Viewer
Version=1.0
Comment=Search and play YouTube videos with MPlayer.
Exec=gtk-youtube-viewer
Icon=gtk-youtube-viewer
StartupNotify=false
Terminal=false
Type=Application
Categories=AudioVideo;You could try this one. I don't know if it works with the current version of youtube-dl - this is a couple years old.
http://distro.ibiblio.org/refracta/file … u1_all.deb
If you want to recompile it, the source package can be found here. This is the same version as above. There may be newer sources (and maybe that's what you were trying to install.)
http://exegnulinux.net/refracta/experim … index.html
Found it - in the changelog for refractainstaller-gui 9.4.0:
Fixed bug: encrypted /home gets incorrect fstab entry
You must have at least 'main' on the deb line, or you'll get nothing. If you add contrib and non-free, it makes those packages available, too. You could put main, contrib and non-free on separate deb lines if you wanted, or all three on one line. Either way does the same thing.
@kekePower: The log ended after the first rsync command, so I can't tell what happened after that. I've seen that happen before, but I don't know the cause. I'll have to try an encrypted install to see if that's what does it.
-H preserves hard links. I don't know if I have any of those. Symlinks are already handled properly (e.g. /vmlinuz and /initrd.img work right.) I've also considered adding -X and -A for xattr and acl. I might make the rsync command more configurable than it already is.
@miyo: Yes, newer versions of the installer are better. Look for 9.4.3 soon, and then 9.5.0 for beowulf and beyond.
fsmithred (not a wizard. I just kick it around until it does what I want.)
Separate isos for free and non-free is a possibility. I'm planning to push for a better solution than what we now have when we get to making beowulf isos. There's also been talk of a libre repo (with libre kernel). But at this point, it's just talk. No actual plans yet.
kekePower: I'd like to see the installer log. (It should be in your home or else in /var/log). Paste it somewhere or email it to me. Encrypting the root, home and changing username should all work. If no, I need to know why, so I can fix it. Thanks.
Is firmware-realtek installed? Is the card set as the default wireless interface in wicd?
I've got an 8723AE and it's working as expected.
Post output of ifconfig and iwconfig (or 'ip a' if you don't have ifconfig).