pre-extras: SRPMS?
by Rex Dieter
I noticed the pre-extras repo doesn't have SRPMS available. Is this
intentional or oversight? Could these be provided?
-- Rex
19 years, 3 months
lvm on x86_64?
by Thomas J. Baker
Trying to install something FC3ish on a Dell 670n without much luck. I
tried booting the latest devel image and it says "lvm is not supported
on this platform". Is this a bug or the truth? Looking through bugzilla,
it looks like the devel image may just be broken.
tjb
---
=======================================================================
| Thomas Baker email: tjb(a)unh.edu |
| Systems Programmer |
| Research Computing Center voice: (603) 862-4490 |
| University of New Hampshire fax: (603) 862-1761 |
| 332 Morse Hall |
| Durham, NH 03824 USA http://wintermute.sr.unh.edu/~tjb |
=======================================================================
19 years, 3 months
Python vs multilib module packaging question
by Joe Orton
In subversion.spec I used:
%define pydir %(python -c 'from distutils import sysconfig; print
sysconfig.get_python_lib()')
to find the directory in which to package Python modules, but on x86_64
this produces /usr/lib/python2.3/site-packages rather than /usr/lib64,
which is presumably wrong.
Is that a Python bug, or is there some other sysconfig.* thing which
should be used to make this work properly?
Regards,
joe
19 years, 3 months
why doesn't yum cache anything?
by Jamie Zawinski
Here's a typical use case for yum with me:
- notice that "xmtr" is not installed (but "mtr" is)
- yum list '*mtr*'
- wait through ~60 seconds of:
Setting up Repo: base
repomd.xml 100% |=================| 1.1 kB
00:00
Setting up Repo: updates-released
repomd.xml 100% |=================| 951 B
00:00
Reading repository metadata in from local files
base : ############################################# 2622/2622
updates-re: ############################################# 405/405
- yum -y install mtr-gtk
- wait through that same ~60 seconds of junk before it actually
starts downloading the package.
So my questions are:
- Is there some way to make yum cache all that crap? I'd be
perfectly ok with it just reusing the same repository data
for days at a time. Certainly there's no need to re-download
it every single time I invoke yum.
- If there's no way to do that... how can you guys stand it?
Do you really suffer through this every time, or do you just
not use yum? Is there something else I should be using instead?
--
Jamie Zawinski jwz(a)jwz.org http://www.jwz.org/
jwz(a)dnalounge.com http://www.dnalounge.com/
http://jwz.livejournal.com/
19 years, 3 months
rawhide report: 20050110 changes
by Build System
Updated Packages:
mozilla-37:1.7.5-3
------------------
* Sun Jan 09 2005 Christopher Aillon <caillon(a)redhat.com> 37:1.7.5-3
- Update pango selection patch to fix cursoring in textareas.
psutils-1.17-24
---------------
* Mon Jan 10 2005 Tim Waugh <twaugh(a)redhat.com> 1.17-24
- Manpage correction for psresize (bug #144582).
rpmdb-fedora-1:4-0.20050110
---------------------------
vsftpd-2.0.1-8
--------------
* Mon Jan 10 2005 Radek Vokal <rvokal(a)redhat.com> 2.0.1-8
- use localtime also in logs (#143687)
19 years, 3 months
what USB-2 CF reader is alleged to work?
by Jamie Zawinski
I'm sorry for asking what you may think is a total newbie question, but
my inability to reliably get pictures off my camera has reached comical
proportions at this point. In the last few years, I've gone through
permutations of three different motherboards, three different CF
readers, and some subset of RH8, RH9, FC2, and FC3, and to this day, the
best way I've found to get pictures off my camera's card has been "plug
it into my girlfriend's mac, and use scp."
So here is my question:
Are any of you running FC3 and able to get pictures off of a
CompactFlash card at USB-2 speeds? If so, what CF reader are
you using? Because I want to go out and buy one of those.
The set of readers I have tried recently are:
- Dazzle USB 2.0 reader, no model number apparent;
- SanDisk ImageMate SDDR-31 USB 1.0 reader;
- (another USB 1.0 reader that I don't have here at the
moment, but that came with my Canon 10-D camera).
All of them do this when I plug them in (card present or not):
usb 5-1: new full speed USB device using address 52
usb 5-1: device not accepting address 52, error -71
usb 5-1: new full speed USB device using address 53
usb 5-1: device not accepting address 53, error -71
Both ehci-hcd and uhci_hcd get loaded. This is after installing
davidz's newly-non-broken version of hald (bug 142183).
The Dazzle doesn't work at all on an OSX Mac, but the other two do.
I have, at various times, seen all three of these work eratically on
previous versions of Linux, though I think the last time was FC2.
I have, in fact, seen the Dazzle work at USB-2 speeds, but not lately.
"Eratically" means that generally they would work immediately after
I rebooted the machine, and I could plug/unplug them right after
that, and they'd continue working; but if I tried to use them again
a few hours later, the only way to make them work would be to reboot
again. No amount of rmmod would bring joy (though some would bring
complete wedgedness.)
--
Jamie Zawinski jwz(a)jwz.org http://www.jwz.org/
jwz(a)dnalounge.com http://www.dnalounge.com/
http://jwz.livejournal.com/
19 years, 3 months
Xen Grub configuration
by Felipe Alfaro Solana
Hi!
After installing kernel-xen0 from RawHide, the following lines were
added to my /boot/grub/menu.lst:
title Fedora Core (2.6.10-1.1074_FC4xen0)
root (hdX,X)
kernel /vmlinuz-2.6.10-1.1074_FC4xen0 ro root=/dev/XXX
initrd /initrd-2.6.10-1.1074_FC4xen0.img
However, this is incorrect, as vmlinuz-2.6.10-1.1074-FC4xen0 cannot be
booted by GRUB directly (must be ran under the control of the XEN
hypervisor). Instead, GRUB *must* boot /boot/xen.gz which is the XEN
hypervisor kernel. Thus, /boot/grub/menu.lst should look like this:
title Fedora Core (2.6.10-1.1074_FC4xen0)
root (hdX,X)
kernel /xen.gz dom0_mem=400000 noreboot
module /vmlinuz-2.6.10-1.1074_FC4xen0 ro root=/dev/XXX
module /initrd-2.6.10-1.1074_FC4xen0.img
Note how now xen.gz is the kernel, and take note of the "dom0_mem"
kernel parameter which is needed for XEN to allocate physical memory
for XEN's domain 0, Omitting the "dom0_mem" parameter makes XEN
allocate too little memory for the domain 0 kernel which, as result,
will crash with an Out of Memory error.
"dom0_mem=400000" could default to "dom0_mem=130000" instead. This
shouldn't be much of a problem since if we try to allocate more memory
than the maximum available RAM, XEN hypervisor will complain. However,
omitting "dom0_mem" will make the Linux kernel crash and reboot, which
is much worse.
Should I fill in a bug report for this?
Thanks.
19 years, 3 months
Re: what USB-2 CF reader is alleged to work?
by Pete Zaitcev
On Sat, 08 Jan 2005 14:56:22 -0800, Jamie Zawinski <jwz(a)jwz.org> wrote:
> So yeah, I've already run so far out of ideas that I've gone down the
> "replace absolutely everything" path. [...]
> Ok, what other info would help?
Please let me know what kernel you are running first. But I have to admit
I do not have good ideas currently. At a minimum this is likely to take
retries with instrumented kernels. Sorry about that. I'll get back to
you about it.
-- Pete
19 years, 3 months
Requesting for Blockers
by Jeff Pitman
How do we go about requested for FC4 blocker status on a bug?
>From kernel 2.6.8, the default codepage for utf8, cp437.ko has been left
out of the config. This causes kernel oopses when listing a vfat
directory which uses unicode characters (chinese in my case). Maybe if
this code page is so critical as to cause an oops, maybe it should be
statically compiled. I dunno. If it's an upstream deal, I hope
someone kind enough can pass on the word.
Bug in question:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=129966
thanks,
--
-jeff
19 years, 3 months
rawhide report: 20050109 changes
by Build System
Updated Packages:
audit-0.6.1-1
-------------
* Sat Jan 08 2005 Steve Grubb <sgrubb(a)redhat.com> 0.6.1-1
- New version: rework auditctl and its man pages.
- Added admin_space_left config option as last chance before
running out of disk space.
gcc-3.4.3-13
------------
* Fri Jan 07 2005 Jakub Jelinek <jakub(a)redhat.com> 3.4.3-13
- fix memory attribute computation for addqi_1_slp (PR target/19012)
- fix TYPE_MODE of enum with __attribute__ ((mode ())) (#144358)
* Wed Jan 05 2005 Jakub Jelinek <jakub(a)redhat.com> 3.4.3-12
- update from gcc-3_4-branch
- PRs c++/14607, middle-end/19175, rtl-optimization/12092, target/17643
- fix ICE in same_translation_unit_p (#144166)
* Mon Dec 27 2004 Jakub Jelinek <jakub(a)redhat.com> 3.4.3-11
- update from gcc-3_4-branch
- PRs c++/17972, c++/18962, c++/18975, java/14104, libobjc/12035,
middle-end/17930, middle-end/18424, middle-end/18493,
middle-end/18590, middle-end/18730, middle-end/18882,
middle-end/19068, other/18508, other/18665, other/19093,
preprocessor/15167, rtl-optimization/16968, target/16819,
target/17990, target/18002, target/18153, target/19005,
target/19010, target/19028, target/19102, target/19147
- fix ICE in dwarf2out (Devang Patel, Eric Botcazou, #143719,
PR debug/16261)
- fix ICE in reshape_init_array (#143034, PRs c++/18384, c++/18327)
kernel-2.6.10-1.1075_FC4
------------------------
* Sat Jan 08 2005 Dave Jones <davej(a)redhat.com>
- Periodic slab debug is incompatable with pagealloc debug.
Disable the latter.
rpmdb-fedora-1:4-0.20050109
---------------------------
19 years, 3 months
