search for: agane

We have a Xen 3.0 / Linux kernel 2.6.15 machine with the domU''s configured for shared /home directories. One of the domU''s is an NFS server, exporting /home, and the other domU''s all mount this. It all functions fine, but it''s pretty slow. I tried untarring a recent Linux kernel tarball. On the NFS server domU this takes about 25 seconds. I didn''t

>> In that case, it needs a cool "release name". :) > > Suggestions welcome! Names of flowers are numerous but not exactly cool. I do not think any other software project has used flower names. Aaron

I am following along in http://llvm.org/docs/GettingStartedVS.html with a Hello World bitcode file. I can run the file using the command `lli HelloWorld.bc`, but now I want to link it into an executable file (on windows). The next thing the document says to run is `llc -filetype=obj HelloWorld.bc` which runs fine and now I have a `HelloWorld.obj` file. It's the last step that is giving me some

On Thu, 13 Oct 2005, Misha Brukman wrote: >> How does this tentative plan sound: we have two more weeks of >> development, then start the release processing part on about Oct 31 >> (spooky!). > > In that case, it needs a cool "release name". :) Suggestions welcome! -Chris -- http://nondot.org/sabre/ http://llvm.org/

Hi, We are seeing more long delays in zpool import, say, 4~5 or even 25~30 minutes, especially when backup jobs are going on in the FC SAN the LUNs resides (no iSCSI LUNs yet). On the same node for the LUNs of the same array, some pools takes a few seconds, but minutes for some. the pattern seems random to me so far. It''s first noticed soon after being upgraded to Solaris 10 U6

Hi List I am hoping that someone here could perhaps give me a straight answer on a question that someone asked me today I have always belived that if you have 5 hard drives 1 50gb second 50gb third 20gb fourth 60gb firth 30gb that the largest would then be the size of the smallest disk, not 80 or 100 or 120 for that matter or am I wrong here? Regards? Per Qvindesland? -------------- next part

Michael Smith wrote: > I would think the logical (and simpler) way to do this would be on the > client side. But as I said, patches welcome. darkice support stream dump on the encoder side, but this is far from logical: in a typical setup, the encoder is a machine not visible from the outside, while the server (per definition) is visible. when generating the stream dump on the encoder,

Michael Smith wrote: > Relaying (done already) and mp3 streaming (done already - but the support > for that is pretty limited. No metadata, for example). Serverside stream > dump doesn't seem terribly important - but if it's something you care > about, adding it should be easy. Patches welcome. This is a convenient feature, used by me & other live streamers to archive