[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#690706: release-notes: kFreeBSD-* speaks a lot about udev & linux kernel



Le Mon, 12 Nov 2012 20:36:21 +0100, Julien Cristau
<jcristau@debian.org> a écrit :

> The release notes need a kfreebsd person looking at them to mark the
> linuxisms and add corresponding info for kfreebsd.  If that doesn't
> happen we'll do as in squeeze and just not build for kfreebsd, I
> think.
> 
> Cheers,
> Julien

Please find attached a *kind* of patch to apply on 3 files :
- release-notes/release-notes.ent
- release-notes/en/issues.dbk 
- release-notes/en/upgrading.dbk

Adding 2 arches (kfreebsd-i386 & kfreebsd-amd64) and exceptions for
some linuxisms I found. I hope this is the correct way, and this could
help to build the release-notes.

Keeping -bsd@l.d.o because I'm not using this kernel for real, and they
know more about it.

Baptiste
--- issues.dbk	2013-01-25 08:32:17.051171800 +0100
+++ ./issues-bj.dbk	2013-01-25 09:24:44.954695200 +0100
@@ -16,7 +16,7 @@
 read the errata, the relevant packages' documentation, bug reports and other
 information mentioned in <xref linkend="morereading"/>.
 </para>
-<section id="udev" condition="fixme">
+<section id="udev" condition="fixme" arch="alpha;amd64;armel;armhf;i386;ia64;mips;mipsel;powerpc;sparc;s390;s390x">
 <title>Problems with devices related to udev</title>
 <para>
 Although <systemitem role="package">udev</systemitem> has been tested
--- release-notes.ent	2013-01-25 08:14:27.957421800 +0100
+++ ./release-notes-bj.ent	2013-01-25 09:23:26.281813200 +0100
@@ -80,7 +80,9 @@
 		    --><phrase arch='powerpc'>powerpc</phrase><!--
 		    --><phrase arch='sparc'>sparc</phrase><!--
 		    --><phrase arch='s390'>s390</phrase><!--
-		    --><phrase arch='s390x'>s390x</phrase>">
+		    --><phrase arch='s390x'>s390x</phrase><!--
+		    --><phrase arch='kfreebsd-i386'>kfreebsd-i386</phrase><!--
+		    --><phrase arch='kfreebsd-amd64'>kfreebsd-amd64</phrase>">
 
 <!-- proper nouns for architectures -->
 <!ENTITY arch-title "<phrase arch='alpha'>Alpha</phrase><!--
@@ -94,7 +96,9 @@
 		  --><phrase arch='powerpc'>PowerPC</phrase><!--
 		  --><phrase arch='sparc'>SPARC</phrase><!--
 		  --><phrase arch='s390'>S/390</phrase><!--
-		  --><phrase arch='s390x'>IBM System z</phrase>">
+		  --><phrase arch='s390x'>IBM System z</phrase><!--
+		  --><phrase arch='kfreebsd-i386'>kFreeBSD 32-bits PC</phrase><!--
+		  --><phrase arch='kfreebsd-amd64'>kFreeBSD 64-bits PC</phrase>">
 
 <!-- default kernel version, taken from d-i... -->
 <!ENTITY kernelversion "<phrase arch='amd64'>3.2</phrase><!--
@@ -107,4 +111,6 @@
                      --><phrase arch='powerpc'>3.2</phrase><!--
                      --><phrase arch='sparc'>3.2</phrase><!--
                      --><phrase arch='s390'>3.2</phrase><!--
-                     --><phrase arch='s390x'>3.2</phrase>">
+                     --><phrase arch='s390x'>3.2</phrase><!--
+		     --><phrase arch='kfreebsd-i386'>9.0</phrase><!--
+		     --><phrase arch='kfreebsd-amd64'>9.0</phrase>">
--- upgrading.dbk	2013-01-25 08:33:16.301171800 +0100
+++ ./upgrading-bj.dbk	2013-01-25 09:23:17.422324800 +0100
@@ -97,7 +97,7 @@
 system will fail to start.</para></footnote> for a significant period of time.
 </para>
 
-<para>
+<para arch="alpha;amd64;armel;armhf;i386;ia64;mips;mipsel;powerpc;sparc;s390;s390x">
 If the system being upgraded provides critical services for your users or the
 network<footnote><para>For example: DNS or DHCP services, specially when
 there is no redundancy or failover. In the DHCP case end-users might be disconnected 
@@ -879,7 +879,7 @@
 that this is not absolutely required, users could do a dist-upgrade
 and then reboot. This is, however, the recommended path to be on the 
 safe side -->
-<section id="upgrading-udev">
+<section id="upgrading-udev" arch="alpha;amd64;armel;armhf;i386;ia64;mips;mipsel;powerpc;sparc;s390;s390x">
 <title>Upgrading the kernel and udev</title>
 <para>
 The <systemitem role="package">udev</systemitem> version in &releasename;
@@ -932,6 +932,7 @@
 http://raphaelhertzog.com/2011/03/14/missing-firmware-in-debian-learn-how-to-deal-with-the-problem/ 
 
 Point to it or copy here? --> 
+<para arch="alpha;amd64;armel;armhf;i386;ia64;mips;mipsel;powerpc;sparc;s390;s390x">
 <para arch="i386;amd64">
 Users of the <systemitem role="package">grub</systemitem> bootloader should
 make sure that <command>update-grub</command> is run as part of the kernel
@@ -953,8 +954,9 @@
 <screen>
 # apt-get install udev
 </screen>
+</para>
 
-<para>
+<para arch="alpha;amd64;armel;armhf;i386;ia64;mips;mipsel;powerpc;sparc;s390;s390x">
 You should reboot the system 
 <footnote><para>If you are logging the upgrade as described in
 <xref linkend="upgradingpackages"/>, please, use <command>script</command> again
@@ -964,9 +966,20 @@
 once you have upgraded both the kernel and  <systemitem role="package">udev</systemitem>.
 </para>
 
+<para arch="kfreebsd-i386;kfreebsd-amd64">
+You should reboot the system 
+<footnote><para>If you are logging the upgrade as described in
+<xref linkend="upgradingpackages"/>, please, use <command>script</command> again
+to log the next steps of the upgrade after the reboot in order to log the
+result of the actions described in <xref linkend="upgrading-full"/>.
+</para></footnote>
+once you have upgraded the kernel.
+</para>
+
 </section>
 
 
+
 <section id="upgrading-full">
 <title>Upgrading the system</title>
 <para>
@@ -1044,7 +1057,7 @@
 </para>
 </section>
 
-<section id="cryptoloop">
+<section id="cryptoloop" arch="alpha;amd64;armel;armhf;i386;ia64;mips;mipsel;powerpc;sparc;s390;s390x">
 <title>cryptoloop support not included in the &releasename; Linux kernel</title>
 <para>
 Support for cryptoloop has been dropped from the Linux kernel packages
@@ -1255,7 +1268,7 @@
 </section>
 
 <!-- TODO: need to be reviewed with information from http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571255 -->
-<section id="newkernel">
+<section id="newkernel" arch="alpha;amd64;armel;armhf;i386;ia64;mips;mipsel;powerpc;sparc;s390;s390x">
 <title>Upgrading your kernel and related packages</title>
 <para>
 This section explains how to upgrade your kernel and identifies potential
@@ -1355,7 +1368,7 @@
 <!-- FIXME: REVIEW for Squeeze this was written for Lenny - drop? (jfs) -->
 <section id="boot-timing">
 <title>Boot timing issues</title>
-<para>
+<para arch="alpha;amd64;armel;armhf;i386;ia64;mips;mipsel;powerpc;sparc;s390;s390x">
 If an initrd created with <systemitem
 role="package">initramfs-tools</systemitem> is used to boot the system, in some
 cases the creation of device files by <systemitem
@@ -1500,7 +1513,7 @@
     upgrading, read ahead.
   </para>
 
-  <section id="avoid-problems-before-upgrading">
+  <section id="avoid-problems-before-upgrading" arch="alpha;amd64;armel;armhf;i386;ia64;mips;mipsel;powerpc;sparc;s390;s390x">
     <title>How to avoid the problem before upgrading</title>
 
     <para>
@@ -1650,7 +1663,7 @@
 <!-- FIXME: This section might not be relevant anymore for Squeeze
   but could be turned into a generic section on how to recover from
   issues -->
-  <section id="how-to-recover">
+  <section id="how-to-recover" arch="alpha;amd64;armel;armhf;i386;ia64;mips;mipsel;powerpc;sparc;s390;s390x">
     <title>How to recover from the problem after the upgrade</title>
 
     <section id="solution1">

Attachment: signature.asc
Description: PGP signature


Reply to: