[SOLVED] Requests for -current (20151216)

dugan · 01-04-2016, 11:40 AM

Quote:

Originally Posted by jostber

The vim package with ruby and clipboard included would be great.

Clipboard support would add an X dependency, and there's a comment in the SlackBuild about why Ruby support isn't enabled.

Personally, I replaced vim with neovim and I'm never going back.

ReaperX7 · 01-04-2016, 02:23 PM

Quote:

Originally Posted by Didier Spaier

In your post #87 you do not say against which source archive are your patches. It seems that you are referring to the source archive http://http.debian.net/debian/pool/m...a2.orig.tar.xz but it would be better to state that explicitly.

Also, this archive is part of Debian source package bundles like this one for Stretch: https://packages.debian.org/source/stretch/grub2

But this bundle contains also a lot of Debian patches in http://http.debian.net/debian/pool/m....debian.tar.xz

Code:

/tmp/grub_debian/debian/patches$ ls | wc -l
90

So my guess is that if Pat would consider using this grub "version" he would check all these patches to see which are worthwhile for Slackware and also possibly tweak all configuration made by Debian when packaging. Some work ahead

I assume that you have checked the patches grub_gpt_legacy_detection_btrfs.patch and grub_zfs-detection.patch against the aforementioned source tarball as they come from elsewhere (even though I do not see the point of the latter as there is no zfs in Slackware). FYI CVE-2015-8370.patch is shipped among the Debian patches.

Also, to really have an usable DejaVu Sans Mono pf2 font one need to run grub-mkfont with a DejaVu TTF font as source and check the exact full name of the output font (this will be done in Slackware Live).

Needless to say, as always I am only speaking on behalf of myself.

PS Slackel provides stuff allowing to configure and install grub as boot loader/boot manager, see http://www.slackel.gr/repo/source/extra/

Tracking this down, and this was what I got listed from ArchLinux's forums and help center.

This error https://bbs.archlinux.org/viewtopic.php?id=100027:

Code:

/sbin/grub-probe: error: cannot find a device for / (is /dev mounted?).

Will pop up when using BtrFS as root on a GPT partitioned system.

And THANK GOD, I found the patch source!

Source URL:
https://bugs.launchpad.net/debian/+s...260/comments/3
https://launchpadlibrarian.net/36483...etection.patch

It does have to be reworked (which I did) for usage with grub-2.02~beta2 as the source patch was for Grub-2.00.

Um... the rest are just rehashing from the .gz compressed patches already used by Slackware in uncompressed states.

The ZFS patch can be ignored though. It only works if you have zfs-on-linux available, and honestly, it's not worth it.

However, I would first try the Grub-git upstream first before using the patches as they may have fixed a few things.

Didier Spaier · 01-04-2016, 02:45 PM

I didn't have "political correctness" in mind, just that to successfully apply a patch one have to know against which files. So my request was more a link to these files that the origin of the patches themselves.

EDIT:

Quote:

Originally Posted by ReaperX7

However, I would first try the Grub-git upstream first before using the patches as they may have fixed a few things.

if you can keep up with updates... Already three commits this year.

That's probably why Fedora chose to built against git _but_ with each patch referring to a precise index, as obviously needed in that case.

Still everything has to be carefully checked. For instance speaking about dejavu fonts I see in configure.ac lines 1591 sqq. after commit aa7bb4607bb799b2790ea008bcfd8d6ca0a6d752:

Code:

for ext in pcf pcf.gz bdf bdf.gz ttf ttf.gz; do
  for dir in . /usr/src /usr/share/fonts/X11/misc /usr/share/fonts/truetype/ttf-dejavu /usr/share/fonts/dejavu /usr/share/fonts/truetype; do
     if test -f "$dir/DejaVuSans.$ext"; then
       DJVU_FONT_SOURCE="$dir/DejaVuSans.$ext"
       break 2
     fi
  done
done

But the DejaVu fonts that we have in Slackware are all in /usr/share/fonts/TTF thus would not been found by configure.ac as is...

ReaperX7 · 01-04-2016, 06:03 PM

Quote:

Originally Posted by Didier Spaier

I didn't have "political correctness" in mind, just that to successfully apply a patch one have to know against which files. So my request was more a link to these files that the origin of the patches themselves.

EDIT:if you can keep up with updates... Already three commits this year.

That's probably why Fedora chose to built against git _but_ with each patch referring to a precise index, as obviously needed in that case.

Still everything has to be carefully checked. For instance speaking about dejavu fonts I see in configure.ac lines 1591 sqq. after commit aa7bb4607bb799b2790ea008bcfd8d6ca0a6d752:

Code:

for ext in pcf pcf.gz bdf bdf.gz ttf ttf.gz; do
  for dir in . /usr/src /usr/share/fonts/X11/misc /usr/share/fonts/truetype/ttf-dejavu /usr/share/fonts/dejavu /usr/share/fonts/truetype; do
     if test -f "$dir/DejaVuSans.$ext"; then
       DJVU_FONT_SOURCE="$dir/DejaVuSans.$ext"
       break 2
     fi
  done
done

But the DejaVu fonts that we have in Slackware are all in /usr/share/fonts/TTF thus would not been found by configure.ac as is...

