users July 2010

users@lists.fedoraproject.org

336 participants
469 discussions

Firefox 4 repo
by Mike Chambers 19 Jul '10

19 Jul '10

Anyone started or know of a repo for installing/upgrading/trying out this from rpm instead of the source? Mainly for F13 but rawhide would be fine too if need be. -- Mike Chambers Madisonville, KY "Best lil town on Earth!"

9 36

None
by terry 19 Jul '10

19 Jul '10

1 0

Re: Fedora 13 installation, does not boot
by Vincent 19 Jul '10

19 Jul '10

> From: "Darr" <darr(a)core.com> > Subject: Re: Fedora 13 installation, does not boot > On Sunday, 18 July, 2010 @14:24 zulu, Vincent Onelli scribed: > > > By runing depmod -a I got the following: > > WARNING: Couldn't open directory /lib/modules/2.6.33.3-85.fc13.i686: > > no such file or directory. > > FATAL: could not > > open /lib/modules/2.6.33.3-85.fc13.i686/modules.dep.temp for writing: > > no such file or directory. > > I log in "modules" directory and found only > > "2.6.33.6-147.fc13.i686.PAE." Does this means that I need to do > > some kind of update? > > Hmmmm.. 2.6.33.3-85.fc13.i686 is the default kernel installed by > fc13 (and boots in rescue mode), though 2.6.33.3-85.fc13.i686.PAE > is usually installed if the processor supports extended addressing, > even if you don't have 4GB or greater RAM installed (4GB might > be the maximum possible with the 8300; if so, PAE would not > provide much of an advantage). > > Fedora keeps the last 3 kernels installed by default... however, there > seems to be only 1 kernel installed on your Dell (indicated by having > only the 2.6.33.6-147.fc13.i686.PAE subdirectory present). > > Did you change the /etc/yum.conf file's installonly_limit parameter ? > > Or do you recall removing the 2.6.33.3-85 kernel after the initial install? no, it never see the boot kernel from the Dell splash screen the cursor goes to the top left of the screen and stays there. > > Someone earlier suggested removing the rhgb and quiet from the kernel > line in the grub menu... then you said you had tried to edit grub.conf - > I'm I couldn't not remove any thing. Grub.conf apparently is a non editable file > sure they were referring to the boot menu that presents right after the POST > screen disappears, allowing you to choose between windows and fedora. > Select the 2.6.33.6-147 kernel, then hit 'a' to alter the kernel > parameters... boot menu never appeared > hit Enter after deleting the rhgb and quiet; that change lasts only for one > boot cycle. I usually just hit Esc when the GUI boot appears to see the > boot messages... essentially the same as removing rhgb and quiet > Is there only 1 kernel listed in that menu, by the way? yes > Sorry for the delay in replying - my ISP has been down most of the day. > By the way, the installation from the alive CD behave the same way.

2 1

Re: Can one now help?
by Parshwa Murdia 19 Jul '10

19 Jul '10

