search for: jamesh

Is there a way to automatically enable Remote Desktop from a NETLOGON script? I want to enable Remote Desktop on *a lot* of machines, but I don't want to do it manually. -- Andrew Gaffney

I have not had any success building a more recent version of GDE than 2.16.0 on CentOS. I tried jhbuild, and went line by line using the how-to web page for jhbuild (http://www.gnome.org/~jamesh/jhbuild.html), and I get hung up on dbus-glib-l (which does not appear to be in CentOS or available for it, at least from base, updates, extras, KB & rpmforge). Garnome is another possibility that I haven't looked at yet 'cuz jhbuild is supposed to be easy and fully automated (it might...

...=heatmap&fun=heatmap.html) is somewhat opaque to someone with my programing skills. Would it be better to reorder the heatmap and then somehow add in the dendrogram with add.expr command? If anyone could suggest something, or point me in the right direction I would greatly appreciate it. jamesh Here are the contents of the two files used as examples above: env.dat: soil1 soil2 soil3 marine1 marine2 marine3 One 23 24 26 0 0 0 Two 43 43 43 3 6 8 Three 56 78 45 23 45 56 Four 6 6 3 34 56 34 Five 2 17 12 76 45 65 ultra.newick: (((One:1,Four:1):1,(Three:1,Two:1):1):1,Five:3):0.0;

I'm transitioning someone's quite old server [Debian] to a new CentOS6 host. All going pretty well. But they server up some functionality using CGI scripts via Apache that use something referred to on the Debian box as the www-mysql package? This a binary that executes HTML pages containing embedded SQL statements. Anyone know where the source for this can be found or if it has a more

hi, I use the oh323 driver to answer H323 calls. The connection is set up normally. In my extensions.conf file I use: exten => s,1,Answer exten => s,2,Playback(demo-instruct) exten => s,3,Hangup So that when a call is answered i get: *CLI> -- Executing Answer("H323/ip$10.0.3.23:32782/6502", "") in new stack -- Executing

hi, i have some newbie questions about channel banks. i have an adtran act-1241 sitting around. it accepts D4 modules, and it contains a number of e&m cards. first of all, how does this thing work? a t1 contains 24 channels, and i noticed that the channel bank has space for 24 cards. what do these cards do? what are their outputs? the ones that are in there have some outputs on the front

/usr/lib/python2.3/site-packages/xen/xm/main.py line 308 should be migrate.main(args) not migrate.main(arg) /usr/lib/python2.3/site-packages/xen/xm/opts.py i couldn''t get ''xm migrate help'' to work without changing line 330 to print ''Usage: '', self.use or ''OPTIONS'' from print ''Usage: '', self.argv[0], self.use

In case it helps anyone, here''s a script I use to boot xen0 over iscsi with an initrd using linux-iscsi and iscsi-init (both on sourceforge). Some (or most) of it might be debian (sarge) specific though. The script goes in /etc/mkinitrd/scripts and puts the bits and pieces in place. It has to prepend stuff to /script in the resultant initrd so it does a few funny things. Add your Ethernet

FWIW, I assign my MAC addresses as "FE:FD:XX:00:YY:ZZ" Where: XX = what xen does to MAC addresses (00 in xen0, 01 in xenU) YY = vmid (unique across all physical servers) ZZ = interface number in xenU (00 = eth0, 01 = eth1) Works for me! Someone asked about trying to find a duplicate MAC address on a network - it''s pretty hard to do as the whole idea is that MAC addresses are

I want to test asterisk (open source pbx) and the simplest way to do so is just to create a new domain and install it there. After some testing I''d like to put an ISDN card in and connect it to the real world. Is there anything about an ISDN card that would make it not work at all under xen, and what would I have to do to make it work under a domain other than 0? Finally, assuming the

> This should already be useful, at least for file-based disks. It''d be > nice to > have the ENBD script working and have some kind of iSCSI script at some > stage. For iSCSI, have a look at iscsi-init at sourceforge. http://iscsi-init.sourceforge.net. Load it as a module in an initrd and it uses some kernel parameters and automatically configures the network and then

There is no CONFIG_SCSI to enable in xenU. Is there any reason for this? I want to try out iSCSI and obviously it needs scsi support. Or would I be better doing it in dom0 and exporting it? thanks James

Whilst tinkering with lvm (which now works great - thanks!), I made a typo which caused the domain to stop booting. I think it was just that I got the config file wrong in terms of which device mapped to which. Anyway, I had specified ''restart=True'' and so the domain was starting to boot, failing, then restarting again. This was the expected behaviour, but it was a pain to kill.

As promised, here''s what I did to get iSCSI root running under XenU under Debian 3.1 (Sarge): Be running linux 2.6 under XenU. Build XenU with SCSI disk support (I did them as modules) Get linux-iscsi 4.0.1.8 from http://sourceforge.net/projects/linux-iscsi/ Build it according to the instructions there (i found it a bit tricky) and install under your XenU Get iscsi-init 4.0.1 from

I have just noticed this message in my kernel logs, reporting the possibility of an error with my memory. This would go a long way towards explaining the problems i''ve been having. This particular error is occuring when i''m not running xen so is obviously not something brought on by xen itself. The strange thing is that the NMI error is always followed by the TLAN: eth0: Adaptor