Re: kernels won't boot
by David Zeuthen
On Thu, 2008-01-03 at 14:08 -0500, Eric Paris wrote:
> > Can you show me more of the log?
> >
The log is more sgrubb.
> I think selinux-policy is busted at the moment. depmod and mkinitrd are
> having trouble in enforcing...
>
> rpm -e kernel-2.6.24-133-blah-blah
> setenforce 0
> yum update kernel
> setenforce 1
>
> if that fixes it blame selinux
>
> Also get the same result if you don't have your storage driver
> in /etc/modprobe.conf so you can look there first...
I'm not running SELinux enforcing mode on any of my machines..
David
16 years, 5 months
Re: [OLPC devel] su/sudo or not to sudo/su (was PATCH: add --loginpause to mingetty)
by Bernie Innocenti
Simon Schampijer wrote:
> does not auto-complete. The bash-completion (141K) package solves this,
> which I tried on my F8 machine. Maybe worth an inclusion since the
> completion works as well for other cases like:
>
> yum in[tab]
>
> (even so in the case of 'yum install b[tab]' it takes a while to list
> the packages).
I love bash-completion and I use it everywhere, but I'd not
support adding it to the base OS for the same reason we do
not install vim-enhanced, links, lftp and all the other nice
console tools.
The default console environment should be just good enough
to perform system recovery, and special administrative tasks
which have no UI yet.
Our OS images have grown over 300MB! I think we could get
them back to 200MB or so just by dropping useless dependencies
and splitting a few packages.
--
\___/
|___| Bernardo Innocenti - http://www.codewiz.org/
\___\ One Laptop Per Child - http://www.laptop.org/
16 years, 5 months
Backporting KDE4?
by Kelly Miller
Hey, since today is the official release date of KDE4, and I know it'll
be going into Rawhide, I wanted to ask if there's going to be official
packages for Fedora 8 to install KDE4.
16 years, 5 months
Re: [libdc] IDCC camera's & firewire juju stack
by Jarod Wilson
Stefan Richter wrote:
> Hans de Goede wrote:
>> Thanks for all the help, I have it working now by building a 2.6.23 kernel with
>> the patchset from here applied:
>> http://me.in-berlin.de/~s5r6/linux1394/updates/
>>
>> Then it works if I lower the number of buffer passed to dc1394_capture_setup()
>> to 2, after also applying this patch:
>> http://marc.info/?l=linux1394-devel&m=119965813322642 ?
>>
>> This is no longer needed and even coriander (from cvs) works fine!
>>
>> This is with a via vt6306 in OHCI 1.1 mode (which is the factory default for
>> this pci card), should the above patches be enough to also get it to work in
>> 1.0 mode? If that is the case I can try flashing it to 1.0 mode and see if that
>> will also work.
I can take care of testing on an VT6306 OHCI 1.0 controller, as well as a
VT6307 OHCI 1.0 controller. Just bumping to the latest linux1394 git code
wasn't enough to get dv capture working (via dvgrab) on one of my VT6307 1.0
controllers, but I'm about to give it a go with the addition of David's
dynamic buffer allocation patch.
> No, according to what several people saw with VT630x in OHCI 1.0 mode,
> there is still the bug that the DMA program stops after receiving one or
> a few frames. This is 100% reproducible with coriander + IIDC camera
> and dvgrab + DV camcorder.
> https://bugzilla.redhat.com/show_bug.cgi?id=415841
>
> As far as I understood, this presumably happens because the problem
> which David Moore addressed with "fw-ohci: Fix for dualbuffer
> three-or-more buffers" is also present but unfixed in the
> packet-per-buffer code.
I can probably get a similar fix added on top of the packet-per-buffer code
today, if it is indeed still needed.
--
Jarod Wilson
jwilson(a)redhat.com
16 years, 5 months
Common configuration for userhelper
by Miloslav Trmač
Hello,
Thanks to Carlo de Wolf's patch, rawhide usermode >= 1.94 supports file
inclusion. The usermode package also provides
/etc/security/console.apps/config-util.
If your package uses usermode to run system-wide configuration
utilities, and is not special for some reason (roughly, if you include
config-util in your PAM config file), please consider replacing the
USER=root
line in your userhelper configuration file by
. config-util
(that is dot, space, "config-util").
See #426095 for more information.
Thank you,
Mirek
16 years, 5 months
IDCC camera's & firewire juju stack
by Hans de Goede
Hi All,
Thanks for all the help, I have it working now by building a 2.6.23 kernel with
the patchset from here applied:
http://me.in-berlin.de/~s5r6/linux1394/updates/
Then it works if I lower the number of buffer passed to dc1394_capture_setup()
to 2, after also applying this patch:
http://marc.info/?l=linux1394-devel&m=119965813322642 ?
This is no longer needed and even coriander (from cvs) works fine!
This is with a via vt6306 in OHCI 1.1 mode (which is the factory default for
this pci card), should the above patches be enough to also get it to work in
1.0 mode? If that is the case I can try flashing it to 1.0 mode and see if that
will also work.
Regards,
Hans
p.s.
Next step building libdc1394 and coriander packages for Fedora!
16 years, 5 months
Re: KDE logout options with F8
by Kevin Kofler
Christopher Aillon <caillon <at> redhat.com> writes:
> If your first reaction had been to ask for more information instead of
> add complaints, I might have mentioned that the plan is to have this for
> F9 (I think so at least, someone can correct me if I'm wrong?). Not
> sure if that counts as long term...
Even if somebody implements a KDE frontend for the GDM backend, that won't make
KDM go away. There's no way KDM is going away for KDE 4.0 which realistically
will be what F9 will be shipping. (And of course, it's even less likely that
said thing would happen in 3.5. Chances that KDE 4.1 will be anywhere near
ready at F9 release are essentially nil, 4.1 might quite possibly not even make
F10.)
> It is a reasonable request. Can you accept reasonable answers? Notting
> and jkeating have already replied with technical analysis explaining why
> it is not possible.
I have suggested at least 2 technical solutions, none of which needs any
changes to Anaconda:
1. revert the default login manager in Base X to XDM. As much as you
(plural "you") hate that, it's the most logical solution and some other people
in this thread are defending it too.
2. change the fallback logic to pick KDM over GDM. As I said, I think we can
easily put KDM in a subpackage so it doesn't accidentally get installed by a
dependency on kdebase, kde-redhat used to do that in FC6 times.
There's another one, which is even less invasive (and doesn't change the
behavior for the neither-GNOME-nor-KDE case as 1. nor for the
both-GNOME-and-KDE case as 2., but really only affects KDE-but-not-GNOME which
is what needs fixing), but has to be implemented as a specialized Anaconda
hack. Pseudocode:
if (! upgrade && KDE selected && ! GNOME selected)
echo 'DISPLAYMANAGER="KDE"' >/mnt/sysimage/etc/sysconfig/desktop
> Besides, we already know it's not going to happen for F8. And F9 we
> could in theory have a better all around solution....
"better" is subjective. If upstream KDE isn't going to drop KDM or recommend
against it, IMHO that fact shouldn't be ignored.
Kevin Kofler
16 years, 5 months
PATCH: add --loginpause to mingetty
by Bernie Innocenti
Hello Florian,
the attached patches add an option to pause login until the user hits
a key.
We need something like it on OLPC because:
- we don't want to set an empty password for either user root or olpc
- at the same time, we want to allow users to login as root at the
console
- finally, we do not wish to waste memory on shells the user hasn't
yet used
The security model we are implementing is very different from UNIX: we
ultimately trust the user at the console, but we don't trust applications
and we don't want them to gain root privileges using su or sudo with no
password.
I'm committing these changes to the OLPC-2 branch of mingetty in
Fedora CVS. Please, let me know you'd like to merge them or
something similar.
--
\___/
|___| Bernardo Innocenti - http://www.codewiz.org/
\___\ One Laptop Per Child - http://www.laptop.org/
16 years, 5 months
