Mailing List Archive: 2007.0 mojo

2007.0 mojo

nightmorph at gentoo

Mar 12, 2007, 1:27 AM

Post #1 of 20 (5587 views)

Hello, it's that time of year again. The first release of the year is
comin' up fast. If you examine recent CVS history, I just added the
2007.0 directory to draft/, and will shortly begin adding stuff to it.

It's my intention to once again do a major version number change, in
keeping with the 2006.0 --> 2006.1 change for all docs, so though our
stuff is at 7.x, it will be 8.x, and in the case of the gtkfe and
gli-dialog handbooks, 2.x to 3.x.

Now, I think I've gotten the last changes to the current/2006.1
handbooks settled with the fix to bug 147358, so I anticipate having a
relatively clean slate to work on in draft/. Any fixes to the current
docs will of course be added to the draft/ docs.

Anyway, that's my plan -- I've a few lists of TODOs for stuff,
especially for the networkless docs, that will be fairly intensive. Now,
from the translators point of view, what do you and don't you want to
see me do to the docs in draft/? Yes, I've done two releases before
this, but .... it's been awhile, so I don't entirely remember. For
sanity's sake I'd like to make sure that my instincts are right. I won't
be revbumping the stuff in draft/, but I assume it's okay to make as
many changes as needed to the stuff in there....or will that mess with
the translators heads? Will you guys be able to pick up on all the changes?

Lemme know what you need me to do for you -- I'll be heading up the
handbook efforts again. It's my job to make the work easier for you guys. :)

Oh, and in good news (good despite the shift into "panic mode"), this
release will see the fix of the media, so that things like the LiveUSB
Howto (liveusb.xml) will work once again.

I intend to partner closely with releng on this one; already I've gotten
some good help with them for the installer docs updates, so thanks for
all that.

Ladies & Gentlemen: Start your engines!

Re: 2007.0 mojo [ In reply to ]

nightmorph at gentoo

Mar 12, 2007, 1:31 AM

Post #2 of 20 (5521 views)

Forgot to add: watch this bug for updates.

http://bugs.gentoo.org/show_bug.cgi?id=170536

Re: 2007.0 mojo [ In reply to ]

Mar 12, 2007, 4:23 AM

Post #3 of 20 (5529 views)

Josh Saddler wrote:
> Anyway, that's my plan -- I've a few lists of TODOs for stuff,
> especially for the networkless docs, that will be fairly intensive. Now,
> from the translators point of view, what do you and don't you want to
> see me do to the docs in draft/?

I'd start with copying current 2006.1 stuff into draft (be sure to
include CVS revision in the commit message as we don't use better SCM
that would keep track of that), then applying any changes that are
required without any revbumps *and* without mixing content and
formatting changes. Each commit should either touch the real content
(and nothing else) or just change formatting, fix typos etc. It's a real
PITA to go through a diff for a paragraph just to see someone fixed
spelling in one word or (even worse) just re-wrapped text.

As an alternative, point me to a working diff implementation that
ignores XML formatting and just shows the real changes :).

<insert usual warning about yoswink's knife here />

Cheers,
-jkt

--
cd /local/pub && more beer > /dev/mouth

Re: 2007.0 mojo [ In reply to ]

wolf31o2 at gentoo

Mar 12, 2007, 5:29 AM

Post #4 of 20 (5536 views)

On Mon, 2007-03-12 at 01:31 -0700, Josh Saddler wrote:
> Forgot to add: watch this bug for updates.
>
> http://bugs.gentoo.org/show_bug.cgi?id=170536

We only use release@gentoo.org for bugs. I send the rest of it
to /dev/null so you're probably looking for releng@gentoo.org
instead. ;]

--
Chris Gianelloni
Release Engineering Strategic Lead
Alpha/AMD64/x86 Architecture Teams
Games Developer/Council Member/Foundation Trustee
Gentoo Foundation

Re: 2007.0 mojo [ In reply to ]

josejx at gentoo

Mar 12, 2007, 6:19 AM

Post #5 of 20 (5534 views)

Josh Saddler wrote:
> Hello, it's that time of year again. The first release of the year is
> comin' up fast. If you examine recent CVS history, I just added the
> 2007.0 directory to draft/, and will shortly begin adding stuff to it.
>
> It's my intention to once again do a major version number change, in
> keeping with the 2006.0 --> 2006.1 change for all docs, so though our
> stuff is at 7.x, it will be 8.x, and in the case of the gtkfe and
> gli-dialog handbooks, 2.x to 3.x.
>
> Now, I think I've gotten the last changes to the current/2006.1
> handbooks settled with the fix to bug 147358, so I anticipate having a
> relatively clean slate to work on in draft/. Any fixes to the current
> docs will of course be added to the draft/ docs.
>
> Anyway, that's my plan -- I've a few lists of TODOs for stuff,
> especially for the networkless docs, that will be fairly intensive. Now,
> from the translators point of view, what do you and don't you want to
> see me do to the docs in draft/? Yes, I've done two releases before
> this, but .... it's been awhile, so I don't entirely remember. For
> sanity's sake I'd like to make sure that my instincts are right. I won't
> be revbumping the stuff in draft/, but I assume it's okay to make as
> many changes as needed to the stuff in there....or will that mess with
> the translators heads? Will you guys be able to pick up on all the changes?
>
> Lemme know what you need me to do for you -- I'll be heading up the
> handbook efforts again. It's my job to make the work easier for you guys. :)
>
> Oh, and in good news (good despite the shift into "panic mode"), this
> release will see the fix of the media, so that things like the LiveUSB
> Howto (liveusb.xml) will work once again.
>
> I intend to partner closely with releng on this one; already I've gotten
> some good help with them for the installer docs updates, so thanks for
> all that.
>
> Ladies & Gentlemen: Start your engines!
>

Hi Josh,

I'll get together my PPC docs changes and get them in CVS asap. Do
we have a timeframe yet?

-Joe
--
gentoo-doc@gentoo.org mailing list

Re: 2007.0 mojo [ In reply to ]

m.mascherpa at gentoo

Mar 12, 2007, 11:57 AM

Post #6 of 20 (5538 views)

On Monday 12 March 2007 12:23:09 Jan Kundrát wrote:
> I'd start with copying current 2006.1 stuff into draft (be sure to
> include CVS revision in the commit message as we don't use better SCM
> that would keep track of that), then applying any changes that are
> required without any revbumps *and* without mixing content and
> formatting changes. Each commit should either touch the real content
> (and nothing else) or just change formatting, fix typos etc. It's a real
> PITA to go through a diff for a paragraph just to see someone fixed
> spelling in one word or (even worse) just re-wrapped text.

Yes please,
that is my request as well! :)

--
Marco Mascherpa

Gentoo Documentation Project
Italian Lead Translator

Re: 2007.0 mojo [ In reply to ]

nightmorph at gentoo

Mar 13, 2007, 11:09 PM

Post #7 of 20 (5528 views)

Joseph Jezak wrote:
> Do we have a timeframe yet?
>
> -Joe

By the end of the month is all I know; releng aims to release this thing
sometime in March.

Re: 2007.0 mojo [ In reply to ]

nightmorph at gentoo

Mar 13, 2007, 11:54 PM

Post #8 of 20 (5535 views)

There are two other things that I want to change for this release, both
related to kernels.

1) kick out any and all code references to 2.4 kernels, assuming none
are available for that arch -- note that things like vanilla-sources
(which may have been a 2.4 kernel package) are unsupported. 2.6 only as
much as possible.

2) update kernel install directions: no more "cp vmlinuz foo" or any
more "cp arch/whatever bar". let's get this thing modernized. No need
for it; a simple "make && make modules_install && make install" does the
whole thing for you, no manual intervention is required, beyond reading
grub.conf to make sure it's pointed to kernel /vmlinuz. "make install"
is much better than the cp crap.

Thoughts? Also, can I get some help in tracking down people from the
alpha, hppa, sparc, and MIPS arch teams on answering a few questions,
such as do they have a packages CD for this release (or any other
CD/media changes), what version will their included kernel be, any
changes to the CFLAGS currently listed at the top of handbook-$arch.xml,
etc. Maybe someone from releng knows all that? Would be much
appreciated, thanks. Well, in addition to finding out the usual "has
anything changed in the install procedures for your arch in this
release". ;)

I figure we have two weeks, tops, to make this all happen, so let's pull
it together and get rolling. I've already added the networked stuff to
draft/ and have begun working on them. Go get 'em! :)

Re: 2007.0 mojo [ In reply to ]

yoswink at gentoo

Mar 14, 2007, 4:06 AM

Post #9 of 20 (5532 views)

Josh Saddler escribiÃ³:
> 2) update kernel install directions: no more "cp vmlinuz foo" or any
> more "cp arch/whatever bar". let's get this thing modernized. No need
> for it; a simple "make && make modules_install && make install" does the
> whole thing for you, no manual intervention is required, beyond reading
> grub.conf to make sure it's pointed to kernel /vmlinuz. "make install"
> is much better than the cp crap.

Excuse me if I'm missing something here but: Is the make_install able to
put bzImage in /boot? although /boot is in a different partition?

>
> Thoughts? Also, can I get some help in tracking down people from the
> alpha, hppa, sparc, and MIPS arch teams on answering a few questions,
> such as do they have a packages CD for this release (or any other
> CD/media changes), what version will their included kernel be, any
> changes to the CFLAGS currently listed at the top of handbook-$arch.xml,
> etc. Maybe someone from releng knows all that? Would be much
> appreciated, thanks. Well, in addition to finding out the usual "has
> anything changed in the install procedures for your arch in this
> release". ;)

Probably contacting with the arch teams via aliases (e.g.
alpha@gentoo.org) is the easiest way of handle this.

Cheers.Regards.

--
Jose Luis Rivero <yoswink@gentoo.org>
Gentoo/Doc Gentoo/Alpha
--
gentoo-doc@gentoo.org mailing list

Re: 2007.0 mojo [ In reply to ]

wolf31o2 at gentoo

Mar 14, 2007, 5:15 AM

Post #10 of 20 (5538 views)

On Tue, 2007-03-13 at 23:54 -0700, Josh Saddler wrote:
> 1) kick out any and all code references to 2.4 kernels, assuming none
> are available for that arch -- note that things like vanilla-sources
> (which may have been a 2.4 kernel package) are unsupported. 2.6 only as
> much as possible.

No architectures are shipping 2.4-enabled media. You can still do an
install for 2.4 on a couple arches, but nobody's shipping it.

> 2) update kernel install directions: no more "cp vmlinuz foo" or any
> more "cp arch/whatever bar". let's get this thing modernized. No need
> for it; a simple "make && make modules_install && make install" does the
> whole thing for you, no manual intervention is required, beyond reading
> grub.conf to make sure it's pointed to kernel /vmlinuz. "make install"
> is much better than the cp crap.

Personally, I don't like this one, but I'm not really the one making the
calls here. My main complaint is that it's actually very inconsistent
in what it does across multiple architectures. As someone who owns (and
uses) 9 architectures, I prefer the manual instructions better as it
gives me a clearer picture of what is actually going on behind the
scenes.

> Thoughts? Also, can I get some help in tracking down people from the
> alpha, hppa, sparc, and MIPS arch teams on answering a few questions,
> such as do they have a packages CD for this release (or any other
> CD/media changes), what version will their included kernel be, any
> changes to the CFLAGS currently listed at the top of handbook-$arch.xml,
> etc. Maybe someone from releng knows all that? Would be much
> appreciated, thanks. Well, in addition to finding out the usual "has
> anything changed in the install procedures for your arch in this
> release". ;)

Well, all you have to do is ask. ;]

Alpha and SPARC will have a packages CD.

I'll get the rest for you today.

> I figure we have two weeks, tops, to make this all happen, so let's pull
> it together and get rolling. I've already added the networked stuff to
> draft/ and have begun working on them. Go get 'em! :)

--
Chris Gianelloni
Release Engineering Strategic Lead
Alpha/AMD64/x86 Architecture Teams
Games Developer/Council Member/Foundation Trustee
Gentoo Foundation

Re: 2007.0 mojo [ In reply to ]

josejx at gentoo

Mar 14, 2007, 6:05 AM

Post #11 of 20 (5535 views)

