Skip to contentSkip to conversation

Trivial question bout EXTRAVERSION and install destination

DISCUSSION JW 3 participants 3 messages Jul 9, 2002 SELinux security module

lore
Share & tools
lore

JW

author
#0 lore raw

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

Hello,

- From http://www.nsa.gov/selinux/doc/readme.html:

13) Configure your boot manager to boot the SELinux kernel.

You can determine the name of the new kernel by
looking in /boot. The new kernel's name will end in "-selinux" (example: "vmlinuz-2.4.18-selinux").

SuSE kernels always install into /boot, but all othe end up in /, with generic names, including selinux's:

ccs001:/usr/src/selinux/policy # ls -l /
<snip>

- -rw-r--r--    1 root     root       520735 Jul  8 19:27 System.map
- -rw-r--r--    1 root     root       520735 Jul  8 17:20 System.old
- -rw-r--r--    1 root     root      1091691 Jul  8 19:27 vmlinuz
- -rw-r--r--    1 root     root      1091636 Jul  8 17:20 vmlinuz.old

1. What is wrong that's causing EXTRAVERSION to be ignored 2 Why are System.map and vmlinuz edning up in / instead of /boot ?

It's not a huge problem, but it's rather perplexing, especially since I had the exact same issue with a grsecurity-patched kernel

Thanks.

- --

- ---------------------------------------------------- Jonathan Wilson
System Administrator
Cedar Creek Software http://www.cedarcreeksoftware.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9KisdQ5u80xXOLBcRAlDgAJ9pFU48hKd0cpDT1Ce5fPdd2St1MgCePiZm Nbjn0fAlizOG9WtMO2C5cGY=
=i1l+
-----END PGP SIGNATURE-----

--
You have received this message because you are subscribed to the selinux list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.

#1 lore raw
Quoted 9 lines · JW

You can determine the name of the new kernel by
looking in /boot. The new kernel's name will end in "-selinux" (example: "vmlinuz-2.4.18-selinux").

SuSE kernels always install into /boot, but all othe end up in /, with generic names, including selinux's:

1. What is wrong that's causing EXTRAVERSION to be ignored 2 Why are System.map and vmlinuz edning up in / instead of /boot ?

Debian kernels end up in /boot with extraversion included in the names.

Also I have been convinced to remove the EXTRAVERSION from the patches I package for Debian to avoid conflicts, but the Debian package build system allows specifying it at compile time.

Quoted 2 lines

It's not a huge problem, but it's rather perplexing, especially since I had the exact same issue with a grsecurity-patched kernel

Not a problem for Debian...

Signature · 3 lines
I do not get viruses because I do not use MS software.
If you use Outlook then please do not put my email address in your
address-book so that WHEN you get a virus it won't use my address in the
Quoted 1 line

From field.

--
You have received this message because you are subscribed to the selinux list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.

#2 lore raw

Hello,

One issue does arise with the EXTRAVERSION, some future patches will not install correctly.

Ed

=> -----Original Message-----
=> From: [email protected] [mailto:[email protected]] On
=> Behalf Of Russell Coker
=> Sent: Tuesday, July 09, 2002 4:57 PM
=> To: [email protected]; SELinux
=> Subject: Re: Trivial question bout EXTRAVERSION and install destination
=>
=> On Mon, 8 Jul 2002 20:15, JW wrote:
=> > You can determine the name of the new kernel by
=> > looking in /boot. The new kernel's name will end in "-selinux" => > (example: "vmlinuz-2.4.18-selinux").
=> >
=> > SuSE kernels always install into /boot, but all othe end up in /, with
=> > generic names, including selinux's:
=> >
=> > 1. What is wrong that's causing EXTRAVERSION to be ignored => > 2 Why are System.map and vmlinuz edning up in / instead of /boot ? =>
=> Debian kernels end up in /boot with extraversion included in the names.
=>
=> Also I have been convinced to remove the EXTRAVERSION from the patches I
=> package for Debian to avoid conflicts, but the Debian package build => system
=> allows specifying it at compile time.
=>
=> > It's not a huge problem, but it's rather perplexing, especially since I
=> had
=> > the exact same issue with a grsecurity-patched kernel =>
=> Not a problem for Debian...
=>
=> --
=> I do not get viruses because I do not use MS software.
=> If you use Outlook then please do not put my email address in your => address-book so that WHEN you get a virus it won't use my address in the
=> >From field.
=>
=> --
=> You have received this message because you are subscribed to the selinux
=> list.
=> If you no longer wish to subscribe, send mail to [email protected]
=> with
=> the words "unsubscribe selinux" without quotes as the message.

--
You have received this message because you are subscribed to the selinux list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.