Yeah hence why I tried to not use Grub-git in the first place, and referenced it only. At least 2.02~beta2 is an actual release (latest known) and it's been out long enough to write patches for correctly. If Grub-git was used, and this is a rough recommendation only, an in-house git pulled and dated tarball would be required, and I doubt that's good practice.

Anywhos, I "think" the raw patch from the link (minus the reworking I did on Slackworks) "might" work on Grub-2.00, but here I'm firing a gun into a blacked out room at a target only 2 inches wide placed at a random location. Suggestion, do so at your own risk.

There are other patches as well possibly for 2.02~beta2, but I'm not certain how useful they'd be, if any since I only tested the known Slackware available patches and the btrfs-detection patch myself, but it got my system working so I can't complain.

As far as ZFS goes, I did more digging and the only thing I know of is some serious hack-fu used by the zfs-on-linux project for their in-house Grub implementation. So yeah, that's a end to that topic.

vigi · 01-05-2016, 03:51 PM

I was wondering if the current slackware n curve installation procedure, could be improved by installing the boot loader earlier in the process? Currently lilo is installed as the final step, and if a mistake is made you have to start the installation from scratch again.
Would it be possible to load the essential modules and the boot loader earlier with a confirmation step, so one knows they have a bookable PC before continuing?

Didier Spaier · 01-05-2016, 04:05 PM

Quote:

Originally Posted by vigi

I was wondering if the current slackware n curve installation procedure, could be improved by installing the boot loader earlier in the process? Currently lilo is installed as the final step, and if a mistake is made you have to start the installation from scratch again.
Would it be possible to load the essential modules and the boot loader earlier with a confirmation step, so one knows they have a bookable PC before continuing?

I do not think that be necessary as you can restart the installation, possibly skipping already performed steps, and if you only miss the boot loader use the DVD installer to start the installed system (as explained in the first script) and then configure and install lilo, either manually or running "liloconfig".

Just be careful if you restart the installer: at the TARGET step indicate on which partition root (/) should be mounted but of course do _not_ format that partition else you would have to redo the installation completely. Then you will have to indicate the SOURCE of packages again but you can skip installing packages if that's done (just click Cancel at the INSTALL step).

ReaperX7 · 01-06-2016, 01:03 AM

What about selecting which bootloader you'd like to use rather than just LILO?

bartgymnast · 01-06-2016, 01:58 AM

I switched to Grub a while ago.
It would be nice to have the installer have you select the bootloader.
something like this.

1. Install LILO as bootloader
2. Install ELILO as bootloader
3. Install Grub as bootloader
4. SKIPP installing a bootloader

Also the current script is confusing.

first the option, LILO and skip, when skipping you get the option ELILO and skip

ReaperX7 · 01-06-2016, 05:17 AM

Options could extend to extlinux/syslinux also.

Didier Spaier · 01-06-2016, 05:37 AM

Why exclude rEFInd, gummiboot (or its fork goofiboot, used by Solus), grub legacy and the kernel's EFI stub loader?

Implementation is left to the reader as an exercise

That being said Slackel does propose the choice between e(lilo) and grub when user wants to install once the Openbox Live image is loaded, so anyone is allowed to customize the Slackware installer to fit ones need.

Whether Pat is ready to accept these changes in genuine Slackware is another story, of course. I wouldn't bet a beer on that...

ReaperX7 · 01-06-2016, 05:45 AM

Grub-legacy isn't pre-installed like syslinux, grub, lilo, and elilo are.

Any pre-installed bootloader would be available depending on the system, and lists for UEFI and BIOS would be ideal, however, as mentioned the bootloaders would have to be preinstalled by the system to be on that list.

Didier Spaier · 01-06-2016, 06:20 AM

In case someone didn't get me, what I really meant is "asking is easy".

Nille_kungen · 01-06-2016, 06:22 AM

LLVM 3.7.1 This release contains bug-fixes for the LLVM 3.7.0 release.
Note that this release is *not* API and ABI compatible with 3.7.0.
This is due to a change in the C API in order to restore ABI/API compatible of the C
API with 3.6.x and 3.8.x.
http://lists.llvm.org/pipermail/llvm...ry/000066.html

MarcT · 01-06-2016, 08:46 AM

A DLNA media server would be good.

I've been using "coherence" http://coherence-project.org/ Python based DLNA server for a while now (to stream audio to my hifi).
It was a pain to make work in 14.1 (due to multiple dependencies) and I'm not looking forward to having that battle again. It also hasn't had much maintenance in the last few years.

Other suggestions welcome (even if they don't make it into -current).

Alien Bob · 01-06-2016, 10:07 AM

Quote:

Originally Posted by MarcT

A DLNA media server would be good.

I've been using "coherence" http://coherence-project.org/ Python based DLNA server for a while now (to stream audio to my hifi).
It was a pain to make work in 14.1 (due to multiple dependencies) and I'm not looking forward to having that battle again. It also hasn't had much maintenance in the last few years.

Other suggestions welcome (even if they don't make it into -current).

I struggled for a long time with minidlna and mediatomb, and those never worked well. Then I switched to Universal Media Server and stuck with that.
It works extremely well and it adds external subtitles to my movies transparently while watching.
All of it is written in Java and requires no compiling, just a little configuration for your specific media devices.