Josh Saddler wrote:
> There are two other things that I want to change for this release, both
> related to kernels.
>
> 1) kick out any and all code references to 2.4 kernels, assuming none
> are available for that arch -- note that things like vanilla-sources
> (which may have been a 2.4 kernel package) are unsupported. 2.6 only as
> much as possible.
>
> 2) update kernel install directions: no more "cp vmlinuz foo" or any
> more "cp arch/whatever bar". let's get this thing modernized. No need
> for it; a simple "make && make modules_install && make install" does the
> whole thing for you, no manual intervention is required, beyond reading
> grub.conf to make sure it's pointed to kernel /vmlinuz. "make install"
> is much better than the cp crap.

I don't have a problem with the "cp crap". It's obvious what it
does and make install doesn't work on all architectures. "make
install" isn't as explicit and may introduce other issues.

-Joe
--
gentoo-doc@gentoo.org mailing list

Re: 2007.0 mojo [ In reply to ]

wolf31o2 at gentoo

Mar 14, 2007, 6:07 AM

Post #12 of 20 (5532 views)

On Tue, 2007-03-13 at 23:54 -0700, Josh Saddler wrote:
> Thoughts? Also, can I get some help in tracking down people from the
> alpha, hppa, sparc, and MIPS arch teams on answering a few questions,
> such as do they have a packages CD for this release (or any other
> CD/media changes), what version will their included kernel be, any
> changes to the CFLAGS currently listed at the top of handbook-$arch.xml,
> etc. Maybe someone from releng knows all that? Would be much
> appreciated, thanks. Well, in addition to finding out the usual "has
> anything changed in the install procedures for your arch in this
> release". ;)

You will still need to talk to the relevant architecture people, but
here's what you asked for specifically.

Alpha: 2.6.19-gentoo-r5
HPPA: 2.6.20.1-hppa
MIPS: 2.6.17.10-mips
SPARC: 2.6.20-gentoo-r1

CFLAGS shouldn't have changed anywhere, since that's all done by
catalyst. For anything else, you'll have to ask specifically what you
want, or talk with the individual architecture coordinators. They're
all listed on the Release Engineering project page.

> I figure we have two weeks, tops, to make this all happen, so let's pull
> it together and get rolling. I've already added the networked stuff to
> draft/ and have begun working on them. Go get 'em! :)

Actually, a bit less than that if we plan on having a release this
month. Remember that it takes us a few days after we've uploaded
everything to stage to the mirrors before we release.

--
Chris Gianelloni
Release Engineering Strategic Lead
Alpha/AMD64/x86 Architecture Teams
Games Developer/Council Member/Foundation Trustee
Gentoo Foundation

Re: 2007.0 mojo [ In reply to ]

neysx at gentoo

Mar 14, 2007, 6:35 AM

Post #13 of 20 (5536 views)

Chris Gianelloni wrote:
> On Tue, 2007-03-13 at 23:54 -0700, Josh Saddler wrote:
>> 1) kick out any and all code references to 2.4 kernels, assuming none
>> are available for that arch -- note that things like vanilla-sources
>> (which may have been a 2.4 kernel package) are unsupported. 2.6 only as
>> much as possible.
>
> No architectures are shipping 2.4-enabled media. You can still do an
> install for 2.4 on a couple arches, but nobody's shipping it.

sparc-sources is still 2.4
hardened-sources still has 2.4 available

>> 2) update kernel install directions: no more "cp vmlinuz foo" or any
>> more "cp arch/whatever bar". let's get this thing modernized. No need
>> for it; a simple "make && make modules_install && make install" does the
>> whole thing for you, no manual intervention is required, beyond reading
>> grub.conf to make sure it's pointed to kernel /vmlinuz. "make install"
>> is much better than the cp crap.
>
> Personally, I don't like this one, but I'm not really the one making the
> calls here. My main complaint is that it's actually very inconsistent
> in what it does across multiple architectures. As someone who owns (and
> uses) 9 architectures, I prefer the manual instructions better as it
> gives me a clearer picture of what is actually going on behind the
> scenes.

My preference as well, even though I use only 7 arches :)

