Michael Hennebry | 1 Sep 2007 01:21
Picon
Picon

Re: DD not working--SUCCESS!

On Fri, 31 Aug 2007, Karl Larsen wrote:

> Michael Hennebry wrote:

> > So far as I can tell, the important thing
> > is not having a separate computer.
> > It is not mounting any partition on either drive.
> > A live CD can boot and run without using a hard drive.
> > It makes its file systems in ram.
> >
> >
>     I don't have enough RAM for a live CD to do dd. The Rescue CD does
> not have dd. I'm wondering if the F7 DVD might have dd? It has it
> somewhere.

You seem to have a rare rescue CD.
One can get away with mounting a source partition read only.
You can use the dd to copy a read only disk.
Do you have a swap partition?
Some live CDs can be told to use that.
It doesn't matter much if a swap partition
changes while it's being copied.

I think that with the right boot parameters
you can come up with everything mounted read only.
In that case, running dd should be possible and reliable.

--

-- 
Mike   hennebry <at> web.cs.ndsu.NoDak.edu
"Horse guts never lie."  -- Cherek Bear-Shoulders
(Continue reading)

Ashley M. Kirchner | 1 Sep 2007 01:31
Favicon

Re: [Fedora] Re: Specifying tmp for tar

Rick Stevens wrote:
> On Fri, 2007-08-31 at 23:18 +0300, Dotan Cohen wrote:
>   
>> I have a 2 GB bz2 archive that unzips to over 10 GB (wikipedia dump).
>> Although I have over 50 GB free in /home, / has only about 8 GB free.
>> Thus, as tar uses /tmp, the / filesystem fills up and I cannot
>> continue. How can I specify a tmp directory for tar in my home
>> directory? Note that man tar makes no mention of a tmp option.
>>     
>
> Boot in single user mode,  Then as root:
>
> 	# mkdir /home/tmp
> 	# chmod 777 /home/tmp
> 	# mv /tmp /tmp-old
> 	# ln -s /home/tmp /tmp
> 	# cp -a /tmp-old/* /tmp

    Doesn't tar only use tmp because it has to uncompress the file 
first?  If that's the case, why not uncompress the file first with bzip2 
somewhere on the file system that actually has space, and then run tar 
to extract the files?  In essence he would be renaming his file to 
archive.tar.bz2, run bunzip2 against it, and then run tar against the 
archive.tar...

    bzip uses whatever the current path is to compress or decompress a 
file, so /tmp wouldn't play a part here.

    That's my theory at least.  The last time I had to uncompress a 
large archive (over 100GiB in size), that's what I did and it worked 
(Continue reading)

Rui Miguel Silva Seabra | 1 Sep 2007 01:29

Re: rt2500 / rt2x00 freeze on shutdown

On Fri, Aug 31, 2007 at 04:43:26PM +0100, Ian Malone wrote:
> So, I'm not sure where to take this.  Is it likely to
> be a wpa_supplicant issue or a rt2500 one?  Has anyone
> else seen similar behaviour?

I have, and I think it's an Linux/rt2x00 problem...

Rui

-- 
Fnord.
Today is Prickle-Prickle, the 25th day of Bureaucracy in the YOLD 3173
+ No matter how much you do, you never do enough -- unknown
+ Whatever you do will be insignificant,
| but it is very important that you do it -- Gandhi
+ So let's do it...?

--

-- 
fedora-list mailing list
fedora-list <at> redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Karl Larsen | 1 Sep 2007 01:49
Picon
Favicon

Re: DD not working--SUCCESS!

Michael Hennebry wrote:
> On Fri, 31 Aug 2007, Karl Larsen wrote:
>
>   
>> Michael Hennebry wrote:
>>     
>
>   
>>> So far as I can tell, the important thing
>>> is not having a separate computer.
>>> It is not mounting any partition on either drive.
>>> A live CD can boot and run without using a hard drive.
>>> It makes its file systems in ram.
>>>
>>>
>>>       
>>     I don't have enough RAM for a live CD to do dd. The Rescue CD does
>> not have dd. I'm wondering if the F7 DVD might have dd? It has it
>> somewhere.
>>     
>
> You seem to have a rare rescue CD.
> One can get away with mounting a source partition read only.
> You can use the dd to copy a read only disk.
> Do you have a swap partition?
> Some live CDs can be told to use that.
> It doesn't matter much if a swap partition
> changes while it's being copied.
>
> I think that with the right boot parameters
(Continue reading)

Vivek J. Patankar | 1 Sep 2007 01:49
Picon
Gravatar

Re: vaio's screen brightness

Andre Kirchner wrote:
> I have just installed Fedora Core 6 in a Vaio laptop,
> and everything is fine except for the screen's
> brightness, which is too dark.
> Does anyone know how do I adjust it, or where can I
> find more information about it?

Did you try the brightness control hotkeys on the laptop keyboard?

-- 
Regards,
विवेक ज. पाटणकर (Vivek J. Patankar)

Registered Linux User #374218
Fedora release 7 (Moonshine)
Linux 2.6.22.4-65.fc7 x86_64

--

-- 
fedora-list mailing list
fedora-list <at> redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

John Rowan | 1 Sep 2007 02:35
Favicon

RE: Linux suitable motherboard/µprocessor?


-----Original Message-----
From: fedora-list-bounces <at> redhat.com
[mailto:fedora-list-bounces <at> redhat.com]On Behalf Of Arch Willingham
Sent: Friday, August 31, 2007 1:40 PM
To: For users of Fedora
Subject: RE: Linux suitable motherboard/µprocessor?

I buy everything from newegg.com. Great service, great prices, great
selection, great place....

-----Original Message-----
From: fedora-list-bounces <at> redhat.com
[mailto:fedora-list-bounces <at> redhat.com]On Behalf Of Claude Jones
Sent: Friday, August 31, 2007 12:41 PM
To: For users of Fedora
Subject: Re: Linux suitable motherboard/µprocessor?

On Friday August 31 2007 12:33:31 pm Bob Goodwin wrote:
> They seem to specialize in "come ons" and a lot of rebates!
>
> /I should unsubscribe from there mail list I guess.
>
> Bob Goodwin

I really dislike Tiger Direct. The missives from the Pres are
particularly obnoxious. The rebate process is a huge pain - I
bought a monitor once with a huge rebate - the forms we had to
fill out were tortuous and used non-intuitive language. It took
over an hour to go throught it all, and I had to get the
(Continue reading)

Tim | 1 Sep 2007 02:51
Picon

Re: DD not working--SUCCESS!

imalone:
>> How would you go about estimating a decent blocksize (other than by
>> testing)?  My first instinct would be to go for some percentage of
>> the drive's cache.

Jacques B:
> Available RAM.  Use as big a block size as can possibly be read into
> RAM (once you start caching to a drive you just as well be writing to
> the destination drive otherwise you slow it down even more).  We
> played around with this a while back and it certainly makes a
> difference (stands to reason as was already explained).
> 
> The one caveat would be if there are errors on the drive.  If that is
> the case, a full block is dropped (so if your block size is 4096
> bytes, then 4K gets dropped instead of 512 bytes - now imagine
> dropping a 256 meg block of data...).  ddrescue will use two block
> sizes - a larger one and a smaller one.  If it hits an error it drops
> back to the smaller one until it gets pass the error and then ramps
> back up to the larger block size.

I had a little play around with blocksizes for dd a while ago, while
zeroing a drive (I was zeroing out a bad drive to see it it'd goad the
drive into automatically sorting out the bad blocks, by itself - it
did).  The first attempt just started out using the default, and that
took ages.  After a bit of fiddling, I settled for using about a meg.

Of course my situation was a bit different, but it's to show that you'd
tweak the option to suit your circumstances.

--

-- 
(Continue reading)

Jim Cornette | 1 Sep 2007 02:59
Picon
Favicon

Re: DD not working

