The officially official Devuan Forum!

You are not logged in.

#1751 Re: Other Issues » [SOLVED] Security update delays » 2019-03-29 17:38:15

anonymous wrote:

dovecot

debian- https://security-tracker.debian.org/tra … -2019-3814
stretch (security)    1:2.2.27-3+deb9u4

devuan in security apt policy/apt-cache policy still has
1:2.2.27-3+deb9u3

hmmm

Not anymore. You must have caught it right before the repo updated.

     1:2.2.27-3+deb9u4 0
        500 http://auto.mirror.devuan.org/merged/ ascii-security/main amd64 Packages
        500 http://pkgmaster.devuan.org/merged/ ascii-security/main amd64 Packages
        500 http://deb.devuan.org/merged/ ascii-security/main amd64 Packages
         10 http://security.debian.org/ stretch/updates/main amd64 Packages

#1752 Re: Devuan » Using Debian packages » 2019-03-29 12:04:14

I guess it's about as safe as it ever was to use outside repos in debian. As long as they don't require systemd, it should be ok. You might run into problems if something expects to see debian and doesn't recognize devuan. Check forum and mailing list archives for discussions about specific apps.

#1753 Re: Installation » mini.iso 16-2-2019 BUG does not install on M2 disks » 2019-03-25 09:39:59

Lysander wrote:
fsmithred wrote:

Does fdisk or lspci see the M2 disk? What's the device name? (/dev/nvme* or something else?)
Is there any useful info in /var/log/installer/syslog?

In my experience fdisk is not good with recognising SD cards - inasmuch as it doesn't see them at all. It's the same for cfdisk but no problem for a graphical installer. Attempting to mount the disk manually doesn't work [/dev/mmcblk0]. It may be a similar issue with M2 disks. I have spent hours looking round the internet for a solution but have found nothing.

Good to know. Thanks. Is gdisk any better?

Maybe your disk shows up in /dev/disk/by-*.  Oh, wouldn't /dev/mmcblk0 be the whole device? Shouldn't you be mounting /dev/mmcblk0p1 or something? (Maybe you just didn't type the entire name.)

#1754 Re: Documentation » HOWTO: Devuan with full disk encryption » 2019-03-25 09:32:48

For the record: If you install from one of the live isos, you would choose to encrypt the root filesystem and not select a separate partition for /boot. That's all. The installer will add the line to /etc/default/grub.

#1755 Re: Installation » mini.iso 16-2-2019 BUG does not install on M2 disks » 2019-03-25 09:00:05

The relevant package name for the bug report is debian-installer.

Does fdisk or lspci see the M2 disk? What's the device name? (/dev/nvme* or something else?)
Is there any useful info in /var/log/installer/syslog?

#1756 Re: Devuan Derivatives » Heads Distro » 2019-03-22 19:22:35

I'm pretty sure I tried refractasnapshot and installer in heads some time ago. I think it works if you add the live-config packages. Newest version of the installer is 9.5.3 and it's in ascii, beowulf and ceres. You don't need to change sources.list for that. Just update the package cache and install what you want.

#1757 Re: Installation » UEFI and NVME help » 2019-03-22 18:35:53

Forgot to mention this...

For uefi, the command is just grub-install. You don't need to tell it where to put the bootloader, because it knows to put it in the efi partition. And every time you run it, it'll make another devuan dir in your efi partition. If you want it to update the bootloader that's in the debian dir (i.e. the one you're actually using) run grub-install --bootloader-id=debian

And I suppose you could turn on secure boot now. I haven't tried that.

#1758 Re: Installation » UEFI and NVME help » 2019-03-22 11:37:41

Either install one of the unsigned kernels (e.g. linux-image-4.19.0-2-amd64-unsigned) or change the name of the bootloader directory from EFI/devuan to EFI/debian.

#1759 Re: Devuan Derivatives » Heads Distro » 2019-03-21 13:38:12

Here's the repo with instructions (and a link to more instructions.)
github.com/headslive/build-system

You can unpack the tor browser bundle on a rw partition and it will keep your setting, bookmarks and downloads in the tor-browser directory. Make sure the partition has exec in the mount options. And look at tomb for encryption. I believe it's already installed.

#1760 Re: Devuan Derivatives » Heads Distro » 2019-03-21 09:29:52

