You are not logged in.
The re-use home option was set up so that the installer would exclude /home from the rsync copy of the live system. I think the installer did exactly what it was told to do, which is not the same as doing what anyone needs it to do.
I'm not sure why you had to add a user. Is there still a user in /etc/passwd named devuan with id 1000?
That log shows that you chose to re-use an existing home partition. If you did that with a new (empty) partition, it would have remained empty. If instead you had chosen the option to "Create a new separate home" it would have copied the files from /home in the live system to the home partition on the sd card.
You're not the first to be confused by this, but I hope you're the last. The option to re-use an existing home as been removed in the next version. 9.5.3 is in ceres, and I plan for it to be in the ascii point-release.
fsmithred wrote:If you got a refractainstaller log in your home, I'd like to see it and try to figure out what went wrong. You can send it to me at gmail or paste it somewhere and provide the link.
Thanks.
Yes of course, how would I go about finding it?
It should be in the primary user's home directory, named refractainstaller_error.log (or something close to that.) If it's not there, get the one from /var/log/, but that one won't be complete. (it gets copied with the rest of the system, before the installer is finished.)
Well, unless I'm misunderstanding, something is going wrong somewhere. This was a new live install and a new /home partition. Of course I created a user during the install, but it didn't seem to want to create a directory for that user in /home so I had to do it manually.
If you got a refractainstaller log in your home, I'd like to see it and try to figure out what went wrong. You can send it to me at gmail or paste it somewhere and provide the link.
Thanks.
Putting home on a separate partition is not the experimental feature. That's been there since around 2011 and does exactly what it's supposed to do - it formats a separate partition, mounts it at /home and copies the live home to it. If you change the user name during the install, it will rename things in your home, including instances of /home/user inside some files that will be changed to /home/your-new-name.
The experimental feature is for re-using an existing home. It does not do what you or anyone else thinks it does, and I think that feature will be gone before next week. All it does is mount your old home partition to /home (adds an entry to fstab). The fact that your home is empty worries me. The installer should not have formatted the re-used partition. Was it a new, empty partition to begin with , or did all your files get wiped?
You're better off just installing to a single partition and then making the changes after first reboot. That way, there will be new config files in the new home that can be moved over to the old home if needed.
Welcome to devuan. I used zenwalk for a year before switching to debian (etch) for its vast repository, so I understand where you're coming from.
The live installer has grown rather clunky, especially since adding support for uefi. It's due for an overhaul. I'm pleased you were able to install to an mmc device. I assume you used the graphical installer, and it showed your partitions correctly. You're the first I've heard of doing that, and I've been wondering if it really works.
Upgrade to beowulf will not mess with /usr or /sbin. It won't change your directories.
Job wrote:Is systemd part of Beowulf?
No. What makes you think that?
Probably the line that says systemd-238 (is that like uranium?) is in ceres and 232 is in testing.
I can assure you it's not in either of those repos. ("No candidate version found for systemd")
Welcome home! Not sure if you saw my no-dbus experiment: https://dev1galaxy.org/viewtopic.php?id=2158
I just happened to be looking at that again today with a mind to create a live-sdk blend for the no-dbus build. (live-sdk is for automated building of live-CD isos.)
Here's one I made (manually) in September. Um, two nodbus builds; i386 and amd64. The one with bpo in the name is ascii with backports kernel (and with dbus.)
https://get.refracta.org/files/experimental/
These isos are POC and fun, but probably not for production.
refracta-lang works in beowulf (no X)
RE iso size.. might there be a way to avoid having two copies of initrd (one in /live and one in the squash, 25 M each as gzip)?
Yeah, that would work. It's not needed in the squash. Just have to make sure that update-initramfs runs during the install.
Thanks, for that. I can make those changes in a point release. I had made a couple isos in October that were under 700mb, but then I ran update/upgrade and the snapshots grew. The initrd should have already been xz compressed unless it somehow reverted during upgrades.
Package list is mostly the same. Dropped atril and all the mate system utils and put in xpdf. Forgot to add noscript in the i386. Probably forgot something else, too.
I thought refracta-lang was specific for lightdm. I switched to lxdm mainly because I was getting better results with other languages.
Speaking of beowulf, I had to make a couple of custom live-config scripts for it. One for lxdm so that it doesn't expect lxde, and one for openssh-server, which hangs on boot while waiting for enough entropy to make the host keys. That one is here - http://distro.ibiblio.org/refracta/file … sh-entropy
When a new stable release is ready, you can change your sources to that release and upgrade. That will replace older versions of software with newer version, and it will probably also remove some obsolete packages and introduce a few new ones. If there are system config files that you've edited, the package manager will usually ask if you want it replaced with the newer config file or not, and it will give you an option to compare the two. It will not mess with any files in your user's home directory.
You don't have to wait for the current release to reach end of life, but you can if you want. The repositories will still be around and will still get security updates.
Here's the LTS schedule. Jessie dies next year and ascii (same as debian stretch) will go on until 2022.
https://wiki.debian.org/LTS
Refracta uses the xfce4 desktop. The desktop is installed without metapackages, which means you can easily remove any parts of it without the whole desktop getting removed due to the dependency chain. If instead, you install xfce from the devuan installer isos or from the devuan desktop-live, you get a more complete destkop, but if you try to remove any parts of it, all of it and your desktop applications may get removed.
If you prefer some other desktop environment or a window manager, you should use one of the installer isos.
Suggested listing:
ThomOS (formerly Crunkbong)
Siva, you didn't mention it, but login/password are thomos/thomos
System boots to console login. Login leads to automatic graphical session in openbox. I don't know how you got no autologin without adding 'noautologin' to the boot command, but you need to either add 'nox11autologin' or do something else to get rid of /etc/profile.d/zz-live-config_xinit.sh.
The boot item for foreign language does not work. The syntax 'lang=it_IT' is specific for lightdm along with refracta-lang, a custom live-config script for changing locale and keyboard at boot. I don't know if it still works. (you don't have that script, anyway). The standard method does work:
locales=it_IT.UTF-8 keyboard-layouts=it
That's as far as I got for now. More later. Looks good so far.
/etc/apt/preferences.d/mxrepo (or some other file name)
Package: *
Pin: origin "mxrepo.com"
Pin-Priority: 400I think that will work. The man page for apt_preferences says that origin can match a hostname. I don't know if you need to make a separate entry for la.mxrepo.com or if the one will get both.
Setting the default release changes the priority from 500 to 990 on the ascii main version. I just tested it - they were both 500 before I set the default.
I guess you'll need to add '-t ascii-security' to your install command.
Is the intel-microcode package installed? That injects a binary into the initrd. I'm wondering if that could be causing the confusion.
This should show you the available commands, and those commands should have man pages. If not, try running each command with the '--help' option.
ls /usr/bin/dvb*No such file or directory
You're sure it's there? You didn't change directory between running xzcat and running file? Try using the full path to the real file instead of the symlink. (/boot/initrd.img-<version>)
BTW, it's better if you don't have the initrd inside the directory where you extract it. You don't want it to end up inside the new initrd when you repack it.
W: Download is performed unsandboxed as root as file '/root/.synaptic/tmp//tmp_sh' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)That's the message you get when you download a package as root. Download as ordinary user instead.
What message do you get when you run
apt install dvb-appsIf it's already installed, apt will tell you that. Look in /usr/share/doc/dvb-apps for information. The package description says "interface::commandline" so that might explain why it's not in the menu.
dpkg -L dvb-appswill give you a list of the files in the package. That will include a list of any commands. There will probably be man pages for those commands.
It goes by too fast for me to see what it says. There are only about four lines of output, and there's no red. I did add 'local vgs vg' to the beginning of do_stop() but I don't know if that would make a difference.
I'm not sure what success you're expecting. Did you repack the initrd, and if so, what changes did you make to it? Or are you still trying to unpack it?
file /boot/initrd.img-4.19.0-2-amd64 should tell you what compression is used. Use the corresponding zcat or xzcat command above to unpack it. Tell me which compression was used and what you found inside the initrd. Possible choices of things to do would be remove the offending files, edit the offending files, maybe something else.
Maybe you're missing these?
Rebuild initrd with gzip compression:
find . -print0 | cpio -0 -H newc -o | gzip -c > ../initrd.img
Rebuild initrd with xz compression:
find . | cpio -o -H newc | xz --check=crc32 --x86 --lzma2=dict=512KiB > ../initrd.img
Then of course, you have to replace the original with your changed version. (keep a backup copy of the original and copy the modified one to /boot, and make sure the name corresponds to what your boot menu expects it to be.)
Forget about the timeouts. The old patch still works. Here's what my do_stop function looks like now. I added the lines between 'dmsetup mknodes' and 'log_action_begin_message...' I did not add the local variable declarations. Those are no longer in this function. Maybe I should.
do_stop() {
dmsetup mknodes
if [ -x /sbin/lvm ]; then
vgs="$(/sbin/lvm vgscan | sed -n '/"/s/^.*"\([^'\'']*\)".*$/\1/p')"
if [ -n "${vgs}" ]; then
for vg in ${vgs}; do
/sbin/lvm vgchange -a n ${vg} >/dev/null 2>&1
done
fi
fi
log_action_begin_msg "Stopping $INITSTATE crypto disks"
crypttab_foreach_entry _do_stop_callback
log_action_end_msg 0
}The initrd is not in gzip format. Use this line instead:
xzcat /initrd.img | cpio -d -i -mYes, you can just call the initrd directly (in /boot) instead of using the symlink.
Please get refractainstaller 9.5.2 from ceres. It should be in the repo by now (or very soon.)
Go ahead and modify refractasnapshot as I indicated a couple posts above and see if it works. If you use the cli script, please add the -d option for a verbose log. If that doesn't work, you may need to do the steps listed below.
More info...
https://lists.debian.org/debian-user/20 … 00195.html
++++ BEGIN apt-listchanges: News MESSAGE ++++
initramfs-tools (0.129) unstable; urgency=medium
* Some systems that do not support suspend-to-disk (hibernation) will
require a configuration change to explicitly disable this.From version 0.128, the boot code waits for a suspend/resume device
to appear, rather than checking just once. If the configured or
automatically selected resume device is not available at boot time,
this results in a roughly 30 second delay.You should set the RESUME variable in
/etc/initramfs-tools/conf.d/resume or
/etc/initramfs-tools/initramfs.conf to one of:- auto - select the resume device automatically
- none - disable use of a resume device
- UUID=<uuid> - use a specific resume device (by UUID)
- /dev/<name> - use a specific resume device (by kernel name)-- Ben Hutchings <ben@decadent.org.uk> Thu, 20 Apr 2017 23:21:32
+0100</ben@decadent.org.uk>++++ END apt-listchanges: News MESSAGE ++++
Hmm.. My resume file contains 'RESUME=none' but there's no RESUME variable in /etc/initramfs-tools/initramfs.conf. I guess the scripts in /usr/share/initramfs-tool/ figured it out in my system. You could add RESUME=none to initramfs.conf then run update-initramfs -u -k all and then make a new snapshot. Note that this would change the host initrd. (both of them)
As ordinary user, in your home run the following commands.
mkdir extracted
cd extracted
zcat /initrd.img | cpio -iThen look in conf/conf.d/zz-resume-auto. If you have more than one kernel, you can replace '/initrd.img' with the real paths, '/boot/initrd.img-4.whatever' (but unpack them into different directories, like extracted and extracted2 for instance.)
My beowulf has conf/conf.d/resume. I don't know why yours is different.
The script is set to remove conf/conf.d/resume and conf/conf.d/cryptroot. Those files don't exist. They changed the name of resume to zz-resume-auto, and not relevant to your case, they moved cryptroot from conf/conf.d/ to the root of the initrd.
OK. Edit /usr/bin/refractasnapshot. Change this:
274 if [ -f conf/conf.d/resume ] ; then
275 echo "Removing resume"
276 rm -f conf/conf.d/resume
277 fiTo this:
274 if [ -f conf/conf.d/zz-resume-auto ] ; then
275 echo "Removing resume"
276 rm -f conf/conf.d/zz-resume-auto
277 fiThe line numbers might be offset by a few. In the gui version it's around lines 321-323.
Edit: Wait. See next post when it arrives. I'd like to know what's inside that file.