Does anyone knows who I should ask about nash and cpio initrd support?
(see my yesterday post)
Or at least where to ask for someone who knows?
Documentation is often out of date and I could not find any information
about why does FC3 changes initrd format from ext2 fs to cpio archive...
Thanks for the pointer to pup stuff.
But, the pup:yum::synaptic:apt-get thing isn't quite correct, as pup is
designed specifically to only address the issue of package updating,
isn't meant to be a general GUI frontend.
Does this mean it won't be able to be used for yum install or yum remove commands? What a shame. Or is there some other aspect of synaptic that you're assuming I know about (not your fault - mine for using it in the comparison) because I have only used it once almost a year ago.
Are there screenshots of pup anywhere?
Do you Yahoo!?
Yahoo! Mail - You care about security. So do we.
Looking at the overlap of the FC4 schedule with the GCC 4.0 schedule,
it appears that shipping GCC 4.0 in FC4 has become viable.
In order to avoid a large duplication of bandwidth by rebuilding
with GCC 4.0 between test releases, Fedora Core 4 Test 1 has now
slipped two weeks to allow for integration of a GCC 4.0 snapshot,
and rebuilds against it.
Fedora Core 4 Test 1 is now scheduled for March 14; the schedule
at http://fedora.redhat.com/participate/schedule/ will be updated
- Is GCC 4.0 released yet?
No. It's likely to be released around mid-April.
- Does that mean Fedora Core 4 will ship with a pre-release compiler?
We're not *that* crazy. If GCC 4.0 is delayed, we will either
revert, or slip.
- What's so cool about GCC 4.0?
GCC 4.0 includes:
- new intermediate languages that allow for new/better optimizations
As part of this, this allows for better compile and run-time memory
checking and overflow protection.
- better and more complete Java support
- Fortran 95 support
- Is GCC 4.0 ABI compatbile with GCC-3.4.x?
- For C/C++, yes.
Last week at FUDCon, I presented a 10-15 minute discussion on the an
ia64 FC4 (hopefully ;)) distribution.
I've had interest from several developers and now am going to make a
general call onto the devel list for others who wish to participate.
Please email prarit(a)sgi.com and we'll see where we go from here.
I think about a dozen digests ago someone mentioned a
program called pup replacing yum. Is there somewhere
I can look to see information about this program? Is
pup to yum as synaptic to apt-get or is it completely
Do you Yahoo!?
Yahoo! Mail - Helps protect you from nasty viruses.
First of all, please direct me to an other mailing list if I'm going off
I've investigated a bit the initrd system and there are some questions I
could no find answers for:
- why are regular desktop distributions always using the initrd system?
I understand that this system is mandatory to load exotic scsi drivers
or add a pause when booting to usb but I wonder why it is always used
- on kernel 2.4 (red hat 9) the initrd image is an ext2 filesystems. It
contains a linuxrc nash script. On kernel 2.6 (fedora 3) the initrd is a
cpio archive and does not contains a linuxrc script. Could someone
briefly explain me why these differences? Particularly I wondering about
1) I tried to repack my custom initrd ext2 filesystem into a cpio
archive and found that when packed as a cpio archive it's not executing
my linuxrc script (is it the way it's supposed to be?)
2) What are the differences between pivot_root and switch_root (new in
3) Why using nash in the first place? Could we just wait until the end
of the linuxrc script? At that time the kernel would move to the new
root fs (whitout the need for pivot_root or switch_root)
And finally, if I'm right the end of the nash script (after switch_root)
is never executed?
We have a computer acting as a server that locks hard (PS2 keyboard
stops responding, prompt never returns, boot gets no further) when USB2
is enabled on FC3 (there were no lockups with FC1). I finally traced
this down to being some sort of interaction between udev and USB2. The
following steps reproduce the problem:
Boot the kernel with init=/bin/sh
mount -n -t proc /proc /proc
mount -n -t sysfs /sys /sys
The machine will hang and not get any further nor will it respond to a
ctrl-alt-del or sysrq commands.
modprobing uhci-hcd before starting udev causes the problem to disappear
as does disabling USB2 (but leaving USB1 on) in the BIOS. Kernels tested
are kernel-2.6.9-1.667 and kernel-2.6.10-1.766_FC3. lspci prints the
following USB controller:
00:07.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 16)
Does this sound like a known issue?
Sitsofe | http://sucs.org/~sits/
Once upon a time, Rahul Sundaram <rahulsundaram(a)yahoo.co.in> said:
> again relying on third parties who might not have the
> knowledge or infrastructure is not very useful. its
> trivially easy to burn a set of ISO images and
> redistribute the CD's. creating ISO images from the
> rpms doesnt seem to be that easy. Am I mistaken?
Making a DVD probably isn't too hard (it somewhat depends on how
anaconda will handle things), since the total size of Extras for one
arch is under 4.5G.
Making CDs will not be as straight-forward, since it won't all fit on
Chris Adams <cmadams(a)hiwaay.net>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.