Cheers,
--
/ Xavier Neys
\_ Gentoo Documentation Project
/
/\ http://www.gentoo.org/doc/en/
--
gentoo-doc@gentoo.org mailing list

Re: 2007.0 mojo [ In reply to ]

wolf31o2 at gentoo

Mar 14, 2007, 8:28 AM

Post #14 of 20 (5524 views)

On Wed, 2007-03-14 at 14:35 +0100, Xavier Neys wrote:
> > No architectures are shipping 2.4-enabled media. You can still do an
> > install for 2.4 on a couple arches, but nobody's shipping it.
>
> sparc-sources is still 2.4
> hardened-sources still has 2.4 available

"but nobody's shipping it"

--
Chris Gianelloni
Release Engineering Strategic Lead
Alpha/AMD64/x86 Architecture Teams
Games Developer/Council Member/Foundation Trustee
Gentoo Foundation

Re: 2007.0 mojo [ In reply to ]

neysx at gentoo

Mar 14, 2007, 8:54 AM

Post #15 of 20 (5523 views)

Chris Gianelloni wrote:
> On Wed, 2007-03-14 at 14:35 +0100, Xavier Neys wrote:
>>> No architectures are shipping 2.4-enabled media. You can still do an
>>> install for 2.4 on a couple arches, but nobody's shipping it.
>> sparc-sources is still 2.4
>> hardened-sources still has 2.4 available

All 2.4 related instructions under /doc/en/handbook/2007.0/, i.e. for
networkless installs, can be dropped indeed.

> "but nobody's shipping it"

This doesn't matter as far as the current handbook is concerned.
Unless the sparc team decides to deprecate sparc-sources, it is available and
needs to stay documented.

Cheers,
--
/ Xavier Neys
\_ Gentoo Documentation Project
/
/\ http://www.gentoo.org/doc/en/
--
gentoo-doc@gentoo.org mailing list

Re: 2007.0 mojo [ In reply to ]

pylon at gentoo

Mar 14, 2007, 10:39 AM

Post #16 of 20 (5527 views)

* Josh Saddler <nightmorph@gentoo.org> [07/03/13 23:54 -0700]:
> 2) update kernel install directions: no more "cp vmlinuz foo" or any
> more "cp arch/whatever bar". let's get this thing modernized. No need
> for it; a simple "make && make modules_install && make install" does the
> whole thing for you, no manual intervention is required, beyond reading
> grub.conf to make sure it's pointed to kernel /vmlinuz. "make install"
> is much better than the cp crap.

AFAIK this does not work on the Pegasos (PowerPC), as an
uncompressed kernel may be too big for loading. We are
stucked to about 3.5MB without initramfs and 4.8MB with the
included initramfs. So we want the zImage or zImage.initrd
copied over. `make install` might not handle this one.

Regards, Lars

--
Lars Weiler <pylon@gentoo.org> +49-171-1963258
Instant Messaging : pylon@jabber.ccc.de
Gentoo Linux PowerPC : Strategical Lead and Release Engineer
Gentoo Infrastructure : CVS Administrator

Re: 2007.0 mojo [ In reply to ]

nightmorph at gentoo

Mar 14, 2007, 11:10 AM

Post #17 of 20 (5530 views)

Joseph Jezak wrote:
> I don't have a problem with the "cp crap". It's obvious what it
> does and make install doesn't work on all architectures. "make
> install" isn't as explicit and may introduce other issues.
>
> -Joe

Well, alrighty then. I hadn't figured "make install" would change its
behavior so much on different platforms. Fortunately, I'd only commented
out that stuff in a couple of handbooks, so I'll go back and revert that
change.

I did, however, have to fix some instances where the directions referred
to cping vmmlinuz, but the *-bootloader files talked about vmlinux.
That'll be the only thing to remain changed.

What about just leaving it for x86+amd64? the "make install" copies
everything properly for me whether or not /boot is a separate partition,
and since I actually have the hardware (a whole 2 arches ;)), I can say
with certainty it causes no issues.

I'm always surprised when people find out there's a "make install"
command to begin with -- it seems like it's one of the best-kept secrets
of kernel compilation, right up there with "make gconfig". It doesn't
cause problems on these two arches, and it's nicer than cping a buncha
stuff and manually naming it. I'd like to keep it in for x86+amd64.
Thoughts?

