Laptop Docked/Undocked Profile Manager
by Steve Fink
Hello Everyone,
I posted this question to Fedora User List so for those of you
subscribed to both, sorry.
Is it possible to build a profile manager for laptops?
For example:
I want to be able to create different hardware profiles for my laptop to
be undocked, docked into dock #1, and docked into dock #2.
Currently kudzu runs and either adds or removes hardware based on which
dock I'm in or undocked as the case may be.
I have to type in the new network info each time and it's time
consuming. If I undock and miss the kudzu screen my laptop locks up
because the SCSI interface is missing.
Is there a way to accomplish this with kudzu or possibly just have kudzu
pass some hardware info to a secondary app that stores the profiles and
compares them then drops in all of the configuration info from there?
Thanks in advance for your replies.
Best,
Steve
19 years, 8 months
Odd behavior in up2date xterm shells
by Harry Putnam
My setup:
*--
Software:
Linux kernel 2.6.7-1.494 Architecture i686
Fedora Core release 2.90 (FC3 Test 1)
Hardware:
model name : Intel(R) Pentium(R) 4 CPU 2.00GHz
cpu MHz : 1994.464
*--
I'm seeing something that just started happening afer my last round of
updates. yum list updates shows:
(all those that people are finding troublesome)
curl
curl-devel
gimp
grip
libcroco
libcroco-devel
librsvg2
librsvg2-devel
vorbis-tools
So I'm up to snuff on everthing else.
What I'm seeing takes place in xterm shells. I use real xterm for my
shells and have for a very long time. What I see is a linebreak being
inserted where it wouldn't used to have been.
Example:
[reader] $ somecmd "start typing like one might with a lis
t <= oops what happened
At character position 58 a line break happens... I've never seen this
before. The terminal --geometry is set to 80x25.
Is this ncurses maybe... or more likely something to do with the new
terminal settings?
19 years, 8 months
Seems to be quicker - GNOME
by Jim Cornette
Though I am tired and GNOME may just seem to be reacting quicker. GNOME
seems very quick with the latest updates applied to the system.
Thanks!
Jim
--
So live that you wouldn't be ashamed to sell the family parrot to the
town gossip.
19 years, 8 months
Error during yum update with latest rawhide for Aug 5, 2004
by Dwaine Garden
During the update from rawhide, I got this error message. I did check
bugzilla. Checking to see if anyone else experienced this...
Downloading Packages
Getting samba-common-3.0.5-2.FC2.1.i386.rpm
samba-common-3.0.5-2.FC2. 100% |=========================| 5.0 MB 00:48
Getting samba-client-3.0.5-2.FC2.1.i386.rpm
samba-client-3.0.5-2.FC2. 100% |=========================| 2.5 MB 00:20
Getting samba-3.0.5-2.FC2.1.i386.rpm
samba-3.0.5-2.FC2.1.i386. 100% |=========================| 14 MB 02:33
Running test transaction:
Test transaction complete, Success!
samba-common 100 % done 1/6
/sbin/ldconfig: File /usr/lib/libkdeinit_kdesktop.so.#prelink#.kWa0x4 is
too small, not checked.
samba 100 % done 2/6
samba-client 100 % done 3/6
Completing update for samba-common - 4/6
/sbin/ldconfig: File /usr/lib/libkdeinit_kdesktop.so.#prelink#.kWa0x4 is
too small, not checked.
Completing update for samba-client - 5/6
Completing update for samba - 6/6
Updated: samba-common 3.0.5-2.FC2.1.i386 samba-client
3.0.5-2.FC2.1.i386 samba 3.0.5-2.FC2.1.i386
Transaction(s) Complete
I have not had any problems with testing, just the error message.
Dwaine.
19 years, 8 months
unrecoverable disk errors
by Patrice Dumas
Hi,
In fedora core 3 test (upgraded with yum from fc2). The kernel is 2.6.7-499.
After a reboot the kernel couldn't launch init (seems that missing /initrd
was the issue).
I rebooted under repair environments and a fc 1, I ran e2fsck, and the root
filesystem had a lot of broken stuff within. When doing a chroot within the
fc3t system I could see that there were a lot of missing files (9308).
(There was nothing in the logs explaining the failure. I fixed my setup
since by reinstalling the rpm with missing files).
Now I thought that I could fix the filesystem errors with e2fsck. But each
time I run e2fsck (with -f the e2fsck provided with fc3t) the same errors pop
up:
==========================================================================
[root@localhost root]# ./e2fsck -c -f /dev/hda1
e2fsck 1.35 (28-Feb-2004)
Checking for bad blocks (read-only test): done
Pass 1: Checking inodes, blocks, and sizes
Error reading block 1278188 (Attempt to read block from filesystem resulted in
short read) while doing inode scan. Ignore error<y>? yes
Force rewrite<y>? yes
Error reading block 1278189 (Attempt to read block from filesystem resulted in
short read) while doing inode scan. Ignore error<y>? yes
Force rewrite<y>? yes
Error reading block 1278190 (Attempt to read block from filesystem resulted in
short read) while doing inode scan. Ignore error<y>? yes
Force rewrite<y>? yes
<skipped>
Error reading block 1572913 (Attempt to read block from filesystem resulted in
short read) while doing inode scan. Ignore error<y>? yes
Force rewrite<y>? yes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/hda1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/hda1: 247256/870912 files (2.9% non-contiguous), 1107924/1741036 blocks
[root@localhost root]#
===========================================================================
I also have had some new errors some times, thus it is possible that my disk is
dying (and more errors seem to show up when I run e2fsck...), but the errors
I report above appear all the time I run e2fsck -f -c.
Maybe it isn't a bug but if it is I can report further.
Pat
19 years, 8 months
mkinitrd-4.0.0-1 might be broken
by Steve G
Hello,
I built the latest from rawhide and installed the 503 kernel. I did a:
mkinitrd vmlinuz 2.6.7-1.503.build
And rebooted the system. On the way up, I got a message saying the "switchroot
mount failed" and it panic'ed. Removing the mkinitrd package and backtracking to
mkinitrd-3.5.24-1 fixed the problem.
Has anyone else noticed this problem? Is mkinitrd-4.0.0 supposed to work with
current rawhide or does it have (unstated) dependencies on packages yet to be
released?
Thanks,
-Steve Grubb
__________________________________
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!
http://promotions.yahoo.com/new_mail
19 years, 8 months
Fedora Core 1 Test Update: ghostscript-7.07-15.3
by Tim Waugh
Please put feedback (both positive and negative) here:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=129062
I will push this as a Fedora Update once I am satisfied that
a) ghostscript works normally
b) gsview also works [since this is the entire point]
Thanks,
Tim.
*/
---------------------------------------------------------------------
Fedora Test Update Notification
FEDORA-2004-252
2004-08-05
---------------------------------------------------------------------
Product : Fedora Core 1
Name : ghostscript
Version : 7.07
Release : 15.3
Summary : A PostScript(TM) interpreter and renderer.
Description :
Ghostscript is a set of software that provides a PostScript(TM)
interpreter, a set of C procedures (the Ghostscript library, which
implements the graphics capabilities in the PostScript language) and
an interpreter for Portable Document Format (PDF) files. Ghostscript
translates PostScript code into many common, bitmapped formats, like
those understood by your printer or screen. Ghostscript is normally
used to display PostScript files and to print PostScript files to
non-PostScript printers.
If you need to display PostScript files or print them to
non-PostScript printers, you should install ghostscript. If you
install ghostscript, you also need to install the ghostscript-fonts
package.
---------------------------------------------------------------------
Update Information:
This update provides shared libraries.
---------------------------------------------------------------------
* Wed Aug 04 2004 Tim Waugh <twaugh(a)redhat.com> 7.07-15.3
- Turn on libgs (bug #129062).
---------------------------------------------------------------------
This update can be downloaded from:
http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/1/
a4ef26ab4ca01df0649789227b7de5dd SRPMS/ghostscript-7.07-15.3.src.rpm
f9481aff9cef7518cefb76d667c25d1d x86_64/ghostscript-7.07-15.3.x86_64.rpm
5402d9610ac2fbbeaac52ef14e751b62 x86_64/ghostscript-devel-7.07-15.3.x86_64.rpm
54b693f11075dade1629df2488cc6384 x86_64/ghostscript-gtk-7.07-15.3.x86_64.rpm
1720a4f4bb4204a53445a5e06e4866a6 x86_64/hpijs-1.5-4.2.x86_64.rpm
efb93a5579b8522d5cc578902c544712 x86_64/debug/ghostscript-debuginfo-7.07-15.3.x86_64.rpm
b8c1390faf2fc64f509bddb373569f50 i386/ghostscript-7.07-15.3.i386.rpm
42592125d32158e5a6e2c83128d6aeff i386/ghostscript-devel-7.07-15.3.i386.rpm
c1d3bce62e464e10c1ae4b542412c593 i386/ghostscript-gtk-7.07-15.3.i386.rpm
1afd7f63a1024feea44ce680edc332b4 i386/hpijs-1.5-4.2.i386.rpm
fcc171ab3d3188f86e242a1ba166d448 i386/debug/ghostscript-debuginfo-7.07-15.3.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-1
---------------------------------------------------------------------
19 years, 8 months
SELinux
by Paul F. Johnson
Hi,
I'm currently running FC3t1 without selinux running (it's switched off
totally on boot up).
If I remove the selinux=0 part from the boot up, I get a pile of errors
saying the directories and other such things don't have the correct
permissions etc.
What do I need to do to set things working correctly so that selinux is
working properly?
TTFN
Paul
--
"Look. If you had one shot, one opportunity, to seize everything you
ever wanted. One moment to capture or would you just let it slip?" -
Marshall Mathers III (Lose Yourself)
19 years, 8 months
Something changed in cron upgrade.
by Harry Putnam
Anyone else noticing they can no longer edit there crontab with
crontab -e? Even as a fully logged in root user I get this message:
You (root) are not allowed to use this program (crontab)
See crontab(1) for more information
I don't see any cron.allow or deny type files. Creating
/etc/cron.allow and listing the needed user there fixes it but:
The man page says in the absence of them, only root user will be
allowed to use -e.
If the cron.allow file exists, then you must be listed therein in order
to be allowed to use this command. If the cron.allow file does not
exist but the cron.deny file does exist, then you must not be listed in
the cron.deny file in order to use this command. If neither of these
files exists, only the super user will be allowed to use this command.
Here, root was denied too. Until added to /etc/cron.allow
19 years, 8 months