please try SELinux again
by Colin Walters
Hi,
Talking with a number of people at the office, it seems a high
percentage of Fedora developers disabled SELinux during FC2 test2, which
was our first attempt at SELinux. Many other users and testers in the
Fedora community likely did so as well.
I think a lot of people are not aware that things have changed (and
generally improved) dramatically since then.
Instead of the original "strict" policy which covered everything, a new
"targeted" policy has been developed which only applies SELinux
restrictions to a few select system daemons. Regular user login
sessions are unrestricted.
This targeted policy will be enabled by default for FC3. But those of
you who are upgrading from existing systems, if you earlier added
selinux=0 to your grub config, or disabled it in /etc/sysconfig/selinux,
will not be testing the new policy.
Please: undo those changes, and give it another try. Be sure
that /etc/sysconfig/selinux has these two lines:
SELINUX=enforcing
SELINUXTYPE=targeted
Also be sure you don't have selinux=0 in your grub configuration.
19 years, 7 months
Direction of wireless networking in Fedora ( was RE: Wireless update to ifup and network-functions )
by Jon Nettleton
Laptop computers are dropping in price and rising in sales. Wireless
( is | is becoming) the de facto standard for home networking. Before
Core 3 gets past the point of no return, I have to ask, "Where does
Fedora Core 3 development stand on this technology?'
For a laptop and even a desktop it seems that a clear cut idea of how
this technology should work needs be addressed. I understand that the
availibility of drivers is somewhat hampered by the manufacturers.
Looking beyond that point, I really see an oversight in how wireless
networking is being treated from the configuration standpoint.
We are really looking at a dichotomy of viewpoints in how this aspect
of networking should work. On the system administration side it is
preferable that the administrator has control over the setup. There
is no variance from the initial setup, and the networking
configurations can be stopped and started but not tampered with.
These configurations should benefit from the flexibility of wireless
to scan and use network identifiers like the AP hardware address or
the ESSID to automagically know how to connect based on existing
network configurations. On the other hand, we see the user
perspective that wants the simplicity of easily using a coffe shop, or
friends wireless connectivity.
I see NetworkManager as a solution to the latter of these issues. It
gives a nice easy gui, and password/key management for the user. I
have proposed a patch as a first stab for the first issue. If there
is no immediate plans for moving away from the ifup/ifdown managment
of network interfaces, I really feel that the wireless configuration
needs to be more dynamic than the existing scripts provide us.
As a wireless laptop user, switching wireless configurations from
location to location has definitely been less than user-friendly.
Setting up multiple profiles to choose from in grub is do-able, but
not really what I am looking for. I would really like to see a much
more dynamic network boot process that wireless networking really
demans when Fedora Core 3 is released.
-Jon
On Wed, 15 Sep 2004 15:14:34 -0400, Jon Nettleton
<jon.nettleton(a)gmail.com> wrote:
>
>
> On Wed, 15 Sep 2004 20:59:57 +0200, Kyrre Ness Sjobak
> <kyrre(a)solution-forge.net> wrote:
> > Love to see it. will you post the link here?
> >
> > ons, 15.09.2004 kl. 17.02 skrev Jon Nettleton:
> >
> >
> > > If have put together a function and some new code for
> > > is_wireless_device that uses iwlist to scan available access points
> > > and then ifup a new configuration file if it finds one matching
> > > ifcfg-DEVICE_ESSID. My questions are.
> > >
> > > 1) Is this the correct list?
> > > 2) Is this something that maintainers are interested in adding?
> > > 3) What is prefered format for patches?
> > >
> > > Hope to help out making Fedora Core 3 the best it can be.
> > >
> > > -Jon
> > >
> >
> >
>
> Here is my first set of working patches.
>
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=132661
>
> I realize that NetworkManager will eventually help solve this problem.
> But I think this is a quick and relatively simple way to get booted
> up and associated with the proper wireless network.
>
19 years, 7 months
Re: Will FC3 grub DTRT wrt installation on software RAID-1 boot arrays
by Alexandre Oliva
On Sep 10, 2004, "Doncho N. Gunchev" <mr700(a)globalnet.bg> wrote:
> When I remove any of the disks (or swap them randomly) it boots
> without problems (even changing hdc to hdd).
Right. Now try to get the first disk to fail in such a way that it
remains visible to the BIOS but it no longer works, or no longer
serves the boot sector correctly, and see how that goes. That's the
kind of scenario you might be willing to protect against, right?
Unfortunately, in this case, it won't renumber the disks, and the
system won't boot up.
> md0 is /boot and everything else is on md1 (LVM). I don't know if
> BIOS moves the first available disk to 0x80
It does. This is exactly what you're tell grub when you change the
device mapping.
--
Alexandre Oliva http://www.ic.unicamp.br/~oliva/
Red Hat Compiler Engineer aoliva(a){redhat.com, gcc.gnu.org}
Free Software Evangelist oliva(a){lsd.ic.unicamp.br, gnu.org}
19 years, 7 months
Re: Will FC3 grub DTRT wrt installation on software RAID-1 boot arrays
by Doncho N. Gunchev
On 2004 09 10 (Friday) 09:14, Alexandre Oliva wrote:
> On Sep 10, 2004, Yusuf Goolamabbas <yusufg(a)outblaze.com> wrote:
>
> > Hi, I haven't tested FC3test as yet and wanted to ask if grub in FC3
> > would do the right thing when installing on a software raid-1 boot array
> > (ie, that it would write to the MBR on both disks) so if there was a
> > disk failure, the machine would still come up.
>
> The right thing depends on your BIOS and on the disk failure mode.
>
> Consider, for example, that you have two disks, 0x80 and 0x81. If you
> naively install boot information on both disks' boot records such that
> it looks for the boot partition in the disk itself, if you remove disk
> 0x80, disk 0x81 may not boot because it becomes 0x80. OTOH, if you
> replace disk 0x80, the BIOS will likely try to boot from it, and
> fail. If it fails over to the other disk, or if you change the BIOS
> settings so as to boot from this other disk, then it might be
> renumbered to 0x80, or it might not. You can't have it work both
> ways, unfortunately.
>
> Then consider more interesting scenarios like multiple disks and you
> may realize that, when lilo claims to be safe for raid 1, it's only
> for a some failure scenarios, and within certain BIOS behaviors.
>
> > I don't know if Grub is capable of this task
>
> It is, but you have to do it yourself, implying what kind of failure
> scenarios you're trying to prepare for.
>
I have a Pentium 4 3000E and EPox EP-4PCAI with three Seagate
ST3160023A disks. I'm testing it with software raid1 and raid5 to
see how it works. I use (waiting for additional IDE controller):
--- cut ---
# grub
grub> root (hd0,0)
grub> setup (hd0)
grub> device (hd0) /dev/hdb
grub> root (hd0,0)
grub> setup (hd0)
grub> device (hd0) /dev/hdc
grub> root (hd0,0)
grub> setup (hd0)
--- cut ---
When I remove any of the disks (or swap them randomly) it boots
without problems (even changing hdc to hdd). My setup is:
--- cut ---
# cat /proc/mdstat
Personalities : [raid1] [raid5]
md1 : active raid5 hda2[0] hdb2[1] hdc2[2]
312046080 blocks level 5, 256k chunk, algorithm 2 [3/3] [UUU]
md0 : active raid1 hda1[0] hdb1[1] hdc1[2]
264960 blocks [3/3] [UUU]
-- cut ---
md0 is /boot and everything else is on md1 (LVM). I don't know if
BIOS moves the first available disk to 0x80, but GRUB loads from any
disk (even if I connect hdc only). I'll try this with more machines
when I have time to.
--
Regards,
Doncho N. Gunchev Registered Linux User #291323 at counter.li.org
GPG-Key-ID: 1024D/DA454F79 http://pgp.mit.edu
Key fingerprint = 684F 688B C508 C609 0371 5E0F A089 CB15 DA45 4F79
19 years, 7 months
Re: Will FC3 grub DTRT wrt installation on software RAID-1 boot arrays
by Alexandre Oliva
On Sep 10, 2004, Yusuf Goolamabbas <yusufg(a)outblaze.com> wrote:
> Hi, I haven't tested FC3test as yet and wanted to ask if grub in FC3
> would do the right thing when installing on a software raid-1 boot array
> (ie, that it would write to the MBR on both disks) so if there was a
> disk failure, the machine would still come up.
The right thing depends on your BIOS and on the disk failure mode.
Consider, for example, that you have two disks, 0x80 and 0x81. If you
naively install boot information on both disks' boot records such that
it looks for the boot partition in the disk itself, if you remove disk
0x80, disk 0x81 may not boot because it becomes 0x80. OTOH, if you
replace disk 0x80, the BIOS will likely try to boot from it, and
fail. If it fails over to the other disk, or if you change the BIOS
settings so as to boot from this other disk, then it might be
renumbered to 0x80, or it might not. You can't have it work both
ways, unfortunately.
Then consider more interesting scenarios like multiple disks and you
may realize that, when lilo claims to be safe for raid 1, it's only
for a some failure scenarios, and within certain BIOS behaviors.
> I don't know if Grub is capable of this task
It is, but you have to do it yourself, implying what kind of failure
scenarios you're trying to prepare for.
--
Alexandre Oliva http://www.ic.unicamp.br/~oliva/
Red Hat Compiler Engineer aoliva(a){redhat.com, gcc.gnu.org}
Free Software Evangelist oliva(a){lsd.ic.unicamp.br, gnu.org}
19 years, 7 months
Will FC3 grub DTRT wrt installation on software RAID-1 boot arrays
by Yusuf Goolamabbas
Hi, I haven't tested FC3test as yet and wanted to ask if grub in FC3
would do the right thing when installing on a software raid-1 boot array
(ie, that it would write to the MBR on both disks) so if there was a
disk failure, the machine would still come up. Currently in FC1/FC2, if
you install on software raid-1 array and then remove the first disk, the
system won't boot up since there is no boot information on the MBR of
the 2nd disk. lilo would do the right thing but since that's being
deprecated. I don't know if Grub is capable of this task
An engineer from Dell has provided a document which gives a workaround
for this
http://lists.us.dell.com/pipermail/linux-poweredge/2003-July/014331.html
Regards, Yusuf
19 years, 7 months
Re: floppy install
by Féliciano Matias
Le jeu 09/09/2004 à 03:07, Lonnie Cumberland a écrit :
> Hello All,
>
> I am starting to get a small feel for the FC2 Linux os with many
> differences from my old Mandrake 10.0 distro and I must say that I like
> what I have seen so far. In as much, I will be re-formatting my machine
> to remove the MDK and put in the FC2 code.
>
> I have seen that I can use a boot.iso burned onto a cdrom to install
> Fedora, but I was wondering what provisions were there for booting from
> a floppy and then installing over the net, NFS, hard drive, http, etc... ?
>
It's "easy" to install FC2.
You need a way to load vmlinuz and initrd.img. These files are in
/isolinux of CD1.
Most common options can be found in the same directory (isolinux.cfg and
*.msg files). askmethod parameter provide the ability to install with
NFS/FTP/HTTP and hard drive method.
For example, copy vmlinuz and initrd.img in the hard drive, then use a
floppy with grub and load vmlinuz/initrd.img :
title Fedore Core 3 _not_T2 (Install)
root(hd0,0)
kernel /vmlinuz ramdisk_size=8192 askmethod
initrd /initrd.img
You can use "Smart Boot Manager"
http://btmgr.webframe.org/index.php3 :
Booting from CD-ROM
Smart BootManager supports booting from almost all kinds
of IDE ATAPI CD-ROM
> Seems that if FC2 only supports bootable CDROM systems then it would be
> hard to place on some older machines or did I miss something?
>
> Thanks All and have a good day,
> Lonnie
>
>
19 years, 7 months
Re: FC2 Grub raid problem, long standing..
by Mogens Kjaer
Jaroslaw Gorny wrote:
...
> With all respect: it's a little bit weird advice because Lilo is not
> supported very well (You cannot choose lilo during install) and we/you
> are promoting grub as default.
You can select lilo during installation if you boot
the installation with "linux lilo".
Mogens
--
Mogens Kjaer, Carlsberg A/S, Computer Department
Gamle Carlsberg Vej 10, DK-2500 Valby, Denmark
Phone: +45 33 27 53 25, Fax: +45 33 27 47 08
Email: mk(a)crc.dk Homepage: http://www.crc.dk
19 years, 7 months
Re: FC2 Grub raid problem, long standing..
by Paul Iadonisi
On Fri, 2004-09-03 at 09:16, Hans Kristian Rosbach wrote:
[snip]
> "grub-install /dev/sda" tells me this:
> "/dev/md0 does not have any corresponding BIOS drive"
>
> /dev/md0 is /boot
>
> This bug shows that this is a LONG TIME standing bug:
> http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=55484
I have a workaround for this. I usually just edit /etc/mtab and
change the /dev/md* entries with the corresponding /dev/sda*
partitions. Use lsraid to determine what those are (or look at your
/etc/raidtab). Then the 'grub-install /dev/sda' should work. You may
also want to do the same for /dev/sdb. Don't forget to change them back
to what they were or things might get a little confused (df, for one,
will not show the correct information). It's a hack, but it's worked
for me. However, I've never tried booting either of my soft-raid1 disks
without the other one.
--
-Paul Iadonisi
Senior System Administrator
Red Hat Certified Engineer / Local Linux Lobbyist
Ever see a penguin fly? -- Try Linux.
GPL all the way: Sell services, don't lease secrets
19 years, 7 months
Re: FC2 Grub raid problem, long standing..
by Jason L Tibbitts III
>>>>> "HKR" == Hans Kristian Rosbach <hk(a)isphuset.no> writes:
HKR> BUT, I cannot boot from any of the two disks since the boot disk
HKR> is the one that died.
I put GRUB on a floppy to cover this situation. I've had machines
where the BIOS will simply not boot from any disk except the first, so
I build a GRUB floppy with a menu entry for each disk that finds /boot
and loads the grub.conf from there.
- J<
19 years, 7 months
