Re: Please help me out with how to customize a Debian 11 ISO

[jose . r . r]

Niltze [Hello]!

On 2023-06-15 04:38, Qi Hou wrote:

Dear experts in Debian,

Pardon me for bothering you, but I have to turn to you for advice.

Recently, I've been struggling to customize a Debian (Bullseye)
installer ISO tarball.
My intention is to embed some features and a specific kernel(5.10.x)
into the ISO
tarball. Then, after deploying the debian system on a
controller(amd64), I could get
a workbench system booted with the specific kernel, and with the
features I specified
being installed by default.

But after days painfull working, I still couldn't figure out how to
let the debian
installer retrieve and unpack the deb file of the specific kernel.

I tried to hack into the file system of Debian ISO, and to collect a
lot of information
from technical blogs on the internet on the procedure of how a Debian
installer booted,
and to iminate mechanism in Debian ISO. But all failed.

What I did are below:

(1) to install feature in system as default
   I need the corresponding deb files, including the installing files
and their
   dependencies, I collected them under /var/cache/apt/ directory on a
machine who
   is connected to the internet, and on which the required features
had been installed.
   Then transfer them under their corresponding directories under
pool/main/, and
   modify the index files, including Packages and Release, as well as
md5sum.txt.

   I set the "priority" field of all features to "standard".

   It seemed what I had done worked.

(2) to install a new kernel and make the system boot with it by
default
   Coming up to this item, I have never felt I made a step forward,
but only stuck.

   I know, maybe I'm wrong, to achieve what I want, I need two images,
linux-image and
   initrd. To get linux-image, I built linux kernel with "make
bindeb-pkg"; and to get
   initrd, I installed linux kernel with commands "make
modules_install" and "make install".

   With linux-image-xxx.deb, I transferred it under the directory
"pool/main/l/linux-signed-amd64",
   and set index files and md5sum.txt.

   With vmlinuz, I used it to override the file named "vmlinuz" under
install.amd/.

   With initrd.img-5.10.x, I compressed it with "gzip", and used it to
override the file named
   "initrd.gz" under install.amd/gtk/.

At last, I recompressed the ISO source into an ISO file, and tried
to install it onto a
virtual machine.

Of course, I failed again. There is an error, "Initramfs unpacking
failed: no cpio magic".

I know actions taken to substitute for the default kernel are
senseless, but I have no idea about
where I should go.

If you could give some advice to help me embed a new kernel into the
debian destro ISO and make
the system boot with it by default, I will appreciate it from the
bottom of my heart.

Thanks for your time.

Sincerely,

Qi Hou

Have you perused this resource? It is a fair starting point ;-)
< https://wiki.debian.org/DebianInstaller/Build >
--
Best Professional Regards.

--
Jose R R
http://metztli.it
-
Download Metztli Reiser4: Debian Buster w/ Linux 5.16.20 AMD64
-
feats ZSTD compression https://sf.net/projects/metztli-reiser4/
---
Official current Reiser4 resources: https://reiser4.wiki.kernel.org/

Bug#974966: debian-installer: please check for libgdk_pixbuf_xlib-2.0 dependencies

[Jose R R]

On Tue, Nov 17, 2020 at 7:31 AM Simon McVittie  wrote:
>
> On Tue, 17 Nov 2020 at 07:13:55 -0800, Jose R R wrote:
> > FYI: clamscan shows
> > tests/test-images/gif-test-suite/max-width.gif:
> > BC.Gif.Exploit.Agent-1425366.Agent FOUND
>
> I'm not really surprised that antivirus software thinks a ridiculously
> wide GIF is trying to exploit browser bugs. It's in the test data
> precisely to make sure gdk-pixbuf doesn't crash if people try to load
> broken and potentially malicious GIFs.
>
> See: https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/150
>
> smcv
Thanks. Now for the last couple of days I had been generating minimal
netboot reiser4 installers with kernel 5.9.3-x thus I had a relevant
set up already.

I rebuilt Gdk-Pixbuf 2.40.0 essentially for Debian backports by
fetching and using your debian directory, thus generating:
libgdk-pixbuf-2.0-0-udeb_2.40.0+dfsg-6.1_amd64.udeb
libgdk-pixbuf2.0-0-udeb_2.40.0+dfsg-6.1_amd64.udeb

Placed the above UDEBs in debian-installer*/build/localudebs/.
Made sure d-i would prioritize them by referencing them in
debian-instller*/build/pkg-lists/netboot/amd64.cfg

Proceeded to test by generating a build_netboot-gtk

Just verifying that the above UDEBs were used:
grep -n 2.40.0+dfsg-6.1
../metztli-5.9.3-2+reiser4~5.1.3-with-parted-v3.3-and-libgdk-pixbuf.out1
224:Get:95 
copy:/usr/tzinti/build/metztli-reiser5/tekitl-d-i_buster5/debian-installer-20190702+deb10u5-sfrn-5-libgdk-pixbuf-2/build
localudebs/ libgdk-pixbuf-2.0-0-udeb 2.40.0+dfsg-6.1 [360 kB]
232:Get:103 
copy:/usr/tzinti/build/metztli-reiser5/tekitl-d-i_buster5/debian-installer-20190702+deb10u5-sfrn-5-libgdk-pixbuf-2/build
localudebs/ libgdk-pixbuf2.0-0-udeb 2.40.0+dfsg-6.1 [944 B]
840:Unpacking libgdk-pixbuf-2.0-0-udeb (2.40.0+dfsg-6.1) ...
844:Unpacking libgdk-pixbuf2.0-0-udeb (2.40.0+dfsg-6.1) ...

GTK PoC d-i with your integrated UDEBs:
< https://metztli.it/buster-reiser5/metztli-reiser4-sfrn5-gtk.iso >
< https://metztli.it/buster-reiser5/metztli-reiser4-sfrn5-gtk.iso.SHA256SUM >

A few screenshots from installation into VirtualBox 6.1.16 on reiser4
-enabled Debian Backports:
< https://metztli.it/buster-reiser5/gtk-test/1.png >
< https://metztli.it/buster-reiser5/gtk-test/2.png >
< https://metztli.it/buster-reiser5/gtk-test/3.png >
< https://metztli.it/buster-reiser5/gtk-test/4.png >

Best Professional Regards.

-- 
Jose R R
http://metztli.it
-
Download Metztli Reiser4: Debian Buster w/ Linux 5.9.3 AMD64
-
feats ZSTD compression https://sf.net/projects/metztli-reiser4/
---
Official current Reiser4 resources: https://reiser4.wiki.kernel.org/

Bug#917940: Reporting abuse

[jose . r . r]

Don't have a cow, RELAX, 'kibi'-

The message was not intended for you/Debian. It was created *before* the 
instance had set up any mail service. I usually just grab the 
installation reports file once it has been created at /tmp and publish 
its format in my blog. Yet somehow I forgot about removing it from the 
temporary directory. Hopefully that gives you some peace.


(Good luck with the https://debamax.com/ gig, dude)

On 2019-01-01 21:42, Cyril Brulebois wrote:

Hi,

I'm now escalating this to the BTS administrators.

This person has been filing many bug reports against installation 
images

that aren't published or supported in any way by the Debian Installer
team. I've asked several times (#842382, #819470, #819484, #858849 at
least from a quick search in mutt) for such bug reports *not* to be
filed in the Debian BTS, but nothing changed…

Please advise how to deal with this situation, and/or take any actions
you think are needed.

Thanks for your time.


Cheers,
--
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


Jose R Rodriguez  (2019-01-01):

Package: installation-reports
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where 
appropriate ***


   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- Package-specific info:

Boot method: ISO written to partition on Second SSD
Image version: https://sourceforge.net/projects/metztli-reiser4/
Date: December 26, 2018, 09:56.

Machine: Supermicro 8-core Intel® Xeon® Processor E3-1270 v6
Partitions:
Filesystem Type 1K-blocksUsed Available Use% Mounted on
udev   devtmpfs  16367576   0  16367576   0% /dev
tmpfs  tmpfs  32763608928   3267432   1% /run
/dev/sda5  reiser4  89636 6343376 215946260   3% /
tmpfs  tmpfs 16381788   0  16381788   0% /dev/shm
tmpfs  tmpfs 5120   0  5120   0% /run/lock
tmpfs  tmpfs 16381788   0  16381788   0% 
/sys/fs/cgroup

/dev/sda1  ext2472036   73322374343  17% /boot
tmpfs  tmpfs  3276356   0   3276356   0% 
/run/user/1000


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [ ]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

No CDROM available to customer, i.e., myself. Thus during acquisition 
of

bare metal server I selected Debian 9 x64, which first SSD came
formatted in ext4. I wanted Metztli Reiser4 but there was no provision
for custom install image.

I made a note of Address, Netmask, Gateway, and Nameserver. I noted, 
as

well the disks had previously been initialized with MSDOS MBR.

On the second SSD I created a small 500MB initial partition which I
formatted in ext2. I copied over Metztli Reiser4 onto that partition. 
I
knew I had to install Metztli Reiser4 as expert, thus, following a 
hint

from 'How to Boot Linux ISO Images Directly From Your Hard Drive'
< 
https://www.howtogeek.com/196933/how-to-boot-linux-iso-images-directly-from-your-hard-drive/ 
>,

by trial and error I wrote to /etc/grub.d/40_custom the following:

menuentry 'Metztli Reiser4 Expert install' {
set isofile='metztli-reiser4.iso'
  insmod gzio
  insmod part_msdos
  insmod ext2
  insmod loopback
loopback loop (hd1,msdos1)/ISOs/$isofile
linux (loop)/linux priority=low vga=788 ---
initrd (loop)/initrd.gz
}

Executed with root privilege: update-grub
Rebooted the remote server -- as I opened up an iKVM console. Booting
proceeded until GRUB screen came about from which I selected my entry
Metztli Reiser4 Expert install... i.e.,
< https://metztli.it/blog/index.php/ixiptli/metztli-reiser4-sfrn-4-2 >
the rest is history ;-)

I have since upgraded to Linux 4.18.0-3+reiser4.0.2-amd64
--

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to 
sub...@bugs.debian.org.


==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="9 (stretch) - installer build 20181028-20:31"
X_INSTALLATION_MEDIUM=netboot

==
Installer hardware-summary:

Re: Install on remote KVM?

[Jose R R]

Niltze-

On Sat, Aug 11, 2018 at 6:37 AM, Ben Hutchings  wrote:
> On Sun, 2018-08-12 at 00:25 +1200, Richard Hector wrote:
>> On 12/08/18 00:16, Ben Hutchings wrote:
>> > On Sat, 2018-08-11 at 22:58 +1200, Richard Hector wrote:
>> > [...]
>> > > I'm mostly familiar with the netinst image, and it's what I generally
>> > > use to install on real hardware.
>> > >
>> > > I'm less familiar with netboot, but have used it for PXE installs 
>> > > (right?)
>> > >
>> > > What I'm missing is how I can use either of them on a remote KVM VPS,
>> > > where I get to see the boot process on some kind of remote console, and
>> > > I have the opportunity to provide a bootable ISO, but not much else.
>> > >
>> > > I've tried providing the netinst ISO, and it boots but can't find itself
>> > > for installing packages.
>> >
>> > OK, so you're only providing the netinst ISO?  Somehow I got the
>> > impression that you were providing a separate initramfs.  Sorry for the
>> > irrelevant answer.
>> >
>> > > Is that a matter of the appropriate storage drivers not being included,
>> > > or is it the way the VPS provider set up the virtual CD?
>> >
>> > It's both!  libvirt can provide (through QEMU) an emulated CD drive
>> > attached to an Intel PATA controller, Intel SATA controller, LSI Logic
>> > SCSI controller or virtio SCSI controller.  I've just verified that the
>> > installer works for all of the first three options, but not virtio.
>> >
>> > If there's an option to configure the CD drive to be attached through
>> > one of the other controllers, you should choose that.  But we should
>> > also add virtio drivers to the standard installer initramfs.
>>
>> Great, thanks heaps for all that effort.
>>
>> I don't think there's (currently) a way to attach it differently (though
>> I could request that, and they well might do it - which might help
>> people who want to install other distros too).
>>
>> But in the meantime, can I tell the installer to download a different
>> initramfs which will work? Or does one of the other installer ISOs (ie
>> not the netinst ones) come with a suitable initramfs?
>
> I can see two options:
>
> - Rebuild the standard installer with virtio-modules included, and then
>   rebuild the netinst ISO image
> - Build an ISO image from the netboot installer
>
> But neither of those are easy unless you're already familiar with the
> process.
>
> Ben.
>
UpCloud provide a similar interface to Virt-Manager when installing
your own OS. They address the issue being discussed here -- by
describing 'a trick' to install your own OS:

< https://www.upcloud.com/support/using-own-installation-media/ >

I can confirm it works as reported in
< https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847230 >


Best Professional Regards.

-- 
Jose R R
http://metztli.it
-
Download Metztli Reiser4: Debian Stretch w/ Linux 4.17 AMD64
-
feats ZSTD compression https://sf.net/projects/metztli-reiser4/
---
Official current Reiser4 resources: https://reiser4.wiki.kernel.org/

Re: Debian installer.

[Jose R R]

On Mon, Jul 17, 2017 at 1:20 PM, Mike Hosken  wrote:
> Let's try this again.
>
> I am trying to build stable install images for HPPA. I have built 'sid'
> images previously from Debian ports.
>
> The troubles I'm having is when I build the installer -
>
> It says while building that my mirror appears invalid and will not use it.
>
> When using the git checkout it gives two errors while building. The invalid
> mirror and it's the wrong kernel, as in not the stable but testing.
>
> I am hoping someone can help me with these questions.
>
> Is there a git repo for the stable installer ?  If so how do I check it out
As far as I know, git is only for unstable Debian-Installer (d-i)

> ? Or do I use the source package in stretch.
If you are building on *and* for (stable) Stretch on HPPA,

apt-get update
apt-get source -d debian-installer

>
> What changes do I need to make ( in the source code) to get Debian-Installer
> when building to trust my unofficial but signed repo to download the udebs
> etc.
Please look in
d-i/build/config/common

OR (dirty but works)

If you are only downloading your kernel & modules you may do a hack in
source of:
< https://packages.debian.org/stretch/base-installer >
and rebuild the udeb(s) and place them under
d-i/build/localudebs/

Might also work (have not tested) by

doing a hack in source -- by adding your mirror to be listed:
< https://packages.debian.org/stretch/choose-mirror >
and rebuild the udeb(s) and place them under
d-i/build/localudebs/

*Add* name of created UDEBs in proper format into list:

d-i/build/pkg-lists/[directory image]/*cfg

>
> Also what changes do I need to make again to source code to specify the
> kernel in my repo.
>
> Any constructive advice would be appreciated.
>
> Mike Hosken
>
> Sent from my iPhone


Best Professional Regards.

-- 
Jose R R
http://metztli.it
-
Download Metztli Reiser4: Debian Stretch with Linux 4.11
-
for AMD64 https://sf.net/projects/metztli-reiser4/
-
Try at no charge http://b2evolution.net for http://OpenShift.com PaaS
-
from our GitHub http://Nepohualtzintzin.com repository. Cloud the easy way!

Re: Debian Reiser4

[Jose R R]

Good day, Ladislav-



On Sat, May 27, 2017 at 12:06 AM, Ladislav Bodnar
 wrote:
> 27.05.2017, 15:03, "Jose R R" :
>> It has as base the official Debian Jessie AMD64 distribution:
>> < https://sf.net/projects/debian-reiser4/ >
>
> The word "Debian" is registered trademark. Please find another name for your
> distribution.
>
> Ladislav

Taking heed of your advice, and on the occasion of June 17, 2017, the
official Debian Stretch release date, I hereby let you know that I
have created alternate Stretch web name for referenced project:
Metztli Reiser4 < https://sf.net/projects/metztli-reiser4/ > so as not
to infringe on Debian's trademark.

In this new debian-installer I began experimenting with Reiser4
-patched experimental kernel 'trunk' -- made available by DD Ben --
advancing gradually until I achieved Linux kernel
4.11.4-1+reiser4.0.1. Which is the kernel that I uploaded and released
on @sourceforge today. Thus, I believe is the only reiser4 -enabled
Stretch released with Linux kernel 4.11 (please note some of the
images reference 'trunk' from my prior experiments).

I have stripped nano editor from the installer and replaced it with
excellent xvi editor < https://github.com/martinwguy/xvi >; and as a
backup there remains elvis-tiny wrapped by vi. Although my testing has
been on limited hardware and cloud environments, I think those
referenced vi-clones will be dormant and awakened to 'save the day'
during unanticipated situations.

Even for a non-expert installation, Metztli-Reiser4 for AMD64 makes
sure to install the reiser4 -enabled kernel at the end of the routine.


Best Professional Regards.


-- 
Jose R R
http://metztli.it
-
Download Metztli-Reiser4: Debian Stretch with Linux 4.11
-
for AMD64 https://sf.net/projects/metztli-reiser4/
-
Try at no charge http://b2evolution.net for http://OpenShift.com PaaS
-
from our GitHub http://Nepohualtzintzin.com repository. Cloud the easy way!

Re: xvi patch to generate UDEB for Debian-Installer

[Jose R R]

Niltze, Martin-

On Tue, Jun 13, 2017 at 1:43 PM, Martin Guy  wrote:
> On 12/06/2017, Jose R R  wrote:
>> Niltze [Hello]-
>>
>> If anyone finds it useful, of course, attached please find a patch to
>> generate a small xvi UDEB -- suitable for embedding in d-i.
>
> Many thanks - duly applied in git master.
>
> Just one thought, maybe for a udeb we should use -Os and maybe clang,
> which drops the code size from 160K to 100K, compared to gcc -O2. What
> do you think?
>
Of course, you are the expert -- I just hack on whatever is out there
to suit whatever happens to be my current interest.

I just hate nano, which is currently embedded by default in
debian-installer (d-i). And even though it is unlikely debian
maintainer of d-i will change his mind, I think other vi people will
find your xvi useful for embedded applications --especially if its
size is reduced further.

As it stands now, I built elvis-tiny and embedded into my d-i
distribution hack; I like it, notwithstanding there are bugs which
have not been addressed (no one updates its code anymore, it seems)
and sometimes manifest themselves when doing editing. I am aware of
them but those quirks may confuse any unsuspecting user.

Thank you very much for your suggestion and elaborating on accepting the patch.

P.S. Here is currently how xvi stacks up against competitor editor
UDEBs; (the nano UDEB is the Debian maintainers' build and likely has
been optimized -- as you suggested for xvi.) Additionally, please note
size may differ as I build & operate on transparent compression
Reiser4 file systems.

du -hs *udeb
64K elvis-tiny-udeb_1.4-23.1_amd64.udeb
64K nano-udeb_2.7.4-1_amd64.udeb
76K xvi-udeb_2.50-1.1_amd64.udeb


Best Professional Regards.

-- 
Jose R R
http://metztli.it
-
Download Debian-Reiser4 for AMD64 https://sf.net/projects/debian-reiser4/
-
Try at no charge http://b2evolution.net for http://OpenShift.com PaaS
-
from our GitHub http://Nepohualtzintzin.com repository. Cloud the easy way!

xvi patch to generate UDEB for Debian-Installer

[Jose R R]

Niltze [Hello]-

If anyone finds it useful, of course, attached please find a patch to
generate a small xvi UDEB -- suitable for embedding in d-i.

from git:
< https://github.com/martinwguy/xvi >


Best Professional Regards

-- 
Jose R R
http://metztli.it
-
Download Debian-Reiser4 for AMD64 https://sf.net/projects/debian-reiser4/
-
Try at no charge http://b2evolution.net for http://OpenShift.com PaaS
-
from our GitHub http://Nepohualtzintzin.com repository. Cloud the easy way!
From b981d84eff3265bca9f37a35ad0d3168b358f744 Mon Sep 17 00:00:00 2001
From: Metztli Information Technology 
Date: Mon, 12 Jun 2017 07:42:53 -0700
Subject: [PATCH] Enabled generation of UDEB for Debian-Installer (d-i)

---
 debian/changelog | 7 +++
 debian/control   | 9 +
 debian/rules | 4 +++-
 3 files changed, 19 insertions(+), 1 deletion(-)

diff --git a/debian/changelog b/debian/changelog
index 293380b..105637c 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+xvi (2.50-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Enabled generation of UDEB for Debian-Installer (d-i) 
+
+ -- Metztli Information Technology   Mon, 12 Jun 2017 04:39:05 -0700
+
 xvi (2.50-1) unstable; urgency=low
 
   * Release 2.50. See RELNOTES-2.50 for a detailed list of changes.
diff --git a/debian/control b/debian/control
index 896c5dc..b0ab835 100644
--- a/debian/control
+++ b/debian/control
@@ -5,6 +5,15 @@ Maintainer: Martin Guy 
 Build-Depends: debhelper (>= 4.0.0), libncurses5-dev
 Standards-Version: 3.6.2
 
+Package: xvi-udeb
+XC-Package-Type: udeb
+Section: debian-installer
+Priority: optional
+Architecture: any
+Depends: ${shlibs:Depends}, ${misc:Depends}
+Description: xvi - udeb
+ Do not install it on a normal system.
+
 Package: xvi
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}
diff --git a/debian/rules b/debian/rules
index 49e7bdb..c86b3d4 100755
--- a/debian/rules
+++ b/debian/rules
@@ -11,7 +11,6 @@
 
 
 
-
 CFLAGS = -g
 
 ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))
@@ -53,6 +52,7 @@ install: build
 	dh_installdirs
 
 	$(MAKE) install DESTDIR=$(CURDIR)/debian/xvi
+	$(MAKE) install DESTDIR=$(CURDIR)/debian/xvi-udeb
 
 
 # Build architecture-independent files here.
@@ -68,6 +68,8 @@ binary-arch: build install
 #	dh_install
 	dh_installmenu
 #	dh_installman
+# Remove the info-bloat from -udeb
+	-rm -rf debian/xvi-udeb/usr/share
 	dh_link
 	dh_strip
 	dh_compress
-- 
2.11.0

Bug#858849: installation-reports: Successful Jessie installation with backported kernel 4.9.16-1+reiser4.0.1 on i915 system AMD64

[Jose R R]

Niltze,

On Wed, Mar 29, 2017 at 8:48 AM, Cyril Brulebois  wrote:
> Hi,
>
> Jose R R  (2017-03-29):
>> With all due respect, 99% of the build code for the debian-installer
>> is yours. As well as the build pulls 99% UDEBs from official debian
>> repositories.
>
> That doesn't mean that everything built on top of it has to be reported
> on Debian mailing lists and bug tracker. See derivative distributions,
> they have their own issue tracker, and only forward specific issues.
>
>> i.e., this is a Debian issue, not mine -- as I did not even touch that
>> code and/or modules -- which 1 month ago actually did work smooth:
>>
>> Netboot debian-installer was unable to load firmware from second USB
>> for wifi connection; accordingly, in another virtual screen, I mounted
>> the 2nd USB and manually copied the firmware directory onto the
>> installer environment /lib. d-i then detected the wifi signal, etc.
>>
>>
>> Second, report on this unofficial jessie-backports kernel
>> 4.9.16-1+reiser4.0.1 sheds light on the fact I experienced *no issue*
>> with module i915, as had been reported by (maintainer?): <
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858078 > thus, in a
>> collateral manner, I am contributing to official debian development.
>
> If you want to reply to submitters/maintainers, reply to specific bug
> reports/threads, instead of sending lengthy mails to other people?
>
>> Finally, I am not requesting *any* support. I am simply reporting that
>> your d-i pulling official UDEBs actually have been successful, with
>> minor modifications and a few extra UDEBs of mine, in my installation
>> experience, following Debian documentation guidelines:
>
> I haven't put words in your mouth and suggested you were requesting some
> support. I'm just not convinced such reports are useful. If you
> encounter specific issues, report specific bug reports against the
> relevant component.
>
> debian-boot@ isn't and shouldn't be the destination of each and every
> thing connected to, or merely using, Debian Installer.
>
>> "We also encourage installation reports to be sent even if the
>> installation is successful, so that we can get as much information as
>> possible on the largest number of hardware configurations." <
>> https://www.debian.org/releases/stable/amd64/ch05s04.html.en#submit-bug
>> >
>
> Sure, with official images.
>
>> If you are still 'bothered' with my sporadic submissions, I encourage
>> you to modify the documentation to specifically exclude the glaring
>> omission.
>
> I could be adding a specific “we don't need reiser4-specific reports”

Please do add that phrase; thus removing any ambiguities and cover the
glaring omission in the Debian documentation.

That clarification will prevent other individuals -- who have
downloaded the netboot installer from SourceForge -- from potentially
reporting via the debian mechanism -- once the installation completes.

Additionally, appending “we don't need reiser4-specific reports” will
be a welcome *explicit* change in policy from other FOSS projects,
like GNU Parted, where the unspoken censorship on reiser4 bites anyone
who submits patches in support of the
'Batman Machine': Reiser4
< https://metztli.it/readOnlyEphemeral/Batman_Machine-Reiser4.pdf >


Again, thank you.


Best Professional Regards.

-- 
Jose R R
http://metztli.it
-
Download Debian-Reiser4 for AMD64 https://sf.net/projects/debian-reiser4/
-
Try at no charge http://b2evolution.net for http://OpenShift.com PaaS
-
from our GitHub http://Nepohualtzintzin.com repository. Cloud the easy way!

Bug#858849: installation-reports: Successful Jessie installation with backported kernel 4.9.16-1+reiser4.0.1 on i915 system AMD64

[Jose R R]

Niltze,

On Mon, Mar 27, 2017 at 8:00 PM, Cyril Brulebois  wrote:
> Hi,
>
> Metztli Information Technology  (2017-03-27):
>> Boot method: CD/USB
>> Image version: https://metztli.it/readOnlyEphemeral/xiuhcohuatl.iso built on 
>> Mar 25 08:35 (2017)
>> Date: Mar 26, 2017, 01:49
>
> A couple of months ago, I asked:
> | Do we need to get installation reports for non-Debian installers?
> | This isn't something we produce, publish, or support, so…
>
> It would be nice if those installation reports could be sent elsewhere;
> thanks already.
>
>
> KiBi.

With all due respect, 99% of the build code for the debian-installer
is yours. As well as the build pulls 99% UDEBs from official debian
repositories.

i.e., this is a Debian issue, not mine -- as I did not even touch that
code and/or modules -- which 1 month ago actually did work smooth:

Netboot debian-installer was unable to load firmware from second USB
for wifi connection;
accordingly, in another virtual screen, I mounted the 2nd USB and
manually copied the firmware
directory onto the installer environment /lib. d-i then detected the
wifi signal, etc.


Second, report on this unofficial jessie-backports kernel
4.9.16-1+reiser4.0.1 sheds light on the fact I experienced *no issue*
with module i915, as had been reported by (maintainer?):
< https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858078 >
thus, in a collateral manner, I am contributing to official debian development.

Finally, I am not requesting *any* support. I am simply reporting that
your d-i pulling official UDEBs actually have been successful, with
minor modifications and a few extra UDEBs of mine, in my installation
experience, following Debian documentation guidelines:

"We also encourage installation reports to be sent even if the
installation is successful, so that we can get as much information as
possible on the largest number of hardware configurations."
< https://www.debian.org/releases/stable/amd64/ch05s04.html.en#submit-bug >

If you are still 'bothered' with my sporadic submissions, I encourage
you to modify the documentation to specifically exclude the glaring
omission.


Best Professional Regards.

-- 
Jose R R
http://metztli.it
-
Download Debian-Reiser4 for AMD64 https://sf.net/projects/debian-reiser4/
-
Try at no charge http://b2evolution.net for http://OpenShift.com PaaS
-
from our GitHub http://Nepohualtzintzin.com repository. Cloud the easy way!

nfs-common 1.3.4-2.1 jessie-backported for Reiser4 newer kernel

[Jose R R]

Niltze, all-

Jessie-Reiser4 had an issue with nfs-common package from the official
Debian Jessie repositories: it hung a newly installed Reiser4 root-fs
Debian and/or would hang during subsequent installation with message:

Setting up nfs-common (1:1.2.8-9) ...

Creating config file /etc/idmapd.conf with new version


Interesting thing is that Sid-Reiser4 would not be affected upon
installation of Sid nfs-common package.

Accordingly, I jessie-backport'ed the newer nfs-common to address the
bug that hung Jessie-Reiser4. It's my pleasure to communicate that the
port apparently resolved the bug-hang issue ;-)

Jessie-backport nfs-common 1.3.4-1 DEB is at usual location at
SourceForge --if anyone desires to provide feedback.

It will subsequently be integrated into Debian-Reiser4 neboot images
-- using SSL-enabled wget to download from metztli.it


Best Professional Regards.


-- 
Jose R R
http://metztli.it
-
Download Debian-Reiser4 for AMD64 https://sf.net/projects/debian-reiser4/
-
Try at no charge http://b2evolution.net for http://OpenShift.com PaaS
-
from our GitHub http://Nepohualtzintzin.com repository. Cloud the easy way!

Reiser4-for-4.8.0 patch and Debian Jessie Backports linux_4.8.11-1~bpo8+1

[Jose R R]

Niltze!

Had to modify/rename Reiser4-for-4.8.0 patch with one-liner:

gzip -dc reiser4-for-4.8.0.patch.gz | \
sed 's/inode_change_ok(inode/setattr_prepare(dentry/' | \
gzip -9 - > reiser4-for-4.8.11+.patch.gz

to get around a build error in linux/fs/reiser4/plugin/inode_ops.c
as elaborated on
< https://metztli.it/blog/index.php/aH2?blog=4 >

And successfully generate U/DEBs for Debian-Installer (d-i)


Best Professional Regards.
-- 
Jose R R
http://metztli.it
-
Download Debian-Reiser4 for AMD64 https://sf.net/projects/debian-reiser4/
-
Try at no charge http://b2evolution.net for http://OpenShift.com PaaS
-
from our GitHub http://Nepohualtzintzin.com repository. Cloud the easy way!

Bug#842040: Please add https support

[Jose R R]

On Fri, Nov 18, 2016 at 8:18 AM, Philipp Kern  wrote:
> On 12.11.2016 18:16, Josh Triplett wrote:
>> On Thu, 10 Nov 2016 01:14:33 -0800 Jose R R  wrote:
>>> On Tue, Oct 25, 2016 at 6:17 AM, Marga Manterola  wrote:
>>>> Package: debian-installer
>>>> Severity: normal
>>>>
>>>> The installer currently doesn't support downloading packages from https
>>>> mirrors, because busybox's wget doesn't support https.
>>>
>>> In order to add SSL support to BusyBox wget, itself to be used wih
>>> ssl_helper, I used matrixssl-3-4-2-open.tgz
>>> < http://www.matrixssl.org/ >
>>>
>>> to build my custom BusyBox udeb for my Reiser4-enabled Debian-Installer
>>> < https://sf.net/projects/debian-reiser4/ >
>>>
>>> No idea if suggestion fulfills bug need - just my 2 cents ;-)
>>
>> Can you provide a link for your patches to busybox wget to add SSL
>> support?  That sounds like it'd substantially decrease size compared to
>> including GNU wget and supporting libraries.
>
> Unfortunately matrixssl isn't even in Debian at this point.
>
The official Debian maintainer(s) busybox source lacks a directory
that is upstream in the busybox official source.
For instance, for upstream busybox-1.25.1, the relevant path to *that*
directory is:

busybox-1.25.1/networking/ssl_helper

then,
If we untar matrixssl-3-4-2-open.tgz , we get directory

matrixssl-3-4-2-open/

copying ssl_helper directory into matrixssl-3-4-2-open/., we build
first matrixssl:

make

After successful build:

cd ssl_helper

./ssl_helper.sh  ## to compile and link the helper, thus

ssl_helper.c generates ssl_helper executable (and ssl_helper.o ? ;-)

To provide SSL-enabled busybox wget you only need the executable ssl_helper

hence,

Prior to building your busybox udeb

create a directory inside your 'official' Debian maintainers busybox
untarred source

mkdir --verbose -p _install/usr/bin

copy your generated executable ssl_helper into above directory, i.e.,

_install/usr/bin/ssl_helper   ##<== executable should be this and here

>From this dirty hack, *any* Debian-helper-generated busybox UDEB
should contain busybox SSL-enabled wget

Sorry, I am busy - but will try to create a patch for official Debian
source from git -- though I am not an official Debian maintainer.

sample from my reiser4 Debian-Installer (d-i):
< 
https://metztli.it/readOnlyEphemeral/busybox-udeb_1.22.0-19.1_amd64.udeb.SHA256SUM
># Text contents
< https://metztli.it/readOnlyEphemeral/busybox-udeb_1.22.0-19.1_amd64.udeb >

If above udeb link is downloaded locally, it may be expanded to analyze as:
dpkg -X busybox-udeb_1.22.0-19.1_amd64.udeb  tempDir

Happy hacking!


Best Professional Regards.

-- 
Jose R R
http://metztli.it
-
Download Debian-Reiser4 for AMD64 https://sf.net/projects/debian-reiser4/
-
Try at no charge http://b2evolution.net for http://OpenShift.com PaaS
-
from our GitHub http://Nepohualtzintzin.com repository. Cloud the easy way!
-

Bug#842040: Please add https support

[Jose R R]

Niltze [Hello]!

On Tue, Oct 25, 2016 at 6:17 AM, Marga Manterola  wrote:
> Package: debian-installer
> Severity: normal
>
> The installer currently doesn't support downloading packages from https
> mirrors, because busybox's wget doesn't support https.

In order to add SSL support to BusyBox wget, itself to be used wih
ssl_helper, I used matrixssl-3-4-2-open.tgz
< http://www.matrixssl.org/ >

to build my custom BusyBox udeb for my Reiser4-enabled Debian-Installer
< https://sf.net/projects/debian-reiser4/ >

No idea if suggestion fulfills bug need - just my 2 cents ;-)

>
> The wget package has been changed to provide a udeb, compiled against the
> libssl udeb, so that it provides https support.
>
> The change needed in d-i is to add the wget udeb and it's dependencies
> (libcrypto1.0.2, libssl1.0.2 and libpcre3) to the initrd.
>
> Regarding total size (as this was mentioned when I discussed this in the
> past), this is the size of the needed udebs:
> -rw-r- 1 marga marga 878072 Sep 26 20:17
> libcrypto1.0.2-udeb_1.0.2j-1_amd64.udeb
> -rw-r- 1 marga marga 153852 Aug 19 12:59 libpcre3-udeb_8.39-2_amd64.udeb
> -rw-r- 1 marga marga 141318 Sep 26 20:17
> libssl1.0.2-udeb_1.0.2j-1_amd64.udeb
> -rw-r- 1 marga marga 147960 Sep 26 15:19 wget-udeb_1.18-4_amd64.udeb
>
> And this is the size difference of the old initrd and the new one:
> -rw-r- 1 marga eng 22580707 Oct 25 02:07 initrd.gz
> -rw-r- 1 marga eng 23381570 Oct 25 15:11 newinitrd.gz
>
> So, approximately 780k extra for the initrd image (3.5% increase)
>
> Thanks!
> --
> Cheers,
> Marga


Best Professional Regards

-- 
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!
-

reiser4progs 1.0.1.0-1.1 for Debian Backports

[Jose R R]

Good day, Felix-

First, thank you for maintaining reiser4progs for Debian alive.

I wanted to suggest if you are willing to backport reiser4progs
1.0.1.0-x.y for the upcoming 'Jessie and a half ' release?
< https://lists.debian.org/debian-boot/2016/07/msg00037.html >

Although I have built reiser4progs 1.0.1.0-1.2 for Jessie as a non-maintainer,
< https://sourceforge.net/projects/debian-reiser4/files/ >
 the upcoming "jessie and a half' project will benefit from an
official maintainer build.


Best Professional Regards.

-- 
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!

Re: Debian kernel 4.7.2-1 build on Sid and Jessie fails

[Jose R R]

On Sat, Sep 3, 2016 at 10:30 AM, Ben Hutchings  wrote:
>
> On Fri, 2016-09-02 at 16:49 +0100, Ben Hutchings wrote:
> > On Fri, 2016-09-02 at 03:35 -0700, Jose R Rodriguez wrote:
> > >
> > > Niltze, all!
> > >
> > > Currently running Reiser4-patched kernel 4.7 built from pristine
> > > source upstream:
> > >
> > > Linux mictlantecuhtli 4.7.0.tezcatlipoca #1 SMP PREEMPT Wed Aug 10
> > > 05:04:17 PDT 2016 x86_64 GNU/Linux
> > >
> > > On the other hand, I have experienced multiple issues building
> > > Debian'ized kernel 4.7.2-1 -- first building on Jessie modified for
> > > GCC 4.9;
> > >  and then attempting build on Jessie-built GCC 5.3. And finally I
> > > attempted the build on Debian Unstable and it failed, as well.
> > > Below are the offending sections -- which, by the way -- roughly
> > > correspond in all instances of Debian and GCC:
> > [...]
> >
> > This happens if you invoke debian/rules directly and not through dpkg-
> > buildpackage.
>
> Rather, it can happen in some circumstances, but...
>
> > debian/rules.real does:
> >
> > ifdef OVERRIDE_HOST_TYPE
> >   CROSS_COMPILE := $(OVERRIDE_HOST_TYPE)-
> > else ifneq ($(DEB_BUILD_ARCH),$(DEB_HOST_ARCH))
> >   CROSS_COMPILE := $(DEB_HOST_GNU_TYPE)-
> > else
> >   CROSS_COMPILE :=
> > endif
> >
> > So the assumption is that all those architecture variables, or none,
> > are defined.  dpkg-buildpackage does define them all.
> >
> > However, debian/rules does:
> >
> > DEB_HOST_ARCH := $(shell dpkg-architecture -qDEB_HOST_ARCH)
> >
> > and does not define any other architecture variables.
>
> ...variable definitions in debian/rules don't automatically propagate
> to debian/rules.real, so this doesn't explain the failure.  And
> although I have seen this failure myself, I can't reproduce it now.
>
> > We should probably include /usr/share/dpkg/architecture.mk in
> > debian/rules instead.
>
> I now think it should be included in debian/rules.real.  However, until
> I have a way to reproduce the problem, I'm not going to attempt a fix.
>
> Ben.
>
> --
> Ben Hutchings
> Once a job is fouled up, anything done to improve it makes it worse.

I much appreciate your hints, Ben. The fault was mine. After a couple
of days of struggle, I modified debian/rules.real by inserting a
couple of extra directives and compared the generated debian/control
file output with previous ones - which provided me relevant insight to
correct my mistake and generate required *.udebs for d-i. Thank you
again, Ben.


Best Professional Regard.

-- 
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!

Re: Debian kernel 4.7.2-1 build on Sid and Jessie fails

[Jose R R]

dules-4.7.0-1+reiser4.0.1-amd64-di
sound-modules-4.7.0-1+reiser4.0.1-amd64-di
hyperv-modules-4.7.0-1+reiser4.0.1-amd64-di
udf-modules-4.7.0-1+reiser4.0.1-amd64-di
fuse-modules-4.7.0-1+reiser4.0.1-amd64-di
dh_fixperms
make[2]: Leaving directory '/mnt/sdb5/usr/src/build/tekitl-4.7.2-1/linux'
make[1]: Leaving directory '/mnt/sdb5/usr/src/build/tekitl-4.7.2-1/linux'

from
http://paste.debian.net/806348/


Thank you again, Ben.


Best Professional Regards

-- 
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!

UEFI Secure Boot back-door keys leak

[Jose R R]

"Either way, it'd be impossible in practise for MS to revoke every
bootmgr earlier than a certain point, as they'd break install media,
recovery partitions, backups, etc."

https://rol.im/securegoldenkeyboot/


Best Professional Regards.

-- 
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!

Re: Thinking about a "jessie and a half" release

[Jose R R]

On Tue, Jul 5, 2016 at 2:01 AM, Christian Seiler  wrote:
>
> On 07/04/2016 03:01 PM, Steve McIntyre wrote:
> > There's something I've been pondering for a while, along with some
> > other folks - it might be useful to do a "jessie and a half" release,
> > similarly to what we did in the etch days. That's *basically* just
> > like a normal jessie release, but with a few key updates:
> >
> >  * backports kernel
> >  * rebuilt d-i to match that kernel
> >  * X drivers
> >  * ... (other things that might be needed for consistency)
> >
> > all rolled up with a small installer image build (netinst, maybe DVD#1).
>
> Why would you call it "Jessie + 1/2"? Wouldn't it be a better idea
Well IBM set a precedent for that: OS/2.
Accordingly, Jessie BP could be called Jessie/2 ;-)

> to regularly have a "backports installer" netinst image? So when
> 8.6 (or 8.7 if it takes longer) comes around, there'll be an image,
> part of the point release, that will contain the backports kernel
> that's current at that time, plus the installer will enable backports
> automatically, plus it will install a preferences.d file that will
> enable pulling kernel + X11 drivers from backports. (But not other
> things.)
>
> This could then be a regular part of the released installer images,
> and any new major release (e.g. Stretch 9.0) would enable the
> preferences.d file + backports automatically, but would still use
> the regular kernel at that point (because there'd be no backports
> then).
>
> That way, you'd have a little more work in the installer in creating
> an image that uses a backports kernel, but there'd be no need in
> having to support a new release in addition to Jessie, because the
> installed system would be equivalent to Jessie + upgrade kernel to
> backports + remove old kernel package. Which is already something
> that people do _now_.
>
> Regards,
> Christian
>


Good luck!

-- 
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!
-

Re: Thinking about a "jessie and a half" release

[Jose R R]

On Mon, Jul 4, 2016 at 6:01 AM, Steve McIntyre  wrote:
> Hey folks,
>
> There's something I've been pondering for a while, along with some
> other folks - it might be useful to do a "jessie and a half" release,
> similarly to what we did in the etch days. That's *basically* just
> like a normal jessie release, but with a few key updates:
>
>  * backports kernel
I built Reiser4-patched (SFRN 4.0.1) Linux kernel 4.6.2-2 from Debian
source (i.e, 'backport') for Jessie on AMD64.

>  * rebuilt d-i to match that kernel
Did - but upon d-i test installation of Debian Desktop Environment, I
found out it(seems *all* GUIs selected in d-i) has a 'nasty'
dependency on xserver-xorg-input-vmmouse for VMware. Those of us not
on proprietary stuff can purge xserver-xorg-input-vmmouse; however,
action will also remove a couple of task*-related packages. Adding the
Stretch repositories and subsequently installing
xserver-xorg-input-vmmouse, it will bring about plenty of X upgrades.

So *yes*:
>  * X drivers
>  * ... (other things that might be needed for consistency)
>
> all rolled up with a small installer image build (netinst, maybe DVD#1).
>
> A lot of arm64 machine users would benefit from this, and maybe owners
> of very recent amd64 machines too, with better support for things on
> the Skylake platform. Those are the only two architectures I'm
> thinking of supporting at this point.
>
> Is anybody else interested in helping? Thoughts/comments?
>
> --


Best Professional Regards.

-- 
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!
-

Bug#823986: installation-reports: "hardware" errors on virtualbox

[Jose R R]

"02:29 < kilobyte> reproduced in virtualbox: lots of I/O errors: ata1.00:
  failed command: WRITE FPDMA QUEUED"

As I frequently test Reiser4-enabled unstable Debian-Installers on
VirtuaBox 5.0.16 (my latest version), on a frequent basis I come
across similar I/O errors: ata related as well as some other
idiosyncrasies related to unstable nature of my d-i builds. Wait a few
days for the debian-installer component UDEBs to stabilize and work
better together --in harmony-- then try your installation again.


On Tue, May 10, 2016 at 6:27 PM, Adam Borowski  wrote:
> Package: installation-reports
> Severity: normal
>
>
> 00:37 < calops> hi, is there any known issue about the testing installer
> (netinst and CD) failing around the "selecting packages"
> step?
> 00:39 < calops> it happens to me both natively on my machine, and as a
> virtualbox guest
> 01:35 < Sledge> calops: anything in syslog?
> 02:29 < kilobyte> reproduced in virtualbox: lots of I/O errors: ata1.00:
>   failed command: WRITE FPDMA QUEUED
>
> Syslog attached.  The failed step was "Select and install software", no
> error message was given other than "installation step failed".
>
> No hardware or software errors on the host, other VMs work fine, so this is
> not a fault of the new version of virtualbox (current unstable --
> 5.0.20-dfsg-1).  And that calops guy reports it's failing on bare metal too.
>
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (150, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.6.0-rc6-debug2+ (SMP w/6 CPU cores)
> Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: sysvinit (via /sbin/init)



-- 
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!
-

Alpha Reiser4 (SFRN 4.0.1) -enabled Debian netboot image

[Jose R R]

Niltze all-

Realizing that change frequency in Debian software components for
Reiser4-enabled Debian (sid) Unstable image renders media stale quite soon,
I created a Jessie netboot image.

Existing instructions should work as a guide,
http://marc.info/?l=reiserfs-devel&m=145824683620735&w=2

and previous links should work, too, i.e.,
metztli.iso --> linux-jessie-reiser4-amd64.deb
metztli.SHA256 --> linux-jessie-reiser4-amd64.SHA256SUM

I suggest installation in expert mode so as to select the Reiser4
(SFRN)-enabled kernel when relevant dialog appears. Menu is a link that
will download Debian kernel 4.5.x -- built under Jessie with a custom built
GCC-5.

If interested in a graphical guide to install Debian Jessie with netboot
ISO/USB media, please see snapshots:

https://metztli.it/blog/index.php/ixiptli/aH4
and then
https://metztli.it/blog/index.php/ixiptli/aH3


Best Professional Regards.

-- 
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!
-

Re: sed: can't read debian/build/build-tools/tools/usb/usbip/config.h: No such file or directory

[Jose R R]

nudging build procedure along...

apt-get install asciidoc libelf-dev libperl-dev python-dev libnuma-dev
libaudit-dev libunwind-dev libdw-dev libudev-dev libiberty-dev usbip
libusbip-dev liblockdep4.4 linux-tools

On Mon, Apr 25, 2016 at 1:25 PM, Jose R R  wrote:
> and, yes, Ben, in other VM instances I have installed asciidoc, (takes
> longer to build) but the outcome is the same.
>
> On Mon, Apr 25, 2016 at 1:21 PM, Jose R R  wrote:
>> Niltze, Ben-
>>
>> Maybe I am dense, but I in several Debian kernels 4.5.x.y I noticed
>> the topic of the subject *and* associated to this recurring fail
>> pattern:
>>
>> On Sun, Apr 17, 2016 at 11:00 AM, Ben Hutchings 
wrote:
>>> On Sun, 2016-04-17 at 06:38 -0700, Jose R R wrote:
>>>> Nilteze, all-
>>>>
>>>> Subject topic of this message prevents building kernel module UDEBs by
>>>> stopping build midway:
>>> [...]
>>>
>>> No, it doesn't.  That error message is ugly, but actually harmless.
>>>  (You can see it in all the old build logs for linux-tools.)
>>>Niltze, Ben-
>>
>> [...]
>> install 'perf-with-kcore.sh'
>>
'/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/build/build-tools/tools/perf/perf-with-kcore'
>> make[6]: Leaving directory
>> '/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/tools/perf'
>> /usr/bin/make
O=/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/build/build-tools/tools/perf
>> prefix=/usr V=1 ARCH=x86 EXTRA_WARNINGS=-Wno-error EXTRA_CFLAGS='-g
>> -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall
>> -D_FORTIFY_SOURCE=2
>> -I/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/tools/perf
>>
-I/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/build/build-tools/tools/perf
>> -isystem
/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/build/build-tools/include'
>> LDFLAGS='-Wl,-z,relro' NO_GTK2=1 perfexecdir=lib/perf_4.5-core
>> plugindir=/usr/lib/traceevent_4.5/plugins
>> STRACE_GROUPS_DIR=share/perf_4.5-core/strace/groups feature-libbfd=0
>> HAVE_CPLUS_DEMANGLE_SUPPORT=1 -C
>> /mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/tools/perf/Documentation
>> man VERSION=4.5
>> make[6]: Entering directory
>> '/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/tools/perf/Documentation'
>> Makefile:208: Please install asciidoc to have the man pages installed
>> rm -f
/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/build/build-tools/tools/perf/perf-data.xml+
>>
/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/build/build-tools/tools/perf/perf-data.xml
>> && \
>> asciidoc -b docbook -d manpage -f asciidoc.conf \
>> --unsafe -a revdate=2016-04-14 -aperf_version= -o
>>
/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/build/build-tools/tools/perf/perf-data.xml+
>> perf-data.txt && \
>> mv
/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/build/build-tools/tools/perf/perf-data.xml+
>>
/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/build/build-tools/tools/perf/perf-data.xml
>> /bin/sh: 2: asciidoc: not found
>> make[6]: ***
[/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/build/build-tools/tools/perf/perf-data.xml]
>> Error 127
>> make[5]: *** [all] Error 2
>> make[4]: *** [all-recursive] Error 2
>> make[3]: *** [all-recursive] Error 2
>> make[2]: *** [debian/stamps/build-tools] Error 2
>> make[1]: *** [binary-arch_amd64_real] Error 2
>> make: *** [binary-arch] Error 2
>> Makefile:281: recipe for target
>>
'/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/build/build-tools/tools/perf/perf-data.xml'
>> failed
>> make[6]: Leaving directory
>> '/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/tools/perf/Documentation'
>>
/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/rules.d/tools/perf/Makefile:49:
>> recipe for target 'all' failed
>> make[5]: Leaving directory
>>
'/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/build/build-tools/tools/perf'
>>
/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/rules.d/Makefile.inc:25:
>> recipe for target 'all-recursive' failed
>> make[4]: Leaving directory
>>
'/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/build/build-tools/tools'
>>
/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/rules.d/Makefile.inc:25:
>> recipe for target 'all-recursive' failed
>> make[3]: Leaving directory
>> '/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/build/build-tools'
>> debian/rules.real:488: recipe for target 'debian/stamps/build-tools&

Re: sed: can't read debian/build/build-tools/tools/usb/usbip/config.h: No such file or directory

[Jose R R]

and, yes, Ben, in other VM instances I have installed asciidoc, (takes
longer to build) but the outcome is the same.

On Mon, Apr 25, 2016 at 1:21 PM, Jose R R  wrote:
> Niltze, Ben-
>
> Maybe I am dense, but I in several Debian kernels 4.5.x.y I noticed
> the topic of the subject *and* associated to this recurring fail
> pattern:
>
> On Sun, Apr 17, 2016 at 11:00 AM, Ben Hutchings  wrote:
>> On Sun, 2016-04-17 at 06:38 -0700, Jose R R wrote:
>>> Nilteze, all-
>>>
>>> Subject topic of this message prevents building kernel module UDEBs by
>>> stopping build midway:
>> [...]
>>
>> No, it doesn't.  That error message is ugly, but actually harmless.
>>  (You can see it in all the old build logs for linux-tools.)
>>Niltze, Ben-
>
> [...]
> install 'perf-with-kcore.sh'
> '/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/build/build-tools/tools/perf/perf-with-kcore'
> make[6]: Leaving directory
> '/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/tools/perf'
> /usr/bin/make 
> O=/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/build/build-tools/tools/perf
> prefix=/usr V=1 ARCH=x86 EXTRA_WARNINGS=-Wno-error EXTRA_CFLAGS='-g
> -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall
> -D_FORTIFY_SOURCE=2
> -I/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/tools/perf
> -I/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/build/build-tools/tools/perf
> -isystem 
> /mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/build/build-tools/include'
> LDFLAGS='-Wl,-z,relro' NO_GTK2=1 perfexecdir=lib/perf_4.5-core
> plugindir=/usr/lib/traceevent_4.5/plugins
> STRACE_GROUPS_DIR=share/perf_4.5-core/strace/groups feature-libbfd=0
> HAVE_CPLUS_DEMANGLE_SUPPORT=1 -C
> /mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/tools/perf/Documentation
> man VERSION=4.5
> make[6]: Entering directory
> '/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/tools/perf/Documentation'
> Makefile:208: Please install asciidoc to have the man pages installed
> rm -f 
> /mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/build/build-tools/tools/perf/perf-data.xml+
> /mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/build/build-tools/tools/perf/perf-data.xml
> && \
> asciidoc -b docbook -d manpage -f asciidoc.conf \
> --unsafe -a revdate=2016-04-14 -aperf_version= -o
> /mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/build/build-tools/tools/perf/perf-data.xml+
> perf-data.txt && \
> mv 
> /mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/build/build-tools/tools/perf/perf-data.xml+
> /mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/build/build-tools/tools/perf/perf-data.xml
> /bin/sh: 2: asciidoc: not found
> make[6]: *** 
> [/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/build/build-tools/tools/perf/perf-data.xml]
> Error 127
> make[5]: *** [all] Error 2
> make[4]: *** [all-recursive] Error 2
> make[3]: *** [all-recursive] Error 2
> make[2]: *** [debian/stamps/build-tools] Error 2
> make[1]: *** [binary-arch_amd64_real] Error 2
> make: *** [binary-arch] Error 2
> Makefile:281: recipe for target
> '/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/build/build-tools/tools/perf/perf-data.xml'
> failed
> make[6]: Leaving directory
> '/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/tools/perf/Documentation'
> /mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/rules.d/tools/perf/Makefile:49:
> recipe for target 'all' failed
> make[5]: Leaving directory
> '/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/build/build-tools/tools/perf'
> /mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/rules.d/Makefile.inc:25:
> recipe for target 'all-recursive' failed
> make[4]: Leaving directory
> '/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/build/build-tools/tools'
> /mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/rules.d/Makefile.inc:25:
> recipe for target 'all-recursive' failed
> make[3]: Leaving directory
> '/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/build/build-tools'
> debian/rules.real:488: recipe for target 'debian/stamps/build-tools' failed
> make[2]: Leaving directory '/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux'
> debian/rules.gen:30: recipe for target 'binary-arch_amd64_real' failed
> make[1]: Leaving directory '/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux'
> debian/rules:47: recipe for target 'binary-arch' failed
>
>

Best Professional Regards.

-- 
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!

Re: sed: can't read debian/build/build-tools/tools/usb/usbip/config.h: No such file or directory

[Jose R R]

Niltze, Ben-

Maybe I am dense, but I in several Debian kernels 4.5.x.y I noticed
the topic of the subject *and* associated to this recurring fail
pattern:

On Sun, Apr 17, 2016 at 11:00 AM, Ben Hutchings  wrote:
> On Sun, 2016-04-17 at 06:38 -0700, Jose R R wrote:
>> Nilteze, all-
>>
>> Subject topic of this message prevents building kernel module UDEBs by
>> stopping build midway:
> [...]
>
> No, it doesn't.  That error message is ugly, but actually harmless.
>  (You can see it in all the old build logs for linux-tools.)
>Niltze, Ben-

[...]
install 'perf-with-kcore.sh'
'/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/build/build-tools/tools/perf/perf-with-kcore'
make[6]: Leaving directory
'/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/tools/perf'
/usr/bin/make 
O=/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/build/build-tools/tools/perf
prefix=/usr V=1 ARCH=x86 EXTRA_WARNINGS=-Wno-error EXTRA_CFLAGS='-g
-O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall
-D_FORTIFY_SOURCE=2
-I/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/tools/perf
-I/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/build/build-tools/tools/perf
-isystem 
/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/build/build-tools/include'
LDFLAGS='-Wl,-z,relro' NO_GTK2=1 perfexecdir=lib/perf_4.5-core
plugindir=/usr/lib/traceevent_4.5/plugins
STRACE_GROUPS_DIR=share/perf_4.5-core/strace/groups feature-libbfd=0
HAVE_CPLUS_DEMANGLE_SUPPORT=1 -C
/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/tools/perf/Documentation
man VERSION=4.5
make[6]: Entering directory
'/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/tools/perf/Documentation'
Makefile:208: Please install asciidoc to have the man pages installed
rm -f 
/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/build/build-tools/tools/perf/perf-data.xml+
/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/build/build-tools/tools/perf/perf-data.xml
&& \
asciidoc -b docbook -d manpage -f asciidoc.conf \
--unsafe -a revdate=2016-04-14 -aperf_version= -o
/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/build/build-tools/tools/perf/perf-data.xml+
perf-data.txt && \
mv 
/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/build/build-tools/tools/perf/perf-data.xml+
/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/build/build-tools/tools/perf/perf-data.xml
/bin/sh: 2: asciidoc: not found
make[6]: *** 
[/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/build/build-tools/tools/perf/perf-data.xml]
Error 127
make[5]: *** [all] Error 2
make[4]: *** [all-recursive] Error 2
make[3]: *** [all-recursive] Error 2
make[2]: *** [debian/stamps/build-tools] Error 2
make[1]: *** [binary-arch_amd64_real] Error 2
make: *** [binary-arch] Error 2
Makefile:281: recipe for target
'/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/build/build-tools/tools/perf/perf-data.xml'
failed
make[6]: Leaving directory
'/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/tools/perf/Documentation'
/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/rules.d/tools/perf/Makefile:49:
recipe for target 'all' failed
make[5]: Leaving directory
'/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/build/build-tools/tools/perf'
/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/rules.d/Makefile.inc:25:
recipe for target 'all-recursive' failed
make[4]: Leaving directory
'/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/build/build-tools/tools'
/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/rules.d/Makefile.inc:25:
recipe for target 'all-recursive' failed
make[3]: Leaving directory
'/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux/debian/build/build-tools'
debian/rules.real:488: recipe for target 'debian/stamps/build-tools' failed
make[2]: Leaving directory '/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux'
debian/rules.gen:30: recipe for target 'binary-arch_amd64_real' failed
make[1]: Leaving directory '/mnt/sdb5/usr/src/build/tekitl-4.5.1-1/linux'
debian/rules:47: recipe for target 'binary-arch' failed


Best Professional Regards.

-- 
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!

Re: Debian with Reiser4-patched Linux kernel on IBM Power8

[Jose R R]

On Wed, Apr 20, 2016 at 4:11 AM, Jonáš Vidra  wrote:
> On Wed, 20 Apr 2016 12:53:48 +0200 Jose R R  wrote:
>
>> is there any reason why Reiser4 SFRN 4.0.1-enabled Debian should not
>> run on Power8? I assume GPT should be selected whereas previously I
>> have tested -- on AMD64 baremetal and cloud -- only MSDOS disk
>> partitioning.
>
>
> There might be some problems with the endianness of the system.
>
> I have tested Reiser4 on 32bit PowerPC several years ago and as far as I
> remember, mounting and using a preformatted partition (mkfs done on an x86
> machine) was possible, but a partition formatted on PowerPC was unusable.
> I can repeat the tests, if you are interested.

No, I won't bother you with that. Just gathering some preliminary
information prior to efforts at building the PPC Reiser4 UDEB module
for my Debian-Installer (d-i) hack.

Thank you much for your insight on 'endianness of the system'.


Best professional Regards.


-- 
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!
-

Debian with Reiser4-patched Linux kernel on IBM Power8

[Jose R R]

Niltze, all-

Looking over the Soflayer bare metal Power8 systems, I see that
Debian's kid, Ubuntu, is the default OS.

http://www.softlayer.com/power-servers

I was pondering an evaluation trial of Reiser4-enabled Debian on IBM
Power8. Up to now I have only successfully tested Reiser4 Software
Format Release Number (SFRN) 4.0.1 on AMD64 baremetal, virtualization
and cloud.

If am allowed to install my own OS,
is there any reason why Reiser4 SFRN 4.0.1-enabled Debian should not
run on Power8? I assume GPT should be selected whereas previously I
have tested -- on AMD64 baremetal and cloud -- only MSDOS disk
partitioning.


Best Professional Regards.

-- 
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!
-

sed: can't read debian/build/build-tools/tools/usb/usbip/config.h: No such file or directory

[Jose R R]

Nilteze, all-

Subject topic of this message prevents building kernel module UDEBs by
stopping build midway:

linux_4.6~rc3-1~exp1.debian.tar.xz  linux_4.6~rc3-1~exp1.dsc
 linux_4.6~rc3.orig.tar.xz and linux/debian packaging from git.

head linux/debian/changelog:

linux (4.6~rc3-1~exp1) experimental; urgency=medium

  * New upstream release candidate

  [ Ben Hutchings ]
  * aufs: Update support patches to aufs4.x-rcN-20160328

 -- Ben Hutchings   Thu, 14 Apr 2016 23:55:15 +0100
[...]

Stage at which it happens:

fakeroot debian/rules source
dh_testdir
/usr/bin/make -f debian/rules.gen source
make[1]: Entering directory '/usr/src/linux'
/usr/bin/make -f debian/rules.real source-featureset ABINAME='4.6.0-rc3'
FEATURESET='none' SOURCEVERSION='4.6~rc3-1~exp1' UPSTREAMVERSION='4.6-rc3'
VERSION='4.6'
make[2]: Entering directory '/usr/src/linux'
=> sed: can't read debian/build/build-tools/tools/usb/usbip/config.h: No
such file or directory <=this line at subject.
test -d .pc
set +e; QUILT_PC=.pc quilt unapplied --quiltrc - >/dev/null && echo 'Patch
series not fully applied'; test $? -eq 1
File series fully applied, ends at patch
bugfix/all/scripts-fix-x.509-pem-support-in-sign-file.patch
mkdir -p 'debian/build'
rm -f 'debian/build/source_none'
ln -s '/usr/src/linux' 'debian/build/source_none'
make[2]: Leaving directory '/usr/src/linux'
make[1]: Leaving directory '/usr/src/linux'

Similar message also was also a show stopper in a certain recent iteration
of linux/debian packaging from git.

Any insight appreciated.


Best Professional Regards.

-- 
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!

Bug#820038: Copy signatures into udebs

[Jose R R]

Thus, in practice it means that an out of Linux source tree module,
like Reiser4, will be a reason for Debian-Installer (d-i) to baulk at
install?

On Mon, Apr 4, 2016 at 4:02 PM, Ben Hutchings  wrote:
> Package: kernel-wedge
> Version: 2.94
> Severity: normal
>
> We will probably implement module signing using detached signatures
> which kmod will concatenate to the modules at load time (see #820010).
> mkinitramfs will need to copy the detached signatures along with all
> the modules it includes in each udeb.
>
> It might also be necessary to add special support for signed kernel
> images, although linux-signed may end up generating the udebs for
> that directly.
>
> Ben.
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages kernel-wedge depends on:
> ii  debhelper  9.20160313
> ii  make   4.1-9
>
> kernel-wedge recommends no packages.
>
> kernel-wedge suggests no packages.
>
> -- no debconf information
>



-- 
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!
-

Bug#819470: installation-reports: Reiser4 Software Format Release Number 4.0.1 kernel successfully installed on Debian Stretch

[Jose R R]

vices: B: EV=120013
/proc/bus/input/devices: B: KEY=40200 3803078f800d001 fedfffef
fffe
/proc/bus/input/devices: B: MSC=10
/proc/bus/input/devices: B: LED=7
/proc/bus/input/devices:
/proc/bus/input/devices: I: Bus=0003 Vendor=80ee Product=0021 Version=0110
/proc/bus/input/devices: N: Name="VirtualBox USB Tablet"
/proc/bus/input/devices: P: Phys=usb-:00:06.0-1/input0
/proc/bus/input/devices: S:
Sysfs=/devices/pci:00/:00:06.0/usb1/1-1/1-1:1.0/0003:80EE:0021.0001/input/input2
/proc/bus/input/devices: U: Uniq=
/proc/bus/input/devices: H: Handlers=mouse0
/proc/bus/input/devices: B: PROP=0
/proc/bus/input/devices: B: EV=1f
/proc/bus/input/devices: B: KEY=1f 0 0 0 0
/proc/bus/input/devices: B: REL=140
/proc/bus/input/devices: B: ABS=3
/proc/bus/input/devices: B: MSC=10
/proc/bus/input/devices:

-- System Information:
Debian Release: stretch/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.4.0-1+reiser4.0.1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)


-- 
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!

Re: SFRN 4.0.1 Reiser4-enabled netboot iso/USB

[Jose R R]

Rather than continue spamming this list(s) every time I build another
Reiser4 enabled iteration of fast changing Unstable (Sid)
Debian-Installer (d-i), I will just replace the resource(s) pointed by
the links:

https://metztli.it/readOnlyEphemeral/metztli.iso
https://metztli.it/readOnlyEphemeral/metztli.SHA256

If you download a Reiser4-enabled netboot image and, upon installation
procedure, Debian stops midway complaining about Packages.xz
(security) not being found and/or selected -- or unable to find
selected version, it is likely the case that Unstable (Sid) Debian is
in transition state and it takes a few days for the repositories to
stabilize again.

Accordingly, as Reiser4-enabled d-i aims at a fast moving target, if
you experience issues like those described, please wait a few days and
then download the ISO image again -- as more likely I will already
have upgraded the netboot ISO image to one that works. As I refine the
image, the build (and test install) may likely be automated so as to
decrease these transition nasty surprises.

On Thu, Mar 17, 2016 at 1:33 PM, Jose R R  wrote:
> Niltze, all!
>
> Reiser4 -enabled Debian-Installer with user selectable Reiser4-patched
> kernel has been submitted to an open minded media organization for
> evaluation:
>
> -- Forwarded message --
> From: Jose R Rodriguez 
> Date: Thu, Mar 17, 2016 at 4:47 AM
> Subject: Re: XXYYY.com Inquiry
> To: XX YYY 
>
>
> Good morning, XX-
>
> Here is a link to an approximately 42 MB Reiser4-enabled
> Debian-Installer (d-i) netboot: metztli.iso
> https://metztli.it/readOnlyEphemeral/metztli.iso
> https://metztli.it/readOnlyEphemeral/metztli.SHA256
>
> If you wanna burn the metztli.iso file to a USB device -- to boot from
> bare metal, for instance:
> (sudo) dd if=metztli.iso of=/dev/sdb bs=4M; sync
> where, of course, /dev/sdb represents your USB device
>
> I recommend doing an expert install from the d-i menu and to install
> Sid -- as d-i is gonna work until the next unstable kernel becomes
> default* (around the weekend). Of course, you may also fall back to
> Stretch -- but not Jessie (stable) as we are using unstable d-i.
>
> Most important: please create a small /boot partition (say 100 - 150
> MB formatted in ext2), since default GRUB2 installer does not
> recognize Reiser4.
>
> Note: since the metztli.iso image runs a streamlined (UDEB) custom
> reiser4-enabled kernel, please ignore the warning (as exemplified in
> snapshot attached). Thus, select yes to continue the install without
> loading (debian repository) kernel modules.
> https://pbs.twimg.com/media/CdxuY-EUEAAC398.jpg:large
>
> And finally when presented with menu list of Linux kernels AMD64
> available to install, of course, select "linux-reiser4-amd64." After a
> successful Debian installation, you'll find syslog at
> /var/log/installer.
>
> Thank you in advance, XX.
>
>
> Best Professional Regards.
>
> P.S Care has bee taken to provide a usable software -- as well as
> limited virtual and/or physical testing -- but as in all free
> software, no implicit and/or explicit warranties are offered by
> Metztli IT.
>

Best Professional Regards.


-- 
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!
-

SFRN 4.0.1 Reiser4-enabled netboot iso/USB

[Jose R R]

Niltze, all!

Reiser4 -enabled Debian-Installer with user selectable Reiser4-patched
kernel has been submitted to an open minded media organization for
evaluation:

-- Forwarded message --
From: Jose R Rodriguez 
Date: Thu, Mar 17, 2016 at 4:47 AM
Subject: Re: XXYYY.com Inquiry
To: XX YYY 


Good morning, XX-

Here is a link to an approximately 42 MB Reiser4-enabled
Debian-Installer (d-i) netboot: metztli.iso
https://metztli.it/readOnlyEphemeral/metztli.iso
https://metztli.it/readOnlyEphemeral/metztli.SHA256

If you wanna burn the metztli.iso file to a USB device -- to boot from
bare metal, for instance:
(sudo) dd if=metztli.iso of=/dev/sdb bs=4M; sync
where, of course, /dev/sdb represents your USB device

I recommend doing an expert install from the d-i menu and to install
Sid -- as d-i is gonna work until the next unstable kernel becomes
default* (around the weekend). Of course, you may also fall back to
Stretch -- but not Jessie (stable) as we are using unstable d-i.

Most important: please create a small /boot partition (say 100 - 150
MB formatted in ext2), since default GRUB2 installer does not
recognize Reiser4.

Note: since the metztli.iso image runs a streamlined (UDEB) custom
reiser4-enabled kernel, please ignore the warning (as exemplified in
snapshot attached). Thus, select yes to continue the install without
loading (debian repository) kernel modules.
https://pbs.twimg.com/media/CdxuY-EUEAAC398.jpg:large

And finally when presented with menu list of Linux kernels AMD64
available to install, of course, select "linux-reiser4-amd64." After a
successful Debian installation, you'll find syslog at
/var/log/installer.

Thank you in advance, XX.


Best Professional Regards.

P.S Care has bee taken to provide a usable software -- as well as
limited virtual and/or physical testing -- but as in all free
software, no implicit and/or explicit warranties are offered by
Metztli IT.


-- 
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!
-

Re: ata1.00: exception Emask 0x0 SAct 0x7f00000c SErr 0x0 action 0x6 frozen

[Jose R R]

Perhaps I spoke too soon, I have successfully selected (from the menu
of d-i) a Reiser4-enabled Linux kernel, built the 'Debian way', during
new Debian installation in a virtual environment:

Selecting a Reiser4-patched Linux Kernel From Reiser4-enabled
Debian-Installer (d-i) Menu

https://metztli.it/blog/index.php/ixiptli/aH3


Best Professional Regards.

On Fri, Mar 18, 2016 at 7:57 PM, Jose R R  wrote:
> Niltze, all-
>
> Any insight appreciated. Thank you.
>
> Using SFRN 4.0.1 Reiser4*-patched kernel source 4.4.6-2 UDEB in unstable d-i
> *(reiser4-for-4.4.0.patch.gz)
>
> It has already happened 3 times during my test install in VirtualBox
> 5.0.14 and 5.0.16
>
> [...]
> Mar 19 01:03:38 anna-install: Installing partman-auto-lvm
> Mar 19 01:03:38 anna[3589]: DEBUG: retrieving e2fsprogs-udeb
> 1.43~WIP.2016.03.15-2
> Mar 19 01:03:40 anna[3589]: DEBUG: retrieving lvm2-udeb 2.02.146-1
> Mar 19 01:03:42 anna[3589]: DEBUG: retrieving partman-auto-lvm 59
> Mar 19 01:03:43 anna[3589]: DEBUG: retrieving partman-lvm 112
> Mar 19 01:03:46 anna-install: Installing partman-auto-crypto
> Mar 19 01:03:46 anna[3736]: DEBUG: retrieving partman-auto-crypto 24
> Mar 19 01:03:48 anna[3736]: DEBUG: retrieving partman-crypto 87
> Mar 19 01:03:50 kernel: [  463.246921] ntfs: driver 2.1.32 [Flags: R/W 
> MODULE].
> Mar 19 01:03:51 kernel: [  463.323580] raid6: sse2x1   gen()  3377 MB/s
> Mar 19 01:03:51 kernel: [  463.402165] raid6: sse2x1   xor()  2977 MB/s
> Mar 19 01:03:51 kernel: [  463.472176] raid6: sse2x2   gen()  5881 MB/s
> Mar 19 01:03:51 kernel: [  463.543505] raid6: sse2x2   xor()  5213 MB/s
> Mar 19 01:03:51 kernel: [  463.622093] raid6: sse2x4   gen() 11703 MB/s
> Mar 19 01:03:51 kernel: [  463.692105] raid6: sse2x4   xor()  8443 MB/s
> Mar 19 01:03:51 kernel: [  463.692108] raid6: using algorithm sse2x4
> gen() 11703 MB/s
> Mar 19 01:03:51 kernel: [  463.692109] raid6:  xor() 8443 MB/s, rmw 
> enabled
> Mar 19 01:03:51 kernel: [  463.692111] raid6: using ssse3x2 recovery algorithm
> Mar 19 01:03:51 kernel: [  463.693511] xor: automatically using best
> checksumming function:
> Mar 19 01:03:51 kernel: [  463.762093]avx   : 39088.000 MB/sec
> Mar 19 01:03:51 kernel: [  463.773480] Btrfs loaded
> Mar 19 01:03:51 kernel: [  463.785316] JFS: nTxBlock = 7975, nTxLock = 63801
> Mar 19 01:03:51 kernel: [  463.797510] Loading Reiser4 (format
> release: 4.0.1) See www.namesys.com for a description of Reiser4.
> Mar 19 01:03:51 kernel: [  463.811589] SGI XFS with ACLs, security
> attributes, realtime, no debug enabled
> Mar 19 01:03:51 md-devices: mdadm: No arrays found in config file or
> automatically
> Mar 19 01:03:51 kernel: [  464.061106] device-mapper: uevent: version 1.0.3
> Mar 19 01:03:51 kernel: [  464.061349] device-mapper: ioctl:
> 4.34.0-ioctl (2015-10-28) initialised: dm-de...@redhat.com
> Mar 19 01:03:51 partman:   No matching physical volumes found
> Mar 19 01:03:51 partman:   Reading all physical volumes.  This may
> take a while...
> Mar 19 01:06:47 partman: mke2fs 1.43-WIP (15-Mar-2016)
> Mar 19 01:06:49 partman: mke2fs 1.43-WIP (15-Mar-2016)
> Mar 19 01:06:57 kernel: [  649.939221] reiser4: sda6: found disk format 4.0.1.
> Mar 19 01:06:57 kernel: [  649.950236] reiser4: sda6: using Hybrid
> Transaction Model.
> Mar 19 01:06:57 kernel: [  650.164258] EXT4-fs (sda1): mounting ext2
> file system using the ext4 subsystem
> Mar 19 01:06:57 kernel: [  650.205386] EXT4-fs (sda1): mounted
> filesystem without journal. Opts: (null)
> Mar 19 01:06:57 kernel: [  650.283688] EXT4-fs (sda5): mounted
> filesystem with ordered data mode. Opts: (null)
> Mar 19 01:06:58 apt-install: Queueing package e2fsprogs for later installation
> Mar 19 01:06:58 apt-install: Queueing package reiser4progs for later
> installation
> Mar 19 01:06:58 apt-install: Queueing package initramfs-tools for
> later installation
> Mar 19 01:06:58 apt-install: Queueing package linux-base for later 
> installation
> Mar 19 01:06:58 apt-install: Queueing package ca-certificates for
> later installation
> Mar 19 01:06:58 main-menu[3206]: (process:3575):
> /lib/partman/free_space/50new/do_option:
> Mar 19 01:06:58 main-menu[3206]: (process:3575): line 226:
> Mar 19 01:06:58 main-menu[3206]: (process:3575):
> /lib/partman/active_partition/copy/choices: not found
> Mar 19 01:06:58 main-menu[3206]: (process:3575):
> Mar 19 01:06:58 main-menu[3206]: (process:3575):
> /lib/partman/free_space/50new/do_option:
> Mar 19 01:06:58 main-menu[3206]: (process:3575): line 226:
> Mar 19 01:06:58 main-menu[3206]: (process:3575):
> /lib/partman/active_partition/copy/choices: not found
> Mar 19 01:06:58 main-menu[3206]: (process:3575):
> Mar 19 01:06:58 main-menu[3206]: (process:3575):
> /lib/part

ata1.00: exception Emask 0x0 SAct 0x7f00000c SErr 0x0 action 0x6 frozen

[Jose R R]

160.191000] wgetD
88003e215900 0 11559   9142 0x
Mar 19 01:32:07 kernel: [ 2160.191011]  88002d4a5100
81a11500 88002d048000 88003fad2150
Mar 19 01:32:07 kernel: [ 2160.191018]  d8ed
88003fad2178  88003c312380
Mar 19 01:32:07 kernel: [ 2160.191024]  8158b0e1
88003fad2108 a041cd7b 
Mar 19 01:32:07 kernel: [ 2160.191031] Call Trace:
Mar 19 01:32:07 kernel: [ 2160.191052]  [] ?
schedule+0x31/0x80
Mar 19 01:32:07 kernel: [ 2160.191094]  [] ?
reiser4_go_to_sleep+0x4b/0x90 [reiser4]
Mar 19 01:32:07 kernel: [ 2160.191105]  [] ?
wake_atomic_t_function+0x60/0x60
Mar 19 01:32:07 kernel: [ 2160.191139]  [] ?
capture_fuse_wait.part.28+0x155/0x160 [reiser4]
Mar 19 01:32:07 kernel: [ 2160.191169]  [] ?
atom_can_be_committed.part.14+0x10/0x10 [reiser4]
Mar 19 01:32:07 kernel: [ 2160.191196]  [] ?
reiser4_try_capture+0x56a/0xb30 [reiser4]
Mar 19 01:32:07 kernel: [ 2160.191205]  [] ?
__alloc_skb+0x60/0x1e0
Mar 19 01:32:07 kernel: [ 2160.191214]  [] ?
__raw_callee_save___pv_queued_spin_unlock+0x11/0x20
Mar 19 01:32:07 kernel: [ 2160.191241]  [] ?
longterm_lock_znode+0x163/0x4d0 [reiser4]
Mar 19 01:32:07 kernel: [ 2160.191272]  [] ?
cbk_cache_search+0x17a/0x280 [reiser4]
Mar 19 01:32:07 kernel: [ 2160.191300]  [] ?
reiser4_object_lookup+0xf2/0x160 [reiser4]
Mar 19 01:32:07 kernel: [ 2160.191337]  [] ?
reiser4_find_entry+0xca/0x360 [reiser4]
Mar 19 01:32:07 kernel: [ 2160.191347]  [] ?
ip_finish_output2+0x159/0x340
Mar 19 01:32:07 kernel: [ 2160.191387]  [] ?
reiser4_lookup_name+0x8d/0x140 [reiser4]
Mar 19 01:32:07 kernel: [ 2160.191435]  [] ?
reiser4_lookup_common+0x63/0x150 [reiser4]
Mar 19 01:32:07 kernel: [ 2160.191445]  [] ? d_alloc+0x55/0x60
Mar 19 01:32:07 kernel: [ 2160.191454]  [] ?
lookup_real+0x19/0x60
Mar 19 01:32:07 kernel: [ 2160.191461]  [] ?
path_openat+0xbbd/0x12f0
Mar 19 01:32:07 kernel: [ 2160.191468]  [] ?
do_filp_open+0x91/0x100
Mar 19 01:32:07 kernel: [ 2160.191476]  [] ?
__raw_callee_save___pv_queued_spin_unlock+0x11/0x20
Mar 19 01:32:07 kernel: [ 2160.191485]  [] ?
do_sys_open+0x139/0x220
Mar 19 01:32:07 kernel: [ 2160.191493]  [] ?
system_call_fast_compare_end+0xc/0x67


Best Professional Regards

-- 
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!
-

Debian progress in automatic download/install of Reiser4 AMD64 kernel

[Jose R R]

Niltze, all-

I have hacked (literally) additional UDEB components of the Unstable
Debian-Installer (d-i) which basically resolve the automatic
modification of /etc/initramfs-tools/modules, SSL download of the
Reiser4-enabled Linux kernel (from my site, as Debian.org and
Devuan.org obviously are not interested) and create initramfs with
Reiser4 support.

Below is my first custom Reiser4 installation into 'Necoc Yaotl' host
virtual machine -- 'remotely' ;-) via ssh -- from another virtual
machine (Cohuatlicue host); this latter executes the menu-driven
expert Debian-Installer (that's how I monitored the successful Reiser4
kernel installation procedure).

https://pbs.twimg.com/media/Cb-bQDRUkAAqD5H.png:large

Only requirement was not to select (any) default Debian kernel(s) from
menu *but* to select to install GRUB (option) to the virtual disk --
*even* if I had not selected any kernel to install. The finish-install
procedure [script(s)] at the end actually performed the 'magic' for
this Reiser4 support hack (took me a while, but worked :)

My next aim is to include the Reiser4 Kernel into the default
menu-driven d-i so as to allow the user to select it. And finally to
create Stable Debian (Jessie) images for a relatively normal user
installation of Reiser4 filesystem.


Best professional Regards.


-- 
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!
-

Reiser4 -enabled Debian Parted 3.2-15.1

[Jose R R]

Niltze-

Updated Reiser4 -enabled Debian Parted DEBs to reflect Sid 3.2-15 released
a couple of days ago. They are bundled in tar:

http://metztli.it/readOnlyEphemeral/debian-parted-3.2-15.1_reiser4.tar

If you need to build the UDEBs for d-i, updated source is at usual:

https://github.com/Metztli/debian-parted-reiser4


Best Professional Regards.

-- 
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!
-

Reiser4 -enabled Debian Parted 3.2-14

[Jose R R]

Niltze-

Updated Debian Parted DEBs to reflect latest debian release of GNU utility:

http://metztli.it/readOnlyEphemeral/debian-parted-3.2-14_reiser4.tar

If in addition to DEBs in tar above, you need to build the UDEBs with
Reiser4-support for Parted in d-i, here is Reiser4 -enabled source:

https://github.com/Metztli/debian-parted-reiser4


Best Professional Regards.

-- 
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!
-

Reiser4 -enabled Sid d-i and Reiser4 Patch for Debian Parted 3.2-13

[Jose R R]

Niltze, all-

Updated Debian version of GNU Parted DEBs:
https://metztli.it/readOnlyEphemeral/debian-parted-3.2-13_reiser4.tar

Reiser4 patch attached if you prefer to apply on your own from source
(and generate corresponding UDEBs):

git clone git://anonscm.debian.org/parted/debian/parted.git

Or already patched source from my Github repo:

https://github.com/Metztli/debian-parted-reiser4



Also, Reiser4 -enabled Debian-installer (d-i) needed to be updated, as
Reiser4-enabled parted is an essential component:

https://metztli.it/readOnlyEphemeral/metztli_it-reiser4_d-i_.01.iso

Your mileage may vary (YMMV), however I suggest installing Stretch
(testing) and/or Sid (unstable).

*If* at the Debian-Installer screen:

"Install the GRUB boot loader on a hard disk"
https://pbs.twimg.com/media/CY-XOmVU0AAkgxM.png:large

user opens another terminal and...
chroot /target
bash
cd /root
wget https://metztli.it/readOnlyEphemeral/linux-image-reiser4.tar

downloads latest available Reiser4 -enabled kernel.

can be untarred and dpkg -i linux-image*deb

*then* no longer is necessary to modify /etc/initramfs-tools/modules

as installation routine will take care of it at "Finish the installation"


Best Professional Regards.

-- 
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!
-


0001-Reiser4-enabled-Debian-version-of-GNU-Parted-patch.patch
Description: Binary data

Re: Reiser4-enabled Debian Unstable (Sid) netboot iso

[Jose R R]

On Mon, Jan 11, 2016 at 8:01 AM, Adam Wilson  wrote:
> On Mon, 11 Jan 2016 07:22:21 +0100
> Cyril Brulebois  wrote:
>
>> Adam Wilson  (2016-01-11):
>> > This is somewhat off-topic, but why was ReiserFS support removed
>> > from d-i? I am a big fan of Reiser3 personally, but I use XFS now.
>>
>> In linux's changelog:
>> | linux (3.10.1-1) unstable; urgency=low
>> | […]
>> |   * udeb: Remove obsolete and unsupported drivers and filesystems
>> | - Remove ppa from scsi-modules
>> | - Remove floppy-modules, irda-modules, parport-modules,
>> plip-modules, |   qnx4-modules, reiserfs-modules, ufs-modules
>> | […]
>> |  -- Ben Hutchings   Tue, 16 Jul 2013 02:06:53
>> +0100
>>
>> It seems it was already being phased out in d-i a few years before
>> that: https://www.debian.org/devel/debian-installer/News/2010/20101030
>
> That is interesting. I distinctly remember the 'ReiserFS' filesystem
> option being present in the Wheezy d-i. The description went something
> like this: 'Journaling filesystem created by Hans Reiser' or something
> along those lines. Your research has revealed otherwise- but I have my
> suspicions. I'm sure I didn't make up that experience.
>
> Perhaps I somehow inadvertently customised my copy of d-i or did an
> advanced install or something, but I doubt it. I was even more inept a
> year ago than I am now.
>
> Why was Reiser3 phased out? It wasn't *grossly* unstable or anything,
> and despite lack of maintenance it was still a good little filesystem
> that could have stayed for longer.
>
> And why UFS? It may be obsolete, but I should think it would be
> relatively stable. Surely a filesystem should only be removed when it
> is actually a steaming wreck,

"not just when the devs don't like it anymore."

You just hit the nail on the head ;-)
https://pbs.twimg.com/media/CWM_CVsUAAAqFSX.png:large

Seems only large organizations have the financial resources to
whitewash their monstrous past and have their code accepted. For an
unfortunate individual like Reiser, well, tough luck -- as FOSS' often
touted technical meritocracy of code selection process is simply
trumped over by a selective 'morality', selective 'altruism', and/or
'religious' (or X) other sort of *unspoken* agreement/fanaticism by
upstream maintainers (gate keepers?).
http://marc.info/?l=reiserfs-devel&m=144979771308703&w=2

Oh, yes, the 'extra cherry on top' by someone 'commenting' at the end
-- throwing extra dirt -- dissing the individual and/or his work/code.
That's the pattern I have observed.


Best Professional Regards.

-- 
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!
-

Re: Reiser4-enabled Debian Unstable (Sid) netboot iso

[Jose R R]

(Bonus) Reiser4 version 4.0.1 -enabled patch for Debian Linux kernel
packaging:

On Wed, Jan 6, 2016 at 2:19 AM, Jose R R  wrote:
> Niltze, all-
>
> I have been building iterations of Debian-Installer (d-i) enhanced
> with Reiser4 4.0.1 kernel, disk and filesystem utilities. Thus far I
> have used a local build on Debian Sid of VirtualBox 5.0.10 environment
> to test multiple Reiser4 installations.
>
> For flexibility, especially if you are testing in a VM, the following
> d-i options may help:
>
> -Network-console: continue installation remotely using SSH
> -Openssh-client-udeb: secure shell client for the Debian installer
>
> Now:
>
> d-i offers three(3) choices:
>
> Jessie (stable)
> Stretch (testing)
> Sid (unstable)
>
> I have verified that *all* can be installed from my custom Reiser4
> d-i; Nevertheless Jessie (stable) needs access to testing and/or
> unstable repositories added at /etc/apt/sources.list in order to
> fulfill dependencies of the unstable kernel in my d-i. Jessie (stable)
> also needs to have newer Reiser4 4.0.1 packages because d-i downloads
> the older (stable) version. I have covered *all* of Jessie conditions
> by building newer unstable versions of its requirements. The downside
> of it is that a user needs to manually intervene at the shell,
> possibly at the expert level.
>
> 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
>
> so that initramfs can be appropriately updated *before* rebooting the
> new Reiser4 installation.
>
> Note that GRUBX does not support booting from /boot Reiser4
> filesystem; accordingly, a small partition must be provisioned for
> booting into a Reiser4 -formatted root (/) partition. The d-i
> partman-reiser4 will format Reiser4 partitions thus:
>
> mkfs.reiser4 -yo "create=reg40" 
>
> Additionally, user may want to provision a /tmp in a non-Reiser4
> partition if the intention is to run MariaDB (MySQL) because -- at the
> very least -- the DB will complain about /tmp issues if it is
> formatted in Reiser4 --personal experience ;-)
>
> With the above said and warning that this is an alpha effort *without*
> any explicit and/or implied guarantee that will be risk-free, here is
> the current yield of of Reiser4 effort:
>
> Reiser4 -enabled Debian-Installer (d-i) netboot mini.iso renamed as:
> http://metztli.it/readOnlyEphemeral//metztli_it-reiser4_d-i.iso
>
> Reiser4 -enabled kernel & modules.README_1st:
>
http://metztli.it/readOnlyEphemeral/linux-image-4.3.0-1-amd64_4.3.3-5_amd64.tar
>
> Reiser4 -enabled Debian GNU Parted packages (install at the end of
> installation procedure); please note that those packages under
> reiser4-parted_3.2-12/misc are optional):
> http://metztli.it/readOnlyEphemeral/reiser4-parted_3.2-12.tar
> (after untarring above referenced, install as)
> cd reiser4-parted_3.2-12
> dpkg -i parted_3.2-12_amd64.deb libparted2_3.2-12_amd64.deb
>
> Next resource is only needed if Jessie was installed. Package below
> will replace the older Reiser4 file utilities:
> http://metztli.it/readOnlyEphemeral/reiser4progs-4.0.1.tar
>
> 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.
>
> With the previous statement said, and if anyone is willing, try the
> above Debian-Installer (d-i) resources while the kernel is fresh...
>
> Feedback and/or suggestions welcome.
>
>
> Best Professional Regards
>
>
> P.S I am already preparing some images for Google Compute Engine (GCE)
> < https://cloud.google.com/compute/ > to add to currently testing
> Reiser4 images created last year.
> --

Based on building a Reiser4 4.0.1 -patched Linux kernel the 'debian way'
(hack, literally -- but it works ;-) prior post:
https://metztli.it/blog/index.php/aH0?blog=4

Creates Reiser4 4.0.1 kernel module UDEB suitable for inclusion into
Debian-Installer (d-i); please, note that, as explained in the referenced
blog above, /usr/share/kernel-wedge/package-list
must also be modified in addition to this patch below attached:


-- 
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!
-


0001-Reiser4-support-for-Debian-AMD64-packaging-to-genera.patch
Description: Binary data

Re: Reiser4-enabled Debian Unstable (Sid) netboot iso

[Jose R R]

(3/3) Reiser4 version 4.0.1 -enabled patches for Debian Installer
components and/or userland utilities:

On Wed, Jan 6, 2016 at 2:19 AM, Jose R R  wrote:
> Niltze, all-
>
> I have been building iterations of Debian-Installer (d-i) enhanced
> with Reiser4 4.0.1 kernel, disk and filesystem utilities. Thus far I
> have used a local build on Debian Sid of VirtualBox 5.0.10 environment
> to test multiple Reiser4 installations.
>
> For flexibility, especially if you are testing in a VM, the following
> d-i options may help:
>
> -Network-console: continue installation remotely using SSH
> -Openssh-client-udeb: secure shell client for the Debian installer
>
> Now:
>
> d-i offers three(3) choices:
>
> Jessie (stable)
> Stretch (testing)
> Sid (unstable)
>
> I have verified that *all* can be installed from my custom Reiser4
> d-i; Nevertheless Jessie (stable) needs access to testing and/or
> unstable repositories added at /etc/apt/sources.list in order to
> fulfill dependencies of the unstable kernel in my d-i. Jessie (stable)
> also needs to have newer Reiser4 4.0.1 packages because d-i downloads
> the older (stable) version. I have covered *all* of Jessie conditions
> by building newer unstable versions of its requirements. The downside
> of it is that a user needs to manually intervene at the shell,
> possibly at the expert level.
>
> 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
>
> so that initramfs can be appropriately updated *before* rebooting the
> new Reiser4 installation.
>
> Note that GRUBX does not support booting from /boot Reiser4
> filesystem; accordingly, a small partition must be provisioned for
> booting into a Reiser4 -formatted root (/) partition. The d-i
> partman-reiser4 will format Reiser4 partitions thus:
>
> mkfs.reiser4 -yo "create=reg40" 
>
> Additionally, user may want to provision a /tmp in a non-Reiser4
> partition if the intention is to run MariaDB (MySQL) because -- at the
> very least -- the DB will complain about /tmp issues if it is
> formatted in Reiser4 --personal experience ;-)
>
> With the above said and warning that this is an alpha effort *without*
> any explicit and/or implied guarantee that will be risk-free, here is
> the current yield of of Reiser4 effort:
>
> Reiser4 -enabled Debian-Installer (d-i) netboot mini.iso renamed as:
> http://metztli.it/readOnlyEphemeral//metztli_it-reiser4_d-i.iso
>
> Reiser4 -enabled kernel & modules.README_1st:
> http://metztli.it/readOnlyEphemeral/linux-image-4.3.0-1-amd64_4.3.3-5_amd64.tar
>
> Reiser4 -enabled Debian GNU Parted packages (install at the end of
> installation procedure); please note that those packages under
> reiser4-parted_3.2-12/misc are optional):
> http://metztli.it/readOnlyEphemeral/reiser4-parted_3.2-12.tar
> (after untarring above referenced, install as)
> cd reiser4-parted_3.2-12
> dpkg -i parted_3.2-12_amd64.deb libparted2_3.2-12_amd64.deb
>
> Next resource is only needed if Jessie was installed. Package below
> will replace the older Reiser4 file utilities:
> http://metztli.it/readOnlyEphemeral/reiser4progs-4.0.1.tar
>
> 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.
>
> With the previous statement said, and if anyone is willing, try the
> above Debian-Installer (d-i) resources while the kernel is fresh...
>
> Feedback and/or suggestions welcome.
>
>
>
>
> P.S I am already preparing some images for Google Compute Engine (GCE)
> < https://cloud.google.com/compute/ > to add to currently testing
> Reiser4 images created last year.
> --

Reiser4 4.0.1 -enabled Reiser4progs utilities to manage Reiser4 4.0.1
derived creation, formatting, and partitioning. In addition to
generating the desired userland utilities for Debian (which are
already in Stretch & Sid debian repos), it creates UDEBs suitable for
inclusion in a Reiser4 4.0.1 -enabled Debian-Installer (d-i)

Patch inclueded in repo:
https://github.com/Metztli/debian-installer-reiser4progs

and attached patch below:

Best Professional Regards

-- 
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!
-


0001-Added-reiser4progs-support-to-generate-UDEBs-for-Deb.patch
Description: Binary data

Re: Reiser4-enabled Debian Unstable (Sid) netboot iso

[Jose R R]

(2/3) Reiser4 version 4.0.1 -enabled patches for Debian Installer
components and/or userland utilities:

On Wed, Jan 6, 2016 at 2:19 AM, Jose R R  wrote:
> Niltze, all-
>
> I have been building iterations of Debian-Installer (d-i) enhanced
> with Reiser4 4.0.1 kernel, disk and filesystem utilities. Thus far I
> have used a local build on Debian Sid of VirtualBox 5.0.10 environment
> to test multiple Reiser4 installations.
>
> For flexibility, especially if you are testing in a VM, the following
> d-i options may help:
>
> -Network-console: continue installation remotely using SSH
> -Openssh-client-udeb: secure shell client for the Debian installer
>
> Now:
>
> d-i offers three(3) choices:
>
> Jessie (stable)
> Stretch (testing)
> Sid (unstable)
>
> I have verified that *all* can be installed from my custom Reiser4
> d-i; Nevertheless Jessie (stable) needs access to testing and/or
> unstable repositories added at /etc/apt/sources.list in order to
> fulfill dependencies of the unstable kernel in my d-i. Jessie (stable)
> also needs to have newer Reiser4 4.0.1 packages because d-i downloads
> the older (stable) version. I have covered *all* of Jessie conditions
> by building newer unstable versions of its requirements. The downside
> of it is that a user needs to manually intervene at the shell,
> possibly at the expert level.
>
> 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
>
> so that initramfs can be appropriately updated *before* rebooting the
> new Reiser4 installation.
>
> Note that GRUBX does not support booting from /boot Reiser4
> filesystem; accordingly, a small partition must be provisioned for
> booting into a Reiser4 -formatted root (/) partition. The d-i
> partman-reiser4 will format Reiser4 partitions thus:
>
> mkfs.reiser4 -yo "create=reg40" 
>
> Additionally, user may want to provision a /tmp in a non-Reiser4
> partition if the intention is to run MariaDB (MySQL) because -- at the
> very least -- the DB will complain about /tmp issues if it is
> formatted in Reiser4 --personal experience ;-)
>
> With the above said and warning that this is an alpha effort *without*
> any explicit and/or implied guarantee that will be risk-free, here is
> the current yield of of Reiser4 effort:
>
> Reiser4 -enabled Debian-Installer (d-i) netboot mini.iso renamed as:
> http://metztli.it/readOnlyEphemeral//metztli_it-reiser4_d-i.iso
>
> Reiser4 -enabled kernel & modules.README_1st:
> http://metztli.it/readOnlyEphemeral/linux-image-4.3.0-1-amd64_4.3.3-5_amd64.tar
>
> Reiser4 -enabled Debian GNU Parted packages (install at the end of
> installation procedure); please note that those packages under
> reiser4-parted_3.2-12/misc are optional):
> http://metztli.it/readOnlyEphemeral/reiser4-parted_3.2-12.tar
> (after untarring above referenced, install as)
> cd reiser4-parted_3.2-12
> dpkg -i parted_3.2-12_amd64.deb libparted2_3.2-12_amd64.deb
>
> Next resource is only needed if Jessie was installed. Package below
> will replace the older Reiser4 file utilities:
> http://metztli.it/readOnlyEphemeral/reiser4progs-4.0.1.tar
>
> 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.
>
> With the previous statement said, and if anyone is willing, try the
> above Debian-Installer (d-i) resources while the kernel is fresh...
>
> Feedback and/or suggestions welcome.
>
>
> Best Professional Regards
>
>
> P.S I am already preparing some images for Google Compute Engine (GCE)
> < https://cloud.google.com/compute/ > to add to currently testing
> Reiser4 images created last year.

Reiser4 4.0.1 -patched partman-reiser4 component integrates Reiser4
support into menu-driven Debian-Installer (d-i) -- requires
reiser4-debian-parted

Included in repo:
https://github.com/Metztli/debian-partman-reiser4

This component source is hacked (literally) and does not exist
currently in Debian. It generates a UDEB that adds the Reiser4 option
to the Debian-Installer (d-i) menu. Please make sure to *also include*
in your d-i UDEBs generated from Reiser4 4.0.1 -enabled Debian.ized
GNU Parted; otherwise, d-i menu driven installation will fail.

-- 
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!
-

Re: Reiser4-enabled Debian Unstable (Sid) netboot iso

[Jose R R]

(1/3) Reiser4 version 4.0.1 -enabled patches for Debian Installer
components and/or userland utilities:

On Wed, Jan 6, 2016 at 2:19 AM, Jose R R  wrote:
> Niltze, all-
>
> I have been building iterations of Debian-Installer (d-i) enhanced
> with Reiser4 4.0.1 kernel, disk and filesystem utilities. Thus far I
> have used a local build on Debian Sid of VirtualBox 5.0.10 environment
> to test multiple Reiser4 installations.
>
> For flexibility, especially if you are testing in a VM, the following
> d-i options may help:
>
> -Network-console: continue installation remotely using SSH
> -Openssh-client-udeb: secure shell client for the Debian installer
>
> Now:
>
> d-i offers three(3) choices:
>
> Jessie (stable)
> Stretch (testing)
> Sid (unstable)
>
> I have verified that *all* can be installed from my custom Reiser4
> d-i; Nevertheless Jessie (stable) needs access to testing and/or
> unstable repositories added at /etc/apt/sources.list in order to
> fulfill dependencies of the unstable kernel in my d-i. Jessie (stable)
> also needs to have newer Reiser4 4.0.1 packages because d-i downloads
> the older (stable) version. I have covered *all* of Jessie conditions
> by building newer unstable versions of its requirements. The downside
> of it is that a user needs to manually intervene at the shell,
> possibly at the expert level.
>
> 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
>
> so that initramfs can be appropriately updated *before* rebooting the
> new Reiser4 installation.
>
> Note that GRUBX does not support booting from /boot Reiser4
> filesystem; accordingly, a small partition must be provisioned for
> booting into a Reiser4 -formatted root (/) partition. The d-i
> partman-reiser4 will format Reiser4 partitions thus:
>
> mkfs.reiser4 -yo "create=reg40" 
>
> Additionally, user may want to provision a /tmp in a non-Reiser4
> partition if the intention is to run MariaDB (MySQL) because -- at the
> very least -- the DB will complain about /tmp issues if it is
> formatted in Reiser4 --personal experience ;-)
>
> With the above said and warning that this is an alpha effort *without*
> any explicit and/or implied guarantee that will be risk-free, here is
> the current yield of of Reiser4 effort:
>
> Reiser4 -enabled Debian-Installer (d-i) netboot mini.iso renamed as:
> http://metztli.it/readOnlyEphemeral//metztli_it-reiser4_d-i.iso
>
> Reiser4 -enabled kernel & modules.README_1st:
> http://metztli.it/readOnlyEphemeral/linux-image-4.3.0-1-amd64_4.3.3-5_amd64.tar
>
> Reiser4 -enabled Debian GNU Parted packages (install at the end of
> installation procedure); please note that those packages under
> reiser4-parted_3.2-12/misc are optional):
> http://metztli.it/readOnlyEphemeral/reiser4-parted_3.2-12.tar
> (after untarring above referenced, install as)
> cd reiser4-parted_3.2-12
> dpkg -i parted_3.2-12_amd64.deb libparted2_3.2-12_amd64.deb
>
> Next resource is only needed if Jessie was installed. Package below
> will replace the older Reiser4 file utilities:
> http://metztli.it/readOnlyEphemeral/reiser4progs-4.0.1.tar
>
> 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.
>
> With the previous statement said, and if anyone is willing, try the
> above Debian-Installer (d-i) resources while the kernel is fresh...
>
> Feedback and/or suggestions welcome.
>
>
> Best Professional Regards
>
>
> P.S I am already preparing some images for Google Compute Engine (GCE)
> < https://cloud.google.com/compute/ > to add to currently testing
> Reiser4 images created last year.

Reiser4 version 4.0.1 -support for Debian.ized GNU Parted -- will
generate DEBs and UDEBs:

Already patched repo:
https://github.com/Metztli/reiser4-debian-parted

OR git clone git://git.debian.org/git/parted/parted.git
and apply patch attached


-- 
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!
-


0001-Reiser4-support-for-debian-parted-based-on-Bart-Hakv.patch
Description: Binary data

Re: Reiser4-enabled Debian Unstable (Sid) netboot iso

[Jose R R]

On Wed, Jan 6, 2016 at 7:20 AM, dimas  wrote:
> 2016-006 05:42 Jose R R  wrote:
>> 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.
> well, i see. right way, probably. but you can the needed hook in any 
> installion
> scripts that you modify anyhow. i think, you messed with any of those, yes?

This issue may be resolved subsequently -- although probably using a
procedure that occurs *earlier* than 'the hooks' :)
>
>> 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.
> ouch, didn't know that it has such a strict restrictions

Using the same Debian Sid Linux kernel source, I generated another
Reiser4-enabled kernel 'the Debian Way' -- but with a custom changelog
that clearly shows has Reiser4 super power :D
https://metztli.it/readOnlyEphemeral/linux-image-4.3.0-1+reiser4.0.1-amd64_4.3.3-5+reiser4.0.2_amd64.tar

Once installed into a Debian distro, a uname -a yields:

Linux [host] 4.3.0-1+reiser4.0.1-amd64 #1 SMP Debian
4.3.3-5+reiser4.0.1 (2016-01-07) x86_64 GNU/Linux

Hence *hold* is not necessary for said kernel.

>
>> 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:
> that's the option, yeah, but placing packages on hold can lead to some 
> expected
> dependecies conflicts in the future, and is generally rather "dirty" way. 
> using
> special package names like "parted-reiser4" is much clear anyhow, what is 
> more,
> you can easily run your local repo with r4-patched kernels/tools/libs, and it
> will be the most clear of obvious way for the enduser to keep all this stuff
> upgraded without worrying whether it's r4-patched stuff or not. this would be 
> a
> perfect variant, i think. user just install "linux--reiser4",
> "parted-...-reiser4" and "whatever--reiser4", and you just build new
> packages from time to time, and everyone have their stuff updated usual way.

Well renaming Debian GNU Parted can wait -- as it is optional for the
user *even* after Debian is installed; i.e., I have embedded the
Reiser4-enabled lib/parted[2] UDEB into previoulsy referenced
Debian-Installer (d-i) netboot ISO:
http://metztli.it/readOnlyEphemeral/metztli_it-reiser4_d-i.iso

Thanks for your suggestions, Dimas.


Best Professional Regards.

-- 
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!
-

Re: Reiser4-enabled Debian Unstable (Sid) netboot iso

[Jose R R]

On Wed, Jan 6, 2016 at 4:21 AM, dimas  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!
-

Reiser4-enabled Debian Unstable (Sid) netboot iso

[Jose R R]

Niltze, all-

I have been building iterations of Debian-Installer (d-i) enhanced
with Reiser4 4.0.1 kernel, disk and filesystem utilities. Thus far I
have used a local build on Debian Sid of VirtualBox 5.0.10 environment
to test multiple Reiser4 installations.

For flexibility, especially if you are testing in a VM, the following
d-i options may help:

-Network-console: continue installation remotely using SSH
-Openssh-client-udeb: secure shell client for the Debian installer

Now:

d-i offers three(3) choices:

Jessie (stable)
Stretch (testing)
Sid (unstable)

I have verified that *all* can be installed from my custom Reiser4
d-i; Nevertheless Jessie (stable) needs access to testing and/or
unstable repositories added at /etc/apt/sources.list in order to
fulfill dependencies of the unstable kernel in my d-i. Jessie (stable)
also needs to have newer Reiser4 4.0.1 packages because d-i downloads
the older (stable) version. I have covered *all* of Jessie conditions
by building newer unstable versions of its requirements. The downside
of it is that a user needs to manually intervene at the shell,
possibly at the expert level.

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

so that initramfs can be appropriately updated *before* rebooting the
new Reiser4 installation.

Note that GRUBX does not support booting from /boot Reiser4
filesystem; accordingly, a small partition must be provisioned for
booting into a Reiser4 -formatted root (/) partition. The d-i
partman-reiser4 will format Reiser4 partitions thus:

mkfs.reiser4 -yo "create=reg40" 

Additionally, user may want to provision a /tmp in a non-Reiser4
partition if the intention is to run MariaDB (MySQL) because -- at the
very least -- the DB will complain about /tmp issues if it is
formatted in Reiser4 --personal experience ;-)

With the above said and warning that this is an alpha effort *without*
any explicit and/or implied guarantee that will be risk-free, here is
the current yield of of Reiser4 effort:

Reiser4 -enabled Debian-Installer (d-i) netboot mini.iso renamed as:
http://metztli.it/readOnlyEphemeral//metztli_it-reiser4_d-i.iso

Reiser4 -enabled kernel & modules.README_1st:
http://metztli.it/readOnlyEphemeral/linux-image-4.3.0-1-amd64_4.3.3-5_amd64.tar

Reiser4 -enabled Debian GNU Parted packages (install at the end of
installation procedure); please note that those packages under
reiser4-parted_3.2-12/misc are optional):
http://metztli.it/readOnlyEphemeral/reiser4-parted_3.2-12.tar
(after untarring above referenced, install as)
cd reiser4-parted_3.2-12
dpkg -i parted_3.2-12_amd64.deb libparted2_3.2-12_amd64.deb

Next resource is only needed if Jessie was installed. Package below
will replace the older Reiser4 file utilities:
http://metztli.it/readOnlyEphemeral/reiser4progs-4.0.1.tar

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.

With the previous statement said, and if anyone is willing, try the
above Debian-Installer (d-i) resources while the kernel is fresh...

Feedback and/or suggestions welcome.


Best Professional Regards


P.S I am already preparing some images for Google Compute Engine (GCE)
< https://cloud.google.com/compute/ > to add to currently testing
Reiser4 images created last year.
-- 
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!
-

Re: Integrate fully partman-reiser4 into d-i

[Jose R R]

Niltze, everyone!

On Mon, Nov 16, 2015 at 7:37 AM, Jose R R  wrote:
> I hacked (literally) a preliminary version of the of GNU Parted 3.2
> source with Reiser4 support.
>
> On Thu, Nov 12, 2015 at 8:23 AM, Edward Shishkin
>  wrote:
>>
>>
>> On 11/12/2015 12:28 PM, Jose R R wrote:
>>>
>>> On Mon, Sep 21, 2015 at 7:49 AM, Edward Shishkin
>>>  wrote:
>>>>
>>>> On 09/21/2015 01:12 PM, Colin Watson wrote:
>>>>>
>>>>> On Sun, Sep 20, 2015 at 07:40:37AM -0700, Jose R R wrote:
>>>>>>
>>>>>> I have realized that although partman-reiser4 udeb enables Reiser4 to
>>>>>> be listed as an option during the Debian-Installer routine of a
>>>>>> netboot ISO image, the lack of support for reiser4 in GNU Parted
>>>>>> (Debian's libparted) prevents installation from the GUI interface.
>>>>>
>>>>> It should be pretty easy to add that to parted, since nowadays the only
>>>>> filesystem support it has is probing support.  I suggest preparing a
>>>>> patch against git://git.sv.gnu.org/parted.git master that adds the
>>>>> ability to detect existing reiser4 partitions and sending it upstream;
>>>>> it should only be on the order of a hundred lines.
>>>>
>>>>
>>>>
>>>> Does anybody care to prepare the patch?
>>>
>>> I am working on it Ed. I have been ironing out some wrinkles from the
>>> last Reiser4 patch proposed several years ago in the GNU Parted
>>> mailing lists. It's components and structure were basically cloned by
>>> the initial btrfs patch submitted to Debian. autoreconf has been my
>>> friend ;-)
>>>
>>>> I think we just need to a read a sector at REISER4_MAGIC_OFFSET
>>>> and check the magic string ("ReIsEr4"), see definition of the struct
>>>> reiser4_master_sb.
>>>
>>> Please enlighten me with reference to its documentation -- online or
>>> in the Reiser4 source code?
>>
>>
>> Alas, only source code..
>>
>> In reiser4 kernel sources look for REISER4_MAGIC_OFFSET
>> and REISER4_SUPER_MAGIC_STRING.
>>
>> In reiser4progs it is called REISER4_MASTER_OFFSET and
>> REISER4_MASTER_MAGIC respectively.
>>
>
> It can be built with the usual:
>
> apt-get install libdevmapper-dev
>
> ./configure [ --prefix=/opt/parted-3.2/usr/local ]
> make
> make install
>
> The resulting parted binary recognizes Reiser4 partitions when invoked
> at your shell:
> $ parted
> GNU Parted 3.2
> Using /dev/xda
> Welcome to GNU Parted! Type 'help' to view a list of commands.
> (parted) print
> And it will print recognized partitions -- including reiser4, of course.
>
> Although it was developed and tested in a local machine,
> I ran PoC build on small Google Compute Engine (GCE) Cloud instance
> with a couple of existing Reiser4 partitions:
>
> Snapshot:
> https://pbs.twimg.com/media/CT8U78zUwAE-ZTc.png:large
>
> Here is GNU Parted 3.2 bz2-compressed src modified for Reiser4 (in
> case I no longer have time to improve it ;-)
> Source: 2.6M reiser4-parted-3.2m.tar.bz2 @
> http://metztli.it/readOnlyEphemeral/reiser4-parted-3.2m.tar.bz2
> SHA256SUM:
> http://metztli.it/readOnlyEphemeral/reiser4-parted-3.2m.tar.bz2.SHA256SUM
>
>

Just to thank all of you for your insightful input on my quest to
create a Debian-Installer (d-i) network ISO image --hacked to natively
partition, format, and install in/to Reiser4 regular and/or
flash-based media.

As mentioned before, I hacked GNU Parted 3.2 to provide Reiser4
*string probe* support only. Subsequently generated appropriate UDEBs:

libparted2-udeb_3.2-10_amd64.udeb
parted-udeb_3.2-10_amd64.udeb
libparted-fs-resize0-udeb_3.2-10_amd64.udeb

By including the above in d-i, I would not get the weird gibberish
when selecting to format root (/) partition in Reiser4 during expert
installation. Notwithstanding, I encountered subsequent error and
thus...

I modified partman-reiser4-1, (yes again) last evening -- since I was
getting something similar to: "debian-installer: Installation freezes
with "The attempt to mount a files system with type ext4 in SCSI1 (0,
0, 0), partition #1 (sda) at / failed." <
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779922 > but, of
course, with reiser4 instead of ext4. Afterwards, I generated another
partman-reiser4_1_all.udeb

At this very moment the native Reiser4 installation is proceeding in a
VirtualBox instance. I did not have to do any unusual hacks to make
the Reiser4-based installation to proceed. Hence my 

Re: Integrate fully partman-reiser4 into d-i

[Jose R R]

I hacked (literally) a preliminary version of the of GNU Parted 3.2
source with Reiser4 support.

On Thu, Nov 12, 2015 at 8:23 AM, Edward Shishkin
 wrote:
>
>
> On 11/12/2015 12:28 PM, Jose R R wrote:
>>
>> On Mon, Sep 21, 2015 at 7:49 AM, Edward Shishkin
>>  wrote:
>>>
>>> On 09/21/2015 01:12 PM, Colin Watson wrote:
>>>>
>>>> On Sun, Sep 20, 2015 at 07:40:37AM -0700, Jose R R wrote:
>>>>>
>>>>> I have realized that although partman-reiser4 udeb enables Reiser4 to
>>>>> be listed as an option during the Debian-Installer routine of a
>>>>> netboot ISO image, the lack of support for reiser4 in GNU Parted
>>>>> (Debian's libparted) prevents installation from the GUI interface.
>>>>
>>>> It should be pretty easy to add that to parted, since nowadays the only
>>>> filesystem support it has is probing support.  I suggest preparing a
>>>> patch against git://git.sv.gnu.org/parted.git master that adds the
>>>> ability to detect existing reiser4 partitions and sending it upstream;
>>>> it should only be on the order of a hundred lines.
>>>
>>>
>>>
>>> Does anybody care to prepare the patch?
>>
>> I am working on it Ed. I have been ironing out some wrinkles from the
>> last Reiser4 patch proposed several years ago in the GNU Parted
>> mailing lists. It's components and structure were basically cloned by
>> the initial btrfs patch submitted to Debian. autoreconf has been my
>> friend ;-)
>>
>>> I think we just need to a read a sector at REISER4_MAGIC_OFFSET
>>> and check the magic string ("ReIsEr4"), see definition of the struct
>>> reiser4_master_sb.
>>
>> Please enlighten me with reference to its documentation -- online or
>> in the Reiser4 source code?
>
>
> Alas, only source code..
>
> In reiser4 kernel sources look for REISER4_MAGIC_OFFSET
> and REISER4_SUPER_MAGIC_STRING.
>
> In reiser4progs it is called REISER4_MASTER_OFFSET and
> REISER4_MASTER_MAGIC respectively.
>

It can be built with the usual:

apt-get install libdevmapper-dev

./configure [ --prefix=/opt/parted-3.2/usr/local ]
make
make install

The resulting parted binary recognizes Reiser4 partitions when invoked
at your shell:
$ parted
GNU Parted 3.2
Using /dev/xda
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
And it will print recognized partitions -- including reiser4, of course.

Although it was developed and tested in a local machine,
I ran PoC build on small Google Compute Engine (GCE) Cloud instance
with a couple of existing Reiser4 partitions:

Snapshot:
https://pbs.twimg.com/media/CT8U78zUwAE-ZTc.png:large

Here is GNU Parted 3.2 bz2-compressed src modified for Reiser4 (in
case I no longer have time to improve it ;-)
Source: 2.6M reiser4-parted-3.2m.tar.bz2 @
http://metztli.it/readOnlyEphemeral/reiser4-parted-3.2m.tar.bz2
SHA256SUM:
http://metztli.it/readOnlyEphemeral/reiser4-parted-3.2m.tar.bz2.SHA256SUM


Best Professional Regards.

-- 
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!
-

Re: Integrate fully partman-reiser4 into d-i

[Jose R R]

On Mon, Sep 21, 2015 at 7:49 AM, Edward Shishkin
 wrote:
> On 09/21/2015 01:12 PM, Colin Watson wrote:
>>
>> On Sun, Sep 20, 2015 at 07:40:37AM -0700, Jose R R wrote:
>>>
>>> I have realized that although partman-reiser4 udeb enables Reiser4 to
>>> be listed as an option during the Debian-Installer routine of a
>>> netboot ISO image, the lack of support for reiser4 in GNU Parted
>>> (Debian's libparted) prevents installation from the GUI interface.
>>
>> It should be pretty easy to add that to parted, since nowadays the only
>> filesystem support it has is probing support.  I suggest preparing a
>> patch against git://git.sv.gnu.org/parted.git master that adds the
>> ability to detect existing reiser4 partitions and sending it upstream;
>> it should only be on the order of a hundred lines.
>
>
>
> Does anybody care to prepare the patch?
I am working on it Ed. I have been ironing out some wrinkles from the
last Reiser4 patch proposed several years ago in the GNU Parted
mailing lists. It's components and structure were basically cloned by
the initial btrfs patch submitted to Debian. autoreconf has been my
friend ;-)

> I think we just need to a read a sector at REISER4_MAGIC_OFFSET
> and check the magic string ("ReIsEr4"), see definition of the struct
> reiser4_master_sb.
Please enlighten me with reference to its documentation -- online or
in the Reiser4 source code?

>> I'd be happy to cherry-pick such a patch into the Debian packaging once
>> it has been committed upstream.
>>
>
Best Professional Regards.


-- 
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!
-

Re: Integrate fully partman-reiser4 into d-i

[Jose R R]

I have realized that although partman-reiser4 udeb enables Reiser4 to
be listed as an option during the Debian-Installer routine of a
netboot ISO image, the lack of support for reiser4 in GNU Parted
(Debian's libparted) prevents installation from the GUI interface.

Moreover, it is clear that although btrfs came *after* Reiser4, the
former had the support of the debian installer team -- which produced
a patch relatively quickly-- but the latter was scorned for whatever
reason and/or undeserved reputation.

Accordingly, although I have been able to generate *all* required
UDEBs to enable the Debian-Installer to format and install Debian into
a Reiser4 root partition, using the GUI interface which makes use of
libparte to accomplish the task is not possible.

On the other hand, using my Reiser4-enabled Debian-Installer netboot
ISO image and selecting "expert install", I successfully installed
Debian into a root partition. Using the menu driven interface, I
initially formated the root partition into JFS -- to satisfy the
installer routine. Then, prior to the "install the base system" menu
option, I opened a shell and tarred the /target/etc/fstab, umounted
the JFS root partition, reformatted: mkfs.reiser4 -o "create=reg40"
/dev/sdaX

Subsequently mounted newly created Reiser4 root partition into
/target; untarred /target/etc/fstab and used nano editor to modify
/etc/fstab -- changing jfs to reiser4 and went back to "install the
base system" interactive menu. Thus Debian routine interface does not
notice the change and the base system installation continues.

There are still some wrinkles to iron out but hopefully I will later
make available a more polished d-i derived Reiser4 Debian-Installer.

Thank you all for your help.


Best Professional Regards.



On Fri, Aug 28, 2015 at 3:56 AM, Jose R R  wrote:
> Niltze, all!>
> (picking up where I left off in previous thread: <
> http://marc.info/?l=reiserfs-devel&m=144040412406067&w=2 >
>
> Initiating a new thread since Debian-Installer's partman-reiser4 seems
> to be partially functioning. All the previous Reiser4 issues have been
> mostly resolved.
>
> So I cloned partman-jfs udeb source into partman-reiser4 udeb (seems
> reiserfs udeb has gotten old) and I modified relevant scripts.
>
> However, I need to fine tune those modified scripts specifically for
> reiser4 in d-i *and* there is where I need your insight.
>
> Basically, option to format device media into Reiser4 is now available
> during relevant d-i phase:
> < https://pbs.twimg.com/media/CNfOQw1VEAEYBUk.png:large >
>
> Nevertheless, I get this gibberish dialog when selecting and
> proceeding (by pressing enter):
> < https://pbs.twimg.com/media/CNfOQ4kUcAAK0Tx.png:large >
>
> If I select continue at the "??? ???" gibberish dialog, d-i is
> apparently able to go to the Partition Settings phase:
> < https://pbs.twimg.com/media/CNfOQpWUYAA8tqY.png:large >
>
> Selecting "Done setting up the partition", notwithstanding, d-i
> returns to initial phase where raw virtual device has not even been
> initiated (with MBR)
>
> Cool thing is partman-reiser4 now makes the Reiser4-patched kernel
> automatically modprobe reiser4-modules:
> < https://pbs.twimg.com/media/CNfOQwxUwAEHh68.png:large >
>
> I have at d-i build/localudebs:
> [...]
> localudebs/mkreiser4-udeb_1.0.9-2_amd64.udeb
> localudebs/reiser4-modules-4.1.0-2-amd64-di_4.1.6-1_amd64.udeb
> localudebs/reiser4progs-udeb_1.0.9-2_amd64.udeb
> localudebs/partman-reiser4_1_all.udeb
> [...]
>
> and added at d-i build/pkg-lists/netboot/amd64.cfg:
> [...]
> fat-modules-${kernel:Version}
> ext4-modules-${kernel:Version}
> jfs-modules-${kernel:Version}
> reiser4-modules-${kernel:Version}
> mkreiser4-udeb
> reiser4progs-udeb
> partman-reiser4
> [...]
>
> Note: without partman-reiser4 specified above, d-i will not show
> option to format in Reiser4 -- even if reiser4 UDEB is included under
> build/localudebs/
>
> Advice welcomed in advance to make the gibberish dialog go away and to
> effectively allow d-i routine to integrate reiser4 fully so as to
> complete the front-end formatting proceduere.
>
>
> Best Professional Regards.
>
>
> --
> 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!
> -



-- 
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!
-

Re: Reiser4: Format 4.0.1: Meta(data) checksums

[Jose R R]

On Thu, Sep 17, 2015 at 8:56 AM, Ivan Shapovalov  wrote:
> On 2015-09-17 at 05:10 -0700, Jose R R wrote:
>> On Sun, Sep 13, 2015 at 6:06 AM, Ivan Shapovalov <
>> intelfx...@gmail.com> wrote:
>> > On 2015-09-13 at 05:57 -0700, Jose R R wrote:
>> > > Here is some additional info:
>> > >
>> > > A while back, I installed Debian Jessie AMD64 into a KVM virtual
>> > > machine and also included the initial non-systemd boot argument:
>> > > preseed/late_command="in-target apt-get install -y sysvinit-core"
>> > > < https://wiki.debian.org/systemd#Installing_without_systemd >
>> > >
>> > > Afterwards a previous reiser4-patched Linux kernel 4.0.x was
>> > > installed
>> > > into the virtual machine and its root fs was subsequently
>> > > formatted
>> > > to
>> > > reiser4.. The virtual machine was working fine:
>> > > < https://pbs.twimg.com/media/CKIKgoZUAAIFx12.png:large >
>> > >
>> > > Yesterday, I installed into the vm a newer 4.1.6 kernel built
>> > > "the
>> > > debian way" except that it was customized with the newer 4.0.1
>> > > Reiser4
>> > > patch. Upon rebooting the VM, I captured a sequence of 4
>> > > snapshots
>> > > (by
>> > > paging down) that basically recreate the fail that I experienced
>> > > priorly in the physical machine:
>> > >
>> > > < https://metztli.it/blog/index.php/ixiptli/non-systemd-debian-si
>> > > d-re
>> > > iser4 >
>> > >
>> > > Accordingly, seems the *lack of systemd* is enough for a Debian
>> > > Sid
>> > > instance to create a bad initrd.img. I have no idea if issue only
>> > > appears with Reiser4 root fs or if it includes other file systems
>> > > as
>> > > root. Work in progress...
>> >
>> > It's presence/absence of crc32c module that matters. Reiser4 does
>> > not
>> > specify that it needs one.
>> >
>> Applied your 3 patches
>> 1/3 < http://marc.info/?l=reiserfs-devel&m=144218573602435&w=2 >
>> 2/3 < http://marc.info/?l=reiserfs-devel&m=144218573602436&w=2 >
>> 3/3 < http://marc.info/?l=reiserfs-devel&m=144218573702437&w=2 >
>>
>> into kernel.org Linux Kernel 4.1.7, but Non-systemd Debian still
>> boots
>> into an emergency shell
>> [...]
>> mount: mounting /dev/sdaX on /root failed: no such file or directory
>> Target fileystem doesn't have requested /sbin/init
>> mount: mounting /dev on /root/dev failed: no such file or directory
>> No init found. Try passing init= bootarg.
>> [...]
>
> Correct; it's now a "cleanly" reported error instead of an oops.
> You will have to manually add crc32c or crc32c_intel module to the
> initramfs, though. I could not find a way to express an explicit
> intermodule dependency in the code (to make module reiser4 depend on
> module crc32c).
>
> Edward's patch selects module crc32c when reiser4 is selected in the
> build config, but it does not make sure that crc32c will end up in the
> initramfs if reiser4 is there (that is, modules.dep will not be
> altered). I'm still wondering how to do that properly.
>
I applied Ed's patch, as well
< http://marc.info/?l=reiserfs-devel&m=144250028326153&w=2 >
but the non-systemd Debian instance continued to generate a bad initrd.img-.

Notwithstanding, based on your suggestions, Ivan, the solution that
works for non-systemd system is to include module directive
crc32c_intel right *before* module reiser4 directive in debian's
/etc/initramfs-tools/modules file, thus:
[...]
crc32c_intel
reiser4
[...]

and those modules will be included during initramfs-tools creation of
initrd.img- file.

Thus, for a new Reiser4(4.0.1)-patched kernel image created "the
debian way", having an initrd image like: initrd.img-4.1.0-2-amd64,

update-initramfs -dk 4.1.0-2-amd64  # Removes (-d) an existing version
(-k) initramfs
update-initramfs -ck 4.1.0-2-amd64   # Creates (-c) a new version (-k) initramfs

Thus, the non-systemd Debian will generate a proper
initrd.img- which will contain *both* sequenced modules *and*
will be able to successfully boot the sysvinit-based system.

I have been running a small PoC non-systemd Debian Jessie, with
Reiser4-patched Linux kernel, on Google Compute Engine (GCE)
infrastructure for over two months now[1].

< https://pbs.twimg.com/media/CPWcGMQVEAElVdi.png:large >

And I was concerned about its survival if this issue persisted.

Thank you all.


Best Professional Regards.


[1]< http://marc.info/?l=reiserfs-devel&m=143237396102328&w=2 >


-- 
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!

Re: Reiser4: Format 4.0.1: Meta(data) checksums

[Jose R R]

On Sun, Sep 13, 2015 at 6:06 AM, Ivan Shapovalov  wrote:
> On 2015-09-13 at 05:57 -0700, Jose R R wrote:
>> Here is some additional info:
>>
>> A while back, I installed Debian Jessie AMD64 into a KVM virtual
>> machine and also included the initial non-systemd boot argument:
>> preseed/late_command="in-target apt-get install -y sysvinit-core"
>> < https://wiki.debian.org/systemd#Installing_without_systemd >
>>
>> Afterwards a previous reiser4-patched Linux kernel 4.0.x was
>> installed
>> into the virtual machine and its root fs was subsequently formatted
>> to
>> reiser4.. The virtual machine was working fine:
>> < https://pbs.twimg.com/media/CKIKgoZUAAIFx12.png:large >
>>
>> Yesterday, I installed into the vm a newer 4.1.6 kernel built "the
>> debian way" except that it was customized with the newer 4.0.1
>> Reiser4
>> patch. Upon rebooting the VM, I captured a sequence of 4 snapshots
>> (by
>> paging down) that basically recreate the fail that I experienced
>> priorly in the physical machine:
>>
>> < https://metztli.it/blog/index.php/ixiptli/non-systemd-debian-sid-re
>> iser4 >
>>
>> Accordingly, seems the *lack of systemd* is enough for a Debian Sid
>> instance to create a bad initrd.img. I have no idea if issue only
>> appears with Reiser4 root fs or if it includes other file systems as
>> root. Work in progress...
>
> It's presence/absence of crc32c module that matters. Reiser4 does not
> specify that it needs one.
>
Applied your 3 patches
1/3 < http://marc.info/?l=reiserfs-devel&m=144218573602435&w=2 >
2/3 < http://marc.info/?l=reiserfs-devel&m=144218573602436&w=2 >
3/3 < http://marc.info/?l=reiserfs-devel&m=144218573702437&w=2 >

into kernel.org Linux Kernel 4.1.7, but Non-systemd Debian still boots
into an emergency shell
[...]
mount: mounting /dev/sdaX on /root failed: no such file or directory
Target fileystem doesn't have requested /sbin/init
mount: mounting /dev on /root/dev failed: no such file or directory
No init found. Try passing init= bootarg.
[...]

Typing dmesg:
[...]
reiser4[exe(801)]: reiser4_init_csum_tfm
(fs/reiser4/checksum.c:11)[intelfx-81]:WARNING: Could not load crc32c
driver

In a couple of days I will build the kernel "the Debian way"; I will
specify -- in relevant module section, at file [kernel source
tree]debian/installer/package-list:
[...]

Package: reiser4-modules
Depends: kernel-image crc-modules # <--- will add that
Priority: extra
Description: Reiser4 filesystem support
 This package contains the Reiser4 filesystem module for the kernel.
[...]

As well as at /usr/share/kernel-wedge/package-list

We will see what happens.


> --
> Ivan Shapovalov / intelfx /
>



-- 
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!

Re: Reiser4: Format 4.0.1: Meta(data) checksums

[Jose R R]

Here is some additional info:

A while back, I installed Debian Jessie AMD64 into a KVM virtual
machine and also included the initial non-systemd boot argument:
preseed/late_command="in-target apt-get install -y sysvinit-core"
< https://wiki.debian.org/systemd#Installing_without_systemd >

Afterwards a previous reiser4-patched Linux kernel 4.0.x was installed
into the virtual machine and its root fs was subsequently formatted to
reiser4.. The virtual machine was working fine:
< https://pbs.twimg.com/media/CKIKgoZUAAIFx12.png:large >

Yesterday, I installed into the vm a newer 4.1.6 kernel built "the
debian way" except that it was customized with the newer 4.0.1 Reiser4
patch. Upon rebooting the VM, I captured a sequence of 4 snapshots (by
paging down) that basically recreate the fail that I experienced
priorly in the physical machine:

< https://metztli.it/blog/index.php/ixiptli/non-systemd-debian-sid-reiser4 >

Accordingly, seems the *lack of systemd* is enough for a Debian Sid
instance to create a bad initrd.img. I have no idea if issue only
appears with Reiser4 root fs or if it includes other file systems as
root. Work in progress...

On Thu, Sep 10, 2015 at 5:10 AM, Ivan Shapovalov  wrote:
> On 2015-09-10 at 04:57 -0700, Jose R R wrote:
>> On Wed, Sep 9, 2015 at 6:16 AM, Ivan Shapovalov > > wrote:
>> > On 2015-09-09 at 00:54 -0700, Jose R R wrote:
>> > > Scratch my previous issue, Ed. It is *not* related to your new
>> > > Reiser4
>> > > software release 4.0.1 module nor reiser4progs.
>> > >
>> > > My usual development environment is a modified non-systemd Debian
>> > > Sid
>> > > (unstable) on a Reiser4 root partition. The kernels built won't
>> > > boot
>> > > in *that* particular instance due to a least one other additional
>> > > issue:
>> > > target filesystem does not have requested /sbin/init
>> >
>> > Could you please elaborate?
>>
>> I can only describe what's going on; still searching for a solution
>> myself.
>>
>> < http://without-systemd.org/wiki/index.php/Main_Page >
>>
>> initrd.imgs created within a debian Sid environment -- with systemd
>> replaced by init -- will fail to mount new reiser4 root file system
>> during boot; whereas,
>> initrd.imgs created within a debian Sid environment -- with systemd -
>> -
>> will mount *any* (systemd and non-systemd) new reiser4 root fs and
>> boots system -- as it should.
>>
>> Issue closely resembles recent ZFS issue <
>> https://github.com/zfsonlinux/zfs/issues/3605 > except that, in this
>> non-systemd particular case, neither mkinitramfs-tools nor
>> dracut-created initrd.imgs are successful.
>>
>> As I am running a couple of more or less similar AMD64 Debian Sid on
>> Reiser4 root fs, I built the initrd.img for a non-systemd Debian Sid
>> inside the environment of a systemd Debian Sid.
>>
>> I already disassembled an older 3.xy.z initrd and compared its
>> contents with a initrd.img 4.1.6 built into this non-systemd Debian
>> Sid but file trees appears similar.
>>
>> < http://linux.koolsolutions.com/2009/11/12/initramfs-ramfs-tmpfs-com
>> pressed-image/
>> >
>>
>> Thus, a kernel I built in this non-systemd environment (Sept. 07,
>> 2015) can be installed in a systemd environment and it will boot;
>> moreover, I can take the initrd.img produced in the systemd
>> enviroment
>> (during kernel installation) and use it to boot this non-systemd
>> system -- and will proceed smoothly into its new Reiser4 4.0.1 root
>> fs.
>>
>> < https://pbs.twimg.com/media/COiiyUtUkAAw95X.png:large >
>>
>
> Very interesting, thanks for the observations. I'm surprised with the
> fact that systemd makes a difference here...
>
> --
> Ivan Shapovalov / intelfx /
>



-- 
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!

Integrate fully partman-reiser4 into d-i

[Jose R R]

Niltze, all!>
(picking up where I left off in previous thread: <
http://marc.info/?l=reiserfs-devel&m=144040412406067&w=2 >

Initiating a new thread since Debian-Installer's partman-reiser4 seems
to be partially functioning. All the previous Reiser4 issues have been
mostly resolved.

So I cloned partman-jfs udeb source into partman-reiser4 udeb (seems
reiserfs udeb has gotten old) and I modified relevant scripts.

However, I need to fine tune those modified scripts specifically for
reiser4 in d-i *and* there is where I need your insight.

Basically, option to format device media into Reiser4 is now available
during relevant d-i phase:
< https://pbs.twimg.com/media/CNfOQw1VEAEYBUk.png:large >

Nevertheless, I get this gibberish dialog when selecting and
proceeding (by pressing enter):
< https://pbs.twimg.com/media/CNfOQ4kUcAAK0Tx.png:large >

If I select continue at the "??? ???" gibberish dialog, d-i is
apparently able to go to the Partition Settings phase:
< https://pbs.twimg.com/media/CNfOQpWUYAA8tqY.png:large >

Selecting "Done setting up the partition", notwithstanding, d-i
returns to initial phase where raw virtual device has not even been
initiated (with MBR)

Cool thing is partman-reiser4 now makes the Reiser4-patched kernel
automatically modprobe reiser4-modules:
< https://pbs.twimg.com/media/CNfOQwxUwAEHh68.png:large >

I have at d-i build/localudebs:
[...]
localudebs/mkreiser4-udeb_1.0.9-2_amd64.udeb
localudebs/reiser4-modules-4.1.0-2-amd64-di_4.1.6-1_amd64.udeb
localudebs/reiser4progs-udeb_1.0.9-2_amd64.udeb
localudebs/partman-reiser4_1_all.udeb
[...]

and added at d-i build/pkg-lists/netboot/amd64.cfg:
[...]
fat-modules-${kernel:Version}
ext4-modules-${kernel:Version}
jfs-modules-${kernel:Version}
reiser4-modules-${kernel:Version}
mkreiser4-udeb
reiser4progs-udeb
partman-reiser4
[...]

Note: without partman-reiser4 specified above, d-i will not show
option to format in Reiser4 -- even if reiser4 UDEB is included under
build/localudebs/

Advice welcomed in advance to make the gibberish dialog go away and to
effectively allow d-i routine to integrate reiser4 fully so as to
complete the front-end formatting proceduere.


Best Professional Regards.


-- 
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!
-

Re: "No kernel modules were found" netboot d-i with custom reiser4 kernel.

[Jose R R]

Niltze, all!


On Thu, Aug 13, 2015 at 3:20 AM, Ben Hutchings  wrote:
> On Thu, 2015-08-13 at 02:45 -0700, Jose R R wrote:
> [...]
>> QUESTION:
>> How do I specify -- prior to building a reiser4-patched kernel the
>> 'debian way' -- a directive to build the *extra* reiser4 module  UDEB?
>>
>> Before/After specifying reiser4 as a module in .config (i.e., make -C
>> debian/build/build_amd64_none_amd64 menuconfig ), I have tried adding
>> the reiser4 directive to the debian/rules.gen inside the kernel tree
>> source -- still it does not generate a reiser4 module UDEB.
> [...]
>
> Look under debian/installer in the linux source package and read the
> kernel-wedge documentation.
>

After some effort, I was successful in creating the *extra*
reiser4-modules UDEB:
reiser4-modules-4.1.0-2-amd64-di_4.1.5-2_amd64.udeb
for
kernel-image-4.1.0-2-amd64-di_4.1.5-2_amd64.udeb

I included relevant directives in the build/pkg-lists/netboot/amd64.cfg, thus:
[...]
fat-modules-${kernel:Version}
ext4-modules-${kernel:Version}   # Without this, d-i won't know about Ext2/3/4
jfs-modules-${kernel:Version}  # Without this, d-i won't know about JFS
reiser4-modules-${kernel:Version} # Thus I thought this would allow
d-i to *know* about reiser4
mkreiser4-udeb   # This provides mkfs.reiser4 to d-i
reiser4progs-udeb# This provides fsck.reiser4 to d-i
[...]

After "make build_netboot" finished and tested the installation mini.iso:

lsmod: shows reiser4 module (which I loaded manually from the d-i shell utility)
https://pbs.twimg.com/media/CNKHCDyUkAA0lic.png:large

However d-i partman still does not recognize the reiser4-formatted partition:
https://pbs.twimg.com/media/CNKHCDmUcAAc6pT.png:large

Which means, I now should attempt to create a partman-reiser4 udeb for d-i?

Thank you for all your help and I appreciate your hints and suggestions.


Best professional Regards.


-- 
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!
-

Re: "No kernel modules were found" netboot d-i with custom reiser4 kernel.

[Jose R R]

On Thu, Jul 30, 2015 at 10:49 PM, Jose R R  wrote:
> On Wed, Jul 29, 2015 at 8:00 AM, Cyril Brulebois  wrote:
>> Hi,
>>
>> Jose R R  (2015-07-29):
>>> Niltze, all-
>>>
>>> Building kernel the 'Debian way':
>>>
>>> Replaced abi string at debian/config/defines (from default value of 2)
>>> to a more descriptive string:
>>>
>>> [abi]
>>> abiname: reiser4
>>>
>>> (guided by hint that debian devs sometimes set abiname string "trunk")
>>>
>>> Everything builds beautifully, especially UDEBs for modules/kernel
>>> like couple shown below:
>>> [...]
>>>
>>> 3.7M  kernel-image-4.0.0-reiser4-amd64-di_4.0.8-2_amd64.udeb
>>> 34M   linux-image-4.0.0-reiser4-amd64_4.0.8-2_amd64.deb
>>>
>>> Once kernel build is finished, I place the approxiamately 54 generated
>>> UDEBs at the installer/build/localudebs directory and modify
>>> installer/build/config/amd64.cfg
>>>
>>> # The version of the kernel to use.
>>> ## KERNELVERSION = $(LINUX_KERNEL_ABI)-amd64
>>> KERNELVERSION = 4.0.0-reiser4-amd64
>>> ## KERNELMAJOR = 2.6
>>> KERNELMAJOR = 4.0
>>> KERNELNAME = vmlinuz
>>>
>>> save modifications and execute command:
>>> make build_netboot-gtk
>>>
>>> The resulting netboot d-i iso image uses the custom kernel to start
>>> the Debian installation -- as can be verified by executing in an
>>> alternate shell: uname -a:
>>> Linux [host] 4.0.0-reiser4-amd64 #1 SMP Debian 4.0.8-2 (2015-07-22)
>>> x86_64 GNU/Linux;
>>>
>>> nevertheless stops at 'no kernel modules were found' and thus d-i can
>>> not proceed further to install custom built kernel with reiser4
>>> built-into-the-kernel support -- much less to detect/format a
>>> disk/partition win Reiser4.
>>>
>>> https://pbs.twimg.com/media/CK-ZehmUwAAjx-V.png:large
>>>
>>> Any insight provided will be appreciated. Thanks in advance.
>>
>> Stuff you put under localudebs/ is only used to replace/complement
>> what's in the archive if something pulls it in. You probably want to
>> add some packages to some list under build/pkg-lists.
>
I am making progress as I have built UDEBs for mkfs.reiser4 and fsck.reiser4:
mkreiser4-udeb_1.0.9-2_amd64.udeb
reiser4progs-udeb_1.0.9-2_amd64.udeb

which in turn I have also placed under build/localudebs.

Prior to d-i's: make build_netboot,

I have also specified at build/pkg-lists/netboot/amd64.cfg

mkreiser4-udeb
reiser4progs-udeb
...
ext4-modules-${kernel:Version}
jfs-modules-${kernel:Version}

the above ext/jfs module UDEBs were generated automatically by
building kernel the 'Debian way', but...

QUESTION:
How do I specify -- prior to building a reiser4-patched kernel the
'debian way' -- a directive to build the *extra* reiser4 module  UDEB?

Before/After specifying reiser4 as a module in .config (i.e., make -C
debian/build/build_amd64_none_amd64 menuconfig ), I have tried adding
the reiser4 directive to the debian/rules.gen inside the kernel tree
source -- still it does not generate a reiser4 module UDEB.

It seems the reiser4 module is needed for the d-i to format and
recognize reiser4. Note that by Ctrl -Alt -Fn I am able to go under
the installer shell and format in reiser4 and subsequently modify the
/etc/fstab from an di-JFS-formatted partition --using nano;
subsequently the installer will continue the installation of Debian
into reiser4-formatted media *unaware* that it was *tricked*.

< https://pbs.twimg.com/media/CMR2xY_UEAAA4M3.png:large >

Thanks in advance for any insight.


Best Professional Regards.

-- 
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!
-

Re: "No kernel modules were found" netboot d-i with custom reiser4 kernel.

[Jose R R]

On Wed, Jul 29, 2015 at 8:00 AM, Cyril Brulebois  wrote:
> Hi,
>
> Jose R R  (2015-07-29):
>> Niltze, all-
>>
>> Building kernel the 'Debian way':
>>
>> Replaced abi string at debian/config/defines (from default value of 2)
>> to a more descriptive string:
>>
>> [abi]
>> abiname: reiser4
>>
>> (guided by hint that debian devs sometimes set abiname string "trunk")
>>
>> Everything builds beautifully, especially UDEBs for modules/kernel
>> like couple shown below:
>> [...]
>>
>> 3.7M  kernel-image-4.0.0-reiser4-amd64-di_4.0.8-2_amd64.udeb
>> 34M   linux-image-4.0.0-reiser4-amd64_4.0.8-2_amd64.deb
>>
>> Once kernel build is finished, I place the approxiamately 54 generated
>> UDEBs at the installer/build/localudebs directory and modify
>> installer/build/config/amd64.cfg
>>
>> # The version of the kernel to use.
>> ## KERNELVERSION = $(LINUX_KERNEL_ABI)-amd64
>> KERNELVERSION = 4.0.0-reiser4-amd64
>> ## KERNELMAJOR = 2.6
>> KERNELMAJOR = 4.0
>> KERNELNAME = vmlinuz
>>
>> save modifications and execute command:
>> make build_netboot-gtk
>>
>> The resulting netboot d-i iso image uses the custom kernel to start
>> the Debian installation -- as can be verified by executing in an
>> alternate shell: uname -a:
>> Linux [host] 4.0.0-reiser4-amd64 #1 SMP Debian 4.0.8-2 (2015-07-22)
>> x86_64 GNU/Linux;
>>
>> nevertheless stops at 'no kernel modules were found' and thus d-i can
>> not proceed further to install custom built kernel with reiser4
>> built-into-the-kernel support -- much less to detect/format a
>> disk/partition win Reiser4.
>>
>> https://pbs.twimg.com/media/CK-ZehmUwAAjx-V.png:large
>>
>> Any insight provided will be appreciated. Thanks in advance.
>
> Stuff you put under localudebs/ is only used to replace/complement
> what's in the archive if something pulls it in. You probably want to
> add some packages to some list under build/pkg-lists.

According to the Debian Installer online reference <
https://wiki.debian.org/DebianInstaller/Modify/CustomKernel > it
suffices to place all the *.udebs at  build/localudebs directory.
There is no other example and/or guidance on how to go about
populating, say (from build/README)

* Anything listed in pkg-lists/local and pkg-lists/*/local is included in
  the image that is built. This is to provide an easy way to add extra
  udebs to a test image.

Thus, there is no indication where the installer will be picking up
the full 34M DEB linux-image-4.0.0-reiser4-amd64_4.0.8-2_amd64.deb so
as to be an option during the installation procedure.

>
> There's also a monolithic target you could use to bundle almost
> everything into your image. This is a bigger hammer though.
>

It fails:
fakeroot make build_monolithic
[...]
Makefile:637: recipe for target 'stamps/get_udebs-monolithic-stamp' failed
Makefile:284: recipe for target '_build' failed
Makefile:278: recipe for target 'build_monolithic' failed

> Mraw,
> KiBi.
Appreciate your reply.


Best Professional Regards.


-- 
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!
-


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cam12q5ruypu+hkgf5mbgv_puouwtiutstvjpsw9gvntknyh...@mail.gmail.com

"No kernel modules were found" netboot d-i with custom reiser4 kernel.

[Jose R R]

Niltze, all-

Building kernel the 'Debian way':

Replaced abi string at debian/config/defines (from default value of 2)
to a more descriptive string:

[abi]
abiname: reiser4

(guided by hint that debian devs sometimes set abiname string "trunk")

Everything builds beautifully, especially UDEBs for modules/kernel
like couple shown below:
[...]

3.7M  kernel-image-4.0.0-reiser4-amd64-di_4.0.8-2_amd64.udeb
34M   linux-image-4.0.0-reiser4-amd64_4.0.8-2_amd64.deb

Once kernel build is finished, I place the approxiamately 54 generated
UDEBs at the installer/build/localudebs directory and modify
installer/build/config/amd64.cfg

# The version of the kernel to use.
## KERNELVERSION = $(LINUX_KERNEL_ABI)-amd64
KERNELVERSION = 4.0.0-reiser4-amd64
## KERNELMAJOR = 2.6
KERNELMAJOR = 4.0
KERNELNAME = vmlinuz

save modifications and execute command:
make build_netboot-gtk

The resulting netboot d-i iso image uses the custom kernel to start
the Debian installation -- as can be verified by executing in an
alternate shell: uname -a:
Linux [host] 4.0.0-reiser4-amd64 #1 SMP Debian 4.0.8-2 (2015-07-22)
x86_64 GNU/Linux;

nevertheless stops at 'no kernel modules were found' and thus d-i can
not proceed further to install custom built kernel with reiser4
built-into-the-kernel support -- much less to detect/format a
disk/partition win Reiser4.

https://pbs.twimg.com/media/CK-ZehmUwAAjx-V.png:large

Any insight provided will be appreciated. Thanks in advance.


Best Professional Regards.


-- 
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!
-


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cam12q5sh659wufmocchdsnfrhdnikfk9iri9mo1akjqmhny...@mail.gmail.com

Re: Building kernel the Debian way fails

[Jose R R]

Appreciated, Ben!


On Sat, Jul 25, 2015 at 7:58 AM, Ben Hutchings  wrote:
> On Fri, 2015-07-24 at 22:23 -0700, Jose R R wrote:
> [...]
>> Procedure executes for a while but then:
>>
>> [...]
>> xt_unregister_targetsmodule:
>> net/netfilter/x_tables, version: 0x1ab6dab6 -> 0x967580ea, export:
>> EXPORT_SYMBOL
>> yield_to module: vmlinux,
>> version: 0x64772de8 -> 0x7e986552, export: EXPORT_SYMBOL_GPL
>> zap_vma_ptes module: vmlinux,
>> version: 0x51123f12 -> 0xe4761abe, export: EXPORT_SYMBOL_GPL
>> zero_fill_biomodule: vmlinux,
>> version: 0x999a9bec -> 0x2f0438ba, export: EXPORT_SYMBOL
>> zerocopy_sg_from_itermodule: vmlinux,
>> version: 0x156cb754 -> 0x3396ed70, export: EXPORT_SYMBOL
>> zl10036_attach   module:
>> drivers/media/dvb-frontends/zl10036, version: 0x01c15872 ->
>> 0x5ad87e01, export: EXPORT_SYMBOL
>> zl10039_attach   module:
>> drivers/media/dvb-frontends/zl10039, version: 0x4d52eac4 ->
>> 0x99661045, export: EXPORT_SYMBOL
>> zl10353_attach   module:
>> drivers/media/dvb-frontends/zl10353, version: 0xd7c34f95 ->
>> 0x6f771756, export: EXPORT_SYMBOL
>>
>> Removed symbols:
>> bdi_unregister   ignored, module:
>> vmlinux, version: 0xa88ae9e6, export: EXPORT_SYMBOL
> [...]
>
> See
> <http://kernel-handbook.alioth.debian.org/ch-versions.html#s-abi-maintenance>
>
> Ben.
>
> --
> Ben Hutchings
> It is easier to change the specification to fit the program than vice versa.
>

A couple of hours ago I increased the abi and repeated the
instructions for the procedure -- which finally ended successfully.


Best Professional Regards.

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


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cam12q5s3rsaor0h+n4x0fycjkzgbkc8acgti0pudo4zflmt...@mail.gmail.com

Building kernel the Debian way fails

[Jose R R]

Niltze, all!

Trying to build a Linux kernel the Debian way -- since I need to have
udebs for my project. I am building on Stretch/Sid and have followed
instructions at:

https://wiki.debian.org/DebianInstaller/Modify/CustomKernel
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official

I get the source and decompress it:
apt-get source linux
(tried with linux-4.0.8-1 AND linux-4.0.8-2)

Apply existing patches:
fakeroot debian/rules source

Use quilt to apply Reiser4 patch:
gzip -dc ../reiser4-for-4.0.4.patch.gz | quilt fold
(finishes without errors)

I then change the configuration before build:
fakeroot make -f debian/rules.gen setup_amd64
make -C debian/build/build_amd64_none_amd64 menuconfig
(enable Reiser4 in the kernel and OS/2 HPFS as module)

And build for the amd64 flavour:
fakeroot make -f debian/rules.gen binary-arch_amd64_none_amd64

Procedure executes for a while but then:

[...]
xt_unregister_targetsmodule:
net/netfilter/x_tables, version: 0x1ab6dab6 -> 0x967580ea, export:
EXPORT_SYMBOL
yield_to module: vmlinux,
version: 0x64772de8 -> 0x7e986552, export: EXPORT_SYMBOL_GPL
zap_vma_ptes module: vmlinux,
version: 0x51123f12 -> 0xe4761abe, export: EXPORT_SYMBOL_GPL
zero_fill_biomodule: vmlinux,
version: 0x999a9bec -> 0x2f0438ba, export: EXPORT_SYMBOL
zerocopy_sg_from_itermodule: vmlinux,
version: 0x156cb754 -> 0x3396ed70, export: EXPORT_SYMBOL
zl10036_attach   module:
drivers/media/dvb-frontends/zl10036, version: 0x01c15872 ->
0x5ad87e01, export: EXPORT_SYMBOL
zl10039_attach   module:
drivers/media/dvb-frontends/zl10039, version: 0x4d52eac4 ->
0x99661045, export: EXPORT_SYMBOL
zl10353_attach   module:
drivers/media/dvb-frontends/zl10353, version: 0xd7c34f95 ->
0x6f771756, export: EXPORT_SYMBOL