Standard methods for persistence won't work with Heads because live-config is not installed. There might be another way to do it, but I don't know how. You could make your own heads iso with live-sdk and add live-config and live-config-sysvinit to the package lists. (I haven't tested that but it should work.)

Keep in mind that full-persistence can reduce security. The read-only system is always clean when you boot up - every boot is the first time. If you just want to be able to save files, create another partition and mount it somewhere in your home.

#1761 Re: Devuan » Possible long-term install of Devuan and initial post-install thoughts » 2019-03-18 16:34:09

You couldn't start X because your home didn't exist.

nobody is an unpriviliged system user that runs some processes so they don't have to run as root. That entry is normal.

#1762 Re: Other Issues » [SOLVED] Security update delays » 2019-03-18 15:31:29

Something must have changed recently. I have an ascii install that has ascii-backports, beowulf and ceres all pinned to 100, and yesterday I noticed that apt-cache policy was telling me that ceres had the Candidate version.

I just changed those pin priorities to 99 and checked again. Now backports has the candidate, and the backports priority shows as 100 even when I've got it set to 99 in my preferences.

It should be showing me the ascii version as the candidate.

Pin-Priority: 100 (on ascii-backports, beowulf and ceres)

user@ascii:~$ apt-cache policy debootstrap
debootstrap:
  Installed: 1.0.89+devuan2
  Candidate: 1.0.114+devuan1
  Version table:
     1.0.114+devuan1 100
        100 http://deb.devuan.org/merged ceres/main amd64 Packages
     1.0.110+devuan1 100
        100 http://deb.devuan.org/merged beowulf/main amd64 Packages
     1.0.110~bpo9+1 100
        100 http://deb.devuan.org/merged ascii-backports/main amd64 Packages
 *** 1.0.89+devuan2 100
        100 /var/lib/dpkg/status
     1.0.89-devuan2.1 500
        500 http://pkgmaster.devuan.org/merged ascii/main amd64 Packages

Pin-Priority: 99 (on ascii-backports, beowulf and ceres)

user@ascii:~$ apt-cache policy debootstrap
debootstrap:
  Installed: 1.0.89+devuan2
  Candidate: 1.0.110~bpo9+1
  Version table:
     1.0.114+devuan1 99
         99 http://deb.devuan.org/merged ceres/main amd64 Packages
     1.0.110+devuan1 99
         99 http://deb.devuan.org/merged beowulf/main amd64 Packages
     1.0.110~bpo9+1 100
        100 http://deb.devuan.org/merged ascii-backports/main amd64 Packages
 *** 1.0.89+devuan2 100
        100 /var/lib/dpkg/status
     1.0.89-devuan2.1 500
        500 http://pkgmaster.devuan.org/merged ascii/main amd64 Packages

Pin-Priority: 50 (on ascii-backports, beowulf and ceres)

user@ascii:~$ apt-cache policy debootstrap
debootstrap:
  Installed: 1.0.89+devuan2
  Candidate: 1.0.110~bpo9+1
  Version table:
     1.0.114+devuan1 50
         50 http://deb.devuan.org/merged ceres/main amd64 Packages
     1.0.110+devuan1 50
         50 http://deb.devuan.org/merged beowulf/main amd64 Packages
     1.0.110~bpo9+1 100
        100 http://deb.devuan.org/merged ascii-backports/main amd64 Packages
 *** 1.0.89+devuan2 100
        100 /var/lib/dpkg/status
     1.0.89-devuan2.1 500
        500 http://pkgmaster.devuan.org/merged ascii/main amd64 Packages

#1763 Re: Devuan » Possible long-term install of Devuan and initial post-install thoughts » 2019-03-18 14:58:30

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?

#1764 Re: Devuan » Possible long-term install of Devuan and initial post-install thoughts » 2019-03-18 04:21:36

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.

#1765 Re: Devuan » Possible long-term install of Devuan and initial post-install thoughts » 2019-03-17 22:25:18

Lysander wrote:
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.)

#1766 Re: Devuan » Possible long-term install of Devuan and initial post-install thoughts » 2019-03-17 16:03:15

Lysander wrote:

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.

#1767 Re: Devuan » Possible long-term install of Devuan and initial post-install thoughts » 2019-03-17 14:28:52

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.

#1768 Re: Devuan » Possible long-term install of Devuan and initial post-install thoughts » 2019-03-17 06:13:49

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.

#1769 Re: Installation » Beowulf, where to download from » 2019-03-15 00:36:49

golinux wrote:
Job wrote:

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")

#1770 Re: Devuan » Burnt burnt burnt... » 2019-03-15 00:27:26

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.

#1771 Re: Devuan Derivatives » Refacta 9.0 Released » 2019-03-09 01:50:57

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.

#1772 Re: Devuan Derivatives » Refacta 9.0 Released » 2019-03-07 02:02:49

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

#1773 Re: Other Issues » Question about versions » 2019-03-07 01:33:45

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.

#1774 Re: Devuan Derivatives » ThomOS - the new outrageous devuan-based switchblade OS » 2019-03-06 01:37:41

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.

#1775 Re: Other Issues » [SOLVED] Security update delays » 2019-03-05 05:02:23

/etc/apt/preferences.d/mxrepo (or some other file name)

Package: *
Pin: origin "mxrepo.com"
Pin-Priority: 400

I 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.

Board footer

Forum Software