> ---------- Forwarded message ---------- > From: Marko Vojinovic <vvmarko(a)gmail.com> > To: users(a)lists.fedoraproject.org > Date: Mon, 19 Jul 2010 04:35:36 +0100 > Subject: Re: Can one now help? > On Sunday, July 18, 2010 23:35:34 Parshwa Murdia wrote: > > Ok, as an aftermath, for educational purposes :-) : > > * The partition /dev/sda1 is what corresponds to the C: partition on > Windows. > It is the so-called "primary" partition, and only 4 of those can exist on > the > disk. They are named /dev/sda1 through /dev/sda4 in Linux. > * You don't have any more primary partitions, and /dev/sda2 is instead a > so- > called "extended" partition, which is actually only a "container label" for > all other partitions that follow, which are not primary. > * The first partition contained inside the extended one is /dev/sda5 (if > the > number were less than 5 it would correspond to a primary partition, and > could > not be inside the extended one). This one is probably the Windows D: > partition. > * As above, /dev/sda6 and /dev/sda7 are also members of the extended > partition, and correspond to your Windows drives E: and F:. Now, somewhere > in > between those letters Windows might stick the CD/DVD drives and assign its > letters differently. The CD/DVD drives are *not* listed by the above fdisk > command, and I can only guess how Windows will order its drive letters. > * The /dev/sda8 partition is also a member of the extended one, and most > probably the Fedora /boot partition, where the kernel and grub files > reside. > Windows does not show a letter for that one, since it doesn't recognize > Linux > partitions in general. > * Finally, the /dev/sda9 partition is again not a real partition, but again > a > container like /dev/sda2 (although of quite different type). It is > contained > inside /dev/sda2, and it contains yet more partitions. This container is of > LVM type, and contains all other Linux partitions (probably root and swap) > inside. These partitions are not listed by fstab. > > I know it sounds complicated. And believe me, it is. That is what you get > when > you mix very old standards (only four partitions allowed on the disk) with > patched technologies and new hyped ideas --- you get one primary partition, > and several of them inside LVM which is inside the extended partition which > is > a bogus primary one. > Really complicated, I would have to see much and try to understand its basics. > Don't ask me how did disk partitioning evolve into such a stupid state. > When > IDE disks were being standardized (long time ago), nobody dreamed that one > day > you might wish to have more than 4 partitions on the disk, dual boot system > and wish to be able to resize partitions on a live disk. So they invented a > stupid and shortsighted standard which had to be patched after it became > *obviously* shortsighted... > > Of course, as you already found out yourself, mounting partitions inside > the > LVM container is not the same as trying to mount the LVM container itself > (the > latter is bound to fail, since it is just a container, not an actual > partition...). Hence the errors. > Yes. Although I am confused about sda8, it is type 83 (ext2/3/4), that one > *should* > have worked. But nevermind now... ;-) > Oh I see. > And of course, I missed to remember that you probably have a LVM container > by > default, so my original instructions didn't work as I thought they should. > My > bad. But you found out what is the proper procedure for that case via > google. > :-) > No probs, it happens in technology. Frankly speaking, I am a novice and a beginner, I just listen to music on Fedora and check my mails but for security reasons, and as it is better than Windows, I am using it. To learn it, it would take much much time for me at least. > Well, the fstab file is a file that contains rows and columns. > Specifically, each > row must contain 6 columns. Column entries are separated with a space. So > for > example, the line > > tmpfs /tmp tmpfs defaults 0 0 > > has "tmpfs" in the first column, "/tmp" in the second, "tmpfs" in the > third, > "defaults" in the fourth, and "0" in fifth and sixth. And that is ok. > > Now, if you look at one of the lines you modified initially, for example: > > /dev/mapper/VolGroup-lv_root / ext4 defaults, noatime, nodiratime 1 1 > > I am counting 7 spaces total, which means that line has 8 columns, which > the > computer does not tolerate. The "defaults,", "noatime," and "nodiratime" > are > distributed into three columns, when they should all be in only one (4-th > column). When you introduced extra spaces, you introduced extra columns, > which > is wrong. The right line should be > > /dev/mapper/VolGroup-lv_root / ext4 defaults,noatime,nodiratime 1 1 > > Now there are no extra columns, you have 5 spaces delimiting 6 columns > total, > and the data in the 4-th column is "defaults,noatime,nodiratime", as it > should > be. The computer knows how to interpret and understand this. > Too much depth, I earlier ran the commands thinking it would simply increase the bandwidth, but running with even a single mistake is really troublesome. > If you want to read more about the structure and syntax of the fstab file, > type > "man fstab" in the terminal, and read on. > > The "man" command stands for "manual", and gives you usage instructions for > whatever command you wish to know about. Try "man mount", "man ls", "man > cd", > "man vgscan", and so on. Try even "man man", there is a manual about using > the > manual. :-) > > If you want to be able to use Linux with greater power, you need to be > skillful in using the terminal. Reading manual pages is the first place to > start learning. If you are very determined to learn, read "man bash". > > If you are a masochist, read "man bash" twice. ;-) > > Precisely. After the explanation above, it should be clear what was wrong > and > why it is now correct. > Yes. > ---------- Forwarded message ---------- > From: JD <jd1008(a)gmail.com> > To: vmarko(a)ipb.ac.rs, Community support for Fedora users < > users(a)lists.fedoraproject.org> > Date: Sun, 18 Jul 2010 20:48:25 -0700 > Subject: Re: Can one now help? > I wonder why the fedora installer did not create a gpt partitioned disk, > instead of old dos partitioning scheme. > If they might have done this, we could have asked "why the fedora installer did not create a old dos partitioning scheme, instead of a gpt partitioned disk." Every part has its own problems. > ---------- Forwarded message ---------- > From: Marko Vojinovic <vvmarko(a)gmail.com> > To: users(a)lists.fedoraproject.org > Date: Mon, 19 Jul 2010 04:50:15 +0100 > Subject: Re: Can one now help? > On Sunday, July 18, 2010 22:56:35 Christofer C. Bell wrote: > > And this is *precisely* why I hate LVM being the default. While a newbie > typically has trouble to understand even the above output, and is > completely > lost with the added layer of complexity of LVM, when something stupid goes > wrong it can easily become rocket science to mount and fix something > inside LVM. > For beginners, its really troublesome. > And the benefit of LVM for a newbie is next to nothing, they are hardly > even > aware what LVM is and how it can be used, let alone manipulate it from a > rescue environment. > > I know LVM is useful if one needs its functionality, but it is a complete > overkill as a default installation choice, IMNSHO. People who know they > need > it typically know how to choose it during installation. People who don't > know > about it typically don't need it. Why it is chosen by default is beyond me. > Everytime, something new they try to do, so they implemented it with LVM, I hope this may be reason.

