conflict between initscripts and pppd
by Hans Christian Studt
I have this problem while trying to update both when i am on-line and when i am not on-line.
On-line
=======
yum -y update
Gathering header information file(s) from server(s)
Server: Fedora Core 2 - i386 - Base
Server: Fedora Core 2 - i386 - Released Updates
Finding updated packages
Downloading needed headers
Resolving dependencies
.conflict between initscripts and pppd
Off-line
========
yum -C -y update
Gathering header information file(s) from server(s)
Server: Fedora Core 2 - i386 - Base
Server: Fedora Core 2 - i386 - Released Updates
Finding updated packages
Downloading needed headers
Resolving dependencies
.conflict between initscripts and pppd
Mvh Hans Christian Studt
Private +45 48 79 79 89
Mobile +45 29 23 54 14
Business +45 36 14 54 14
mailto:hc@studt.dk http://hc.studt.dk
Powered by Linux 2.6.6-1.435.2.1
19 years, 8 months
Re: mozilla freezes FC2 machine
by Anne & Lynn Wheeler
sporadic machine freeze with mozilla 1.7, 1.7.1, 1.8, nightly builds,
etc. happens when loading new page either in displayed tab or background
tab. happens with kde and gnome, smp and non-smp kernels.
however it doesn't happen with mozilla 1.6 (shipped with fc2)
machine frozen ... doesn't respond to any keys or mouse. doesn't respond
to any network activity thru enet port. power (off) button doesn't
respond ... have to pull the plug, plug it back in and then hit the
power (on) button (power cycle)
nothing in any log file.
--
Anne & Lynn Wheeler | http://www.garlic.com/~lynn/
19 years, 8 months
in search of kuser
by Lars G
hi
anyone knows where kuser hides in kde 3.2.3 ?
i guess it should be in kdeadmin, but it's not there.
thanks
lars
19 years, 8 months
Current kernel giving an error
by Paul F. Johnson
Hi,
I seem to be getting an error with the latest kernel (2.6.7-1.476)
svc : bad direction 256, aborting request
No idea what it's trying to do, it doesn't seem to be holding up the
system, just is a tad annoying when I'm doing anything via the terminal.
TTFN
Paul
--
"If I face my God tomorrow, I can tell Him I am innocent.
I've never harmed anyone. I have cheated no one.
I have deceived no one. I have hurt no one.
Except myself. And that He will forgive me." - Hans Holzel
19 years, 8 months
smbmount and $homes with samba
by Mike old
For some reason smbmount refuses point-blank to mount samba home shares
useably
eg: this is on the same machine
mount -t smbfs -o
username=mike,password=******* //data_cc/datacc /home/mike/smbtest
opts: rw
opts: username=mike
opts: password=tuxopen
mount.smbfs started (version 3.0.3-5)
added interface ip=192.168.1.6 bcast=192.168.1.255 nmask=255.255.255.0
Connecting to 192.168.1.6 at port 445
5647: tree connect failed: Call returned zero bytes (EOF)
SMB connection failed
Other machine
mount -t smbfs -o
username=mike,password=********,ip=192.168.1.6 //data_cc/mike /mnt/test
[root@localhost root]# ls /mnt/test
ls: /mnt/test: No such file or directory
ls -l
drwxr-xr-x 1 root root 4096 Jul 9 10:36 data
drwxr-xr-x 2 root root 512 Jan 1 1970 floppy
drwxr-xr-x 2 root root 4096 May 25 18:22 src
?--------- ? ? ? ? ? test
Global shares mount fine - anyone any idea what is going on here.
19 years, 8 months
Re: mozilla freezes FC2 machine(?)
by Anne & Lynn Wheeler
for the past 3-4 weeks or so ... i've gotten very sporadic
machine freezes (nothing is running and have to power
cycle) when mozilla is loading some website.
Happens with mozilla 1.7 thru 1.8a thru current nightly
builds. happens whether new website is being loaded into
visable tab or background tab. mozilla's is running with
java, javascript, popups, etc all disabled.
happens up thru smp kernel 2.6.6-1.435.2.3
machine is new dell 8100 with threading enabled and a
SMP kernel.
did not happen with earlier fc2 (smp) kernels prior to 4
weeks or so ago. doesn't seem to be mozilla since was using
some of the same mozillas prior to the freezing appearing.
by the time I noticed it happening, I had deleted earlier
kernels where the freezes weren't happening.
the mozilla web page load issue is the only situation
that i've observed it happening.
19 years, 8 months
xmms segfaults on custom kernel based on kernel-sourcecode-2.6.7-1.476
by Lars G
hi
testing a kernel based on kernel-sourcecode-2.6.7-1.476
i get an segfault trying to run xmms-1.2.10-4
the kernel says:
Jul 8 18:00:49 bigbadmachine kernel: bad: xmms(4208) scheduling while
atomic (2)!
Jul 8 18:00:49 bigbadmachine kernel: [<c02f84a6>] schedule+0x76/0x45d
Jul 8 18:00:49 bigbadmachine kernel: [<c0113045>]
sys_sched_yield+0x3a/0x40
Jul 8 18:00:49 bigbadmachine kernel: [<c014c4a7>] coredump_wait+0x2b/0x82
Jul 8 18:00:49 bigbadmachine kernel: [<c014c5cd>] do_coredump+0xcf/0x1c3
Jul 8 18:00:49 bigbadmachine kernel: [<c011c517>]
__dequeue_signal+0x132/0x13b
Jul 8 18:00:49 bigbadmachine kernel: [<c011c535>] dequeue_signal+0x15/0x54
Jul 8 18:00:49 bigbadmachine kernel: [<c011daba>]
get_signal_to_deliver+0x2cd/0x32b
Jul 8 18:00:49 bigbadmachine kernel: [<c0104dd2>] do_signal+0x4e/0xc6
Jul 8 18:00:49 bigbadmachine kernel: [<c01384e3>] vma_link+0x45/0xd2
Jul 8 18:00:49 bigbadmachine kernel: [<c0139047>]
do_mmap_pgoff+0x4b0/0x5d6
Jul 8 18:00:49 bigbadmachine kernel: [<c0109c9a>] sys_mmap2+0x6e/0xa1
Jul 8 18:00:49 bigbadmachine kernel: [<c0110b0c>] do_page_fault+0x0/0x47f
Jul 8 18:00:49 bigbadmachine kernel: [<c0104e71>]
do_notify_resume+0x27/0x36
Jul 8 18:00:49 bigbadmachine kernel: [<c02fa482>] work_notifysig+0x13/0x15
Jul 8 18:00:49 bigbadmachine kernel: bad: xmms(4208) scheduling while
atomic (2)!
Jul 8 18:00:49 bigbadmachine kernel: [<c02f84a6>] schedule+0x76/0x45d
Jul 8 18:00:49 bigbadmachine kernel: [<c0111ff6>] activate_task+0x53/0x5e
Jul 8 18:00:49 bigbadmachine kernel: [<c02f88d9>]
wait_for_completion+0x10/0xca
Jul 8 18:00:49 bigbadmachine kernel: [<c011c58c>] signal_wake_up+0x18/0x19
Jul 8 18:00:49 bigbadmachine kernel: [<c011c953>]
specific_send_sig_info+0x86/0x8d
Jul 8 18:00:49 bigbadmachine kernel: [<c014c446>] zap_threads+0x68/0x9e
Jul 8 18:00:49 bigbadmachine kernel: [<c014c4d7>] coredump_wait+0x5b/0x82
Jul 8 18:00:49 bigbadmachine kernel: [<c014c5cd>] do_coredump+0xcf/0x1c3
Jul 8 18:00:49 bigbadmachine kernel: [<c011c517>]
__dequeue_signal+0x132/0x13b
Jul 8 18:00:49 bigbadmachine kernel: [<c011c535>] dequeue_signal+0x15/0x54
Jul 8 18:00:49 bigbadmachine kernel: [<c011daba>]
get_signal_to_deliver+0x2cd/0x32b
Jul 8 18:00:49 bigbadmachine kernel: [<c0104dd2>] do_signal+0x4e/0xc6
Jul 8 18:00:49 bigbadmachine kernel: [<c01384e3>] vma_link+0x45/0xd2
Jul 8 18:00:49 bigbadmachine kernel: [<c0139047>]
do_mmap_pgoff+0x4b0/0x5d6
Jul 8 18:00:49 bigbadmachine kernel: [<c0109c9a>] sys_mmap2+0x6e/0xa1
Jul 8 18:00:49 bigbadmachine kernel: [<c0110b0c>] do_page_fault+0x0/0x47f
Jul 8 18:00:49 bigbadmachine kernel: [<c0104e71>]
do_notify_resume+0x27/0x36
Jul 8 18:00:49 bigbadmachine kernel: [<c02fa482>] work_notifysig+0x13/0x15
Jul 8 18:00:49 bigbadmachine kernel: note: xmms[4208] exited with
preempt_count 1
Jul 8 18:00:49 bigbadmachine kernel: bad: xmms(4208) scheduling while
atomic (1)!
Jul 8 18:00:49 bigbadmachine kernel: [<c02f84a6>] schedule+0x76/0x45d
Jul 8 18:00:49 bigbadmachine kernel: [<c0115a91>]
release_console_sem+0x8b/0xc0
Jul 8 18:00:49 bigbadmachine kernel: [<c0113926>] mm_release+0x47/0x7c
Jul 8 18:00:49 bigbadmachine kernel: [<c0116f4e>] do_exit+0xcc/0x36d
Jul 8 18:00:49 bigbadmachine kernel: [<c01172b7>] sys_exit_group+0x0/0xd
Jul 8 18:00:49 bigbadmachine kernel: [<c011daf3>]
get_signal_to_deliver+0x306/0x32b
Jul 8 18:00:49 bigbadmachine kernel: [<c0104dd2>] do_signal+0x4e/0xc6
Jul 8 18:00:49 bigbadmachine kernel: [<c01384e3>] vma_link+0x45/0xd2
Jul 8 18:00:49 bigbadmachine kernel: [<c0139047>]
do_mmap_pgoff+0x4b0/0x5d6
Jul 8 18:00:49 bigbadmachine kernel: [<c0109c9a>] sys_mmap2+0x6e/0xa1
Jul 8 18:00:49 bigbadmachine kernel: [<c0110b0c>] do_page_fault+0x0/0x47f
Jul 8 18:00:49 bigbadmachine kernel: [<c0104e71>]
do_notify_resume+0x27/0x36
Jul 8 18:00:49 bigbadmachine kernel: [<c02fa482>] work_notifysig+0x13/0x15
Jul 8 18:00:49 bigbadmachine kernel: bad: xmms(4208) scheduling while
atomic (1)!
Jul 8 18:00:49 bigbadmachine kernel: [<c02f84a6>] schedule+0x76/0x45d
Jul 8 18:00:49 bigbadmachine kernel: [<c0143c3f>] __fput+0xd1/0xf1
Jul 8 18:00:49 bigbadmachine kernel: [<c011659c>]
put_files_struct+0x5b/0xae
Jul 8 18:00:49 bigbadmachine kernel: [<c011705b>] do_exit+0x1d9/0x36d
Jul 8 18:00:49 bigbadmachine kernel: [<c01172b7>] sys_exit_group+0x0/0xd
Jul 8 18:00:49 bigbadmachine kernel: [<c011daf3>]
get_signal_to_deliver+0x306/0x32b
Jul 8 18:00:49 bigbadmachine kernel: [<c0104dd2>] do_signal+0x4e/0xc6
Jul 8 18:00:49 bigbadmachine kernel: [<c01384e3>] vma_link+0x45/0xd2
Jul 8 18:00:49 bigbadmachine kernel: [<c0139047>]
do_mmap_pgoff+0x4b0/0x5d6
Jul 8 18:00:49 bigbadmachine kernel: [<c0109c9a>] sys_mmap2+0x6e/0xa1
Jul 8 18:00:49 bigbadmachine kernel: [<c0110b0c>] do_page_fault+0x0/0x47f
Jul 8 18:00:49 bigbadmachine kernel: [<c0104e71>]
do_notify_resume+0x27/0x36
Jul 8 18:00:49 bigbadmachine kernel: [<c02fa482>] work_notifysig+0x13/0x15
Jul 8 18:00:49 bigbadmachine kernel: bad: xmms(4208) scheduling while
atomic (1)!
Jul 8 18:00:49 bigbadmachine kernel: [<c02f84a6>] schedule+0x76/0x45d
Jul 8 18:00:49 bigbadmachine kernel: [<c0143c3f>] __fput+0xd1/0xf1
Jul 8 18:00:49 bigbadmachine kernel: [<c011659c>]
put_files_struct+0x5b/0xae
Jul 8 18:00:49 bigbadmachine kernel: [<c011705b>] do_exit+0x1d9/0x36d
Jul 8 18:00:49 bigbadmachine kernel: [<c01172b7>] sys_exit_group+0x0/0xd
Jul 8 18:00:49 bigbadmachine kernel: [<c011daf3>]
get_signal_to_deliver+0x306/0x32b
Jul 8 18:00:49 bigbadmachine kernel: [<c0104dd2>] do_signal+0x4e/0xc6
Jul 8 18:00:49 bigbadmachine kernel: [<c01384e3>] vma_link+0x45/0xd2
Jul 8 18:00:49 bigbadmachine kernel: [<c0139047>]
do_mmap_pgoff+0x4b0/0x5d6
Jul 8 18:00:49 bigbadmachine kernel: [<c0109c9a>] sys_mmap2+0x6e/0xa1
Jul 8 18:00:49 bigbadmachine kernel: [<c0110b0c>] do_page_fault+0x0/0x47f
Jul 8 18:00:49 bigbadmachine kernel: [<c0104e71>]
do_notify_resume+0x27/0x36
Jul 8 18:00:49 bigbadmachine kernel: [<c02fa482>] work_notifysig+0x13/0x15
guess it has something todo with the voluntary preemption patch?
the precompiled kernel works ok with xmms, and i have seen that
preempt is disabled and preemp_voluntary is enabled in this one.
i have both enabled in my custom config, and everything plays nice and
speedy so far, with the exception of xmms.
haven't found any info about preempt_voluntary on the web, so my question
is, can one use preempt and preempt_voluntary together, or
is it a silly idea?
best
lars
19 years, 8 months
Fedora Core 2 Test Update: texinfo-4.7-4
by Tim Waugh
Please test this out. I plan to make this a released update next
Thursday (July 15th).
---------------------------------------------------------------------
Fedora Test Update Notification
FEDORA-2004-213
2004-07-08
---------------------------------------------------------------------
Product : Fedora Core 2
Name : texinfo
Version : 4.7
Release : 4
Summary : Tools needed to create Texinfo format documentation files.
Description :
Texinfo is a documentation system that can produce both online
information and printed output from a single source file. The GNU
Project uses the Texinfo file format for most of its documentation.
Install texinfo if you want a documentation system for producing both
online and print documentation from the same source file and/or if you
are going to write documentation for the GNU Project.
---------------------------------------------------------------------
Update Information:
This updates the texinfo package to the latest version, 4.7.
---------------------------------------------------------------------
* Wed Jul 07 2004 Tim Waugh <twaugh(a)redhat.com> 4.7-4
- Build for FC2.
* Tue Jun 29 2004 Tim Waugh <twaugh(a)redhat.com> 4.7-3
- Fix grouping in user-defined macros.
* Mon Jun 28 2004 Tim Waugh <twaugh(a)redhat.com> 4.7-2
- Build requires ncurses-devel (bug #126600).
* Fri Jun 25 2004 Tim Waugh <twaugh(a)redhat.com> 4.7-1
- 4.7.
* Tue Jun 15 2004 Elliot Lee <sopwith(a)redhat.com>
- rebuilt
* Tue Mar 02 2004 Tim Waugh <twaugh(a)redhat.com>
- Fixed compiler warning (bug #117097).
---------------------------------------------------------------------
This update can be downloaded from:
http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/2/
043e0fc7f6c1fd512b11e32355e027ac SRPMS/texinfo-4.7-4.src.rpm
bcd37d072bbe11073426d3432cb306ae x86_64/texinfo-4.7-4.x86_64.rpm
b7b25558bb0962f315a54cd7f7852fba x86_64/info-4.7-4.x86_64.rpm
2e63c8393208223f49c2d3d9023be686 x86_64/debug/texinfo-debuginfo-4.7-4.x86_64.rpm
92af605dbc8bcd0f3bfaf5a98c6df54f i386/texinfo-4.7-4.i386.rpm
4590049dba9f668441250a05ab0374d9 i386/info-4.7-4.i386.rpm
1740904e2b5766882365d6f940a17b9d i386/debug/texinfo-debuginfo-4.7-4.i386.rpm
This update can also be installed with the Update Agent; you can
launch the Update Agent with the 'up2date' command. You may
need to edit your up2date channels configuration. Within
/etc/sysconfig/rhn/sources enable the following line:
yum updates-testing http://fedora.redhat.com/updates/testing/fedora-core-2
---------------------------------------------------------------------
19 years, 8 months
RE: Evo-1.5 latest build
by Ernest L. Williams Jr.
-----Original Message-----
From: fedora-test-list-bounces(a)redhat.com on behalf of Mike Chambers
Sent: Wed 7/7/2004 6:41 PM
To: Fedora Beta
Subject: Evo-1.5 latest build
I saw this was being built last night, but take it that it either takes
awhile to compile/build the packages, or ran into problems?
===================================
The version that I got from rawhide is unstable now. Causing me to have to use kmail for a mail client.
The application is crashing in relation to the address book.
Could you put the latest build as a RPM on rawhide?
--
Mike Chambers
Madisonville, KY
"It's always better to hurt a little now, than to hurt a lot later!"
--
fedora-test-list mailing list
fedora-test-list(a)redhat.com
To unsubscribe:
http://www.redhat.com/mailman/listinfo/fedora-test-list
19 years, 8 months