Karl Larsen wrote:
> Jim Cornette wrote:
>> Karl Larsen wrote:
>> Alas the LABEL problems and many others kept me busy doing
>>> stupid things.
>>
>> You really like to discourage people from attempting to help you with 
>> the above comment.
>    No the stupid things were of my own doing. Not setting the bios 
> properly, operating from the new hard drive when I thought I was on the 
> old hard drive. I didn't know two sets of the same LABEL will load up odd.
> 

Sorry, my English skills are poor. I read the comments as other people 
kept advising you to do stupid things. Many other problems would have 
been more clear to me.

> 
>> Anyway, last posting giving you stupid things to try. You got it 
>> altogether and need no replies to your queries.
>>
>    That is not the case. I learned dd is a way to do this from this list 
> and I am trying to make it work. Lots of help has I hope made this happen.
>>>
>>>    This time I know much more 8-)
>>
>    And it is from my experience  and that of the people on this list.

I learn quite a bit from the problems and solutions to the problems 
others encounter. I very rarely use some of the programs others need at 
(Continue reading)

Tim | 1 Sep 2007 03:13
Picon

Re: LVM or FS:EXT3?

On Fri, 2007-08-31 at 12:21 +0100, Alan Cox wrote:
> The disks themselves. I've yet to meet a reliable disk, ever year or
> two one dies on me. 

How do you treat them?

With all due respect to the Google research that says hot drives aren't
a problem, I don't buy it.  Warm drives, maybe, but I've seen plenty
that get painfully hot, and those drives did become unreliable.  When
I've built, or rebuilt, systems so that the drives don't roast, they
seem to last well.

You also want to minimise vibration.  Use all four screw mount points,
and firmly.  If you hear it buzzing, that's not good.

-- 
[tim <at> bigblack ~]$ uname -ipr
2.6.22.4-65.fc7 i686 i386

Using FC 4, 5, 6 & 7, plus CentOS 5.  Today, it's FC7.

Don't send private replies to my address, the mailbox is ignored.
I read messages from the public lists.

--

-- 
fedora-list mailing list
fedora-list <at> redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

(Continue reading)

mcforum | 1 Sep 2007 03:59

Yum is ill again

Resolving Dependencies
--> Running transaction check
---> Package dcraw.i386 0:8.77-1.fc7 set to be updated
---> Package ntp.i386 0:4.2.4p2-3.fc7 set to be updated
---> Package cryptsetup-luks.i386 0:1.0.5-4.fc7.1 set to be updated
---> Package pidgin.i386 0:2.1.1-1.fc7 set to be updated
---> Package crontabs.noarch 0:1.10-15.fc7 set to be updated
---> Package liboil.i386 0:0.3.12-9.fc7 set to be updated
---> Package kdebindings.i386 0:3.5.7-1.fc7.1 set to be updated
---> Package glibmm24.i386 0:2.12.10-1.fc7 set to be updated
---> Package libpurple.i386 0:2.1.1-1.fc7 set to be updated
--> Processing Dependency: perl(DCOP) for package: kdesdk
Traceback (most recent call last):
  File "/usr/bin/yum", line 29, in <module>
    yummain.main(sys.argv[1:])
  File "/usr/share/yum-cli/yummain.py", line 135, in main
    (result, resultmsgs) = base.buildTransaction() 
  File "/usr/lib/python2.5/site-packages/yum/__init__.py", line 540, in buildTransaction
    (rescode, restring) = self.resolveDeps()
  File "/usr/lib/python2.5/site-packages/yum/depsolve.py", line 885, in resolveDeps
    (checkdep, missing, conflict, errormsgs) = self._processReq(dep, prcoformat_need)
  File "/usr/lib/python2.5/site-packages/yum/depsolve.py", line 334, in _processReq
    requirementTuple, errormsgs)
  File "/usr/lib/python2.5/site-packages/yum/depsolve.py", line 469, in _requiringFromInstalled
    return self._requiringFromTransaction(reqpkg, requirement, errorlist)
  File "/usr/lib/python2.5/site-packages/yum/depsolve.py", line 574, in _requiringFromTransaction
    reqpkg = self.tsInfo.matchNaevr(name=name, ver=version, rel=release)[0]
IndexError: list index out of range

perl seems to be contaminating everything.
(Continue reading)


Gmane