devel June 2004

devel@lists.fedoraproject.org

236 participants
219 discussions

Join GPG web of trust?
by Chris McDonough 02 Jun '04

02 Jun '04

Hi, A while back I volunteered to submit/maintain a Zope package to/for fedora.us ( http://www.redhat.com/archives/fedora-devel-list/2004-April/msg01016.html ). Upstream problems which violated the QA policy have been resolved now, and I believe I'm ready to submit a package. Is there someone on this list willing to sponsor me into the GPG web of trust? - C

3 3

Re: Why are there only i686 and i586 Version of glibc and kernel? -- not "older systems," "older ISAs"
by Bryan Smith 02 Jun '04

02 Jun '04

Matthew Miller wrote: > Enough people seem to care about keeping older-system support in Core, > and I don't care enouigh about moving it out, that I going to just > drop this for now. No point in arguing. Just FYI, it's not about "older systems." It's about "older ISAs." Some of these embedded x86 processors are very fast, have all the latest "toys" around them, but are very low power, with everything in a single chip. The way they do this is with an older ISA. IDT-Centaur's original WinChip, which ran well over 200MHz (up to 300MHz?), was actually a non-pipelined 486 ISA, with a massive (at the time) amount of cache. It was not only cheaper to make, but took less than 18 months to design, and worked with standard 3.3V signaling. A lot of companies licensed that design for use in their own products (STMicro?). IDT-Centaur is also a major MIPS partner, so doing this was nothing new to them. In fact, I wouldn't be surprised to find out a lot of companies did, and have 6th-Gen equivalent performing x86 cores that are only 486 ISA compatible. The rule of thumb is, everything that can be built for 386 ISA, should be built for it. Optimize for 686 architectures (PPro/II+, Athlon, etc...), but make it 386 ISA compatible. If that is not possible (e.g., NPTL), then 486 ISA. -- Bryan J. Smith, E.I. -- b.j.smith(a)ieee.org

3 2

P2 CPU "class," but 386/486 ISA "core" are commonplace -- WAS: i586/686 glibc/kernel
by Bryan Smith 02 Jun '04

02 Jun '04

This isn't about making a "lite" distro. Fedora "Core" _should_ continue to ship with the _same_ performance, memory and storage requirements. I'm talking about not assuming that a 100MHz+ system has a Pentium ISA (instruction set architecture) compatible CPU or higher. Most people seem to assume this, when there are a _lot_ of systems that don't. A _lot_ of 100MHz+ CPUs. We're talking a "system-on-a-chip" that eats up maybe 1-2Ws, or maybe hundreds of milliwatts. But they run at 133MHz or even higher, have 32-bit or even 64-bit memory bus interfaces, support even 128Mbit SDRAM technology (upto 512MB of SDRAM) and have peripherials up the wazzu on the chip itself (PCI masters, ATA100, PCCard/PCMCIA, USB, etc...). But the ISA is often only a 486 or lower! Even when the product is sold as 5th-Gen (Pentium) or 6th-Gen (Pentium II) "class" chip! Now AMD has licensed National Semi's Geode products. The Geode are the Cyrix M2 core, which are Pentium ISA. These are quickly commonplace. But AMD was is still selling its E86/SCLAN series too (and was its _only_ product for awhile), which kicks some serious butt at 133MHz, with lots of on-board peripherials. Same deal with STMicro and others. These are _huge_ in Europe, as well as non-US markets, and a lot of imports into the US as well. STMicro is notorious for marketing them as "Pentium/Pentium-II" class because they run at 100MHz, have 64-bit memory busses, PCI, ATA, USB, etc... support. But underneath, the _majority_ of STMicro products are i486 ISA. These systems are all over the place. In black boxes atop of your TV that have 128MB+ of RAM, 10-20GB disks, etc... Serious power. That's why I'm all for making the distro i686 optimized, but i386 ISA compatible. With x86-64 being adopting this year, there is little reason to start worrying about "performance." x86-64 distros will be optimized to the max, because x86-64 is a whole new architecture. But for plain Jane x86, there is little sense to break i386 ISA compatibility. Yes, _assume_ the "performance/memory/disk" equivalent of a Pentium Pro/II or higher. But leave the instruction set compatibility (ISA) at i386 -- please, for Fedora adoption sake. -- Bryan J. Smith, E.I. -- b.j.smith(a)ieee.org

3 2

Re: Why are there only i686 and i586 Version of glibc and kernel? -- not "lite," "Core" capable systems
by Bryan Smith 02 Jun '04

02 Jun '04

Matthew Miller wrote: > I've been suggesting it. Or, not dumping it, but making those systems > be the focus of a Fedora Lite instead of Fedora Core. But it seems to > be vastly unpopular. No, we're talking systems that _are_ capable of running Fedora _Core_. We're talking settop boxes, notepads, inventory devices, military interfaces, etc... stuff with _full_ GUIs! Stuff that has 128MB+ of RAM, a 20GB+ disk (typically 2.5" or even 1") and wireless networking. We're talking _modern_ applications! The only exception is the "core" of the sub-2W SoC is typically a 486 ISA. At the same time, its performance spanks a Pentium Pro silly! > Sure, but they're by their nature not normal desktop systems -- > they're special purpose devices. Right? Having Linux running on them > is cool; I just don't see it as a market for _core_. Huh? If an engineer likes Fedora, he's most likely going to want to use Fedora as a base for these devices. If a device is capable of using a popular distro, it _will_. Fedora is _ideal_ for these applications! We're not talking "Having Linux running on them is cool" -- these devices are _already_ running Linux _now_! _Millions_ already! > And my point is -- if you don't see them, then I don't think they're > what FC is aimed at anyway. AFAICT, Fedora Core is aimed at providing a community that shares a popular distro. The distro is aimed at people who have systems that are at least 5th/6th generation "class" performance, 128MB+ RAM and a hard drive. I'm not taking about accomodating any "lite" systems. That's what MontaVista and other "embedded" Linux systems do. No, I'm talking about an, again, 5th/6th generation "class" performing device, 128MB+ RAM and a hard drive. They have GUIs, are used for It's a crapload easier to not only build but, more importantly, _maintain_ (which is 80% of the engineering cycle) the distribution. If they can tap Fedora Core, then it's 99% easier. I'm not advocating changing Core (that's for another project ;-). But darn it, why oh why don't you guys realize that there are literally millions of systems running Linux _now_ that have a 486 ISA? Not some "old" system that needs Fedora "Lite," but one with 128MB+ RAM, a hard drive, a GUI and performance that smacks a Pentium Pro silly. -- Bryan J. Smith, E.I. -- b.j.smith(a)ieee.org

1 0

Re: Why are there only i686 and i586 Version of glibc and kernel? -- more "mainstream" or "popular"?
by Bryan Smith 02 Jun '04

02 Jun '04

Matthew Miller wrote: > Okay. "Older" isn't the right word. "Non-mainstream PC" maybe. > You mention embedded x86 processors -- that's exactly my point. I _swear_ this is _not_ meant to be argumentative. But you mention "mainstream." What does that mean? If it means "more popular," I'm not sure that's a good term. Because there are a _crapload_ of these systems out there (literally millions, probably 30% already running Linux). It wouldn't hurt if Fedora booted on this if possible. They have the performance, memory and disk required. As long as the software can be built for the ISA, I say leave it be. There's a good reason to aim for 386 ISA, 486 ISA if needbe. 686 still makes a nice optmization, as long as 386/486 is still the target ISA. That's all my point is. 486 ISA is still quite commonplace, even if you don't see the millions of systems where it's at. -- Bryan J. Smith, E.I. -- b.j.smith(a)ieee.org

2 1

Rebuilding Arjan's kernel-*.src.rpm
by Chris Kloiber 02 Jun '04

02 Jun '04

Is there a new magic rpmbuild option to make the kernel-sourcecode and/or kernel-doc in the same run as making kernel-smp and kernel? Perhaps some combination of --target= ? If built at different times, will the kernel-sourcecode be useful for building additional modules if needed, or have the kernel headers necessary been added into the kernel and kernel-smp rpms? -- Chris Kloiber

4 4

rawhide report: 20040602 changes
by Build System 02 Jun '04

02 Jun '04

Updated Packages: anaconda-10.0.1-0.20040602002947 -------------------------------- * Wed Jun 02 2004 Anaconda team <bugzilla(a)redhat.com> - built new version from CVS * Fri Apr 30 2004 Jeremy Katz <katzj(a)redhat.com> - Update description, remove prereq on stuff that was only needed for reconfig mode * Tue Feb 24 2004 Jeremy Katz <katzj(a)redhat.com> - buildrequire libselinux-devel arts-1.2.2-4 ------------ * Tue Jun 01 2004 Karsten Hopp <karsten(a)redhat.de> 1.2.2-4 - remove -O0 on ia64 cups-1.1.20-13 -------------- * Tue Jun 01 2004 Tim Waugh <twaugh(a)redhat.com> 1:1.1.20-13 - Enable optimizations on ia64 again. gettext-0.14.1-3 ---------------- * Wed Jun 02 2004 Leon Ho <llch(a)redhat.com> - packaged lib files for devel - moved some of the files to different sub-pkg - fix problem on x86_64 build gkrellm-2.2.0-1 --------------- * Mon May 31 2004 Warren Togami <wtogami(a)redhat.com> 2.2.0-1 - upgrade to 2.2.0 - #123846 bogus dep - Cleanup deps, build deps, and docs jcode.pl-2.13-10 ---------------- * Wed Jun 02 2004 Akira TAGOH <tagoh(a)redhat.com> 2.13-10 - no noarch anymore. (#124756) kernel-2.6.6-1.406 ------------------ * Tue Jun 01 2004 Arjan van de Ven <arjanv(a)redhat.com> - refresh ext3 reservation patch libdv-0.102-2 ------------- * Sun May 30 2004 Warren Togami <wtogami(a)redhat.com> 0:0.102-2 - Bug #123367 -devel Req gtk+-devel mpage-2.5.4-1 ------------- * Tue Jun 01 2004 Tim Waugh <twaugh(a)redhat.com> 2.5.4-1 - 2.5.4. ncurses-5.4-7 ------------- * Sun May 30 2004 Florian La Roche <Florian.LaRoche(a)redhat.de> - remove ncurses-c++-devel rpm, all files are also part of ncurses-devel * Sat May 29 2004 Joe Orton <jorton(a)redhat.com> 5.4-6 - fix xterm terminfo entry (Hans de Geode, #122815) openssh-3.6.1p2-35 ------------------ * Tue Jun 01 2004 Daniel Walsh <dwalsh(a)redhat.com> 3.6.1p2-35 - Remove CLOSEXEC on STDERR rpm-4.3.2-0.1 ------------- * Tue Jun 01 2004 Jeff Johnson <jbj(a)jbj.org> 4.3.2-0.1 - use /etc/selinux/targeted/contexts/files/file_contexts for now. - disable file contexts into package metadata during build. - fix: dev package build on s390x hack around. - fix: "/path/foo.../bar" was losing a dot (#123844). - fix: PIE executables have basename-as-soname provides (#123697). - add aurora/sparc patches (#124469). - use poll(2) if available, avoid borked aurora/sparc select (#124574). rpmdb-fedora-2-0.20040602 ------------------------- selinux-policy-strict-1.13.2-4 ------------------------------ * Tue Jun 01 2004 Dan Walsh <dwalsh(a)redhat.com> 1.13.2-4 - Fix hotplug and udev * Tue Jun 01 2004 Dan Walsh <dwalsh(a)redhat.com> 1.13.2-3 - Fix handling of selinux_config_t and default_context_t selinux-policy-targeted-1.13.2-4 -------------------------------- * Tue Jun 01 2004 Dan Walsh <dwalsh(a)redhat.com> 1.13.2-4 - Fix hotplug and udev * Tue Jun 01 2004 Dan Walsh <dwalsh(a)redhat.com> 1.13.2-3 - Fix handling of selinux_config_t and default_context_t spamassassin-3.0-0.0.svn20040530 -------------------------------- * Mon May 31 2004 Warren Togami <wtogami(a)redhat.com> - 3.0-svn20040530 - svn snapshot 20040530 - #124870 prevent service startup failure due to old -a option - #124871 more docs - #124872 unowned directories sylpheed-0.9.11-1 ----------------- * Mon May 31 2004 Akira TAGOH <tagoh(a)redhat.com> 0.9.11-1 - New upstream release. system-config-printer-0.6.100-1 ------------------------------- * Tue Jun 01 2004 Tim Waugh <twaugh(a)redhat.com> 0.6.100-1 - 0.6.100: - Set LANG=C before running /usr/sbin/alternatives (bug #124217). vnc-4.0-1.beta5.6 ----------------- * Tue Jun 01 2004 Tim Waugh <twaugh(a)redhat.com> 4.0-1.beta5.6 - Turn ppc64 builds on again. * Tue Jun 01 2004 Tim Waugh <twaugh(a)redhat.com> 4.0-1.beta5.5 - Exclude ppc64 until the build machine is fixed. - Undo last vnc.def change to get vnc.so back. wvdial-1.53-14 -------------- * Tue Jun 01 2004 Karsten Hopp <karsten(a)redhat.de> 1.53-14 - remove -O0 xfce4-panel-4.0.5-4 ------------------- * Tue Jun 01 2004 Than Ngo <than(a)redhat.com> 4.0.5-4 - add buildrequires on startup-notification-devel, bug #124948 - use %find_lang macros, bug #124948 * Mon May 31 2004 Than Ngo <than(a)redhat.com> 4.0.5-3 - own %{_libdir}i/xfce4, bug #124826 xmms-1.2.10-3.p --------------- * Mon May 31 2004 Warren Togami <wtogami(a)redhat.com> 1:1.2.10-3.p - #124701 -devel req gtk+-devel

1 0

Strange dial-up Internet question
by Steven P. Ulrick 01 Jun '04

01 Jun '04

Hello, Everyone :) If this is off topic, I do apologize, but I assure you that I have tried everything imagineable to figure out this problem, with no success so far. I figure with all the brilliant minds on this list, that someone may have some wisdom for me :) The problem is this: Sometimes when I attempt to connect to the Internet, the KPPP login screen will give me a message about there being "NO DIAL TONE" (Kppp's emphasis, not mine) I'll go downstairs, get our cordless phone, and guess what? There most definitely IS a dial tone. So, I go back upstairs with the phone, which leads me to believe we have a dial tone, and attempt to connect to the Internet. Guess what? "NO DIAL TONE" I figured out, apparently in a moment of inspiration, that if I attempt to connect to the Internet with the phone turned on (the talk button pushed to "on", just like I was going to call someone) that I can connect to the Internet every time! If I go through all that, turn the phone on and connect to the Internet, and then shut the phone off, I still remain connected to the Internet. I must add at this point that even though it will connect with the phone turned on, it connects at a pretty slow speed (example: 26400 as opposed to our norman 45333+) I have also discovered that if I unplug the phone completely from the jack that it's plugged into in the kitchen, that I cannot connect to the Internet. One of the frustrating things about this is that the problem is intermittent. For example, I just had a guy from the phone company come out and he replaced our network interface box on the side of the house (it had been hit by lightning) Well, I couldn't get this problem to occur, for the purpose of showing it to him. I also assumed that because our interface box had been fried that that could have been the cause of what I described above. I just discovered that this is not the case :( I am sitting here typing this with our cordless phone on, connected at a speed of only 26400, with a new network interface box on the outside of our house, and a brand new U.S. Robotics 56k v92 Internal PCI Fax/Voice modem in our computer, and the problem persists. If anyone has ever run up against a problem like this, I would love to have your wisdom on this. If you feel this is off topic, I would prefer that you would contact me off list, unless you feel your response could help someone else. To summarize, here are the things I've done to try to fix this: 1. New modem, as described above. 2. Had the phone company come out, and they replaced the network interface box outside. I will have my dad look at the inside wiring again, but I think that he already did that. In closing, I know that this might seem really weird, having to have a phone turned on to be able to connect to the Internet, but I am NOT making this up! Anyway, thanks in advance for any wisdom you may be able to give me on this :) Steven P. Ulrick

1 1

Why are there only i686 and i586 Version of glibc and kernel?
by dragoran 01 Jun '04

01 Jun '04

Why not add a glibc and kernel which are optimized for pentium 4 in FC3 ? This would increase the perfomance on newer PC but also works on older ones by still including the i686 and i586 versions.

10 13

Using a non-default file system in the "minimal installation"
by Martin Olsson 01 Jun '04

01 Jun '04

Hi, It would be nice if one could choose to use reiserfs (or any other file system) when doing a minimal installation WITHOUT having the disk3 available. I mean, alot of users want to choose minimal install and then apt-get/yum home their packages later on, but the file system is something you really want from scratch so it should be possible (and practical) to use a non-default file system in the minimal install. Therefore I suggest that file systems util packages etc be moved from disk3 (and wherever they reside atm) to disk1. Where can I find the list of packages that is included in the Fedora Core 2 minimal installation? Regards, /m

2 1

building packages for FC2 for external kernel modules
by Thomas Vander Stichele 01 Jun '04

01 Jun '04

Hi all, I'd like to spark some discussion on how to properly package kernel modules for FC2. I have personally packaged a few kernel module packages for FC1 for fedora.us (see http://thomas.apestaart.org/download/pkg/fedora-1-i386-fedora-stable/) and Ville Skytta has packaged some others using a different technique. I have spent some time this week getting more familiar with the linux 2.6 buildsystem, and have come up with a similar system to what I had for 2.4. I'd like to explain the various parts of the problem and solution and get some feedback so I can fix the procedure and propose it to fedora.us First of all, a few things are different with 2.6 and FC2: - you cannot use kernel-source anymore to build for all archs (i586, i686 - athlon is dropped) and types (regular and -smp) This is because you need a bunch of different headers and built files - these built files are packaged in the kernel rpm and install in /lib/modules/`uname -r`/build which is now no longer a symlink to /usr/src/linux-(rel) but a real directory. This effectively prevents you from building kernel modules for more than one arch at the same time on your system, since there's no way to install the same kernel rpm for different archs. - afaict the FC2 kernel no longer uses symbol versioning (MODVERSIONS not defined, and Module.symvers only contains "0" versions. I have no idea why this change has been made. - 2.6 has a new kbuild system that makes it possible to build out-of-source kernel modules more reliably/easily So, how does the current procedure work ? - I wrote a script (http://thomas.apestaart.org/download/tmp/kmd.py) which takes a set of kernel rpms for the same-version release, but different arch/types, extracts them, then creates a symlink/copy forest that produces a tree of dirs with the same contents as each of the four rpms (http://thomas.apestaart.org/download/pkg/fedora-2-i386-fedora-stable/kernel…) The reason for doing this is so that modules for each arch/target combo can again be built on one kernel, and the resulting rpm is smaller than four copies of the other rpms. Currently, this rpm puts files in /usr/share/kernel-module-devel-2.6.5-1.358 : common kernel-smp-2.6.5-1.358.i586.rpm kernel-2.6.5-1.358.i586.rpm kernel-smp-2.6.5-1.358.i686.rpm kernel-2.6.5-1.358.i686.rpm common is a symlink to /lib/modules/`uname -r` (which can be regular or smp, and is symlinked at %post time by the rpm). the four other directories are named exactly like the rpm they were part of, and contains a tree of files that are different to the others, and symlinks to the common directory. - In the autostars project, we have come up with a set of scripts and a sample project to package kernel modules and build them reliably and reproducably against any kernel build tree (http://cvs.sourceforge.net/viewcvs.py/autostars/autostars/linux/) This has been updated with a full set of procedures to build for 2.6 as well. Given only the argument --with-linuxdir=/usr/share/kernel-module-devel-(ver-rel)/(rpm dir), it can build the correct kernel module. (This same project can still be used to build 2.4 modules correctly as well, including redhat's special defines for boot,enterprise,smp,bigmem from /boot/kernel.h) For 2.6, it includes a libtool-like script that takes care of installing modules and taking into account symbol versions. - like before, I have created patches to hostap and ipw2100 drivers to autotoolize them using this setup. This only takes ten minutes if you're used to autotools, and ten more if you want it to work out of the box for both 2.4 and 2.6 (assuming the source allows this). - Since ipw2100 needs symbol versions and include files from hostap, I've made the hostap rpm install these files as part of a kernel-module-devel-hostap-(ver-rel) rpm, in the same tree as the original kernel-module-devel rpm. all hostap*.symvers files end up in e.g. /usr/share/kernel-module-devel-2.6.5-1.358/kernel-2.6.5-1.358.i686.rpm (which is where Modules.symvers lives). The .h files I have for now put in /usr/share/kernel-module-devel-2.6.5-1.358/kernel-2.6.5-1.358.i686.rpm/include/modules/hostap - the spec files for ipw2100 and hostap need some small tweaks to build both on pre-fc2 (with 2.4) and post-fc2. It mainly consists of the first buildrequire'ing kernel-source and kernel, and the second buildrequiring kernel-module-devel-(ver-rel). For hostap, depending on 2.4 or 2.6, different symbol versioning files are installed (builddir/include/linux/modules/*.ver versus builddir/*.symvers) Currently the configure invocation is slightly different too, but this could be fixed. The resulting rpms are up at http://thomas.apestaart.org/download/pkg/fedora-2-i386-fedora-stable/kernel… and http://thomas.apestaart.org/download/pkg/fedora-2-i386-fedora-stable/kernel… and are of course built with mach. I'd appreciate it if some other people (particularly on smp, though I don't even know if there are people with an ipw2100 AND dual cpu's) try them out and let me know if it works. I'll work on some other kernel module projects as well (I've done the qc-usb module too, but the resulting module doesn't seem to work correctly. The original upstream build against my /lib/modules tree doesn't work either, so I'm sure it's not my changes that break it :)) Here is a list of things I still need to decide or fix and would like to have input on: - the devel rpm containst the kernel's version and release as part of the name, in accordance with fedora.us's policy for actual kernel modules. It's not possible to have a "-" in the version number, so I can't put kernel ver/rel in that, and I don't want to stick it in the release tag since then it's impossible to buildrequire: it properly since on fedora.us the resulting rpm gets a 0.fdr.2 appended to the release tag. Is this ok ? - the devel rpm currently stores its files in /usr/share/kernel-module-devel-(ver-rel) Would it be more appropriate to put stuff in /usr/lib/kernel-module-devel-(ver-rel) instead ? - the devel rpm is currently set with arch i386. I've considered making it noarch, since it contains files for more than one arch. But I assume it's not possible anyway to easily build for x86, ppc and ia64 on the same machine (though the -devel rpm could still be created for all of them since it just unpacks rpms and compares files). Which of the two would be preferable in this case ? - the hostap rpm does the following: - when built with --target i386, it does the build for the four arch/type combos and packages only the devel files (symbol versions + headers), installing them in the same dir as the kernel-module-devel rpm. - when built with --target i586 or i686, it does only one build for the given 'kernel' uname -r define, and removes the devel files. This would be an argument in favour of having the -devel packages be i386; I don't think it's possible to build a -devel rpm for ppc, x86 and ia64 at the same time if you have to actually build the files. - currently, .symvers files are installed in the root of the builddir, and include files are installed in builddir/include/modules/(basename of module). For the .symvers, I think this is an ok location. For the headers, I'm not sure yet. Of course, this needs to be a location we need to agree on so interdependent modules can be built correctly. For building ipw2100, an extra include directive is given in the Makefile.am patch that points to builddir/include/modules/hostap Any suggestions on standardizing this or is this ok ? What would projects like these be expected to install them to normally ? - the module spec files could be made to work with fc2 and pre-fc2. I normally use a check to scan /etc/fedora-release and build a conditional based on that. Maybe it should check for the kernel version instead ? If so, can that be done reliably without invoking rpm as part of the check ? Is it worth it to try and integrate, or would it make more sense to just do 2.4 and 2.6 spec files separately ? - I cannot test the smp versions because my machine cannot boot the smp kernel. For all 2.4 kernels this worked fine. Has it become impossible to run smp kernels on up machines ? Does anyone know more about this ? - Anyone know why FC2 module versioning is turned off ? AFAIK the build setup we've come up with would take symbol versioning into account correctly if it were turned on. - any other suggestions/questions/objections ? Thanks, Thomas Dave/Dina : future TV today ! - http://www.davedina.org/ <-*- thomas (dot) apestaart (dot) org -*-> yes i am a long way from home <-*- thomas (at) apestaart (dot) org -*-> URGent, best radio on the net - 24/7 ! - http://urgent.fm/

