The officially official Devuan Forum!

You are not logged in.

#2076 Re: Installation » How to install Devuan system/language into spanish? [solved] » 2018-05-29 14:34:57

That does help, thanks. You definitely installed from the desktop-live. If you booted into Italian, then any system messages would be in Italian. The English parts are from the installer script. The debconf dialogues for locales, tzdata and keyboard would have been in Italian, too. I can see that those ran correctly this time. I don't know why they didn't work for you the first time.

#2077 Re: Installation » A journey thorugh ASCII » 2018-05-28 15:29:59

I don't know a way around that problem. Debian "fixed" pinning last year, and some things that used to work no longer do.

#2078 Re: Installation » How to install Devuan system/language into spanish? [solved] » 2018-05-28 15:27:44

keos wrote:

As you said the user, HE, was able to run the installer in Italian ... !!

-- there is a problem with the installer.

Thanks!!

I'm still trying to figure out what installer you used. The one I wrote and maintained does not have any translation files. That's the only installer on the desktop-live iso. There are two versions of it: refractainstaller-yad, which starts from the desktop icon or menu and has a graphical interface, and refractainstaller, which runs in a root terminal or console.

If the installer gave you instructions in Italian, you must have been running the regular debian(devuan)-installer, which can only be started from the boot menu of the installer isos. (not the live isos).

Regardless of which installer you used, the dialogues for locale, timezone and keyboard should have come up at the beginning of the installation. If that did not happen, then yes, there is a problem, but you're the only one who has encountered it. More information would be needed to figure out why that happened.

#2079 Re: Installation » How to install Devuan system/language into spanish? [solved] » 2018-05-27 16:05:16

I think just the system was in Italian. "everything" meaning desktop, menus, apps, and console/terminal.

What I don't understand is why the dialogues for locale, tzdata and keyboard didn't come up at the beginning of the install. Those are in the pre-install script and can be turned off in the config file for the cli script and in the options menu for the graphical installer. (maybe he un-checked that box.)

#2080 Re: Installation » A journey thorugh ASCII » 2018-05-27 15:58:38

-I used the dist-upgrade command out of Debian habits, and I wonder if this is the culprit of my woes, because it installed dbus and slim; shame on me for not reading through the 800+ upgraded packages.  Also in this episode: dbus and slim are now pinned to never download.

You must use dist-upgrade or the equivalent (aptitude full-upgrade) to get to the next release. Warning: pinning ain't what it used to be. Stuff that's blocked on install is not necessarily (or maybe not at all) blocked on dist-upgrade. I've seen libsystemd0 come in like that on upgrading from jessie to ascii.

-It's using about 10-15mb more ram than jessie and I'm not really sure why.  This isn't an unreasonable amount, but it is noticeable.  Did anyone else experience this after they upgraded?

Yes, I experienced this on upgrades from lenny to squeeze to wheezy to jessie to ascii. I don't recall what happened from sarge to etch to lenny, but I'll bet it was similar.

#2081 Re: Installation » How to install Devuan system/language into spanish? [solved] » 2018-05-27 03:12:21

I'm certain that there are no working translations for the installer. There is a German translation, but the way the script is written causes some problems. It's on my todo list.

keos wrote:

i pressed f2 to display languages but nothing happened

To change the language, use backspace to erase and then type what you want. Try to ignore the repeating lines.

#2082 Re: DIY » largely for siva (+ anybody interested): distro remixing methods » 2018-05-26 12:57:08

The correction you requested:
While I have made a few experimental isos that started with a debootstrap install, I usually start with a netinstall iso and un-check everything except standard system utilities in the tasksel window. Add the cli refracta tools and make some config changes, and then make the no-X iso. 

For the desktop iso, I start with an install from the no-X. That way, I still have both systems and can update both no-X and desktop isos.

...and the one you didn't:

Older versions of refractasnapshot used the isohybrid command from isolinux. More recent versions make the isohybrid as part of the xorriso command.

I like the idea of changing an existing iso. David Hare (dzz of Exegnulinux and Refracta) wrote a script to do that, and that script was included in refracta8 (jessie). I should make sure it still works and include it in refracta9.

remaster-snapshot does the following:
# Four stages (script will execute one selected action only then exit):
# 1. Extract and unsquash a live-cd
# 2. Chroot the unpacked system with appropriate bind mounts
# 3. Prepare for "live" use and squash the unpacked system
# 4. Build a new ISO

