search for: upheavals

On Thu, Dec 18, 2014 at 7:20 AM, David Both <dboth at millennium-technology.com> wrote: > +1 > > It can be quite annoying when the X console is changed from one Virtual > Console to another as happens with almost every release of CentOS and > Fedora. I would really like it to be always consistent at Console 7. And the > "real" system console should always be

On 12/28/14 20:52, Always Learning wrote: > > On Thu, 2014-12-18 at 10:30 -0600, Les Mikesell wrote: > >> .............. The design changes are done in Fedora, by >> people who apparently never liked unix or consistency, not the people >> using Red Hat or CentOS that already have things working that they >> would like to keep working the same way across

All, Caveat: New user naivete to follow. I''m starting an application in Rails and I can''t use Gems. (There are legal implications in deploying unknown code here.) But Rails seems to have an extraordinary dependence on Gems. If I say ''rails PROJECT'', then the PROJECT directory gets created with supporting scripts, etc., but since they work internally

On 29/12/14 01:52, Always Learning wrote: > > On Thu, 2014-12-18 at 10:30 -0600, Les Mikesell wrote: > >> .............. The design changes are done in Fedora, by >> people who apparently never liked unix or consistency, not the people >> using Red Hat or CentOS that already have things working that they >> would like to keep working the same way across upgrades.

Hello Guys? I need to revert the X11 graphical server to Console 7. and enable VT1 as normal text as it was on the old distr.. Sincerely AndyBe

We have been network booting FreeBSD for some time with pxeboot. But now we would like to have menu of OSs to boot and got the idea somewhere that gpxelinux could do that for us. We copied gpxelinux.0 from the syslinux-4.02 distribution and replaced pxeboot with "gpxelinux" in the dhcpd.conf file. Indeed with a configuration file in pxelinux.cfg like this: default freebsd

...st Canadian authors seem to have found out about this the hard way ;-). The relevant document was called Stentor document ID-0001 "CALL MANAGEMENT SERVICE (CMS) CALLING NUMBER DELIVERY (CND) (Single and Multiple Message Format) Terminal-to-Network Interface". Following the upheavals in the Canadian telecom market it is now Bell Interface Document <http://www.bell.cdn-telco.com/bid/> BID-0001 and will cost you CAN$50 to download. Incidentally, Stentor's standard also allows for a Parameter Type 06, which includes a flag that indicates that the call is...

On Thu, 2014-12-18 at 10:30 -0600, Les Mikesell wrote: > .............. The design changes are done in Fedora, by > people who apparently never liked unix or consistency, not the people > using Red Hat or CentOS that already have things working that they > would like to keep working the same way across upgrades. What type of large commercial organisation lets undisciplined people

Ian Pratt wrote: > I sometimes think about moving the list onto our own majordomo setup, > but it would be quite an upheaval for subscribers, particularly those > that have mail filters set up. What do people think? Happy with > sourceforge, or time to move? I''m all for moving - the lag is frustrating. As to the filters, mine is set on having the [xen-devel] tag in the

2010/1/6 Talin <viridia at gmail.com> In my compiler, the multiple passes for resolving type names is done first, > using high-level type classes, before any LLVM IR is involved. The high > level classes are needed anyway since the LLVM type model does not capture > concepts such as const, up-casting, and other aspects of high-level types. > (Actually, I don't have discrete

Hi, I've followed the instructions on constructing recursive types ( http://llvm.org/docs/ProgrammersManual.html#BuildRecType) and I can succesfully create simple recursive types using the C bindings (e.g. struct Test { struct Test *t };). I want to generalize this to get type information from my language into generated LLVM code. My language allows arbitrary forward type declarations that I

I attempted the following: resources { service: purge => true, noop => true } service { sshd: ensure => running; iptables ensure => running; } And got the following message: notice: Starting configuration run err: Found a bug: uninitialized constant Parse notice: Finished configuration run in 0.47 seconds When I remove the ''resources'' line, everything works

Dear All- There are a lot of the following type of errors in my client and NFS logs following a recent volume expansion. [2012-02-16 22:59:42.504907] I [dht-layout.c:682:dht_layout_dir_mismatch] 0-atmos-dht: subvol: atmos-replicate-0; inode layout - 0 - 0; disk layout - 9203501 34 - 1227133511 [2012-02-16 22:59:42.534399] I [dht-common.c:524:dht_revalidate_cbk] 0-atmos-dht: mismatching