3 4

Why is hotplug disabled when loading network modules
by Jean-Rene Cormier 01 Jun '04

01 Jun '04

Hi, I have a laptop with an Intel Pro Wireless 2100 card and I'm using the ipw2100 driver which loads the firmware through hotplug and was wondering why the firmware wasn't getting loaded at boot time. Someone on the IPW2100-devel list mentioned that hotplug was getting disabled in the is_available function in /etc/sysconfig/network-scripts/network-functions and looking at that file I can see that I have these lines which do disable it: HOTPLUG=`cat /proc/sys/kernel/hotplug` echo "/bin/true" > /proc/sys/kernel/hotplug modprobe $1 > /dev/null 2>&1 || { echo "$HOTPLUG" > /proc/sys/kernel/hotplug return 1 } echo "$HOTPLUG" > /proc/sys/kernel/hotplug Why is hotplug disabled when loading the module? And what should be the "proper way" of loading the firmware? Jean-Rene Cormier

2 1

Need grub interface -- define specifics
by Bryan Smith 01 Jun '04

01 Jun '04

ndbecker2(a)verizon.net wrote: > I found it was very difficult to find information on how to repair this. > The grub info itself has lots of detail, but is remarkably short on basic > howto. > Anyway, what Fedora can really use is a way to rerun grub-install, possibly > with changed parameters. > I am a highly experienced user, but I have to do grub-install just > infrequently enough that it's always a major PIA to dig up the info on how > to do it. >From my understanding, this is caused by differences in BIOS disk number to Linux disk device mappings. It's difficult to compensate for this issue automatically, regardless of LILO or GRUB. Maybe there is a way to automatically extract the BIOS disk number and then re-create the mapping file. But when do you do it? Sometimes people just swap disks once, but should it be run automatically then? Detail what it _should_ do _exactly_ and then I can better tell you if it is feasible or not. -- Bryan P.S. The only alternative is to do what Windows does. Have a "dumb" MBR boot the "active" primary partition on BIOS disk 80h, and _hope_ there is a driver for it in the root C:\. Heck, XP doesn't even let you change ATA drivers. I had to hack the registry manually once to do this when I changed a mainboard (after a SiS chipset mainboard blew and a ViA chipset mainboard was put in -- not good when you're 1,100 miles from home with 1 computer ;-). -- Bryan J. Smith, E.I. -- b.j.smith(a)ieee.org

