search for: egotists

Hello. Lost my test hardware, being used for other purposes. Any idea what the mimimum hardware for a 1-FXO (X100P), 4 FXS (TDM400, 4 analog phones) setup ? Regards...martin -- One nice thing about egotists: they don't talk about other people.

...#39;t format = "%H:%M:%OS6" work as documented? -- Sam Steingold (http://sds.podval.org/) on CentOS release 5.3 (Final) http://dhimmi.com http://openvotingconsortium.org http://palestinefacts.org http://honestreporting.com http://www.memritv.org http://camera.org There are two kinds of egotists: 1) Those who admit it 2) The rest of us

Nov 19, 2003 To Everyone on this list... What's been suggested for a FAQ and other "much needed information" for such a _HIGHLY_ technical software product has been proven thousands of times in the past few months. Even an untrained monkey can see that, including many geeks. Those that are against it are the very _few_ arrogant self-centered egotistical few that think their middle

Quick question: In ocfs2_create_new_inode_locks(), we claim: 1436 /* 1437 * We don't want to use DLM_LKF_LOCAL on a meta data lock as they 1438 * don't use a generation in their lock names. 1439 */ 1440 ret = ocfs2_create_new_lock(osb, &OCFS2_I(inode)->ip_inode_lockres, 1, 0); Ass you can see, we pass '0' for the 'local'

This sounds like a necessary sanity check for raising teen-agers. Brian Brunner brian.t.brunner at gai-tronics.com (610)796-5838 Brian Brunner brian.t.brunner at gai-tronics.com (610)796-5838 >>> BillsCentOS at triad.rr.com 11/07/05 04:23PM >>> Folks, If the reward is nothing more than the egotistical satisfaction of telling that SOB where to get off let the damn issue

There are couple of excellent patches available from http://www.ssi.bg/~ja for advance routing,load balancing,link-failover etc. Any idea why these patches are not yet integrated into the upstream kernel? Thanks

Hello Sunil, attached is a patch which implements full quota support for ocfs2 tools. It's based against ocfs2-tools git's master branch. Would you please consider inclusion of the patch? Thanks. Honza -- Jan Kara <jack at suse.cz> SUSE Labs, CR -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Quota-support-for-ocfs2-tools.patch

Replaced calls to kmalloc followd by memcpy with a single call to kmemdup. This patch was found using coccicheck. Signed-off-by: Alexandru Gheorghiu <gheorghiuandru at gmail.com> --- fs/ocfs2/localalloc.c | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/fs/ocfs2/localalloc.c b/fs/ocfs2/localalloc.c index aebeacd..839183f 100644 --- a/fs/ocfs2/localalloc.c +++

Folks, To keep track of what we want to upstream in the 2.6.28-rc cycle, I've put together a branch called 'xattr-28' with almost all of the patches merged. You can see it and pull it from my linux-2.6.git repository. View: http://oss.oracle.com/git/?p=jlbec/linux-2.6.git;a=shortlog;h=xattr-28 Pull: git://oss.oracle.com/git/jlbec/linux-2.6.git xattr-28 The branch contains the

Ooops, last one didn't CC ocfs2-devel. On Mon, Oct 13, 2008 at 06:16:15PM -0700, Joel Becker wrote: > @@ -232,25 +231,17 @@ int ocfs2_populate_inode(struct inode *inode, struct ocfs2_dinode *fe, > ocfs2_mount_local(osb) || !ocfs2_stack_supports_plocks()) > use_plocks = 0; > > - /* this means that read_inode cannot create a superblock inode > - * today. change if

Currently, when listing xattrs, kernel define XATTR_LIST_MAX as 65536 in include/linux/limits.h, so it can't handle too many xattrs. But with ocfs2 xattr tree, we actually have no limit for the number. And it will pollute the message with something like this when listing. (27738,0):ocfs2_iterate_xattr_buckets:3158 ERROR: status = -34 (27738,0):ocfs2_xattr_tree_list_index_block:3264 ERROR:

heyas- I believe there is a need for a standard vorbis comment field to encode "Total Number of Tracks (on a CD)". Why we need this -------------------- - Existing Vorbis programs already implement this, inconsistently, and hence don't interoperate. These seems the key reason to me. - MP3s include this - Some software (e.g., iTunes) uses this information, e.g., to display

Folks, I *suggest* that little or no reply to this is warranted. It's just the statements of an old fart trying to make a (slightly) better environment for all of us. These thoughts are offered for consideration and use as you see fit. For some, "Hey, that'll work for me too" is the hoped for result. No discussion is intended or warranted, IMO. If you recognize yourself in

Hi all, I have a bug with OCFS through configfs : to illustrate this, try : while true ; do ls -l /sys/kernel/config/cluster/ocfs2/heartbeat ; done& while true ; do echo 31> /sys/kernel/config/cluster/ocfs2/heartbeat/dead_threshold ; done& So, I have a kernel crash : BUG: unable to handle kernel NULL pointer dereference at 0000000000000040 IP: [<ffffffffa01fd214>]

Hi all, I have a bug with OCFS through configfs : to illustrate this, try : while true ; do ls -l /sys/kernel/config/cluster/ocfs2/heartbeat ; done& while true ; do echo 31> /sys/kernel/config/cluster/ocfs2/heartbeat/dead_threshold ; done& So, I have a kernel crash : BUG: unable to handle kernel NULL pointer dereference at 0000000000000040 IP: [<ffffffffa01fd214>]

In commit ea455f8ab68338ba69f5d3362b342c115bea8e13, we move the dentry lock put process into ocfs2_wq. This is OK for most case, but as for umount, it lead to at least 2 bugs. See http://oss.oracle.com/bugzilla/show_bug.cgi?id=1133 and http://oss.oracle.com/bugzilla/show_bug.cgi?id=1135. And it happens easily if we have opened a lot of inodes. For 1135, the reason is that during umount will call