Association of personal computer users needs installfest support at UAT
February 7 and 8th for their regional conference at _UAT.
Obnosis.com BlackBerry Message
-Original Message-
From: Stephen cryptwo...@gmail.com
Date: Wed, 17 Dec 2008 22:38:10
To:
Hmm maybe i can find someone to help me sort out my wine graphical
issues with the Radeon 2900XT i have :-)
Thanks for the details.
Personally i think this is a decent idea.
On Wed, Dec 17, 2008 at 9:35 PM, Dazed_75 lthiels...@gmail.com wrote:
Installing any variety of Linux we have or the
I'm developing a presentation called (tentatively), Why Open source hates
Marketing. It's not technical though. Should be entertaining, if I get my
act together like I did here http://blip.tv/file/1210527. Appropriate or
no?
On 2008-12-16 21:14, der.hans wrote:
moin moin,
this is a call
Mark Zyniecki wrote:
Well, Matt, I do live in BFE if that's what you call living half way
between Flagstaff and Williams.
That's pretty close to BFE, but at least you don't have to drive 150
miles to the closest Interstate highway.
The WinXP modem init string is: AT F E0 C1 D2 V1 S0=0\V1
In
I'd like to hear it. I think it's important to think not just about
the technology, but also how it's promoted and perceived.
alex
On Dec 18, 2008, at 9:43 AM, Steven Shaffer wrote:
I'm developing a presentation called (tentatively), Why Open source
hates Marketing. It's not technical
I would try setting mru and mtu to 1492, as long as your phone connection
is good, you want the biggest packet possible.
You can even try 1500, but that might cause a little degradation.
1492, should improve your situation, but I'm not sure how much.
The differences in the init string I see,
Those recomendations are valid for broadband, but this is analog dialup,
so anything over 576 is gonna cause delays. Windows is defaulting to an
MTU of 576, which is why it's working better right now. You don't want
the biggest packet possible when your bandwidth is limited, it's like a
OK, I did it...
I compiled an all-modules kernel and I am using udev inside my initramfs
init to find my root partition and boot the system.
It works cool... :)
It wasn't easy, and after lots of tries with klibc-1.5, I gave it up and
went to a straight glibc (2.8-20080929).
Also, sorting
If I remember correctly, the initrd ramdisk is freed back once you
switch over to the real root filesystem. I don't remember if you have to
do anything special other than switching to the real root.
This page has some more info.
http://www.ibm.com/developerworks/linux/library/l-initrd.html
Thanks! :)
But just to clarify, initrd is not initramfs.
For what I have read, they are pretty similar, but also have fundamental
differences. I ditched initrd because initramfs is here to replace it, so I
haven't looked at it carefully.
But again, for what I have read, and being unfamiliar
Tried rsync -av /home/username /media/disk for the first time. Every
thing appeared to go well but there was an error message at the end:
rsync error: some files could not be transferred (code 23) at
main.c(977) [sender=2.6.9]
Running diff -r /home/holtzm /media/disk/home returned nothing
I have a friend who is doing a contract job.
please reply to to...@guadagno.org
He needs help modifying css styles for http://www.cmsmadesimple.org/
He is willing to discuss pricing, so its a paying gig.
---
PLUG-discuss mailing list -
A) rdiff
You might use dircmp instead of rdiff to include the dot . files?
dircmp holtzcm /media/disk/home
B) rsync
1) rsync reports a code 23 when there's a problem with the
password file, even when the right password is supplied and files are
transferred.
This:
http://www.media.rice.edu/media/NewsBot.asp?MODE=VIEWID=11823 [1]
has (apparently) been out there on the web since 11/21/2008,
but it was just recently called to my attention in an e-mail message
-- which mentioned that it would probably be picked up by
Computerworld; and -- sure
Did you capture rsync's output?
It should tell you exactly which file it could not deal with.
Tee the output and grep for error may give you info.
In addition to the problems Lisa mentioned, rsync also can choke on
linked files.
Harold
-Original Message-
From: Robert Holtzman
On Thu, 18 Dec 2008, koder wrote:
Did you capture rsync's output?
It should tell you exactly which file it could not deal with.
There was no indication of a problem except for the error message at the
end.
Thanks.
--
Bob Holtzman
If you think you're getting free lunch,
check the price of
On Fri, 19 Dec 2008, Lisa Kachold wrote:
A) rdiff
You might use dircmp instead of rdiff to include the dot . files?
dircmp holtzcm /media/disk/home
Ran a search on dircmp and most everything I found said diff did the
same thing. One message asked specifically where to d/l dircmp and all
17 matches
Mail list logo