2 1

Need grub interface
by Neal Becker 01 Jun '04

01 Jun '04

anaconda does a great job setting up grub. Just one problem. AFAICT, there is no convenient way to redo this process. I just added a drive to my machine, and I needed to redo grub. All drive numbers changed. I found it was very difficult to find information on how to repair this. The grub info itself has lots of detail, but is remarkably short on basic howto. Anyway, what Fedora can really use is a way to rerun grub-install, possibly with changed parameters. I am a highly experienced user, but I have to do grub-install just infrequently enough that it's always a major PIA to dig up the info on how to do it.

1 0

problem with Linux 2.6.6-1.403 and scsi
by Rui Miguel Silva Seabra 01 Jun '04

01 Jun '04

I think it doesn't bite me (unless usb-storage for some reason needs it), but I think there might be some problem... This happened with 2.6.6-1.397 too! Rui [root@roque root]# apt-get install kernel#2.6.6-1.403 Reading Package Lists... Done Building Dependency Tree... Done The following NEW packages will be installed: kernel#2.6.6-1.403 0 upgraded, 1 newly installed, 0 removed and 2 not upgraded. Need to get 14.0MB of archives. After unpacking 35.1MB of additional disk space will be used. Get:1 ftp://ftp.pt.freshrpms.net pub/freshrpms/ayo/fedora/linux/development/i386/core kernel#2.6.6-1.403 2.6.6-1.403 [14.0MB] Fetched 14.0MB in 2m44s (85.3kB/s) Committing changes... Preparing... ########################################### [100%] 1:kernel ########################################### [100%] WARNING: /lib/modules/2.6.6-1.403/kernel/drivers/scsi/pcmcia/fdomain_cs.ko needs unknown symbol kernel_scsi_ioctl WARNING: /lib/modules/2.6.6-1.403/kernel/drivers/scsi/fdomain.ko needs unknown symbol kernel_scsi_ioctl Done.