Another place to customize a system is during the installation. Refracta installer has a point where it pauses to allow you to chroot into the installed system and make changes. You can edit configs and add or remove software at this point. (Note: you could also do those things in the live session, before running the installer, but adding software would use up a lot of RAM.)

#2083 Re: Installation » How to install Devuan system/language into spanish? [solved] » 2018-05-26 11:34:18

siva wrote:

EDIT: I downloaded the amd64 iso from the link you provided and can confirm the behavior.  The second line of the boot menu, "Other languages," should solve your problem.  The default language is Italian, and you should see "locales=it_IT.UTF-8 layout=it".  Edit it: change it to "locales=es_ES.UTF-8 layout=es".  When I booted, however, it didn't change the language to Spanish.  Here's a screenshot for the devs because I have to leave: https://image.ibb.co/gF2GBT/Screenshot_ … _51_40.png

This works on my copy. Except layout=es should really be keyboard_layouts=es. Check the sha256sum of your copy of the file to make sure it was a good download.

If you boot into Spanish this way and run the installer, the installer will still be in English, but the live system and the installed system will be in Spanish.

#2084 Re: Desktop and Multimedia » VLC no longer starts » 2018-05-22 22:22:32

Yeah, something is weird. I don't know what. I just tried it on four different systems, and in all cases, vlc will get upgraded. One system was installed by debootstrap last fall, has no task-* packages and has Recommends excluded. The other three were desktop-live isos - one from February, the official beta and the official rc.

What about the first command I suggested? Does it give you any useful output?

#2085 Re: Desktop and Multimedia » VLC no longer starts » 2018-05-22 14:37:13

The version you want is in ascii-security. If you don't have that repo enabled, you should enable it. If the version from there is not installing, then you can name the repo in the command.
apt-get  -t ascii-security install vlc (maybe you need to add the plugins to that command, too, and maybe a full-upgrade would have installed the newer version.)

#2086 Re: Installation » Manual Install Lightdm Polkit Problem » 2018-05-19 00:55:03

No, don't re-do your install. If you do, you'll get the task- package, and that might get in your way if you want to be selective about what parts to keep. (Try to remove one piece that the task package depends on, and your entire desktop goes on the autoremove list.)

I don't know if anyone gave you this link, but here are Irrwahn's instructions on which polkit libs you need:
https://dev1galaxy.org/viewtopic.php?pid=8217#p8217

#2087 Re: Installation » Manual Install Lightdm Polkit Problem » 2018-05-18 23:36:53

fig, I'm pretty sure you already are using elogind. Look under the hood.

elogind has been around for a few months. It was forked from gentoo. That, and the corresponding libraries allow us to offer more desktops in the installer.

It's elogind and libpam-elogind for kde, cinnamon and lxqt;
consolekit and libpam-ck-connector for xfce and mate.

lxde is a little more confusing, because it can provide a couple more 'kits to get in the way. It's possible to install and use it, but it wasn't coming out of the box right, so we removed it from the tasksel list.

And those are not the only combinations that work.

I made a chart when the beta was released, but it's obsolete. Things have changed.

#2088 Re: Installation » Manual Install Lightdm Polkit Problem » 2018-05-18 21:40:06

Well, if you had a different desktop, it would be the right polkit. Maybe it would have worked better if you installed kde first. Not sure of that. If you choose kde from the installer, it installs task-kde-desktop, which would pull in the right libpolkit packages. But if you install the plasma-dekstop parts without the task- package, you get whatever kde thinks it should have.

I think I see the problem. Instead of depending on consolekit, it should probably depend on consolekit or elogind. But lightdm is not one of the packages that we change.

A bug report to devuan might be good to remind us that it's a problem, so that the solution becomes common knowledge. It also might motivate someone to fix it.

I have no idea what a bug report to debian would do. Theyre probably not interested in making a package depend on a package that isn't in their repo. (i.e. elogind)

# apt-cache depends lightdm
lightdm
  Depends: adduser
  Depends: dbus
 |Depends: <libpam-systemd>
    libpam-elogind
  Depends: consolekit
 |Depends: lightdm-gtk-greeter
  Depends: <lightdm-greeter>
    lightdm-gtk-greeter
    lightdm-kde-greeter
<snip>

#2089 Re: DIY » Tips for using Palemoon » 2018-05-18 21:21:33

I don't know the details of how firejail works, but I understand that it limits access to the user's directories. I imagine there are ways around it, but every little hurdle will help. Pretty sure I've been using firejail ever since you (fig) told me about it. That was back on the refracta forum in a thread about Xephyr, I think.