2 2

Firefox Beta
by John Wendel 19 Jul '10

19 Jul '10

I installed the latest Firefox Beta on a 32-bit F11 box, and I'm really impressed. So, I decided to install it on my 64-bit F13 box. The problem - the F13 box is 64-bit only and the Firefox beta seems to be 32-bit, so I need a set of 32-bit libraries. Since the Firefox install isn't an RPM, I need to satisfy the dependencies manually. Is there and easy way to determine what libraries are required to run Firefox? Thanks, John

4 4

How's gnash for flash comin' ?
by Bill Case 19 Jul '10

19 Jul '10

Hi; Does anybody have an idea when we might see an update for gnash. I keep watching the threads, upgrades etc. to see if one is on the way. I am trying to avoid going back to adobe flash, but I am losing too many services because of it and/or Mozilla. The latest google (GNU and others) information I can find goes back to Feb 15, 2010. -- Regards Bill Fedora 13, Gnome 2.30.2 Evo.2.20.2, Emacs 23.2.1

2 1

Grub2 question
by JD 19 Jul '10

19 Jul '10

Has anyone installed grub2 on F13? If yes, did it work OK? did you have to manually modify any files in /boot/grub? If it did not work, was it easy to get back to legacy grub?

7 18

RE: Fedora 13 installation, does not boot
by Vincent 19 Jul '10

19 Jul '10