Removed symbols:
bdi_unregister   ignored, module:
vmlinux, version: 0xa88ae9e6, export: EXPORT_SYMBOL
debian/rules.real:160: recipe for target
'debian/stamps/build_amd64_none_amd64_plain' failed
make[1]: *** [debian/stamps/build_amd64_none_amd64_plain] Error 1
make[1]: Leaving directory '/mnt/sda8-tekitl/usr/src/linux-4.0.8'
debian/rules.gen:25: recipe for target
'binary-arch_amd64_none_amd64_real' failed
make: *** [binary-arch_amd64_none_amd64_real] Error 2


Thank you in advance for any insight. Appreciated.


Best Professional Regards


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


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cam12q5q0b_kgj9e8ti2swagqwsccgu6zd2-eulz-jvuxxl4...@mail.gmail.com

custom kernel and added module udebs

[Jose R R]

Niltze!

I am building my own debian installer to which I am adding my custom
kernel from pristine source and my reiser4 experimental module.

I built the kernel 'the debian way'

make deb-pkg

but the purportedly required *udebs to be included in the
debian-installer tree were not built -- only the pertinent *debs

I am using as a guide (<
https://wiki.debian.org/DebianInstaller/Modify/CustomKernel >)

and (< 
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official
>)

Any hints on the right direction will be appreciated.


Best Professional Regards.

-- 
Jose R R
http://www.metztli-it.com
-
NEW Apache OpenOffice 4.1.0! Download for GNU/Linux, Mac OS, Windows.
-
Daylight Saving Time in USA & Canada ends: Sunday, November 02, 2014
-


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cam12q5qqsdyuw5sem+si8ysnr2na1myj4hknhfbz4ssgy1j...@mail.gmail.com