There's also sandboxy, which I know even less about and have never tried. Has anyone here used it?

#2090 Re: Hardware & System Configuration » i need help with some packages (SOLVED) » 2018-05-17 02:39:30

Usually, all you need to do is:

apt-get install build-essential linux-headers-$(uname -r)

and you'll get the headers for the running kernel along with the build tools.

#2092 Re: Installation » SOLVED - chroot live build - kernel panic » 2018-05-06 17:06:35

Just noticed something while closing tabs - you only did live-boot and live-config. You might need to add live-config-sysvinit and live-boot-initramfs-tools. I'm pretty sure you can install the newer versions without backporting them.

#2093 Re: Installation » SOLVED - chroot live build - kernel panic » 2018-05-06 13:38:35

I think the ehci-orion message just happens to occur near the point when init tries to switch-root, and that's a common place for problems.

I can confirm that your basic procedure works. I have a new install of desktop-live on my hard drive, so I chrooted into it and started making isos. I had to do a little more, because it's an encrypted install, (remove conf/conf.d/cryptroot from initrd). Installed 4.15 from backports, did not remove 4.9, made another snapshot and it boots 4.15 normally.

Oh yeah, I had to remove intel-microcode before I could unpack and repack the initrd.

And I didn't backport anything. Just running ascii and chrooting into another ascii install. Maybe something else in jessie needs to be upgraded for this to work.

#2094 Re: Installation » SOLVED - chroot live build - kernel panic » 2018-05-05 20:49:08

still complaining about ehci-orion not being in modules.dep

It always says that when there's a problem. Don't chase that ghost. What was in conf/conf.d/ in the initrd? That's usually where the problem is.

#2095 Re: Installation » SOLVED - chroot live build - kernel panic » 2018-05-04 13:56:08

If the backports version doesn't work, try the ascii version. You should be able to install it in jessie. In the past (couple years ago) I used the sid version in debian jessie.

#2096 Re: Installation » SOLVED - chroot live build - kernel panic » 2018-05-04 02:24:00

There's no more aufs in the kernel (4.9 or 4.14)

You may need a newer version of live-boot* and live-config*. 20170112 should work (works for me) and is in ascii.
If you have a union=aufs (or union=anything) in your boot command, remove it.

The fix in that bug report was for live-build, which is not used here.

#2097 Re: Devuan Derivatives » [MiyoLinux] New Releases Uploaded » 2018-05-02 11:43:51

Upload trick:

Open up some port in your router (other than 80) and direct it to the local machine that's running a web server. Put your iso somwhere under /var/www/html so it can be downloaded from a remote location.
ssh into sourceforge
wget the iso from your webserver. If the connection breaks, repeat with wget -c and it will continue where it left off.
Close the port when you're done.

#2098 Re: Desktop and Multimedia » when X is killed, lightdm restarts it [SOLVED] » 2018-05-02 11:18:03

/etc/init.d/lightdm start|stop|restart

or

service lightdm start|stop|restart

An alternate solution would be to remove the lightdm symlinks for one runlevel. Easy way: install sysv-rc-conf, run it and remove the check mark from lightdm for runlevel 3. (arrows, space bar and q to quit). Then in a root terminal, just run

init 3

to get to multi-user without graphical environment. 

To restart lightdm:

init 2

#2099 Re: Installation » SOLVED - chroot live build - kernel panic » 2018-05-02 11:11:44

cp /boot/initrd.img-4.14-whatever .
mkdir extracted
cd extracted
zcat ../initrd.img-blah  | cpio -i

Then examine the files in conf/conf.d/. Look for something that has a wrong uuid or device name.

When you install a newer kernel, it takes over the symlinks, /vmlinuz and /initrd.img, which will be used by refractasnapshot. It copies them to  work/iso/live. The usual procedure is to install the new kernel first, then remove the old kernel. There are two reasons for doing it in this order: 1. Usually, the old kernel is running when you do this, so you can't remove it until you boot into the new kernel. 2. In case the new kenel doesn't work, you can still boot the old one. Since you're doing this in a chroot, it shouldn't matter.

If you want more than one kernel in the iso, you need to copy it to the same place with a different name, and you need to make a boot entry for it. Make sure you have set save_work=yes in the config file.

#2100 Re: Other Issues » A couple of issues apt-file and sudo » 2018-05-01 11:59:21

apt-file works for me in ascii, using pkgmaster.devuan.org or deb.devuan.org.

Did you run apt-file update?

Board footer

Forum Software