Re: 2007.0 mojo [ In reply to ]

wolf31o2 at gentoo

Mar 14, 2007, 11:56 AM

Post #18 of 20 (5531 views)

On Wed, 2007-03-14 at 16:54 +0100, Xavier Neys wrote:
> Chris Gianelloni wrote:
> > On Wed, 2007-03-14 at 14:35 +0100, Xavier Neys wrote:
> >>> No architectures are shipping 2.4-enabled media. You can still do an
> >>> install for 2.4 on a couple arches, but nobody's shipping it.
> >> sparc-sources is still 2.4
> >> hardened-sources still has 2.4 available
>
> All 2.4 related instructions under /doc/en/handbook/2007.0/, i.e. for
> networkless installs, can be dropped indeed.
>
> > "but nobody's shipping it"
>
> This doesn't matter as far as the current handbook is concerned.
> Unless the sparc team decides to deprecate sparc-sources, it is available and
> needs to stay documented.

<wolf31o2|mobile> gustavoz: are you guys going to be supporting
sparc-sourcces anymore?
<gustavoz> wolf31o2|mobile: not for release media, probably a couple
more releases in portage though
<wolf31o2|mobile> k... reason I ask is because of -doc
<wolf31o2|mobile> so they need to leave the 2.4 instructions in the
handbook
<gustavoz> oh, no new 2.4 installs so no
<wolf31o2|mobile> no?
<wolf31o2|mobile> ok
<wolf31o2|mobile> thanks
<gustavoz> 2007.0 doesn't have a 2.4 profile
<gustavoz> *subprofile

--
Chris Gianelloni
Release Engineering Strategic Lead
Alpha/AMD64/x86 Architecture Teams
Games Developer/Council Member/Foundation Trustee
Gentoo Foundation

Re: 2007.0 mojo [ In reply to ]

weeve at gentoo

Mar 14, 2007, 12:31 PM

Post #19 of 20 (5529 views)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, 13 Mar 2007, Josh Saddler wrote:

> 2) update kernel install directions: no more "cp vmlinuz foo" or any
> more "cp arch/whatever bar". let's get this thing modernized. No need
> for it; a simple "make && make modules_install && make install" does the
> whole thing for you, no manual intervention is required, beyond reading
> grub.conf to make sure it's pointed to kernel /vmlinuz. "make install"
> is much better than the cp crap.

SPARC and SPARC64 Makefiles in the kernel do not provide a make install or
equivalent and will need cp instructions.

Not sure how many other arches this may apply to.

Cheers,
- --
Jason Wever
Gentoo/Sparc Team Co-Lead
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFF+E2RdKvgdVioq28RAhgQAJ40sx+N/Vn2qp3YdUZQaR8+b8vbPgCfeLtr
VpK74saRNsBOcq/VqiqQS+Y=
=40j+
-----END PGP SIGNATURE-----
--
gentoo-doc@gentoo.org mailing list

Re: 2007.0 mojo [ In reply to ]

nightmorph at gentoo

Mar 30, 2007, 10:36 PM

Post #20 of 20 (5544 views)

Josh Saddler wrote:
> Hello, it's that time of year again. The first release of the year is
> comin' up fast. If you examine recent CVS history, I just added the
> 2007.0 directory to draft/, and will shortly begin adding stuff to it.

Hello again everyone. The docs are coming along nicely; the networkless
handbooks for all arches are almost finished, and I think the networked
handbooks are done or just about done as well, pending some review from
myself and JoseJX for PPC and I should probably get Stuart to poke MIPS.

Anyway, this is a brief status update as well as a ** note to
translators** :

When you've finished your translation, be sure to either uncomment the
appropriate language listing in handbook/index.xml and 2007.0/index.xml,
or else get one of the GDP members with commit access to the tree to get
it fixed for you.

I just noticed that none of the translations for 2006.1/index.xml were
ever uncommented; there's no listing at all of available languages.
Sorry :/ -- I suppose one of us should get it uncommented anyway,
because there were so many translations made. (I can't believe I let a
whole release go by without remembering to do this, apologies).

Thanks,

Josh