again thank you for explanations/clarifications.
have a good day, regards, lacsaP.
Le mar. 21 mars 2023 à 11:16, Genes Lists a écrit :
> On 3/21/23 04:26, lacsaP Patatetom wrote:
> > hi everybody,
>
> >
> > my development workstation is running 6.1.20-1-lts and I made
> >
On 3/21/23 04:26, lacsaP Patatetom wrote:
hi everybody,
my development workstation is running 6.1.20-1-lts and I made
linux-lts-ro-6.1.15-1-x86_64.pkg.tar.zst and
linux-lts-ro-headers-6.1.15-1-x86_64.pkg.tar.zst packages on it : if now
I want to compile on this development workstation
hi everybody,
if point #1 is now relatively clear to me (eg. out of tree kernel modules
need to recompile, otherwise it should work with few exceptions), point #2
is still pending.
so I rephrase my question hoping to find an answer ;-)
my development workstation is running 6.1.20-1-lts and I
lvm is a good one , bpftrace and other tools that might rely on kernel
hooks , or something specific module or statically compiled feature , but
as Ralf said , the vast majority of user land applications can be used
interchangeably with different kernels .
On Mon, 20 Mar 2023 at 11:59, lacsaP
thank you for your feedback Ralf which is in line with Genes' explanations.
the application that could fall into the mentioned category and that I am
paying attention to is lvm, but previous tests show that this is not the
case (the lvm2 package provided by ArchLinux behaves as expected with the
On Mon, 2023-03-20 at 07:42 -0400, Genes Lists wrote:
>
> The kernel headers are used to compile out-of-tree kernel modules for
> that kernel. You should always install kernel and its companion
> headers file. While there may be cases where the headers are not
> actually changed and it may work
it's clear yes, thanks for these explanations/clarifications.
Le lun. 20 mars 2023 à 12:42, Genes Lists a écrit :
>
> >
> > if I understand correctly, I can install my package
> > linux-lts-perso-6.1.15-2-x86_64.pkg.tar.zst, boot on it (eg. "my"
> > kernel) and continue to use the binaries
On Mon, 2023-03-20 at 12:27 +0100, lacsaP Patatetom wrote:
> if I understand correctly, I can install my package linux-lts-perso-
> 6.1.15-2-x86_64.pkg.tar.zst, boot on it (eg. "my" kernel) and continue
> to use the binaries present on my system while they have not been
> compiled with its (new)
if I understand correctly, I can install my package
linux-lts-perso-6.1.15-2-x86_64.pkg.tar.zst, boot on it (eg. "my"
kernel) and continue to use the binaries present on my system while they
have not been compiled with its (new) headers and especially for the
binaries that call the
Le lun. 20 mars 2023 à 12:00, Genes Lists a écrit :
> On 3/20/23 06:44, lacsaP Patatetom wrote:
>
> Please don't top post on mailing lists.
>
I use GMail and just click on "Respond to all" : is this the "top post" ?
should I only answer you or not put you individually in the answer since
you
Hi,
I'm not sure if I understand what the OP tries to achieve.
I install "linux" and "linux-rt-lts" from repositories, but build
"linux-rt" myself. To keep different versions of "linux-rt 4.19, I add
an extension, "cornflower", "pussytoes" or "securityink". I misuse
pkgrel to inform me if
On Mon, 20 Mar 2023 at 11:00, Genes Lists wrote:
> On 3/20/23 06:44, lacsaP Patatetom wrote:
>
> Please don't top post on mailing lists.
>
>
> Honestly, my best advice to you is stop trying to build kernels.
>
>
Hmm the saying to give a person a fish feeds them for a day, teach them how
to fish
On 3/20/23 06:44, lacsaP Patatetom wrote:
Please don't top post on mailing lists.
I don't understand what 'problem' you are speaking of. All you've asked
is if you can install a kernel headers from a different build - the
general answer is "no" - don't ever do that.
I already explained if
not renaming the package and modifying pkgrel can indeed lead me to
confusion, but it's just personal compilation. ok : good practices you
encourage ;-)
version 6.1.20 has just been downloaded and will be soon in place but my
question remains : how to target 6.1.15 when evolving under 6.x.y (or
On 3/20/23 05:27, lacsaP Patatetom wrote:
hi,
- When you change the source you must also bump pkgrel as the package
is now different.
- If you want to build your own version of an Arch package, you should
not use same package name as the official Arch package - this will only
lead to
hi,
I have some questions about the compilation process which I am not familiar
with.
#1 using ArchLinux PKGBUILD, I recompiled the LTS kernel with a slight
change introduced in the block/blk-core.c file and two files were generated
: linux-lts-6.1.15-1-x86_64.pkg.tar.zst and
16 matches
Mail list logo