2 1

requesting more bugzilla permissions
by Marius Andreiana 01 Jun '04

01 Jun '04

Hi Please add more rights to my bugzilla account, marius_bugs at galuna.ro I'd like to bug triage and QA from time to time. Here are the bugs I've added comments to so far: http://bugzilla.redhat.com/bugzilla/buglist.cgi?query_format=&short_desc_ty… I also have privileged accounts on bugzillas at gnome.org and mozilla.org Thanks! -- Marius Andreiana Galuna - Solutii Linux in Romania http://www.galuna.ro

1 0

rawhide report: 20040601 changes
by Build System 01 Jun '04

01 Jun '04

Updated Packages: rpmdb-fedora-2-0.20040601 -------------------------

1 0

Self-Introduction: Alex Perez
by Alex Perez 01 Jun '04

01 Jun '04

[If you get this twice, my sincere apologies.] Hi there, my name is Alexander Joseph Perez, and I'm a co-maintainer of the GNUstep.org website and have been using GNUstep.org for several years. I'm from Santa Rosa, California, in the USA, am a full time anthropology student at Santa Rosa Junior College and work part time as a lowly help desk technician for the City of Santa Rosa, California. I'm writing this e-mail because I've recently noticed that the most recent release of Fedora Core (2) does not contain any GNUstep packages, and as I've just installed it after getting sick and tired of Debian, I'd like to change that. I am intimately famaliar with the build process, and have a significant amount of personal contact online with the GNUstep core development team on a daily basis. I'd be willing to do QA on my packages as long as the requirements were reasonable. In short, I'd like to expose GNUstep to a wider audience now that it is ready for such exposure. GNUstep has been a long-lived project, and "we're not dead yet" seems to have become our mantra. GNUstep is not dead. In fact it's alive and well, and with the inclusion of GNUstep packages into Fedora Core, one of the more popular distributions of Linux, we will gain the potential to expose many more people to GNUstep and its offerings. As I said previously, I'm a current GNUstep.org website maintainer, and am working on unifying the disparate GNUstep-related documentation sources which are/have been strewn across the expanse of the Internet until recently (much of it still is). I love the simplicity and true Object-Oriented nature of the Objective-C programming language, which GNUstep is based on. My associate, Andrew Pinski, is the GCC libobjc (GCC Objective-C runtime) maintainer and works periodically for apple as his college career permits. I recently worked with him to make sure that some of the patches to the Objective-C runtime were integrated into libobjc head. If anyone here has any questions, please feel free to contact me at aperezATstudentDOTsantarosaDOTedu as I'd be glad to answer or clarify any points I've made here. I am not subscribed to the fedora-devel mailing list and do not wish to be unless I am "accepted" and allowed to create and provide GNUstep packages to Fedora. My GPG fingerprint is 2F36 2A89 14B4 B58F 176B 1B26 5E4D 5FCA 9190 2041 and this has been uploaded to pgp.mit.edu Cheers, Alex Perez -- pub 1024D/91902041 2004-05-31 Alex Perez (MrBIOS) <aperez(a)student.santarosa.edu> Key fingerprint = 2F36 2A89 14B4 B58F 176B 1B26 5E4D 5FCA 9190 2041 sub 2048g/380DB427 2004-05-31

4 3

Re: Missing ethereal after installation of FC2
by "Nils O. Selåsdal" 01 Jun '04

01 Jun '04

On Sun, 2004-05-30 at 18:00, Charles R. Anderson wrote: > On Sun, May 30, 2004 at 05:41:22PM +0200, Casper Pedersen wrote: > > I have found a bug in ethereal-0.10.3.2 which is installed with FC2. > > I've filed bug 124721, and here is the fix for it > > + %{_bindir}/ethereal > > + %{_sbindir}/ethereal > > Those two files are not supposed to be in the ethereal package, since > they are in the ethereal-gnome package. The bug is perhaps that ethereal-gnome should be installed as well. I also got a little puzzled by ethereal beeing installed by default, but not ethereal-gnome.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

devel June 2004