similar to: about new Centos SIG distro releases

Dear List, I need a barplot with vertical bars. Each bar should have a label. The problem is, that the labels are too long, so they overlap, or only every seccond label is displayed in the output. Here is a little syntax: dd <- c(100,110,90,105,95) barplot(dd,names.arg=c('Conduct Disorders','Attention Deficit', 'Eating Disorders',

The future of the CentOS Project is CentOS Stream, and over the next year we?ll be shifting focus from CentOS Linux, the rebuild of Red Hat Enterprise Linux (RHEL), to CentOS Stream, which tracks just ahead of a current RHEL release. CentOS Linux 8, as a rebuild of RHEL 8, will end at the end of 2021. CentOS Stream continues after that date, serving as the upstream (development) branch of Red

This is an article I came across on zdnet.com. You may or may not agree with it. Personally, I don't. Anyway, here's the link to it. I thought some of you might want to read it, and form your own opinion. http://blogs.zdnet.com/Murphy/?p=769 Thanks for the help on the wireless problem. Jim

Hi dear all, In my laptop(ubuntu 11.10 64bit), I maintained a released R (2.14) and a developmental R, I can specify qplot(..., alpha = ) in R 2.14 , but when I try to use transparency in developmental R, I got a warning message and the plot is clearly not I want. minimal example: > qplot(data = mtcars, x = mpg, y = cyl, alpha = cyl) Warning message: In grid.Call.graphics(L_points, x$x, x$y,

Hi dear all, In my laptop(ubuntu 11.10 64bit), I maintained a released R (2.14) and a developmental R, I can specify qplot(..., alpha = ) in R 2.14 , but when I try to use transparency in developmental R, I got a warning message and the plot is clearly not I want. minimal example: > qplot(data = mtcars, x = mpg, y = cyl, alpha = cyl) Warning message: In grid.Call.graphics(L_points, x$x, x$y,

I built some reasonably successful tools in a graphical database for reconstructing the developmental turning points for feedback loop driven natural processes. I'm trying to move it to R and am having difficulty with the very basics, i.e. a) defining time series using time as a natural number rather than a place in a table. I was also hoping b) someone might have built some of the

eWeek reviewed Samba 2.2 at : http://www.zdnet.com/eweek/stories/general/0,11011,2712294,00.html - they seem to like it ! It's certainly encouraging to get trade coverage like this, I'm hoping the more people who report Samba use in their organisation to press outlets will encourage them to cover more Open Source/Free Software products ! Cheers, Jeremy Allison, Samba Team. --

Hello all, This is something that I am sure has a really suave solution in R, but I can't quite figure out the best (or even a basic) way to do it. I have a simple linear regression that is fit with lm for which I would like to estimate the x intercept with some measure of error around it (confidence interval). In biology, there is the concept of a developmental zero - a temperature under

Hi all, For people who are looking for some objective numbers to help recommend Samba to their employers (I know there are some of you on this list :-) you might want to look at the following couple of articles. The first one is in Smart Reseller (a USA trade press magazine) at : http://www.zdnet.com/sr/stories/issue/0,4537,2196106,00.html titled : "The Best Windows File Server:

Samba digest 1966, Jeremy Allison wrote: > For people who are looking for some objective > numbers to help recommend Samba to their employers (I > know there are some of you on this list :-) you might > want to look at the following couple of articles. > > The first one is in Smart Reseller (a USA trade press > magazine) at : > >

Link here http://news.zdnet.com/2100-9595_22-318208.html Will H264 become web standard in the future?

Link here http://news.zdnet.com/2100-9595_22-318208.html Will H264 become web standard in the future?

Hi So after reading this, felt I should apply the fix to a CentOS6 VPS that I have. http://www.zdnet.com/article/linux-tcp-flaw-lets-anyone-hijack-internet-traffic/ The article doesn't talk about CentOS or Redhat, but I assume the problem is the same, and hoping the solution is the same. However that doesn't seem to be the case. [root at vps ~]# uname -r 2.6.32-042stab108.7 [root at

Questions re this statement in the ZDNET article -- "In all cases, users reported that downgrading systems to a previous release to reverse the BootHole patches usually fixed their problems." A previous release of what? GRUB2 So that's my first question. Second. I'm assuming the the muti-screen UEFI settings I see are standard for more recent BIOS -- not sure of version. Do

On Fri, Nov 4, 2016 at 8:59 AM, Johnny Hughes <johnny at centos.org> wrote: > On 11/04/2016 04:38 AM, James Hogarth wrote: > > As a heads up RHEL 7.3 is released: > > <snip> > > 1. Is CentOS-7.3 done yet? Answer: NO! > > And it is NOT CentOS-7.3 .. it is CentOS-7 (1611) based on RHEL-7.3 > Sources. The main tree will be labeled '7.3.1611' on

I *know* there has been a lot going on, and congratulations on getting CentOS 8 out! But(!), I don't see any updates to CO 7.7.1908 in the "updates" directory on the mirrors I typically use. All the files date from Sept. 14th. Is something broken? -- *Matt Phelps* *Information Technology Specialist, Systems Administrator* (Computation Facility, Smithsonian Astrophysical

I notice two versions on the Web site, 0.2.2 being shown as developmental. I'm building a new server that will run Icecast 1.3.11 and I'm wondering how stable Ices 0.2.2 is? Are there enough fixes in it that it's worth using it? Thanks, Hunter --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list,

I recently uploaded a developmental version of the Matrix package, Matrix_0.6-1.tar.gz, to CRAN where it is in the src/contrib/1.9.0/Other directory. It requires some of the packages that will appear in R-1.9.0. This version marks a major redesign of the Matrix package to use S4 classes and methods and to incorporate sparse matrix manipulations using routines from TAUCS

Hi, While puppet creates its own directories for internal stuff (puppetca, state, etc.), there''s a fair bit of latitude given to where things like manifests and uploaded files live. I didn''t get much guidance from the docs when I first set things up so I mostly poked at things until the worked. Take a look at the following and let me know if this looks reasonable; if so, it

That's all well and good, but how about you actually include the minor number AND the release date? I.e. 7.3-1104 for CentOS 7.3 released today, for example. I'm all for the SIGs to keep track of their own upstreams, but surely there's a better way to do this that doesn't annoy the heck out of us Joe-Blows out here. A lot of us don't have the time (or inclination) to deal