reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jose R R <Jose.r.r@metztli-it.com>
To: reiserfs-devel <reiserfs-devel@vger.kernel.org>,
	debian-boot@lists.debian.org
Subject: Re: Reiser4-enabled Debian Unstable (Sid) netboot iso
Date: Wed, 6 Jan 2016 05:42:10 -0800	[thread overview]
Message-ID: <CAM12Q5Q_pdr27TEr4ZRY+2ZVG_VYfhZ6AeEHQyPatOL7UVXUXQ@mail.gmail.com> (raw)
In-Reply-To: <20160106152102.21774e48@Ulf.tvoe.tv>

On Wed, Jan 6, 2016 at 4:21 AM, dimas <dimas000@ya.ru> wrote:
> great job, man!
Appreciated.

>
>> As for Stretch and Sid, manual intervention is required only to modify
>> /etc/initramfs-tools/modules file by adding at the end:
>> crc32c_intel
>> reiser4
>> *before* installing the custom Reiser4 kernel, thus:
>> dpkg -i linux-image-4.3.0-1-amd64_4.3.3-5_amd64.deb
> why dion't you do that by postinst trigger, before update-initramfs one? or
> modify upd-initrmfs trigger, adding couple of lines...
I have built a modified version of initramfs-tools package that has as
default those Reiser4 -specific settings
but wanted to allow d-i to select most of its packages from regular
Debian repositories.

I will keep in mind your suggestion while I think about improving the
user experience, though. Thanks.
>
>> dpkg -i parted_3.2-12_amd64.deb libparted2_3.2-12_amd64.deb
> would be much more comfortable, if you add "reiser4" to the package version.
> like "x.y.z-n+reiser4". or maybe even name a package "parted-reiser4", with
> smth like "provides: parted" and "conflicts: parted", so that it won't be
> overwritten by original version on upgrade, but satisfy dependencies on "parted"

That suggestion is probably fine for the reiser4-parted DEBs but the
kernel included in d-i is 'picky' and I have not had luck changing its
name to something other than *official* Debian because d-i then
refuses to install from the Debian repositories.

Notwithstanding, one way that I have prevented overwriting
Reiser4-enabled Debian packages is by placing a *hold* on them, thus:

For the kernel, for instance:
echo "linux-image-4.3.0-1-amd64 hold" | dpkg --set-selections

And for Debian Parted:
echo "parted hold" | dpkg --set-selections
echo "libparted2 hold" | dpkg --set-selections

And we can check for those packages effectively being on *hold* and
not replaced by Debian package manager, thus:

dpkg --get-selections | grep linux-image
dpkg --get-selections | grep parted

>
>> Although I have created patches for most (or all ;-) of the above at
>> GitHub, I realize Debian Unstable (Sid) is a fast moving development
>> effort and within a couple of weeks the kernel referenced above will
>> be outdated and d-i will refuse to install.
> hmm, not sure about d-i logic, but what's the problem with slightly older
> kernel? i'm running on 3.x (custom-setup r4 patched) on testing with no
> problems so far

After Debian is installed, a custom kernel version/name will survive
-- as well as an official kernel on *hold* ; however, during a *new*
Debian installation d-i seems *very* picky about matching
kernel/changelog version(s) with packages in repositories.

-- 
Jose R R
http://metztli.it
---------------------------------------------------------------------------------------------
Try at no charge http://b2evolution.net for http://OpenShift.com PaaS
---------------------------------------------------------------------------------------------
from our GitHub http://Nepohualtzintzin.com repository. Cloud the easy way!
---------------------------------------------------------------------------------------------

  reply	other threads:[~2016-01-06 13:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-06 10:19 Reiser4-enabled Debian Unstable (Sid) netboot iso Jose R R
2016-01-06 12:21 ` dimas
2016-01-06 13:42   ` Jose R R [this message]
2016-01-06 15:20     ` dimas
2016-01-08  9:38       ` Jose R R
2016-01-07  8:11 ` Jose R R
2016-01-08 18:32   ` dimas
2016-01-09  3:07     ` Jose R R
     [not found]   ` <20160111084732.48bf9447@multivac.localdomain>
     [not found]     ` <20160111062221.GC23329@mraw.org>
     [not found]       ` <20160111190158.58dc383f@multivac.localdomain>
2016-01-12  8:34         ` Jose R R
2016-01-11 10:28 ` Jose R R
2016-01-11 10:39 ` Jose R R
2016-01-11 10:52 ` Jose R R
2016-01-11 11:42 ` Jose R R
     [not found]   ` <CAM12Q5Tj3xgN5izBa0jA8Mn1Mu7-RqRKTmStoNUfmJNtb=EtNA@mail.gmail.com>
2016-01-11 11:46     ` Fwd: " Jose R R

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAM12Q5Q_pdr27TEr4ZRY+2ZVG_VYfhZ6AeEHQyPatOL7UVXUXQ@mail.gmail.com \
    --to=jose.r.r@metztli-it.com \
    --cc=debian-boot@lists.debian.org \
    --cc=reiserfs-devel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).