Gnome-vfs2-obexftp and Nokia N72
by Rogue
Hi All
Has anyone been successful in using the obexftp package to work with
their Nokia N72 models? I can see the phone in the browser, connect to
the phone, but I can not get it to display any data!
Now I know that Nokia, pretty much like ATI, is a pain when it comes to
good integration with linux, but none the less, has anyone been able to
get this to work?
thanks,
Rogue
16 years, 9 months
F7 : vncserver and gnome fighting
by Skunk Worx
On FC6 I could startx and vncserver in pretty much any order and all was
well*
Under F7 I see an oddity in that some panels widgets only survive as
"first instance".
Let the system be setup with /etc/sysconfig/vncservers -> 1:user 2:user.
Case 1 : vncserver before startx : The vnc clients have all widgets
displayed as expected whether or not user starts X. If user logs in, and
starts X, two configured widgets do not appear that should be present.
Attempting to add the two missing widgets to the panel fail. "vncserver
wins".
Case 2 : startx first, then vncserver : The user desktop has all panels
and widgets displayed as configured. Now start vncserver. In this case,
the vnc connections show the same two widgets missing. "desktop wins".
So it looks like a "first instance wins" problem under F7. I tested this
against FC6 and all widgets are present in both scenarios.
The two widgets that appear in one place and not the other are Clock and
Window List.
Shall I bz this?
*an interesting case under FC6 and F7, if one starts a desktop, without
vncserver running, then opens an xterm, becomes root, and starts
vncserver, the servers take a long time to start and an error about a
timeout on /root/.xauthXXX error is displayed as each instance starts.
16 years, 9 months
F7 Mixer settings
by Antonio M
Whenever I changed settings in gnome-audio-manager at following
start-up, they were lost.
I inserted a line in etc/rc.d/rc.local :
alsactl restore
and now mixer settings are retained after I issued a alsactl store.
But it is a trial: is it correct???
--
Antonio Montagnani
Skype : antoniomontag
16 years, 9 months
FC7 Power Down/Power Button issue
by MLists
Have a new system, thought I'd use it to do some testing of FC7. did a
clean install, no additional packages other than the defaults.
Two problems.
- the system didn't start to shut down when I hit the power switch
- when I did a shutdown -h the system went through the shutdown process,
said "system halted" and waited for me to press the power switch
Thinking perhaps it was the motherboard, I wiped that install and did a
clean install of FC6. No problem, shutdown starts when I push the power
switch and the machine shuts off automatically.
Wiped the system yet again and did another clean install of FC7. this time
the system does actually shutdown automatically when I do a shutdown -h but
still no joy on having the shutdown start when I push the power button.
Anyone have any ideas/suggestions on what might be going on, and how I can
get the "proper" behaviors working.
Cheers,
>>>>> Mike <<<<<
16 years, 9 months
LDAP Howto
by Per Qvindesland
Hello List,
Does anyone know about a SIMPLE howto to configure ldap to share address
book for email clients? after having googled for hours I can find plenty
but their one of two 1. not simple or 2. just don't work so I am hoping
that someone here can point me in the right direction.
Kind regards
Per Qvindesland
16 years, 9 months
OT - Re: Microsoft closes another deal, is redhat next?
by Jacques B.
On 6/15/07, Antonio Olivares <olivares14031(a)yahoo.com> wrote:
> Dear all,
>
> In midst of the Microsoft Linux deals, Novell, Xandros, Linspire, ..., etc. The question arises will Red Hat fall into Microsoft's deals?
>
> http://biz.yahoo.com/seekingalpha/070614/38396_id.html?.v=1
>
> Inquiring minds want to know.
> I hope that it does not fall into these kinds of pacts.
>
> Regards,
>
> Antonio
Interesting. Maybe MS is looking to merge their platform into a Linux
platform following Mac OS X using BSD as their launching platform.
Will we eventually see MS Linux where it will be running Linux under
the hood, but with a MS look, feel, and compatibility? MS would be
able to step away from some of the underlining OS challenges leaving
that to the Linux community and concentrate on putting a MS face on
it. It was suggested at one point that Vista will be MS' last OS.
Don't know what was meant by that. Maybe this is what was being
suggested or foreseen...
Jacques
16 years, 9 months
F7 KDE USB Disk/Memory Stick Umounting
by Dr J Austin
Hi
I have an external USB disk and a USB stick
which behave differently under KDE when selecting
"Safely Remove"
They both have 3 partitions /boot, /, SWAP
(With Fedora installs on as it happens)
[root@naxos ~]# ls -l /dev/sdc*
brw-r----- 1 root disk 8, 32 2007-06-29 11:34 /dev/sdc
brw-r----- 1 root disk 8, 33 2007-06-29 11:34 /dev/sdc1
brw-r----- 1 root disk 8, 34 2007-06-29 11:34 /dev/sdc2
brw-r----- 1 root disk 8, 35 2007-06-29 11:34 /dev/sdc3
sdc1 and sdc2 are both mounted as per their "labels" (if inserted separately)
When Safely Remove is selected
1. The USB disk umount the 2 partitions
but leaves the icons on the dektop
and leaves /dev/sdc, /dev/sdc1 and /dev/sdc2
2. The USB memory stick umount the 2 partitions
removes the icons from the desktop
and only leaves /dev/sdc
naxos ~ 1005# ls -l /dev/sdc*
brw-r----- 1 root disk 8, 32 2007-06-29 10:42 /dev/sdc
Thus the USB memory stick has to be removed and re-inserted to regain access.
For the USB disk you can just click on the icon
1. Why are the two "identical" devices treated differently?
2. Is there an easy method of changing all USB sticks
to act the same as the USB Disk?
Its just annoying !
Surely you don't have to dig into hal/udev to fix this
Regards
john
16 years, 9 months
nVidia 7300 GT
by Michael McGillick
Hi:
I have a Mac Pro with Intel-Based processors. The graphics card included with the system was the nVidia 7300GT. Prior to installing Fedora, I bought an ATI X1900 XT graphics card and have successfully used this under both Mac OS X and Windows Vista (few minor issues under Vista, but acceptable). After installing Fedora 7, I've been unable to get my system to correctly use the card and resolution of my 2560x1600 monitor.
My question is in regards to the 7300GT. Is this card supported by Fedora 7, meaning will it properly detect and install the drivers during the install process, or does it require some hocus pocus on my part to get it to work properly? I've already gone through this with the ATI card, and have no desire to do so again. I'm not a gamer, so the it's not critical that I have the best card available. I simply want to be able to display my desktop in 2560x1600 and have a nice clean picture and fonts.
I'd appreciate hearing from anyone who has this card or has worked with it and how it's supported. Thanks.
- Michael
16 years, 9 months
Re: selinux eradicator?
by Tom Horsley
> The most actively updated selinux package is selinux-policy. So you
> should be able to remove this without too many dependencies.
>
> policycoreutils does have lots of packages that require it so getting
> rid of it will be a problem. libselinux is a core library which you
> can't remove. libsemanage and libsepol are required by policycoreutils.
>
> So I would just remove selinux-policy-* and you should see far less updates.
That seemed to work. I also found I could remove the setroubleshoot
stuff with no dependency issues. Any of the remaining packages seem
to transitively drag in every other rpm on the system :-).
Thanks.
16 years, 10 months
RAID gotchas!
by Jeffrey Ross
Well I converted my single disk system last night into a dual disk
RAID-1 setup and preserved all my data. I Thought I'd share an overview
of the process and what I had problems with, maybe somebody here can use
my experiences to help them.
First some background, I'm running Fedora 7 with all the current fedora
patches, I am not using any third part repositories (yet) like Livna or
Freshrpms.
The system is an Intel Pentium D processor with an Intel DG965RY
motherboard utilizing 2- 400GB Seagate ST3400620AS SATA drives. NOTE:
don't forget to remove the tiny jumper (and promptly loose it in carpet)
on the drive to allow it to run at 3.0GB/s if your system allows it, the
jumper comes installed by default limiting speed to 1.5Gb/s.
My system was running fine on /dev/sda, I added the new disk as /dev/sdb
and partitioned it as follows:
/dev/sdb1 1 32 257008+ fd Linux raid
autodetect
/dev/sdb2 33 1307 10241437+ fd Linux raid
autodetect
/dev/sdb3 1308 1829 4192965 fd Linux raid
autodetect
/dev/sdb4 1830 48641 376017390 5 Extended
/dev/sdb5 1830 2199 2971993+ fd Linux raid
autodetect
/dev/sdb6 2200 2568 2963961 fd Linux raid
autodetect
/dev/sdb7 2569 48641 370081341 fd Linux raid
autodetect
My partitions were laid out as follows:
/dev/sdb1 = /dev/md1 = /boot
/dev/sdb2 = /dev/md2 = /usr
/dev/sdb3 = /dev/md3 = swap
/dev/sdb4 = extended partition
/dev/sdb5 = /dev/md5 = /var
/dev/sdb6 = /dev/md6 = /
/dev/sdb7 = /dev/md7 = /home
I kept the partition number the same as the raid partition number just
because it made my life easier to keep track of everything but there is
no reason it needs to match.
next I needed to create the partitions, this was pretty simple, I used
the following command:
mdadm --create /dev/md1 --level=1 --raid-devices=2 /dev/sdb1 missing
mdadm --create /dev/md2 --level=1 --raid-devices=2 /dev/sdb2 missing
mdadm --create /dev/md3 --level=1 --raid-devices=2 /dev/sdb3 missing
mdadm --create /dev/md5 --level=1 --raid-devices=2 /dev/sdb5 missing
mdadm --create /dev/md6 --level=1 --raid-devices=2 /dev/sdb6 missing
mdadm --create /dev/md7 --level=1 --raid-devices=2 /dev/sdb7 missing
Note the "missing" at the end of the command, this will allow the system
to create the raid volumes since the other disk isn't available yet.
I created the file /etc/mdadm.conf and put the following in it. NOTE:
if boot off a raid drive or load the raid module before mounting the
partitions I don't think you need the "ARRAY" entries, but I used them
anyway.
/etc/mdadm.conf:
# Who should get alerts?
MAILADDR root
ARRAY /dev/md1 devices=/dev/sda1,/dev/sdb1
ARRAY /dev/md2 devices=/dev/sda2,/dev/sdb2
ARRAY /dev/md3 devices=/dev/sda3,/dev/sdb3
ARRAY /dev/md5 devices=/dev/sda5,/dev/sdb5
ARRAY /dev/md6 devices=/dev/sda6,/dev/sdb6
ARRAY /dev/md7 devices=/dev/sda7,/dev/sdb7
NOTE: until the second disk was added to the array I only had one entry
following the devices entry (eg devices=/dev/sdb1)
now you need to create the file systems, I kept everything as ext3
mkfs -V -t ext3 /dev/mdX
where X was 1, 2, 5, 6, & 7
Don't forget swap!
mkswap /dev/md3
Now mount your new partitions, I mounted them under "/mnt"
mkdir /mnt/new-root
mount /dev/md6 /mnt/new-root
create the new mount points (you could restore root first then just
mount them)
mkdir /mnt/new-root/var
mkdir /mnt/new-root/usr
mkdir /mnt/new-root/home
mkdir /mnt/new-root/boot
mount /dev/md1 /mnt/new-root/boot
mount /dev/md2 /mnt/new-root/usr
etc
Now comes the fun part, you need to move your data to the new
partition. Although I've read where you can shrink the partition and
convert to a raid volume, I decided against that.
I used dump/restore using the command:
dump -0 -b 1024 -f - /dev/sdaX | restore -rf -
NOTE: I'd recommend single user mode for the copy, better yet unmount
the source volume if possible, secondly run this command in the
destination directory!
Second NOTE: by using the option -b 1024 the performance of dump was
increased about 10 fold however upon completion you will get "broken
pipe" error, I found everything was copied properly and didn't worry
about it.
All your data is copied to the RAID volume but a reboot will only load
from the old disk. I did the following:
modified /etc/fstab to read:
/dev/md6 / ext3 defaults 1 1
/dev/md7 /home ext3 defaults 1 2
/dev/md5 /var ext3 defaults 1 2
/dev/md2 /usr ext3 defaults 1 2
/dev/md1 /boot ext3 defaults 1 2
/dev/md3 swap swap
defaults 0 0
Note for clarity I removed tmpfs, devpts etc. Also in hindsight I
probably could just use the label command "e2labe /dev/md1 /boot" etc
but I wanted to be positive what would be mounted.
I modified grub.conf on *both* the new partition and the old partition
to read:
kernel /vmlinuz-2.6.21-1.3228.fc7 ro root=/dev/md6
and then ran grub to install the boot loaded on the disks.
grub-install /dev/sda
grub-install /dev/sdb
At this point I rebooted.... and if your familiar with how raid works
you'll know the system wouldn't boot. At this point I booted off the
rescue disk and was able to mount all my raid partitions. Of course
that didn't help me get the system reloaded so I started searching the
internet for clues.
The answer came in mkinitrd mounted my partitions in the recovery mode,
now knowing what I know now should have been prior to the first reboot.
rename the existing initrd file to something else ( eg .old ?) then from
the new /boot directory run the following, and copy it to the old boot
directory as well (unless you can boot from /dev/sdb in your bios)
mkinitrd --preload=raid1 initrd-2.6.21.1.3228.fc7.img 2.6.21.1.3228.fc7
At this point you should be able to reboot and the system will be
running on the (degraded) RAID disks.
If your happy with everything then you can repartition your original
drive (fdisk) to match /dev/sdb once that is done you need to add the
new partitions to the raid volume. To do this enter the command:
mdadm --add /dev/mdX /dev/sdaX (where X is the partition number of the
volume)
Do this for all your remaining partitions, and then you can cat
/proc/mdstat and see the volumes being rebuilt ( hint: "watch cat
/proc/mdstat")
Your done!
Hope this was helpful to somebody.
Jeff
16 years, 10 months