> From: Harald Hoyer <harald.hoyer(a)gmail.com> > Subject: Re: Fedora 13 installation, does not boot > On 07/18/2010 04:24 PM, Vincent Onelli wrote: > >> From: "Darr"<darr(a)core.com> > >> On Saturday, 17 July, 2010 @23:56 zulu, Vincent Onelli scribed: > >> > >>> I used the rescue disk typed: chroot /mnt/sysimage > >>> then dracut -f /boot/initramfs-$(uname -r).img $(uname -r) and got the > >>> fallowing answer: > >>> find:'/lib/modules/2.6.33.3-85.fc13.i686/':no such file or directory > >> > >> Follow that same rescue procedure and after chroot, run > >> # depmod -a > >> > >> Then repeat the dracut command, i.e. > >> # dracut -f /boot/initramfs-$(uname -r).img $(uname -r) > >> > > By runing depmod -a I got the following: > > WARNING: Couldn't open directory /lib/modules/2.6.33.3-85.fc13.i686: no > > such file or directory. > > FATAL: could not > > open /lib/modules/2.6.33.3-85.fc13.i686/modules.dep.temp for writing: no > > such file or directory. > > I log in "modules" directory and found only > > "2.6.33.6-147.fc13.i686.PAE." Does this means that I need to do some > > kind of update? > > > > > > Just call dracut with the correct kernel version! $(uname -r) would take the > version of the current running kernel. It seems the rescue system is running a > different kernel, than your system will do. So you just have to run dracut: > > # export KVER=2.6.33.6-147.fc13.i686.PAE > # dracut -f /boot/initramfs-${KVER}.img $KVER > Here dracut did run for a few seconds don't know what it did, or what suppose to do in th end it didn't report any thing. The end results, no change. I didn't want to give up, I made another Download from www.fedoraproject.org/en/get-fedora-all i386 bitTorrent, same result, however, this time I found the 2.6.33.3-85.fc13.i686.PAE I ran dracut and gat same result. I thank you to stick with me this far, if you thank we reach the end of the try list I will go back to fc12

1 0

Who's moderating this forum?
by Marcel Rieux 19 Jul '10

19 Jul '10

Since I'm in rant mode, I might as well continue. There's a lot to be said about how Fedora doesn't work! On *Thu Jun 24 01:36:32 UTC 2010, **Joel Rees* wrote about there being no instructions to revert from Nvidia to Nouveau drivers: "No, re-installing to clear up a mess that may take more time to clear up by hand than simply backing up your data and re-installing. "Either way, it's an education, and you didn't come to Fedora expecting not to be educated, did you? ================ Since when is reinstalling "an education"? Is this how Alan Cox, who sometimes writes on this group, got educated? Of course, if you never installed Linux, you might learn a few things. What swap, / and home partitions are, for instance. But if you ever installed Linux, what does finding where are the data files for Firefox, Thunderbird, Evolution, etc, will learn you about Linux? Nobody ever learned Linux this way. I you want to learn Linux, you go linuxcommand.org and you learn bash. You learn awk, sed, python, perl, php, C, assembler, whatever. This will get you somewhere, not reinstalling. Of course, the guy was bash-ing :) a so-called troll who doesn't howl with the wolf pack. Is this the kind of attitude that will move Fedora and Red Hat forward? Is the "You pay for Fedora in part with your time, in part with some sacrifice, relative to things like drivers and such." the attitude that prevails at Ubuntu, even if Ubuntu users sometimes have to solve problems too? How come, when such comments occur, nobody says: "Sorry, this is full bullshit. There's a problem." How come there's never any problem when normal users say there is. Is the user always being wrong the right attitude that will move Fedora/Red Hat forward? I said it isn't Ubuntu's attitude, it's certainly even less at Google's Chrome OS. Is this how Apple got so popular with a *NIX system? The typical answer to this is "You don't like Fedora? Go away. Use Ubuntu, Chrome OS, whatever you like." Who's contributing this kind of nonsense that will eventually leave Red Hat in some kind of Sun bubble? I don't understand how come nobody responsible for this group tries to make discussions move forward to better results for Red Hat, whether it be about uninstalling Nvidia drivers or OOo not offering basic features that Red Hat should rely on to sell its support, etc. Who's teh Steve Jobs here who says "The user is right!" ? IMO, there is a flaw in this list's moderation. And that's my contribution.

22 69

Gotta love embedded developers...
by Tom Horsley 19 Jul '10

19 Jul '10

Out of curiosity I downloaded the GPLed source code for the firmware in my new Netgear WNR3500L router. The first thing I see is the build instructions which start with: 1. This package has been built successfully on Fedora Core 2. Compiling this package on platforms other than Fedora Core 2 may have unexpected results. Now there's someone who doesn't want their development platform changing on them :-). (This is the netgear firmware mind you, not dd-wrt, which is a different kettle of fish...).

7 10

← Newer
1
...
18
19
20
21
22
23
24
...
47
Older →

Jump to page: