Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #191444 > unrolled thread
| Started by | Nicholas Geovanis <nickgeovanis@gmail.com> |
|---|---|
| First post | 2018-01-23 22:10 +0100 |
| Last post | 2018-01-25 23:40 +0100 |
| Articles | 20 on this page of 64 — 14 participants |
Back to article view | Back to linux.debian.user
Question on CVE-2017-5754 on Debian 8.9 Nicholas Geovanis <nickgeovanis@gmail.com> - 2018-01-23 22:10 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Sven Hartge <sven@svenhartge.de> - 2018-01-23 22:20 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Nicholas Geovanis <nickgeovanis@gmail.com> - 2018-01-23 22:40 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Sven Hartge <sven@svenhartge.de> - 2018-01-23 22:40 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-23 23:10 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-23 23:50 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Richard Hector <richard@walnut.gen.nz> - 2018-01-24 00:00 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Nicholas Geovanis <nickgeovanis@gmail.com> - 2018-01-24 00:10 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Jonathan Dowland <jmtd@debian.org> - 2018-01-24 11:20 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Nicholas Geovanis <nickgeovanis@gmail.com> - 2018-01-24 17:10 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Nicholas Geovanis <nickgeovanis@gmail.com> - 2018-01-24 19:20 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Nicholas Geovanis <nickgeovanis@gmail.com> - 2018-01-24 00:10 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Michael Stone <mstone@debian.org> - 2018-01-24 00:20 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Richard Hector <richard@walnut.gen.nz> - 2018-01-24 02:20 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-24 12:20 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-24 12:40 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-24 13:10 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-24 13:50 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Sven Hartge <sven@svenhartge.de> - 2018-01-24 14:10 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-24 14:30 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Sven Hartge <sven@svenhartge.de> - 2018-01-24 14:50 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Vincent Lefevre <vincent@vinc17.net> - 2018-01-24 15:20 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-24 15:40 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-24 17:10 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-24 17:30 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Greg Wooledge <wooledg@eeg.ccf.org> - 2018-01-24 17:30 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-24 18:10 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 The Wanderer <wanderer@fastmail.fm> - 2018-01-24 18:30 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Greg Wooledge <wooledg@eeg.ccf.org> - 2018-01-24 18:40 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-24 19:10 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-24 19:20 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-24 19:40 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-24 21:30 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Michael Lange <klappnase@freenet.de> - 2018-01-24 23:40 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-25 02:00 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-25 10:40 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Michael Lange <klappnase@freenet.de> - 2018-01-25 11:00 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-25 13:00 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-25 14:00 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Greg Wooledge <wooledg@eeg.ccf.org> - 2018-01-25 14:10 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-25 14:40 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-25 17:20 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Michael Lange <klappnase@freenet.de> - 2018-01-25 18:30 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-25 19:40 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-25 19:50 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Michael Lange <klappnase@freenet.de> - 2018-01-25 22:00 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Brian <ad44@cityscape.co.uk> - 2018-01-25 20:30 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-25 22:00 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-25 18:40 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Michael Lange <klappnase@freenet.de> - 2018-01-25 22:10 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-25 23:10 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-25 23:30 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-25 23:40 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Michael Lange <klappnase@freenet.de> - 2018-01-25 23:40 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-26 00:10 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Michael Lange <klappnase@freenet.de> - 2018-01-26 00:20 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Michael Fothergill <michael.fothergill@gmail.com> - 2018-01-24 18:30 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Vincent Lefevre <vincent@vinc17.net> - 2018-01-25 15:30 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Greg Wooledge <wooledg@eeg.ccf.org> - 2018-01-25 15:40 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 David Wright <deblis@lionunicorn.co.uk> - 2018-01-25 16:10 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Vincent Lefevre <vincent@vinc17.net> - 2018-01-25 23:20 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Jochen Spieker <ml@well-adjusted.de> - 2018-01-25 21:30 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Sven Joachim <svenjoac@gmx.de> - 2018-01-25 21:40 +0100
Re: Question on CVE-2017-5754 on Debian 8.9 Vincent Lefevre <vincent@vinc17.net> - 2018-01-25 23:40 +0100
Page 3 of 4 — ← Prev page 1 2 [3] 4 Next page →
| From | Michael Fothergill <michael.fothergill@gmail.com> |
|---|---|
| Date | 2018-01-25 14:40 +0100 |
| Message-ID | <vbPUZ-6zn-7@gated-at.bofh.it> |
| In reply to | #191527 |
[Multipart message — attachments visible in raw view] — view raw
On 25 January 2018 at 13:01, Greg Wooledge <wooledg@eeg.ccf.org> wrote: > On Thu, Jan 25, 2018 at 12:36:46PM +0000, Michael Fothergill wrote: > > If I become sid and install the kernel correctly, could I go back to > being > > just buster (sounds like an energy drink) and carry on using the new > kernel? > > No. > > It seems I have to become sid here. MF
[toc] | [prev] | [next] | [standalone]
| From | Michael Fothergill <michael.fothergill@gmail.com> |
|---|---|
| Date | 2018-01-25 17:20 +0100 |
| Message-ID | <vbSpQ-8dj-7@gated-at.bofh.it> |
| In reply to | #191528 |
[Multipart message — attachments visible in raw view] — view raw
On 25 January 2018 at 13:14, Michael Fothergill < michael.fothergill@gmail.com> wrote: > > > On 25 January 2018 at 13:01, Greg Wooledge <wooledg@eeg.ccf.org> wrote: > >> On Thu, Jan 25, 2018 at 12:36:46PM +0000, Michael Fothergill wrote: >> > If I become sid and install the kernel correctly, could I go back to >> being >> > just buster (sounds like an energy drink) and carry on using the new >> kernel? >> >> No. >> >> It seems I have to become sid here. > I have become sid and installed a ton of dependencies from the experimental respository and finally installed gcc 8. After some rehab I will study the web page on compiling kernels in debian. I need to get the set up to use the GCC 8 compiler I have just installed. Cheers MF > > > MF > > >
[toc] | [prev] | [next] | [standalone]
| From | Michael Lange <klappnase@freenet.de> |
|---|---|
| Date | 2018-01-25 18:30 +0100 |
| Message-ID | <vbTvz-nr-1@gated-at.bofh.it> |
| In reply to | #191538 |
On Thu, 25 Jan 2018 15:59:04 +0000 Michael Fothergill <michael.fothergill@gmail.com> wrote: > I have become sid and installed a ton of dependencies from the > experimental respository and finally installed gcc 8. Oh, from a quick glance it looked like half a dozen might suffice :-) > > After some rehab I will study the web page on compiling kernels in > debian. > > I need to get the set up to use the GCC 8 compiler I have just > installed. I have done this a lot lately (needed a custom kernel for a new laptop). Basically all I had to do was install make-kpkg + a number of other related packages. Once all that was in place I just had to pick a source tarball from kernel.org and unzip it, copy the latest config I had in /boot to linux-<version>/.config , then run # yes "" | make oldconfig from within the source-directory and then start compiling with something like # fakeroot make-kpkg --initrd --append-to-version=-<whateveryoulike> kernel-image kernel-headers The man page of make-kpkg gives hints about how to force a gcc version in its description paragraph, never tried this myself, though. Good luck!! Michael .-.. .. ...- . .-.. --- -. --. .- -. -.. .--. .-. --- ... .--. . .-. Computers make excellent and efficient servants, but I have no wish to serve under them. Captain, a starship also runs on loyalty to one man. And nothing can replace it or him. -- Spock, "The Ultimate Computer", stardate 4729.4
[toc] | [prev] | [next] | [standalone]
| From | Michael Fothergill <michael.fothergill@gmail.com> |
|---|---|
| Date | 2018-01-25 19:40 +0100 |
| Message-ID | <vbUBj-139-5@gated-at.bofh.it> |
| In reply to | #191539 |
[Multipart message — attachments visible in raw view] — view raw
On 25 January 2018 at 17:20, Michael Lange <klappnase@freenet.de> wrote: > On Thu, 25 Jan 2018 15:59:04 +0000 > Michael Fothergill <michael.fothergill@gmail.com> wrote: > > > I have become sid and installed a ton of dependencies from the > > experimental respository and finally installed gcc 8. > > Oh, from a quick glance it looked like half a dozen might suffice :-) > > > > > After some rehab I will study the web page on compiling kernels in > > debian. > > > > I need to get the set up to use the GCC 8 compiler I have just > > installed. > > I have done this a lot lately (needed a custom kernel for a new laptop). > Basically all I had to do was install make-kpkg + a number of other > related packages. Once all that was in place I just had to pick a source > tarball from kernel.org and unzip it, copy the latest config I had > in /boot to linux-<version>/.config , then run > > # yes "" | make oldconfig > > from within the source-directory and then start compiling with > something like > > # fakeroot make-kpkg --initrd --append-to-version=-<whateveryoulike> > kernel-image kernel-headers > > The man page of make-kpkg gives hints about how to > force a gcc version in its description paragraph, never tried this > myself, though. > I installed the kernel-package thing and then looked at the make-kpkg man entry. I couldn't find the option talking about choosing the gcc version you mentioned - maybe the language was too coded for me. Also if I use this command: make ARCH=i386 defconfig should ARCH=amd64 or something be appropriate for me running my amd64 kaveri box here? Also is fakeroot installed by default or do I need to install it separately? Thanks for the hints here. MF > > Good luck!! > > Michael > > > .-.. .. ...- . .-.. --- -. --. .- -. -.. .--. .-. --- ... .--. . .-. > > Computers make excellent and efficient servants, but I have no wish to > serve under them. Captain, a starship also runs on loyalty to one > man. And nothing can replace it or him. > -- Spock, "The Ultimate Computer", stardate 4729.4 > >
[toc] | [prev] | [next] | [standalone]
| From | Michael Fothergill <michael.fothergill@gmail.com> |
|---|---|
| Date | 2018-01-25 19:50 +0100 |
| Message-ID | <vbUL0-171-9@gated-at.bofh.it> |
| In reply to | #191541 |
[Multipart message — attachments visible in raw view] — view raw
I have been looking at the web page here: https://wiki.debian.org/BuildADebianKernelPackage and noticed that the source file is supposed to be put in /usr/src it says. It thinks the file would have a format like this: *linux-source-x.x.tar.bz2* The file I downloaded from the kernel.org site looks like this: linux-4.14.15.tar.xz I think that is the same thing here (please correct me if I am wrong). It is currently sitting in my Downloads directory. I am going to move it to the /usr/src directory and then run the other commands. Cheers MF
[toc] | [prev] | [next] | [standalone]
| From | Michael Lange <klappnase@freenet.de> |
|---|---|
| Date | 2018-01-25 22:00 +0100 |
| Message-ID | <vbWMO-2ih-15@gated-at.bofh.it> |
| In reply to | #191542 |
Hi, On Thu, 25 Jan 2018 18:26:52 +0000 Michael Fothergill <michael.fothergill@gmail.com> wrote: > I have been looking at the web page here: > > https://wiki.debian.org/BuildADebianKernelPackage > > and noticed that the source file is supposed to be put in /usr/src it > says. > > It thinks the file would have a format like this: > > > > *linux-source-x.x.tar.bz2* > The file > I downloaded from the kernel.org site looks like this: > > > > linux-4.14.15.tar.xz > > I think that is the same thing here (please correct me if I am wrong). the tarball's format doesn't matter, you'll have to unpack it anyway :-) > > It is currently sitting in my Downloads directory. > > I am going to move it to the /usr/src directory and then run the other > commands. That doesn't matter either, I have done this from somewhere in ~/ , I guess /usr/src is just a recommendation where the sources belong. Maybe you'll need it there if you compile 3rd party modules or something, not sure about that. > I couldn't find the option talking about choosing the gcc version you > mentioned - maybe the language was too coded for me. It's right at the start of the man page, paragraph "DESCRIPTION": " Also, please note that some versions of gcc do not interact well with the kernel sources (gcc 2.95 has problems compiling the kernel without the flag '-fno-strict-aliasing'. This issue has been taken care of for recent kernels (2.2 and 2.4 series are fine) (I think you may have to edit the makefile for older kernels, or something). You may control which version of gcc used in kernel compilation by setting the Makefile variables CC and HOSTCC in the top level kernel Makefile. You can do this simply by setting the environment variable MAKEFLAGS. To observe, try: % KBUILD_VERBOSE=1 MAKEFLAGS="CC=gcc-4.4" make-kpkg configure " > > Also > > if I use this command: > > make ARCH=i386 defconfig > > should ARCH=amd64 or something be appropriate for me running my amd64 > kaveri box here? I never explicitely defined ARCH, I guess you only need to do so if you e.g. want to compile an i386 kernel on an amd64 machine or vice versa. > > Also is fakeroot installed by default or do I need to install it > separately? That's a separate package. Regards Michael .-.. .. ...- . .-.. --- -. --. .- -. -.. .--. .-. --- ... .--. . .-. Where there's no emotion, there's no motive for violence. -- Spock, "Dagger of the Mind", stardate 2715.1
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2018-01-25 20:30 +0100 |
| Message-ID | <vbVnH-1yq-1@gated-at.bofh.it> |
| In reply to | #191541 |
On Thu 25 Jan 2018 at 18:15:29 +0000, Michael Fothergill wrote: > Also is fakeroot installed by default or do I need to install it > separately? apt show fakeroot | grep -i priority What do you think? > Thanks for the hints here. Where are we going? It seems a long time getting there. :) -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | Michael Fothergill <michael.fothergill@gmail.com> |
|---|---|
| Date | 2018-01-25 22:00 +0100 |
| Message-ID | <vbWMN-2ih-11@gated-at.bofh.it> |
| In reply to | #191543 |
[Multipart message — attachments visible in raw view] — view raw
On 25 January 2018 at 19:25, Brian <ad44@cityscape.co.uk> wrote: > On Thu 25 Jan 2018 at 18:15:29 +0000, Michael Fothergill wrote: > > > Also is fakeroot installed by default or do I need to install it > > separately? > > apt show fakeroot | grep -i priority > > What do you think? > > > Thanks for the hints here. > > Where are we going? It seems a long time getting there. :) > It's OK. I ran apt show fakeroot | grep -i priority and got: root@mikef-PC:/usr/src# apt show fakeroot | grep -i priority WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Priority: optional root@mikef-PC:/usr/src# Also I put the kernel file in /usr/src and then ran the following: tar -xaf linux-4.14.15.tar.xz It seemed to run OK but I don't know where it put the unpacked files. The creation dates show etc they are not in the /usr/src directory or in a new directory created in it. Some docs say you shouldn't put the src files in the src directory - but others do. Bit odd. Comments appreciated. Regards MF -- > Brian. > >
[toc] | [prev] | [next] | [standalone]
| From | Michael Fothergill <michael.fothergill@gmail.com> |
|---|---|
| Date | 2018-01-25 18:40 +0100 |
| Message-ID | <vbTFg-rP-9@gated-at.bofh.it> |
| In reply to | #191538 |
[Multipart message — attachments visible in raw view] — view raw
On 25 January 2018 at 15:59, Michael Fothergill < michael.fothergill@gmail.com> wrote: > > > On 25 January 2018 at 13:14, Michael Fothergill < > michael.fothergill@gmail.com> wrote: > >> >> >> On 25 January 2018 at 13:01, Greg Wooledge <wooledg@eeg.ccf.org> wrote: >> >>> On Thu, Jan 25, 2018 at 12:36:46PM +0000, Michael Fothergill wrote: >>> > If I become sid and install the kernel correctly, could I go back to >>> being >>> > just buster (sounds like an energy drink) and carry on using the new >>> kernel? >>> >>> No. >>> >>> It seems I have to become sid here. >> > > I have become sid and installed a ton of dependencies from the > experimental respository and finally installed gcc 8. > > After some rehab I will study the web page on compiling kernels in debian. > > I need to get the set up to use the GCC 8 compiler I have just installed. > > Cheers > > MF > OK, I went through the dependency detox program (and had some electrodes hooked up to my ears etc) and made a good recovery. I looked at some web pages on the debian way of compiling kernels etc. My general strategy is as follows: 1. Download the latest stable kernel from the kernel archives; this is 4.14.15 - I have done this. 2. Use the tar xf /usr/src/linux-source-4.14.15.tar.xz command to unpack the kernel source file. 3. cd to the directory where the kernel source lives 4. Reuse the config file from the 4.14.15 rc8 kernel I already have installed e.g. cp /boot/config-3.16.0-4-amd64 ~/kernel/linux-source-3.16/.config 5. run make menuconfig (I do this in gentoo) I will make sure libncurses5-dev (or does it need to be newer?) is installed to configure it using the recycled config file from 4 above. 6. Run make-kpkg clean. 7. Then run fakeroot make-kpkg --initrd --revision=1.0.custom kernel_image. 8. Then install the kernel as follows: dpkg -i ../linux-image-4.14.15-subarchitecture_1.0.custom_i386.deb. 9. Reboot and look for new kernel in grub menu and log in. 10. Run the patch checker to see that KPTI and retpoline patched are turned on properly. Please critique the above list. I am going to read more documentation and improve it before going ahead with this. Cheers MF > > > >> >> >> MF >> >> >> >
[toc] | [prev] | [next] | [standalone]
| From | Michael Lange <klappnase@freenet.de> |
|---|---|
| Date | 2018-01-25 22:10 +0100 |
| Message-ID | <vbWWt-2AP-9@gated-at.bofh.it> |
| In reply to | #191540 |
On Thu, 25 Jan 2018 17:12:48 +0000 Michael Fothergill <michael.fothergill@gmail.com> wrote: > My general strategy is as follows: > > 1. Download the latest stable kernel from the kernel archives; this is > 4.14.15 - I have done this. Not sure, but didn't you want the very latest 4.15rc for some Meltdown/Spectre issues? Are these also in 4.14.15? > > 2. Use the tar xf /usr/src/linux-source-4.14.15.tar.xz command to > unpack the kernel source file. > > 3. cd to the directory where the kernel source lives > > 4. Reuse the config file from the 4.14.15 rc8 kernel I already have > installed e.g. cp /boot/config-3.16.0-4-amd64 > ~/kernel/linux-source-3.16/.config > > 5. run make menuconfig (I do this in gentoo) I will make sure > libncurses5-dev (or does it need to be newer?) is installed to > configure it using the recycled config file from 4 above. This shouldn't be necessary, unless you want to enable something that's turned off by default. That 'yes "" | make oldconfig' thing worked well here and is surely faster :) > > 6. Run make-kpkg clean. > > 7. Then run fakeroot make-kpkg --initrd --revision=1.0.custom > kernel_image. > > 8. Then install the kernel as follows: dpkg -i > ../linux-image-4.14.15-subarchitecture_1.0.custom_i386.deb. > > 9. Reboot and look for new kernel in grub menu and log in. > > 10. Run the patch checker to see that KPTI and retpoline patched are > turned on properly. > > Please critique the above list. I am going to read more documentation > and improve it before going ahead with this. Regards Michael .-.. .. ...- . .-.. --- -. --. .- -. -.. .--. .-. --- ... .--. . .-. It would be illogical to assume that all conditions remain stable. -- Spock, "The Enterprise Incident", stardate 5027.3
[toc] | [prev] | [next] | [standalone]
| From | Michael Fothergill <michael.fothergill@gmail.com> |
|---|---|
| Date | 2018-01-25 23:10 +0100 |
| Message-ID | <vbXSz-3dW-43@gated-at.bofh.it> |
| In reply to | #191559 |
[Multipart message — attachments visible in raw view] — view raw
> Not sure, but didn't you want the very latest 4.15rc for some
> Meltdown/Spectre issues? Are these also in 4.14.15?
>
>
>
I copied the config file from the boot directory for the current 4.15.0
rc8 kernel as .config.
I then ran make menuconfig and then realised I didn't need to change
anything and exited.
I didn't run your
yes ""| make oldconfig thing - it seemed a bit peculiar to me.
Maybe I should have.
Instead I ran the command recommended here:
https://wiki.debian.org/BuildADebianKernelPackage
which was
make ARCH=i386 defconfig
I then ran
make-kpkg
and it then asked me lots of questions concerning kernel options that I had
to answer interactively.
I think I should have tried your funny quotation pipe command with the
oldconfig option - it would have been better.
Here is some of the output before it crashed:
kexec system call (KEXEC) [Y/n/?] y
kexec file based system call (KEXEC_FILE) [N/y/?] n
kernel crash dumps (CRASH_DUMP) [Y/n/?] y
kexec jump (KEXEC_JUMP) [N/y/?] n
Physical address where the kernel is loaded (PHYSICAL_START) [0x1000000]
0x1000000
Build a relocatable kernel (RELOCATABLE) [Y/n/?] y
Randomize the address of the kernel image (KASLR) (RANDOMIZE_BASE)
[Y/n/?] y
Alignment value to which kernel should be aligned (PHYSICAL_ALIGN)
[0x200000] 0x200000
Randomize the kernel memory sections (RANDOMIZE_MEMORY) [Y/n/?] y
Support for hot-pluggable CPUs (HOTPLUG_CPU) [Y/?] y
Set default setting of cpu0_hotpluggable (BOOTPARAM_HOTPLUG_CPU0) [N/y/?]
n
Debug CPU0 hotplug (DEBUG_HOTPLUG_CPU0) [N/y/?] n
vsyscall table for legacy applications
1. Native (LEGACY_VSYSCALL_NATIVE)
> 2. Emulate (LEGACY_VSYSCALL_EMULATE)
3. None (LEGACY_VSYSCALL_NONE)
choice[1-3?]: 2
Built-in kernel command line (CMDLINE_BOOL) [N/y/?] n
#
# configuration written to .config
#
make[2]: Leaving directory '/usr/src/linux-4.14.15'
make \
ARCH=x86_64 dep
make[2]: Entering directory '/usr/src/linux-4.14.15'
Makefile:942: *** "Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y,
please install libelf-dev, libelf-devel or elfutils-libelf-devel". Stop.
make[2]: Leaving directory '/usr/src/linux-4.14.15'
debian/ruleset/targets/common.mk:194: recipe for target
'debian/stamp/conf/kernel-conf' failed
make[1]: *** [debian/stamp/conf/kernel-conf] Error 2
make[1]: Leaving directory '/usr/src/linux-4.14.15'
/usr/share/kernel-package/ruleset/minimal.mk:93: recipe for target
'debian/stamp/conf/minimal_debian' failed
make: *** [debian/stamp/conf/minimal_debian] Error 2
Failed to create a ./debian directory: at /usr/bin/make-kpkg line 970.
root@mikef-PC:/usr/src/linux-4.14.15#
It has written things to the config file so I think I might be wise to
delete it, copy it over again
and repeat everything with the Shakespearian pipe command next time.
Suggestions on recovering gracefully here are welcome.
Regards
MF
>
>
>
>
>
>
> .-.. .. ...- . .-.. --- -. --. .- -. -.. .--. .-. --- ... .--. . .-.
>
> It would be illogical to assume that all conditions remain stable.
> -- Spock, "The Enterprise Incident", stardate 5027.3
>
>
[toc] | [prev] | [next] | [standalone]
| From | Michael Fothergill <michael.fothergill@gmail.com> |
|---|---|
| Date | 2018-01-25 23:30 +0100 |
| Message-ID | <vbYbU-3kL-5@gated-at.bofh.it> |
| In reply to | #191562 |
[Multipart message — attachments visible in raw view] — view raw
Dear All, I ran it again after deleting the .config file, copy the one /boot over again and running the yes """| oldconfig command and makekpkg and it ran and crashed again: https://pastebin.com/GJkEMVvc Should I have run make clean or something before repeating everything? Regards MF
[toc] | [prev] | [next] | [standalone]
| From | Michael Fothergill <michael.fothergill@gmail.com> |
|---|---|
| Date | 2018-01-25 23:40 +0100 |
| Message-ID | <vbYlB-3o7-39@gated-at.bofh.it> |
| In reply to | #191565 |
[Multipart message — attachments visible in raw view] — view raw
On 25 January 2018 at 22:04, Michael Fothergill < michael.fothergill@gmail.com> wrote: > Dear All, > > I ran it again after deleting the .config file, copy the one /boot over > again > and running the yes """| oldconfig command and makekpkg > > and it ran and crashed again: > > https://pastebin.com/GJkEMVvc > > > Should I have run make clean or something before repeating everything? > > Regards > > MF > Dear All, I am going to carry on with this discussion in a new post on kernel compilation. Thanks MF
[toc] | [prev] | [next] | [standalone]
| From | Michael Lange <klappnase@freenet.de> |
|---|---|
| Date | 2018-01-25 23:40 +0100 |
| Message-ID | <vbYlB-3o7-27@gated-at.bofh.it> |
| In reply to | #191562 |
Hi, On Thu, 25 Jan 2018 21:43:19 +0000 Michael Fothergill <michael.fothergill@gmail.com> wrote: > > Not sure, but didn't you want the very latest 4.15rc for some > > Meltdown/Spectre issues? Are these also in 4.14.15? > > > > > > > > I copied the config file from the boot directory for the current 4.15.0 > rc8 kernel as .config. > > I then ran make menuconfig and then realised I didn't need to change > anything and exited. > > I didn't run your > > yes ""| make oldconfig thing - it seemed a bit peculiar to me. > > Maybe I should have. > > Instead I ran the command recommended here: > > https://wiki.debian.org/BuildADebianKernelPackage > > which was > > make ARCH=i386 defconfig Didn't want to build for amd64? If yes, you should have followed the advice from that page saying: "Create a defconfig with the following command, please change ARCH=i386 to match your target architecture:" I only built kernel packages for amd64 on an amd64 system, so I never had to explicitely specify ARCH. > > I then ran > > make-kpkg > > and it then asked me lots of questions concerning kernel options that I > had to answer interactively. > > I think I should have tried your funny quotation pipe command with the > oldconfig option - it would have been better. Actually I don't remember which tutorial I borrowed this from; as far as I know it will set the default values for any new option not present in the old config. > > > > Here is some of the output before it crashed: > > > > kexec system call (KEXEC) [Y/n/?] y > kexec file based system call (KEXEC_FILE) [N/y/?] n > kernel crash dumps (CRASH_DUMP) [Y/n/?] y > kexec jump (KEXEC_JUMP) [N/y/?] n > Physical address where the kernel is loaded (PHYSICAL_START) [0x1000000] > 0x1000000 > Build a relocatable kernel (RELOCATABLE) [Y/n/?] y > Randomize the address of the kernel image (KASLR) (RANDOMIZE_BASE) > [Y/n/?] y > Alignment value to which kernel should be aligned (PHYSICAL_ALIGN) > [0x200000] 0x200000 > Randomize the kernel memory sections (RANDOMIZE_MEMORY) [Y/n/?] y > Support for hot-pluggable CPUs (HOTPLUG_CPU) [Y/?] y > Set default setting of cpu0_hotpluggable (BOOTPARAM_HOTPLUG_CPU0) > [N/y/?] n > Debug CPU0 hotplug (DEBUG_HOTPLUG_CPU0) [N/y/?] n > vsyscall table for legacy applications > 1. Native (LEGACY_VSYSCALL_NATIVE) > > 2. Emulate (LEGACY_VSYSCALL_EMULATE) > 3. None (LEGACY_VSYSCALL_NONE) > choice[1-3?]: 2 > Built-in kernel command line (CMDLINE_BOOL) [N/y/?] n > # > # configuration written to .config > # > make[2]: Leaving directory '/usr/src/linux-4.14.15' > make \ > ARCH=x86_64 dep > make[2]: Entering directory '/usr/src/linux-4.14.15' > Makefile:942: *** "Cannot generate ORC metadata for > CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or > elfutils-libelf-devel". Stop. make[2]: Leaving directory > '/usr/src/linux-4.14.15' debian/ruleset/targets/common.mk:194: recipe > for target 'debian/stamp/conf/kernel-conf' failed > make[1]: *** [debian/stamp/conf/kernel-conf] Error 2 > make[1]: Leaving directory '/usr/src/linux-4.14.15' > /usr/share/kernel-package/ruleset/minimal.mk:93: recipe for target > 'debian/stamp/conf/minimal_debian' failed > make: *** [debian/stamp/conf/minimal_debian] Error 2 > Failed to create a ./debian directory: at /usr/bin/make-kpkg line 970. > root@mikef-PC:/usr/src/linux-4.14.15# Funny thing: just for the sport I tried the same thing on a siduction system this evening and ended up with the same error message. Had no time to investigate yet, it looks a bit like this one: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804813 but this one's old and claims to be solved. Here: http://forums.debian.net/viewtopic.php?t=74424 it is suggested that an upper case letter in the path to the sources might be the culprit, but then I have upper case characters here on stretch too, which didn't harm. Here: http://forums.debian.net/viewtopic.php?t=116146 it is suggested that installing gcc-<version>-plugin-dev might help, might be worth a try. However here on stretch nothing like this is installed, and still it works. Maybe libgcc-<version>-dev is missing? Here: https://superuser.com/questions/677372/error-when-compiling-linux-kernel someone suggests that bc must be installed. Got that here on stretch, not sure if it might be missing on siduction. > > > It has written things to the config file so I think I might be wise to > delete it, copy it over again > and repeat everything with the Shakespearian pipe command next time. > > > > Suggestions on recovering gracefully here are welcome. I always cleaned up the source directory with # make mrproper After that you should be able to start over again. Regards Michael .-.. .. ...- . .-.. --- -. --. .- -. -.. .--. .-. --- ... .--. . .-. Earth -- mother of the most beautiful women in the universe. -- Apollo, "Who Mourns for Adonais?" stardate 3468.1
[toc] | [prev] | [next] | [standalone]
| From | Michael Fothergill <michael.fothergill@gmail.com> |
|---|---|
| Date | 2018-01-26 00:10 +0100 |
| Message-ID | <vbYOB-3MC-1@gated-at.bofh.it> |
| In reply to | #191567 |
[Multipart message — attachments visible in raw view] — view raw
On 25 January 2018 at 22:35, Michael Lange <klappnase@freenet.de> wrote: > Hi, > > On Thu, 25 Jan 2018 21:43:19 +0000 > Michael Fothergill <michael.fothergill@gmail.com> wrote: > > > > Not sure, but didn't you want the very latest 4.15rc for some > > > Meltdown/Spectre issues? Are these also in 4.14.15? > > > > > > > > > > > > > I copied the config file from the boot directory for the current 4.15.0 > > rc8 kernel as .config. > > > > I then ran make menuconfig and then realised I didn't need to change > > anything and exited. > > > > I didn't run your > > > > yes ""| make oldconfig thing - it seemed a bit peculiar to me. > > > > Maybe I should have. > > > > Instead I ran the command recommended here: > > > > https://wiki.debian.org/BuildADebianKernelPackage > > > > which was > > > > make ARCH=i386 defconfig > > Didn't want to build for amd64? If yes, you should have followed the > advice from that page saying: > "Create a defconfig with the following command, please change ARCH=i386 > to match your target architecture:" > I only built kernel packages for amd64 on an amd64 system, so I never had > to explicitely specify ARCH. > Should it not be ARCH =x86-64 rather than amd64. It is so confusing. MF > > > > > I then ran > > > > make-kpkg > > > > and it then asked me lots of questions concerning kernel options that I > > had to answer interactively. > > > > I think I should have tried your funny quotation pipe command with the > > oldconfig option - it would have been better. > > Actually I don't remember which tutorial I borrowed this from; as far as > I know it will set the default values for any new option not present in > the old config. > > > > > > > > > Here is some of the output before it crashed: > > > > > > > > kexec system call (KEXEC) [Y/n/?] y > > kexec file based system call (KEXEC_FILE) [N/y/?] n > > kernel crash dumps (CRASH_DUMP) [Y/n/?] y > > kexec jump (KEXEC_JUMP) [N/y/?] n > > Physical address where the kernel is loaded (PHYSICAL_START) [0x1000000] > > 0x1000000 > > Build a relocatable kernel (RELOCATABLE) [Y/n/?] y > > Randomize the address of the kernel image (KASLR) (RANDOMIZE_BASE) > > [Y/n/?] y > > Alignment value to which kernel should be aligned (PHYSICAL_ALIGN) > > [0x200000] 0x200000 > > Randomize the kernel memory sections (RANDOMIZE_MEMORY) [Y/n/?] y > > Support for hot-pluggable CPUs (HOTPLUG_CPU) [Y/?] y > > Set default setting of cpu0_hotpluggable (BOOTPARAM_HOTPLUG_CPU0) > > [N/y/?] n > > Debug CPU0 hotplug (DEBUG_HOTPLUG_CPU0) [N/y/?] n > > vsyscall table for legacy applications > > 1. Native (LEGACY_VSYSCALL_NATIVE) > > > 2. Emulate (LEGACY_VSYSCALL_EMULATE) > > 3. None (LEGACY_VSYSCALL_NONE) > > choice[1-3?]: 2 > > Built-in kernel command line (CMDLINE_BOOL) [N/y/?] n > > # > > # configuration written to .config > > # > > make[2]: Leaving directory '/usr/src/linux-4.14.15' > > make \ > > ARCH=x86_64 dep > > make[2]: Entering directory '/usr/src/linux-4.14.15' > > Makefile:942: *** "Cannot generate ORC metadata for > > CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or > > elfutils-libelf-devel". Stop. make[2]: Leaving directory > > '/usr/src/linux-4.14.15' debian/ruleset/targets/common.mk:194: recipe > > for target 'debian/stamp/conf/kernel-conf' failed > > make[1]: *** [debian/stamp/conf/kernel-conf] Error 2 > > make[1]: Leaving directory '/usr/src/linux-4.14.15' > > /usr/share/kernel-package/ruleset/minimal.mk:93: recipe for target > > 'debian/stamp/conf/minimal_debian' failed > > make: *** [debian/stamp/conf/minimal_debian] Error 2 > > Failed to create a ./debian directory: at /usr/bin/make-kpkg line 970. > > root@mikef-PC:/usr/src/linux-4.14.15# > > Funny thing: just for the sport I tried the same thing on a siduction > system this evening and ended up with the same error message. > Had no time to investigate yet, it looks a bit like this one: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804813 > > but this one's old and claims to be solved. > Here: > http://forums.debian.net/viewtopic.php?t=74424 > it is suggested that an upper case letter in the path to the sources > might be the culprit, but then I have upper case characters here on > stretch too, which didn't harm. > Here: > http://forums.debian.net/viewtopic.php?t=116146 > it is suggested that installing gcc-<version>-plugin-dev might help, > might be worth a try. However here on stretch nothing like this is > installed, and still it works. Maybe libgcc-<version>-dev is missing? > Here: > https://superuser.com/questions/677372/error-when-compiling-linux-kernel > someone suggests that bc must be installed. Got that here on stretch, not > sure if it might be missing on siduction. > > > > > > > It has written things to the config file so I think I might be wise to > > delete it, copy it over again > > and repeat everything with the Shakespearian pipe command next time. > > > > > > > > Suggestions on recovering gracefully here are welcome. > > I always cleaned up the source directory with > > # make mrproper > > After that you should be able to start over again. > > Regards > > Michael > > .-.. .. ...- . .-.. --- -. --. .- -. -.. .--. .-. --- ... .--. . .-. > > Earth -- mother of the most beautiful women in the universe. > -- Apollo, "Who Mourns for Adonais?" stardate 3468.1 > >
[toc] | [prev] | [next] | [standalone]
| From | Michael Lange <klappnase@freenet.de> |
|---|---|
| Date | 2018-01-26 00:20 +0100 |
| Message-ID | <vbYYh-3Q0-3@gated-at.bofh.it> |
| In reply to | #191570 |
Hi,
On Thu, 25 Jan 2018 22:43:57 +0000
Michael Fothergill <michael.fothergill@gmail.com> wrote:
> Should it not be ARCH =x86-64 rather than amd64.
>
> It is so confusing.
Hmm, to be honest, I don't know. As I said, if you build for amd64 on an
amd64 system, you don't need to care about that, the current system's
architecture is the default.
And fyi, meanwhile I couldn't stop myself from booting siduction once
more. Installing one package or other taht people in archived mailing
lists suggested didn't help. Removing upper case characters from the path
neither. Then I tried and removed my clumsy attempts to force the use of
gcc-8 and found that with gcc-7 everything appears to work fine.
A closer look at what I am doing revealed that even the simple
'yes ""| make oldconfig' threw errors when using gcc-8. Seems like there
is a non-trivial problem here. The error message about the
missing /debian directory seems misleading, actually here there was some
C-code snippet underlined in red (printed just above that error message)
which I assume is likely the real problem. Maybe the best bet is to wait
until gcc-7.3 arrives in testing.
Regards
Michael
.-.. .. ...- . .-.. --- -. --. .- -. -.. .--. .-. --- ... .--. . .-.
A man either lives life as it happens to him, meets it head-on and
licks it, or he turns his back on it and starts to wither away.
-- Dr. Boyce, "The Menagerie" ("The Cage"), stardate
unknown
[toc] | [prev] | [next] | [standalone]
| From | Michael Fothergill <michael.fothergill@gmail.com> |
|---|---|
| Date | 2018-01-24 18:30 +0100 |
| Message-ID | <vbx21-2CG-9@gated-at.bofh.it> |
| In reply to | #191490 |
[Multipart message — attachments visible in raw view] — view raw
On 24 January 2018 at 16:19, Greg Wooledge <wooledg@eeg.ccf.org> wrote: > On Wed, Jan 24, 2018 at 03:49:08PM +0000, Michael Fothergill wrote: > > If you can be sid and experimental together then I guess [...] > > Experimental is not a release. You can't "be experimental". It is > merely a place where individual packages are uploaded, when they are > considered "not ready to be in unstable yet". > > Typically the package maintainer EXPECTS these packages to have bugs, > and wants focused help from people who are familiar with the package > to find and squish them. Or, the package may be uploaded in a "known > broken" condition because it could still be useful in highly specialized > circumstances, where the new features outweigh the known bugs. > > The packages in experimental do NOT automatically migrate into unstable > or testing. They are not part of the normal package lifecycle. > > To use a package from experimental, you must download it directly, and > install it directly. You don't use apt or its cousins, unless it's > to backfill dependencies (apt-get -f install) from your actual release. > Does that mean you use dpkg -i to ibstall it then? Cheers MF
[toc] | [prev] | [next] | [standalone]
| From | Vincent Lefevre <vincent@vinc17.net> |
|---|---|
| Date | 2018-01-25 15:30 +0100 |
| Message-ID | <vbQHn-74x-3@gated-at.bofh.it> |
| In reply to | #191490 |
On 2018-01-24 11:19:36 -0500, Greg Wooledge wrote: > To use a package from experimental, you must download it directly, and > install it directly. You don't use apt or its cousins, unless it's > to backfill dependencies (apt-get -f install) from your actual release. aptitude installs experimental packages automatically. -- Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Date | 2018-01-25 15:40 +0100 |
| Message-ID | <vbQR3-79g-9@gated-at.bofh.it> |
| In reply to | #191533 |
On Thu, Jan 25, 2018 at 03:24:21PM +0100, Vincent Lefevre wrote: > On 2018-01-24 11:19:36 -0500, Greg Wooledge wrote: > > To use a package from experimental, you must download it directly, and > > install it directly. You don't use apt or its cousins, unless it's > > to backfill dependencies (apt-get -f install) from your actual release. > > aptitude installs experimental packages automatically. It is terrifying. (Seriously, if you've configured it to do that, WHY?!? Do you hate your computer so much that you want it to die?)
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2018-01-25 16:10 +0100 |
| Message-ID | <vbRk5-7yR-1@gated-at.bofh.it> |
| In reply to | #191535 |
On Thu 25 Jan 2018 at 09:31:27 (-0500), Greg Wooledge wrote: > On Thu, Jan 25, 2018 at 03:24:21PM +0100, Vincent Lefevre wrote: > > On 2018-01-24 11:19:36 -0500, Greg Wooledge wrote: > > > To use a package from experimental, you must download it directly, and > > > install it directly. You don't use apt or its cousins, unless it's > > > to backfill dependencies (apt-get -f install) from your actual release. > > > > aptitude installs experimental packages automatically. > > It is terrifying. > > (Seriously, if you've configured it to do that, WHY?!? Do you hate > your computer so much that you want it to die?) Perhaps they haven't spotted the depository's symlink lrwxrwxrwx 1 1176 1176 12 Aug 04 2008 rc-buggy -> experimental Cheers, David.
[toc] | [prev] | [next] | [standalone]
Page 3 of 4 — ← Prev page 1 2 [3] 4 Next page →
Back to top | Article view | linux.debian.user
csiph-web