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
12 years, 2 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, 11 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.
13 years, 3 months
Enabling Airport wireless on Macbook Air with F12
by Colin Paul Adams
Thanks to Chris Smart, Peter Danenberg and others, I have been able to
install Fedora 12 as the sole O/S on my Macbook Air (first
generation).
However the wirless networking is not enabled.
I am following the instructions in
http://docs.fedoraproject.org/wireless-guide/f12/en-US/html-single/#chap-... .
There was no wireless device shown in the network Configuration, so I
clicked New and added a device for hardware Apple Airport.
I also tried adding wireless device on the Hardware tab (eth0), but although
it allows me to do this, after I save and then reopen the Network
Configuration, the hardware only shows a device pan0 of Type Ethernet
(which was there from the start). It does appear on the Devices tab
(it didn't originally until I added it), but has staus of inactive,
and no means to activate it.
However, even after restarting the computer, the wireless icon on the
panel says there are no network devices available.
So I tried removing the device from control by NetworkManager, and
activated it manually. But then I get:
Device eth0 does seem to be present, delaying initalization.
What do I need to do?
--
Colin Adams
Preston Lancashire
13 years, 6 months
Kernel boot problems or is my hard drive failing ?
by linux guy
If I power down my laptop via the usual KStart->Shutdown means, it can
take up to 4 restart attempts before it fully boots.
It has no problem launching grub and the kernel selection screen. That
it does reliably every time. After that, there are issues.
Twice I will get a back screen with a flashing cursor. Then I will get
an ehci -19 error. Then it will boot properly.
My fscks are fine. I had a block error once, about two weeks ago, but
that was with an older F12 kernel after completely crashing during a
resume from suspend to RAM.
Is anyone else experiencing a problem booting ? Does this sound like a
kernel problem or is my hard drive failing ?
Thanks
$ uname -a
Linux localhost.localdomain 2.6.31.9-174.fc12.i686.PAE #1 SMP Mon Dec 21
06:04:56 UTC 2009 i686 i686 i386 GNU/Linux
13 years, 9 months
Vinagre???
by Antonio M
I have two boxes, both have UltraVNC and Vinagre (Remote desktop
viewer), exactly the same packages both in F11 fully updated
When I connect from A to B both Vinagre and UltraVNC work, but when I
connect from Ato B UltraVNC works fine but in Vinagre I see the list
of remote desktops, but when I try to connect I get the message
Connection closed: The connection to host B has been closed.
Any idea??
Tnx
--
Antonio Montagnani
Skype : antoniomontag
SIP: antoniomontag(a)ekiga.net
13 years, 9 months
assertion in NetworkManager
by Philipp Böhm
Hello @all,
after upgrading to Fedora 12 I get some problems with NetworkManager for
example Wireless Networks were disabled and you couldn't avtivate this.
Some entries in /var/log/messages shows me an assertion in
NetworkManager. I will post these line and I hope that somebody can help
me. My wireless-device is an Atheros AR242x 802.11abg Wireless PCI
Express Adapter (wlan0).
/var/log/messages:
Nov 22 11:00:18 philipps-toshi NetworkManager: <info> Wireless now
enabled by radio killswitch
Nov 22 11:00:18 philipps-toshi rpc.statd[1270]: Version 1.2.1 Starting
Nov 22 11:00:19 philipps-toshi NetworkManager: ifcfg-rh: parsing
/etc/sysconfig/network-scripts/ifcfg-wlan0 ...
Nov 22 11:00:19 philipps-toshi NetworkManager: ifcfg-rh: error:
Missing SSID
Nov 22 11:00:19 philipps-toshi NetworkManager: ifcfg-rh: parsing
/etc/sysconfig/network-scripts/ifcfg-eth0 ...
Nov 22 11:00:19 philipps-toshi NetworkManager: ifcfg-rh: read
connection 'System eth0'
Nov 22 11:00:19 philipps-toshi NetworkManager: ifcfg-rh: parsing
/etc/sysconfig/network-scripts/ifcfg-lo ...
Nov 22 11:00:19 philipps-toshi NetworkManager: <info> (wlan0): driver
supports SSID scans (scan_capa 0x01).
Nov 22 11:00:19 philipps-toshi NetworkManager: <info> (wlan0): new
802.11 WiFi device (driver: 'ath5k')
Nov 22 11:00:19 philipps-toshi NetworkManager: <info> (wlan0): exported
as /org/freedesktop/NetworkManager/Devices/0
Nov 22 11:00:19 philipps-toshi NetworkManager: <info> (wlan0): now managed
Nov 22 11:00:19 philipps-toshi NetworkManager: <info> (wlan0): device
state change: 1 -> 2 (reason 2)
Nov 22 11:00:19 philipps-toshi NetworkManager: <info> (wlan0): bringing
up device.
Nov 22 11:00:19 philipps-toshi kernel: ADDRCONF(NETDEV_UP): wlan0: link
is not ready
Nov 22 11:00:19 philipps-toshi NetworkManager: <info> (wlan0):
preparing device.
Nov 22 11:00:19 philipps-toshi NetworkManager: <info> (wlan0):
deactivating device (reason: 2).
Nov 22 11:00:19 philipps-toshi NetworkManager:
supplicant_interface_acquire: assertion `mgr_state ==
NM_SUPPLICANT_MANAGER_STATE_IDLE' failed
13 years, 9 months