Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Status of 3.x hardened-sources for ppc64?
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Gentoo on PPC
View previous topic :: View next topic  
Author Message
jhardin
n00b
n00b


Joined: 12 Oct 2005
Posts: 30

PostPosted: Mon Jan 16, 2012 3:41 am    Post subject: Status of 3.x hardened-sources for ppc64? Reply with quote

Can anybody say whether / when the 3.x hardened-sources ebuild(s) will be marked stable for ppc64?

Are there any serious problems with these kernels, or is it just a matter of few people using this on ppc64?

Thanks for any info.
Back to top
View user's profile Send private message
gringo
Advocate
Advocate


Joined: 27 Apr 2003
Posts: 3748

PostPosted: Mon Jan 16, 2012 1:49 pm    Post subject: Reply with quote

Quote:
is it just a matter of few people using this on ppc64?


more than probably, ppc doesnt have enough manpower right now.
I would say, give it a try and if it works for you, open a bug with your experience.

( Will tell the mods to move this to ppc, hopefully you get more answers there).

cheers
Back to top
View user's profile Send private message
John R. Graham
Administrator
Administrator


Joined: 08 Mar 2005
Posts: 7888
Location: Somewhere over Atlanta, Georgia

PostPosted: Mon Jan 16, 2012 1:54 pm    Post subject: Reply with quote

Moved from Kernel & Hardware to Gentoo on PPC.

- John
_________________
I can confirm that I have received between 0 and 999 National Security Letters.
Back to top
View user's profile Send private message
jhardin
n00b
n00b


Joined: 12 Oct 2005
Posts: 30

PostPosted: Wed Jan 18, 2012 3:19 am    Post subject: Reply with quote

gringo wrote:
I would say, give it a try and if it works for you, open a bug with your experience.

Okay, hardened-3.1.5 compiled using my existing working config, installed in /boot, yaboot.conf updated and yabin run, the new kernel label is present at boot...
...but it refuses to boot the new kernel even though I type in the new image label! It boots to the existing #1 kernel.

Is there anything in yaboot that would cause it to boot to kernel #1 when you type in the label for kernel #5? Is this a symptom of a problem in the kernel? Or is yaboot doing something screwy?

yaboot.conf:
Code:
## Change `unconfigured' to your bootstrap partition eg: /dev/hda2
boot=/dev/sda2

## device is the OpenFirmware device path to the disk containing
## kernel images.  if your disk is /dev/hda you can find the
## OpenFirmware path by running the command: ofpath /dev/hda DO NOT
## specify a partition number for this!  On IBM hardware you can
## generally comment this out.

device=hd:

## partition is the partition number where the kernel images are
## located.  The kernel images should be on your root filesystem, so
## this is usually the same partition number as your root filesystem.
## so if root = /dev/hda3 (the 3rd partition) then you should have
## partition=3  This *MUST* be set correct or yaboot won't boot!  This
## option can be either set globally as shown here, or per image in
## the image= sections

partition=4

## delay is the amount of time in seconds the dual boot menu (if one
## is configured, by the presense of macos, macosx, etc options here)
## will wait before choosing the default OS (GNU/Linux or the value of
## defaultos=).  If you omit this then the value of timeout=
## (converted to seconds) will be used.

delay=10

## timeout is the amount of time in tenths of a second that yaboot
## will wait before booting the default kernel image (the first image=
## section in this config file or the value of default=).

timeout=40
install=/usr/lib/yaboot/yaboot
magicboot=/usr/lib/yaboot/ofboot

## Change the default colors, fgcolor is the text color, bgcolor is
## the screen background color. (default: fgcolor=white, bgcolor=black)
#fgcolor=black
#bgcolor=green

## Password supplied in plaintext, required for yaboot to boot, unless
## restricted is also present (see below). Be sure to
## chmod 600 /etc/yaboot.conf if you set this!

#password=secret

## Password supplied as an md5 hash, see above

#password=$1$saltstrg$HnJ/gcM3oKhNbnzUPgXTD/

## A password is only required to boot an image specified here if
## parameters are specified on the command line or if the user enters
## an image is not specified in the configuration file at all (ie.
## arbitrary file load).  restricted can also be placed in an image
## section in that case any image not including the restricted keyword
## will be fully password protected.

#restricted

## image is the kernel itself, commonly kept in / but also commonly
## found in /boot.  Note that /boot should generally not be its own
## partition on powerpcs, its not necessary and complicates things.
## Make sure /boot is on the partition specified by partition= see
## above.  /boot should never be an HFS filesystem.  You may point
## image= to a symbolic link so long as the symlink does not cross
## partition boundries.

image=/boot/vmlinux-2.6.36-hardened-r9
   label=linux.hardened
   root=/dev/sda4
   partition=4
   read-only

image=/boot/vmlinux-2.6.37-gentoo-r4
   label=linux
   root=/dev/sda4
   partition=4
   read-only

image=/boot/vmlinux-2.6.37-gentoo-r4-knowngood
   label=linux.good
   root=/dev/sda4
   partition=4
   read-only

image=/boot/vmlinux-2.6.36-hardened-r9-knowngood
   label=linux.good.hardened
   root=/dev/sda4
   partition=4
   read-only

image=/boot/vmlinux-3.1.5-hardened
   label=linux.test.hardened
   root=/dev/sda4
   partition=4
   read-only

image=/boot/G5
   label=linux.installcd
   root=/dev/sda4
   partition=4
   initrd=/boot/G5.igz
   read-only

enablecdboot
enableofboot
Back to top
View user's profile Send private message
gringo
Advocate
Advocate


Joined: 27 Apr 2003
Posts: 3748

PostPosted: Wed Jan 18, 2012 9:23 am    Post subject: Reply with quote

Quote:
the new kernel label is present at boot...
...but it refuses to boot the new kernel even though I type in the new image label! It boots to the existing #1 kernel.


beats me ... really have no clue.
Open a bug and hopefully someone of the toolchain or hardened team can reproduce the problem and help you out.

good luck !
Back to top
View user's profile Send private message
jhardin
n00b
n00b


Joined: 12 Oct 2005
Posts: 30

PostPosted: Wed Jan 18, 2012 8:55 pm    Post subject: Reply with quote

...okay, this is embarrassing. I neglected to update the kernel symlink but I thought I had. I actually was recompiling and installing 2.6.whatever. D'oh! :oops:

So, now I am actually compiling 3.1.x, and I'm getting fatal errors. Sorry for the false alarm about yaboot.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Gentoo on PPC All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum