OT: a problem about text manipulation
by Paul Smith
Dear All
I have a text file with more than 300000 of lines like the following:
1 E E E
2 C D
3 B E D
4 C E D
5 D E
I am looking for an automatic way of transforming my text file into
another one with the format
1 E
1 E
1 E
2 C
2 C
3 B
3 B
3 D
4 C
4 C
4 D
5 E
Any ideas?
Thanks in advance,
Paul
17 years, 7 months
evolution + maildir
by Michal Janda
Hi,
is there any chance how to use evolution and store mail at maildir, not
mbox? I am downloading several mail list via pop3 and the mbox file is
getting too big.
Michal
--
ICQ - 132536462
www.mountainbike.cz
17 years, 7 months
Issues w/ Xorg 7.0, Dell L610, and i810 drivers
by Philip Prindeville
I'm using a Dell L610 to run FC5 (updated), and it has an i915GM controller,
which uses the i810 drivers...
I can't seem to configure it correctly (I've attached the config I'm
using). It
seems to have two issues.
(1) it probes for the monitor DDC sync values, which disagree with what I've
explicitly configured, but looking at the Xorg.0.log file, it gives
no indication
of what the EDID actually said the values were (grrr... you can never
have too
much logging).
(2) it then complains that "1400x1050" isn't a known modeline (no mode of
this name), even though I've explicitly configured a modeline with that
exact setting.
and the second head (in this case, connected to a Dell 1704FPV via DVI
hanging off a port-replicator) never seems to light up.
I've attached both the config and the log file. If anyone has had luck with
this, please let me know.
Thanks,
-Philip
# Xorg configuration created by system-config-display
Section "ServerLayout"
Identifier "Multihead layout"
Screen 0 "Screen0" LeftOf "Screen1"
Screen 1 "Screen1" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Synaptics" "CorePointer"
InputDevice "Mouse0" "AlwaysCore"
Option "Xinerama" "off"
Option "Clone" "on"
EndSection
Section "Files"
# Multiple FontPath entries are allowed (they are concatenated together)
# By default, a font server independent of the X server is
# used to render fonts.
FontPath "unix/:7100"
EndSection
Section "Module"
Load "dbe"
Load "extmod"
Load "fbdevhw"
Load "glx"
Load "record"
Load "freetype"
Load "type1"
Load "dri"
Load "synaptics"
EndSection
Section "InputDevice"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"
# To disable the XKEYBOARD extension, uncomment XkbDisable.
# Option "XkbDisable"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# Or if you just want both to be control, use:
# Option "XkbOptions" "ctrl:nocaps"
#
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "no"
EndSection
Section "InputDevice"
Identifier "Synaptics"
Driver "synaptics"
Option "Device" "/dev/input/mice"
Option "Protocol" "auto-dev"
Option "Emulate3Buttons" "yes"
Option "LeftEdge" "120"
Option "RightEdge" "830"
Option "TopEdge" "120"
Option "BottomEdge" "650"
Option "FingerLow" "14"
Option "FingerHigh" "15"
Option "MaxTapMove" "110"
Option "VertScrollDelta" "20"
Option "HorizScrollDelta" "20"
Option "MinSpeed" "0.3"
Option "MaxSpeed" "0.75"
EndSection
Section "Monitor"
### Comment all HorizSync and VertSync values to use DDC:
Identifier "Monitor0"
VendorName "Dell"
ModelName "Dell 1400x1050 Laptop Display Panel"
### Comment all HorizSync and VertSync values to use DDC:
HorizSync 31.5 - 90.0
VertRefresh 59.0 - 75.0
ModeLine "1400x1050" 108.0 1400 1444 1556 1688 1050 1050 1053 1066
Option "noDDC" "true"
Option "dpms"
EndSection
Section "Monitor"
Identifier "Monitor1"
VendorName "Dell"
ModelName "Dell 1704FPV (Digital)"
### Comment all HorizSync and VertSync values to use DDC:
HorizSync 30.0 - 81.0
VertRefresh 56.0 - 76.0
Option "dpms"
EndSection
Section "Device"
Identifier "Videocard0"
Driver "i810"
VendorName "Intel Corporation"
BoardName "Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller"
BusID "PCI:0:2:0"
Screen 0
EndSection
Section "Device"
Identifier "Videocard1"
Driver "i810"
VendorName "Intel Corporation"
BoardName "Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller"
BusID "PCI:0:2:1"
Screen 1
EndSection
Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1400x1050" "1280x960" "1152x864" "1024x768" "800x600" "640x480"
EndSubSection
EndSection
Section "Screen"
Identifier "Screen1"
Device "Videocard1"
Monitor "Monitor1"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1280x1024"
EndSubSection
EndSection
Section "DRI"
Group 0
Mode 0666
EndSection
17 years, 7 months
firewire problems galore
by Gene Heskett
Greetings all;
I'm trying to make my sony trc460 work with kino, but while I can get
video from it, I can't control it from kino-8.0.
I just unloaded all the 1394 related stuffs, ran the /usr/bin/mkrfc2734
from the libavc1394 package to see if that might help, but apparently not.
According to the logs, SELinux is possibly getting in the way from
stanza's like this:
Oct 14 20:44:53 diablo kernel: ieee1394: hpsb_update_config_rom() is
deprecated
Oct 14 20:44:53 diablo kernel: ieee1394: Failed to generate
Configuration ROM image for host 0
Oct 14 20:46:19 diablo kernel: video1394: Removed video1394 module
Oct 14 20:49:09 diablo kernel: ieee1394: raw1394: /dev/raw1394 device
initialized
Oct 14 20:49:09 diablo kernel: audit(1160873349.191:20): avc: denied {
getattr } for pid=23297 comm="pam_console_app" name="raw1394" dev=tmpfs
ino=80146 scontext=system_u:system_r:pam_console_t:s0-s0:c0.c255
tcontext=system_u:object_r:device_t:s0 tclass=chr_file
Oct 14 20:49:09 diablo kernel: audit(1160873349.191:21): avc: denied {
setattr } for pid=23297 comm="pam_console_app" name="raw1394" dev=tmpfs
ino=80146 scontext=system_u:system_r:pam_console_t:s0-s0:c0.c255
tcontext=system_u:object_r:device_t:s0 tclass=chr_file
Running 'dvcont play':
root@diablo ~]# dvcont play
couldn't set port: Invalid argument
Then repeating:
[root@diablo ~]# /usr/bin/mkrfc2734
couldn't set port: Invalid argument
an ls of /dev:
[root@diablo ~]# ls /dev
audio dri hda log mem ppp ram2
rtc tty1 tty20 tty31 tty42 tty53 tty7 vcs3 vcsa7
audio1 dsp hda1 loop0 mixer ptmx ram3
sequencer tty10 tty21 tty32 tty43 tty54 tty8 vcs4 X0R
bus dsp1 hda2 loop1 mixer1 pts ram4
sequencer2 tty11 tty22 tty33 tty44 tty55 tty9 vcs5 zero
cdrom dvd hda3 loop2 net ram ram5
shm tty12 tty23 tty34 tty45 tty56 ttyS0 vcs6
cdrom-hdc dvd-hdc hda5 loop3 null ram0 ram6
snapshot tty13 tty24 tty35 tty46 tty57 ttyS1 vcs7
cdrw dvdrw hda6 loop4 nvram ram1 ram7
snd tty14 tty25 tty36 tty47 tty58 ttyS2 vcsa
cdrw-hdc dvdrw-hdc hda7 loop5 par0 ram10 ram8
stderr tty15 tty26 tty37 tty48 tty59 ttyS3 vcsa1
cdwriter dvdwriter hdc loop6 parport0 ram11 ram9
stdin tty16 tty27 tty38 tty49 tty6 urandom vcsa2
cdwriter-hdc dvdwriter-hdc hpet loop7 parport1 ram12 ramdisk
stdout tty17 tty28 tty39 tty5 tty60 usb vcsa3
console fd initctl MAKEDEV parport2 ram13 random
systty tty18 tty29 tty4 tty50 tty61 vcs vcsa4
core full input mapper parport3 ram14 raw1394
tty tty19 tty3 tty40 tty51 tty62 vcs1 vcsa5
disk gpmctl kmsg md0 port ram15 root
tty0 tty2 tty30 tty41 tty52 tty63 vcs2 vcsa6
so it appears that a control devicename is not being created, and the
control device section of the kino prefs is blank:, as shown by the
attached screen snapshot.
Does anyone have a clue? This, FWIW, worked fairly well for kino-7.5
running on an FC2 system with the old kernels. This was before the
major rewrite of the ieee1394 drivers in the kernel that broke ALL
ieee1394 applications at the time. I've bitched about this before for
those with good memories.
Anyway, is there now anything that can be done for this, or are we
forever stuck with a broken ieee1394 interface in linux?
The following is what is logged after a fresh reboot, which I had a hell
of a time with, having to disable wlan0 before I could stop the kernel
panics and complete the boot process.
Anyway, this is whats logged when the camera, already powered up, is
plugged into the 4 pin FW port on this lappy, an HP dv5120us, running
uptodate FC5.
Oct 14 21:18:56 diablo udevd-event[2580]: pass_env_to_socket: passed 422
bytes to socket '/org/freedesktop/hal/udev_event',
Oct 14 21:18:56 diablo udevd[417]: udev_event_run: seq 773 forked, pid
[2589], 'add' 'drivers', 0 seconds old
Oct 14 21:18:56 diablo udevd-event[2589]: udev_rules_get_run: rule
applied, 'dv1394' is ignored
Oct 14 21:18:56 diablo udevd-event[2588]: run_program: '/sbin/modprobe'
returned with status 0
Oct 14 21:18:56 diablo udevd-event[2584]: run_program:
'/lib/udev/udev_run_devd' returned with status 0
Oct 14 21:18:56 diablo udevd-event[2580]: udev_event_run: seq 768 finished
Oct 14 21:18:56 diablo udevd-event[2593]: udev_rules_get_run: rule
applied, 'raw1394' is ignored
Oct 14 21:18:56 diablo udevd-event[2589]: udev_device_event: device
event will be ignored
Oct 14 21:18:56 diablo udevd-event[2588]: pass_env_to_socket: passed -1
bytes to socket '/org/kernel/udev/monitor',
Oct 14 21:18:56 diablo udevd-event[2584]: pass_env_to_socket: passed 196
bytes to socket '/org/freedesktop/hal/udev_event',
Oct 14 21:18:56 diablo udevd[417]: udev_event_run: seq 774 forked, pid
[2593], 'add' 'module', 0 seconds old
Oct 14 21:18:56 diablo udevd-event[2593]: udev_device_event: device
event will be ignored
Oct 14 21:18:56 diablo udevd-event[2589]: udev_event_run: seq 773 finished
Oct 14 21:18:56 diablo udevd-event[2588]: run_program:
'/lib/udev/udev_run_hotplugd'
Oct 14 21:18:56 diablo udevd-event[2584]: run_program:
'/sbin/pam_console_apply /dev/dv1394-0 '
Oct 14 21:18:56 diablo udevd-event[2593]: udev_event_run: seq 774 finished
Oct 14 21:18:56 diablo udevd-event[2588]: run_program:
'/lib/udev/udev_run_hotplugd' returned with status 0
Oct 14 21:18:56 diablo udevd-event[2584]: run_program:
'/sbin/pam_console_apply' returned with status 0
Oct 14 21:18:56 diablo udevd[417]: udev_done: seq 768, pid [2580] exit
with 0, 1 seconds old
Oct 14 21:18:56 diablo udevd-event[2588]: run_program:
'/lib/udev/udev_run_devd'
Oct 14 21:18:56 diablo udevd-event[2584]: udev_event_run: seq 772 finished
Oct 14 21:18:56 diablo udevd-event[2588]: run_program:
'/lib/udev/udev_run_devd' returned with status 0
Oct 14 21:18:56 diablo udevd[417]: udev_done: seq 773, pid [2589] exit
with 0, 0 seconds old
Oct 14 21:18:56 diablo udevd-event[2588]: pass_env_to_socket: passed 422
bytes to socket '/org/freedesktop/hal/udev_event',
Oct 14 21:18:56 diablo udevd[417]: udev_done: seq 772, pid [2584] exit
with 0, 1 seconds old
Oct 14 21:18:56 diablo udevd-event[2588]: udev_event_run: seq 770 finished
Oct 14 21:18:56 diablo udevd[417]: udev_done: seq 774, pid [2593] exit
with 0, 0 seconds old
Oct 14 21:18:56 diablo udevd[417]: udev_done: seq 770, pid [2588] exit
with 0, 1 seconds old
Oct 14 21:18:56 diablo udevd[417]: udev_event_run: seq 775 forked, pid
[2597], 'add' 'ieee1394_protocol', 0 seconds old
Oct 14 21:18:56 diablo udevd-event[2597]: udev_rules_get_name: rule
applied, 'raw1394' becomes 'raw1394'
Oct 14 21:18:56 diablo udevd[417]: udev_event_run: seq 776 forked, pid
[2598], 'add' 'drivers', 0 seconds old
Oct 14 21:18:56 diablo udevd-event[2598]: udev_rules_get_run: rule
applied, 'raw1394' is ignored
Oct 14 21:18:56 diablo udevd-event[2597]: create_node: creating device
node '/dev/raw1394', major = '171', minor = '0', mode = '0600', uid =
'0', gid = '0'
Oct 14 21:18:56 diablo udevd-event[2598]: udev_device_event: device
event will be ignored
Oct 14 21:18:56 diablo udevd-event[2597]: pass_env_to_socket: passed -1
bytes to socket '/org/kernel/udev/monitor',
Oct 14 21:18:56 diablo udevd-event[2598]: udev_event_run: seq 776 finished
Oct 14 21:18:56 diablo udevd-event[2597]: run_program:
'/lib/udev/udev_run_hotplugd'
Oct 14 21:18:56 diablo udevd[417]: udev_done: seq 776, pid [2598] exit
with 0, 0 seconds old
Oct 14 21:18:56 diablo udevd-event[2597]: run_program:
'/lib/udev/udev_run_hotplugd' returned with status 0
Oct 14 21:18:56 diablo udevd-event[2597]: run_program:
'/lib/udev/udev_run_devd'
Oct 14 21:18:56 diablo udevd-event[2597]: run_program:
'/lib/udev/udev_run_devd' returned with status 0
Oct 14 21:18:56 diablo udevd-event[2597]: pass_env_to_socket: passed 192
bytes to socket '/org/freedesktop/hal/udev_event',
Oct 14 21:18:56 diablo udevd-event[2597]: run_program:
'/sbin/pam_console_apply /dev/raw1394 '
Oct 14 21:18:56 diablo udevd-event[2597]: run_program:
'/sbin/pam_console_apply' returned with status 0
Oct 14 21:18:56 diablo kernel: audit(1160875136.916:6): avc: denied {
getattr } for pid=2601 comm="pam_console_app" name="raw1394" dev=tmpfs
ino=14070 scontext=system_u:system_r:pam_console_t:s0-s0:c0.c255
tcontext=system_u:object_r:device_t:s0 tclass=chr_file
Oct 14 21:18:56 diablo udevd-event[2597]: udev_event_run: seq 775 finished
Oct 14 21:18:56 diablo kernel: audit(1160875136.916:7): avc: denied {
setattr } for pid=2601 comm="pam_console_app" name="raw1394" dev=tmpfs
ino=14070 scontext=system_u:system_r:pam_console_t:s0-s0:c0.c255
tcontext=system_u:object_r:device_t:s0 tclass=chr_file
What clues can be extracted from all this?, I feel like I'm drowning in
useless data here.
--
Cheers, Gene
17 years, 7 months
SDRAM or DDRAM in linux
by Niklaus
Hi,
I have access to a remote linux machine. I have a root account on it.
I need to know whether the installed RAM is SDRAM or DDRAM.
Unfortunately i will be going to the site next month when i have to
upgrade the machine with more capacity. Few of them are hardware
related but if you know the answer please help me.
1) How do i find out when the machine is online , if it is SDRAM or
DDRAM. I tried dmidecode utility but i was not sure about the type.
Can someone help me out by pasting the output for both DDR and SDRAM
in dmidecode or similar.
2) Can both SDRAM and DDRAM be present at a time in the same
motherboard. I mean can i have 256MB of SDRAM chip and a 256 MB of
DDRAM on the same motherboard.
If yes what are the conditions.
3) Is a motherboard designed for only one type of RAM , like if we
remove all the SDRAMs can we put DDR in it or it is either designed
for DDR or SDRAM.
Regards
Nik
17 years, 7 months
Gutenprint for FC5
by Kanwar Ranbir Sandhu
Hello All,
Has anyone installed gutenprint on a FC5 box? Does it work well?
Should it be avoided? I'm about to give it a shot in order to use a
printer that is supported in gutenprint, but not in the gimp-print
package in FC5.
Also, are there any rpms out there? I haven't been able to find any so
far.
Thanks,
Ranbir
--
Kanwar Ranbir Sandhu
Linux 2.6.17-1.2187_FC5 i686 GNU/Linux
18:06:23 up 2 days, 12:35, 2 users, load average: 0.19, 0.42, 0.50
17 years, 7 months
NFS, SELinux and firewalls
by Tom Weniger
Greetings All,
I have installed FC6 on my home network and am enjoying the new
release. Tip of my fedora to the developers.. Job well done!
What is the status of using NFSv4 with SELinux and firewall enabled? I
have tried to get it going over my home network but to no avail
without disabling SELinux and the firewall. Is this problem strictly a
NFS issue? Has anyone been able to use NFS with SELinux and firewall
enabled?
--
Virtually,
Tom W
17 years, 7 months
pc hanging frequently
by Stephen Liu
Hi folks,
FC5_32bit
gnome desktop
Athlon 1.4G
2thMax mobo 8KHA
PC hung frequently while running Firefox and "yum update" on console.
Therefore I started runlevel 3 (init3, textmode) discovering the cause
as follow;
# yum update
.....
download 1/32 openoffice.org-co ================
Soft lockup detected on CPU#0
<c643dacd> Soft lockup_tick+0x90/0xal
<c0423ds0> update_process_times+0x35/0x5
<c0406134> time interruppt+0x60/0x98
<c643db6a> handle_IRQ_events+0x23/0x4c
<c043dc0f>__do_IRQ+0x7c/0xd1
<c6405042> do_IRQ+0x70/0x80
......
PC hung here.
I tried several times encountering the same problem. Having checked
BIOS pages and can't find any change there.
Please help. TIA
B.R.
SL
17 years, 7 months
