Question on shredding a terebyte drive
by Dean S. Messing
I have a terebyte sata drive that I need to securely wipe clean. It
originally had 2 partitions. I deleted them using `fdisk', rebooted,
and then as root ran
shred -vz /dev/sdd
The drive is capable of about 60MB/sec, but shred is only "shredding"
about 25MB every 5 seconds according to its output. Since the default
number of passes is 25, this works out to about 5 days.
The `shred' process is running at 100% CPU, presumably computing
the special random patterns for erasure. Since I have 4 CPUs
would creating 4 unformatted partions on the drive and then running
something like:
shred -vz /dev/sdd1
shred -vz /dev/sdd2
shred -vz /dev/sdd3
shred -vz /dev/sdd4
in parallel cut my time? Would be just as secure?
Thanks
Dean
11 years, 11 months
Alpine will not show attachments
by Tom Diehl
Hi,
I am running alpine-2.00-1.fc10.x86_64 on an F10 box. If I get a message with
an html or file attachment and I try to open it, I get an error that
"Firefox can't find the file at /tmp/img--46112.htm" The correct program opens
up but I always get the can't find file errors. If the message contains a URL
then it comes up and displays properly.
Does anyone know how to troubleshoot this problem?
Regards,
--
Tom Diehl tdiehl(a)rogueind.com Spamtrap address mtd123(a)rogueind.com
12 years, 7 months
dell e6500 lost fn-f8 key with 2.6.32 kernels
by Brian Millett
In the 2.6.32 kernels, I've seemed to have lost the ability to use the
fn-f8 key to togle external displays. Using xev I see that
KeyPress event, serial 35, synthetic NO, window 0x5800001,
root 0x15a, subw 0x5800002, time 869383, (55,45), root:(93,132),
state 0x50, keycode 33 (keysym 0x70, p), same_screen YES,
XLookupString gives 1 bytes: (70) "p"
XmbLookupString gives 1 bytes: (70) "p"
XFilterEvent returns: False
KeyRelease event, serial 35, synthetic NO, window 0x5800001,
root 0x15a, subw 0x5800002, time 869531, (55,45), root:(93,132),
state 0x50, keycode 33 (keysym 0x70, p), same_screen YES,
XLookupString gives 1 bytes: (70) "p"
XFilterEvent returns: False
This works just fine with the 2.6.31.12-174.2.22.fc12.x86_64, but not
with any of the 2.6.32 kernels.
Any hints?
Thanks.
--
Brian Millett - [ Delenn (re: Japanese stone garden), "The Gathering"]
"On my world, there are books, thousands of pages, about the power of one
mind to change the Universe. But none say it as clearly as this."
12 years, 9 months
Upgrading : give me strength ...
by Beartooth
I've tried all the tricks on this list a/o the troubleshooting
site, over and over. I finally gave up : downloaded and burned a DVD --
and *still* hit the catch-22 error, with too little space in mnt/sysimage/
boot.
Now what?
Can I simply delete all of /boot, or everything in it? All of
grub.conf? Or what? It's going to be a royal pain if I have to burn all
my data to media, and then sneakermail that back onto each machine,
instead of just upgrading f11 ....
--
Beartooth Staffwright, Neo-Redneck Not Quite Clueless Power User
I have precious (very precious!) little idea where up is.
12 years, 11 months
gpk-update-viewer vs. yum
by Beartooth
Is it just me??
I've noticed, on several machines (PC, laptop, netbook) that if
the machine has no connection, or thinks it has none, the gpk function
claims there are no updates; but if I doubt that and run yum update, it
may immediately get over a hundred -- or at least report a failure to
connect.
Couldn't gpk do the same??
--
Beartooth Staffwright, Neo-Redneck Not Quite Clueless Power User
I have precious (very precious!) little idea where up is.
12 years, 11 months
Sound doesn't work after upgrade from F13 to F14.
by Terry Letsche
Hi.
I had a working F13 system on my Aspire Laptop. I upgraded to F14 off
the DVD.
If I boot up and use a F13 kernel, everything is fine. If I boot with
the F14 kernel, no sound.
Running the alsamixer shows as if sound is there (the levels jump
around), but no sound comes out the speakers. I have checked the alsa
mixer to make sure everything is turned up, and stored the settings
(alsoctl store 0).
My alsa setup is at
http://www.alsa-project.org/db/?f=80...1fd871a78cefd9
This is on an Aspire 7736Z-4088 running kernel Linux hortlette
2.6.35.6-48.fc14.x86_64 #1 SMP Fri Oct 22 15:36:08 UTC 2010 x86_64
x86_64 x86_64 GNU/Linux
lspci reports: 00:1b.0 Audio device: Intel Corporation 82801I (ICH9
Family) HD Audio Controller (rev 03)
Slot: 00:1b.0
Class: Audio device
Vendor: Intel Corporation
Device: 82801I (ICH9 Family) HD Audio Controller
SVendor: Acer Incorporated [ALI]
SDevice: Device 0296
Rev: 03
lsmod|grep snd shows:
snd_hda_codec_intelhdmi 9993 1
snd_hda_codec_realtek 298211 1
snd_hda_intel 24399 4
snd_hda_codec 86743 3 snd_hda_codec_intelhdmi,snd_hda_codec_realtek,snd_
hda_intel
snd_hwdep 6392 1 snd_hda_codec
snd_seq 53791 0
snd_seq_device 6191 1 snd_seq
snd_pcm 80190 3 snd_hda_intel,snd_hda_codec
snd_timer 19892 2 snd_seq,snd_pcm
snd 63968 16 snd_hda_codec_intelhdmi,snd_hda_codec_realtek,snd_
hda_intel,snd_hda_codec,snd_hwdep,snd_seq,snd_seq_
device,snd_pcm,snd_timer
soundcore 6576 1 snd
snd_page_alloc 7559 2 snd_hda_intel,snd_pcm
Any ideas? I'm flummoxed. Like I said, booting into an F13 kernel and
everything works fine!
Thanks for any suggestions.
12 years, 12 months
VirtualBox VBoxVMM.so: cannot open shared object file
by Tod Thomas
The full messages is:
VirtualBox: supR3HardenedMainGetTrustedMain:
dlopen("/usr/lib/virtualbox/VirtualBox.so",) failed: VBoxVMM.so: cannot
open shared object file: No such file or directory
The VBoxVMM.so file is in the same directory as the VirtualBox.so file.
Also:
ldd /usr/lib/virtualbox/VirtualBox.so
linux-gate.so.1 => (0x00bec000)
libXinerama.so.1 => /usr/lib/libXinerama.so.1 (0x00110000)
libGL.so.1 => /usr/lib/libGL.so.1 (0x00961000)
VBoxVMM.so => /usr/lib/virtualbox/VBoxVMM.so (0xb7625000)...
shows its in the correct dir.
This thread suggests it has something to do with glibc:
https://bugzilla.redhat.com/show_bug.cgi?id=645500
This thread suggests it has been fixed:
https://bugzilla.rpmfusion.org/show_bug.cgi?id=1465
If all of this information is correct will it soon become part of the
FC13 yum update stream?
Thanks - Tod
13 years
Init fails on FC14
by Heinz Diehl
Hi,
after a boot into Gnome and opening a root console,
switching to runlevel 3 (or whatever) fails. "init 3" or "telinit 3"
does simply nothing, and the box begins to lock up. There's no problem to
boot into runlevel 3 or whatever.
Does anybody here encounter the same, and know a solution?
13 years