FC3rc1 - firefox problem
by Thomas Taylor
Hi all:
Spent two days getting FC3rc1 loaded and setup to my liking. Decided to do a
fresh install instead of an upgrade to avoid problems. Took lots of time to
get all the old info (saved in a separate partition) imported and working.
One thing isn't working though.
When I try to open Firefox, I get a "Choose User Profile" dialog box. The
only entry in the box is default. If I select default and click on "Start
Firefox", I get an error message saying "Profile in use, choose another
profile or create a new one".
I then create a new user profile (tom) and Firefox starts and appears to work
properly. When I exit Firefox and look in the ~/.mozilla/firefox which
contains a new profile dirtectory (z3w8dazx.tom) which appears to contain the
correct information. However, when I try to open Firefox again, the profile
manager again opens with only "default" user which still doesn't work.
Anyone else run into this problem yet? I've tried checking
permissions/ownership but they seem okay. Any suggestions?
Thanks, Tom
--
Tom Taylor
Registered linux user #263467
19 years, 7 months
Understanding volume manager
by AWC Maillists
Ok,
I am trying out FC3 RC2... installing on two identically configured
machines:
HP Proliant ml330 g3
768mb RAM
Adaptec Serial ATA RAID 2410SA Enclosure Kit
4 300GB SATA Maxtor drives configured as RAID5
I have not used the onboard IDE or the onboard IDE raid as they are evil
non-standard beasts - but with the above RAID I'm not too upset.
Now I have a question about the new (to me) Volume Manager options when
partitioning the drive. In the past I would partition the drive as follows:
100mb - /boot
15gb - /
152mb - swap partition
Remainder of drive - /home
With the above I can install a new OS easily by simply formatting the
first three partitions and leaving the /home parition alone so the data
is available with a fresh install. BUT, I would never be able to resize
the /home partition unless I wanted to delete the partition and lose the
data on the partition.
Now with the LVM option I am thinking of doing the following:
Create 100mb /boot parition (outside of the volume)
Creating one Volume Group for the remainder of the array called: RAID5Array
In that Group create three Logical Volume names:
LinuxDrive = / = 15gb
SwapFile = Swap partition = 1520mb
HomeDrive = /home = Remainder of array ~840gb
With this setup I should be able to the following:
- Resize any of the Logical Volume Names without destroying data
- Add a second RAID5 array - make it part of the RAID5Array and then add
the new capacity to either a new Logical Volume Name or to expand one
(or more) of the existing Logical Volumes to use the new storage
capacity. This can be done without destroying any data.
I just have some questions regarding this:
1) Soooo, is my understanding of LVM correct, or am I missing something
very important?
2) Is these any performance hit with using LVM versus the older method
of paritioning the hard drive?
If posting this query here is incorrect, I apologize, but Volumes are
being created when your use "autopartition" during the install process
in FC3. (And FC2 did not create volumes during the autopartition
stage... so I ignored it back then.) So I thought I would ask here -
but if I should ask this elsewhere I would appreciate being pointed in
the correct direction.
Thanks.
--- Charles
19 years, 7 months
Re: Averatec Laptop Useless Under FC3RC1
by D Canfield
Michal Jaegermann wrote:
>>- Try the install a third time using the text mode installer. Install
>>succeeds, but...
>>- Upon reboot, when the graphical grub should be displayed, the screen
>>goes blank,
>>
>>
>
>I have not a clue about your laptop but you mean here 'rhgb' or
>a grub menu? If it is rhgb which gives you troubles then you
>can hit 'a' on grub screen and replace 'rhgb' boot option with '3'.
>What then? What about '1' instead of '3' (and no 'rhgb' of course).
>Or maybe just dropping rhgb is enough (the same as replacing 'rhgb'
>with '5' for a default installation).
>
>Once you booted to a shell prompt it is always easier to try
>figure out what next and how to start X. If you can install in
>a text mode then you can surely boot to at least level 3.
>
>If it is really a grub menu then this is mighty weird as there is
>really nothing "graphical" at this moment yet. What if you will
>boot into a rescue and comment out "splash" from your grub.conf? It
>is there only to make things "pretty".
>
> Michal
>
>
I truly mean grub. As in, the machine says "loading grub stage2..." (if
I remember correctly) and then instantly black-screens. There is no
grub menu where I could change the runlevel or anything. I'm guessing
whatever issue this is, is a VESA-level issue of some kind.
FWIW, lspci under FC2 says this is a VIA VT8378 [S3 UnivChrome] video card.
19 years, 7 months
ntfs kernel module
by Folke Lemaitre
Why isn't the ntfs module built by default?
Not very handy, having to get src rpms, building them configuring
kernel sources and building ntfs module...
,Folke
19 years, 7 months
Re: Reiserfs question
by Borkowski Dariusz
>Wouldn't it be an anaconda bug not to do this, ie. not automatically
>disable SELinux (and warn about it) when reiserfs is used?
>BTW. What does Reiser provide that ext does'nt?
Reiser is better in recovering after sudden power off. I had problems
with ext3. After few power downs I lost some files. With reiserfs I have
never lost one file in similar situation. It seems (but here I may be
wrong) that reisers is faster when processing big amount of small files.
Darek Borkowski
>ons, 27.10.2004 kl. 13.58 skrev Timothy Sandel:
> On Wed, 2004-10-27 at 13:46 +0200, Borkowski Dariusz wrote:
> > Hi,
> >
> > how to install FC3 with ReiseFS? I tried it with FC3test2 (after
booting
> > ISO typed: linux reiserfs) but installer stops just before
formatting
> > partitions. I sent a bug to bugzilla.redhat.com and someone replied
that
> > it was because of SELinux.
> > I have question. It is possible to install (format) reiserfs
partition
> > with SELinux enabled? Or if not how to disable SELinux and enable
> > ReiserFS?
> >
> This has been answered numerous times on this list...
> You must disable selinux at boot.
>
> linux reiserfs selinux=0
>
>
> > thanks in advance
> >
> > Darek Borkowski
19 years, 7 months
RC1?
by Mark Haney
Okay where'd RC1 come from? I think I missed that memo. Is it just
another name for T3?
--------------------------------------
Mark Haney
Network Administrator
InterAct Public Safety Systems
mhaney(a)interactsys.com
Fedora Core release 2 (Tettnang) Kernel: 2.6.8-1.521 GNU/Linux
09:38:21 up 1:59, 1 user, load average: 3.85, 3.49, 3.13
19 years, 7 months
RE: FC3t3 -- udev and SCSI devices
by Bill Cronk
Harald wrote:
> what is printed in /var/log/messages for your second RAID box?
> In rc.sysinit:
/sbin/mdadm A s
> is run if /etc/mdadm.conf is present
First there is an error in the dmesg output that I find to be intense:
Program scsi_unique_id is using a deprecated scsi ioctl, please convert it to SG_IO
Many many lines of this message
As for my RAID boxes here is what I have found out so far:
If I run at the prompt /sbin/mdadm A s it exits with the following message:
mdadm: error opening /dev/md1: No such file or directoy
I decided to update the FC3t3 to FC3rc1 and discovered something interesting which sheds some light on the problem. When disk druid started up and I flagged the two partitions I needed to reformat and set the mount points, I noticed for the first time, since I currently had both RAID boxes connected yet, that the two RAID boxes showed up in the drive listing. Now I can see what part or possibly all of the problems I am seeing are caused by. Both RAID boxes are listed as /dev/md0
obviously they both can not operate as /dev/md0, but now it makes sense. I figure that when creating a RAID box part of the superblock structure carries the info regarding the drive configuration and /dev/md? tag.
A little history about the RAID boxes, both were created on separate servers as /dev/md0 connections.
I would assume that when the RAID box is auto detected that it reads in the md0 tag and passes it to udev which now can not setup a connection because the md0 tag is already accounted for with the first RAID box which also accounts for the lack of the /dev/md1 file being created.
This also means that if I move the other two RAID boxes over to the U160 SCSI ports that now the problem will be recreated again two more times since they are also setup as /dev/md0.
So now the question is how can the md0 tag be changed to an md1 tag without destroying the data on the RAID box and will it actually then fix the problem?
BTW, if you need them I can email the configuration files directly to you such as the /etc/mdadm.conf file.
Also, why does the system insist on automatically creating /media/scsidevice and /media/scsidevice1 mount points for the first SCSI drive from each RAID box?
Bill
19 years, 7 months
FC3 RC1 - Networked LPD server printing still not working.
by Gerry Tool
I have just done a fresh install of FC3, Release Candidate 1. Printing
to a networked LPD server still will not work. This is a bug (#133064)
that is assigned to the kernel.
It seems to be dormant without attention. It will prevent anyone using
a networked LPD print server from using FC3.
Gerry Tool
19 years, 7 months