similar to: Re: Retiring the Tao Linux project

Displaying 20 results from an estimated 9000 matches similar to: "Re: Retiring the Tao Linux project"

2006 Jun 15
0
CentOS-announce Digest, Vol 16, Issue 5
Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When
2006 May 26
3
New member, new OS, old Tao user
Mr. Parsley, the main man at the Tao Linux group, has announced that he will no longer be able to do his thing for Tao Linux. Just recently, I had decided to investigate CentOS 4 before his announcement, and liked a lot of what I saw. Due to the Tao announcement, I have decided that CentOS will "have" to be the OS for my company in the future. Hence, my new membership to this list.
2006 Dec 11
1
Migrating from Tao
Hi all ! I have a box here that is till running tao linux, and I hadn't time to migrate to centos. This morning, I got to taolinux.org, and see that the website is out. Does someone have the "howto" on how to migrate frm tao to centos nearby ? Thanks, Nicolas
2007 Apr 07
3
Tao Live 5.00 released
Hi all, I am proud to announce the release of Tao Live 5.00. This live CD is based on the Beta release of CentOS 5 and includes multimedia enhancements from rpmforge.net repository. Tao Live uses a Squash filesystem to fit 2 GB of programs into a standard bootable CD. OpenOffice.org, Firefox, Gaim, XMMS, MPlayer, K3B and many other programs are included. Tao Live 5.00 is available via
2006 Feb 03
0
[LLVMdev] [fwd] LLVA, TAO Intent, Morphun, DualCor
Misha Brukman wrote: > I don't know the current status of the LLVA project, so I will let the > current developers chime in. Please send all LLVM and LLVA questions to > llvmdev at cs.uiuc.edu . My apologies for the late reply. > > ----- Forwarded message from N O S P A M <ti_dak at yahoo.com> ----- > > Date: Tue, 17 Jan 2006 09:47:32 -0800 (PST) > From: N O
2006 Jan 30
2
[LLVMdev] [fwd] LLVA, TAO Intent, Morphun, DualCor
I don't know the current status of the LLVA project, so I will let the current developers chime in. Please send all LLVM and LLVA questions to llvmdev at cs.uiuc.edu . ----- Forwarded message from N O S P A M <ti_dak at yahoo.com> ----- Date: Tue, 17 Jan 2006 09:47:32 -0800 (PST) From: N O S P A M <ti_dak at yahoo.com> Subject: LLVA, TAO Intent, Morphun, DualCor Hello I want to
2006 Feb 04
1
[LLVMdev] [fwd] LLVA, TAO Intent, Morphun, DualCor
Is the source code for llva available esp the linux kernel port. Is there a project page for llva ? Mike On 2/3/06, John Criswell <criswell at cs.uiuc.edu> wrote: > Misha Brukman wrote: > > I don't know the current status of the LLVA project, so I will let the > > current developers chime in. Please send all LLVM and LLVA questions to > > llvmdev at cs.uiuc.edu .
2004 Jun 27
0
Kernel packages and 3rd party kernel modules
Hi, I'd like to come back to this topic. We've discussed this before on IRC but there's still no acceptable solution implemented. 3rd party kernel-modules are build against the official Red Hat kernels, to make them work with the TaoLinux/CentOS kernels there are specific requirements: + kernel RPM package should provide the same version/release + kernel version/release should
2005 Jan 12
3
bind and 3.4
Hello, I encountered a problem when upgrading from 3.3 to 3.4 on i386. The machine is a production name server running bind. Looks like the new rpm moved my named.conf to .rpmsave and chkconfig'ed bind to off. That's really bad. A more gentle behavior would have been to save the new named.conf to .rpmnew and not mess with initscripts. Anyone else notice that? Francois Caen
2023 Oct 03
0
maptools, rgdal, rgeos and rgrass7 retiring Monday, October 16
The legacy R spatial infrastructure packages maptools, rgdal and rgeos will be archived by CRAN on Monday, October 16, 2023; rgrass7 has already been replaced by rgrass and will be archived with the retiring packages. The choice of date matches the previously announced archiving during October 2023, and the specific date matches the release schedule of Bioconductor 3.18 (some Bioconductor
2023 Oct 03
0
maptools, rgdal, rgeos and rgrass7 retiring Monday, October 16
The legacy R spatial infrastructure packages maptools, rgdal and rgeos will be archived by CRAN on Monday, October 16, 2023; rgrass7 has already been replaced by rgrass and will be archived with the retiring packages. The choice of date matches the previously announced archiving during October 2023, and the specific date matches the release schedule of Bioconductor 3.18 (some Bioconductor
2006 Oct 11
1
Retiring test2spec?
Hi all, We''re thinking about retiring the test2spec translation tool because it''s becoming a maintenance problem. Is anyone using it? Would anyone miss it if it went away? Aslak
2019 Jun 18
3
Retiring VS2015 Support
AFAICT we traditionally only support building llvm/clang with the 2 most recent releases of Visual Studio. With the release of VS2019, what do people think of retiring VS2015 support before the next major llvm/clang release? As well as simplifying C++14 migration (admittedly only a little), this should also let us remove a number of hacks (e.g. the alignas/AlignedCharArray hack in
2021 Mar 13
1
On retiring some terminology
On 3/12/21 9:14 PM, Rusty Bower wrote: > Manager/subscriber seems most accurate > > Sent from my iPhone > >> On Mar 12, 2021, at 20:13, Douglas Parsons <doug at parsonsemail.com> wrote: >> >> ? >> In place of secondary how about subscriber? It would be accurate to >> the role. I'd been going to suggest controller and ... something.
2021 Mar 13
1
On retiring some terminology
On 3/12/21 9:14 PM, Rusty Bower wrote: > Manager/subscriber seems most accurate > > Sent from my iPhone > >> On Mar 12, 2021, at 20:13, Douglas Parsons <doug at parsonsemail.com> wrote: >> >> ? >> In place of secondary how about subscriber? It would be accurate to >> the role. I'd been going to suggest controller and ... something.
2023 Jan 20
1
[fdo] Retiring the GitHub mirrors
Hello everyone, For many years now, we have maintained mirrors of numerous FDo projects on GitHub, under the following organisations: https://github.com/freedesktop https://github.com/mesa3d https://github.com/wayland-project A bit over a month ago, a new security feature in git started preventing our script from updating these repos, which wasn't noticed right away due to people being on
2021 Mar 13
1
[EXTERNAL] Re: On retiring some terminology
Jim, The terminology I recall for that one-to-many relationship is publisher-subscriber. Larry Baker US Geological Survey 650-329-5608 baker at usgs.gov<mailto:baker at usgs.gov> On Mar 12 2021, at 6:24:38 PM, Phil Stracchino via Nut-upsuser <nut-upsuser at alioth-lists.debian.net<mailto:nut-upsuser at alioth-lists.debian.net>> wrote: This email has been received from
2021 Mar 13
1
[EXTERNAL] Re: On retiring some terminology
Jim, The terminology I recall for that one-to-many relationship is publisher-subscriber. Larry Baker US Geological Survey 650-329-5608 baker at usgs.gov<mailto:baker at usgs.gov> On Mar 12 2021, at 6:24:38 PM, Phil Stracchino via Nut-upsuser <nut-upsuser at alioth-lists.debian.net<mailto:nut-upsuser at alioth-lists.debian.net>> wrote: This email has been received from
2021 Mar 12
2
On retiring some terminology
Hello fellow NUTs :) Some time ago an issue https://github.com/networkupstools/nut/issues/840 was raised, and with current work underway to publish a standard on NUT protocol it became more urgent - to retire the master/slave terminology from NUT configuration and documentation. I looked around for suitable synonyms, and for our primary use-case with upsmon roles - where it either manages an
2021 Mar 12
2
On retiring some terminology
Hello fellow NUTs :) Some time ago an issue https://github.com/networkupstools/nut/issues/840 was raised, and with current work underway to publish a standard on NUT protocol it became more urgent - to retire the master/slave terminology from NUT configuration and documentation. I looked around for suitable synonyms, and for our primary use-case with upsmon roles - where it either manages an