text:
Talk:Dylan and Cole Sprouse

Date format in citations
Yesterday I aligned as many citations as I could with YYYY-MM-DD (ISO 8601/international all-numeric, basically) format since that seemed to be the style most dates on citations were using save some newer ones. I was doing this manually (and was sick) so I stopped to take a break without completing the job and ended up not coming back to it yesterday. This morning (last night? ...early March 29 UTC), Joeyconnick converted all the dates in citations to MMMM DD, YYYY (i.e. March 29, 2018, the format commonly used in the US) via a script. I don't think either date format has special merit over the other, but I felt the change warranted discussion. (I'm personally in support of YYYY-MM-DD, largely because the article ended up almost entirely consistent in that date format first and I don't think "some dates are still inconsistent" was a good enough reason to switch all the otherwise consistent dates to the format of the few that weren't consistent with them.) Does anyone care one way or the other? - Purplewowies (talk) 16:09, 29 March 2018 (UTC)
 * Basically the reasoning is MOS:TIES... articles about American subjects (like TV and film in addition to actors) use American spelling so in the case of inconsistencies, it seems reasonable to default to mdy, which is the "American" date format. I did go back to the version of the page before started standardizing on ymd... there was a real mix of dates, including ones in dmy, and mixes within citations between dates and access dates. I would argue yyyy-mm-dd is less easily "human readable" than dmy or mdy and we should be making choices that make it easier for readers to parse articles. Finally, if  was going to revert so we could have a discussion, they should have reverted to the version before their own date changes given those were just as bold as mine were. —Joeyconnick (talk) 16:50, 29 March 2018 (UTC)
 * ...Fair, regarding which version to revert to. I didn't realize MOS:TIES (or for an even more specific link, MOS:DATETIES) applied here (my understanding of it was rusty) so I was working from something more like MOS:DATEVAR. I suppose given that information I'll withdraw my own dispute here. (Part of me is a little curious as to others' thoughts on the subject, but... *shrug*) - Purplewowies (talk) 19:28, 29 March 2018 (UTC)
 * Oh... I had forgotten about MOS:DATETIES. That is a bit more relevant. Yes, there is WP:CITEVAR, so no one should be wholescale changing the format if it's already consistent, so I guess when it's not it just comes down to do you go with the format most-used or something like MOS:DATETIES. Which is subjective and not governed by a specific guideline (that I know of). I do appreciate that yyyy-mm-dd is the least ambiguous in terms of numeric formats. I'm Canadian, so we deal with a variety of formats, but mdy tends to predominate as far as "written-out"/prose formats, whereas dd-mm-yyyy tends to predominate over the more American mm-dd-yyyy in terms of numeric ones. I could live with this article either way (mdy prose or yyyy-mm-dd numeric)—I just saw you were going in chunks and I was like, "Oh I know a script for that!" and then I thought about whether the numeric format was the right choice. I appreciate you being cordial and willing to discuss; if a bunch of people chime in and want yyyy-mm-dd, I will be similarly reasonable and let my objections go. —Joeyconnick (talk) 19:50, 29 March 2018 (UTC)

MOS:BOLDAVOID and their individual articles
The MOS is a guideline and not policy, but I figured I'd bring this up. I've reverted linkings of the names of the two in the first sentence with the rationale that it's not in line with MOS:BOLDAVOID (and that there's a note just above the first sentence that links each name already) but I'm not 100% on what's the best course of action, now that I think about it. I see the utility in linking it there, so... *awkward shrugging* I think there are probably about three different ways to deal with this:

 * 1) Link the bold. (Because BOLDAVOID is a guideline and there will always be exceptions)
 * 2) Leave the links where they are in the third paragraph. (Status quo, in line with BOLDAVOID)
 * 3) Rephrase some early part of the lede to allow the names to be linked closer to the start of the article. (In line with BOLDAVOID but still changes link location)

I have a weird related question, as to whether the rephrasing of their names is technically in line with MOS:TITLEABSENTBOLD. (It... probably is in line. I'm just tired and my brain is fried.) Strangely, if it isn't, that introduces a fourth option of unbolding the names and linking the first instances. I dunno. I'm confused. Thoughts? - Purplewowies (talk) 17:58, 7 September 2018 (UTC)
 * Given the way the first line is currently worded (with their full names, which may well be unnecessary in the lead), those names should not be bolded as per MOS:BOLDAVOID since the first sentence does not then include "Dylan and Cole Sprouse". So you could easily have:
 * Dylan Thomas Sprouse and Cole Mitchell Sprouse (born August 4, 1992) are American actors.
 * Although honestly given the whole genesis of them having a shared article, I would probably change it to:
 * Dylan Thomas Sprouse and Cole Mitchell Sprouse (born August 4, 1992) are identical twin American actors [or "are American actors who are identical twins"].
 * The whole reason they have a shared page is their twin-ness (twin-ity?), so it probably should be mentioned right up front. —Joeyconnick (talk) 18:48, 7 September 2018 (UTC)
 * "Identical" was left out because consensus (eight years ago) was that no one (even them) had a consistent and sure answer as to whether they were identical or fraternal (I haven't checked to see if anything has changed), but all good points. I think BOLDAVOID is just about linking in the bolded part of the lede, though, and the bolding of the names is TITLEABSENTBOLD. It feels like it could go either way, because every other person's full name is mentioned and bolded in their article, so theoretically it shouldn't be different... but somehow it feels like it departs from the titling of the article more than a single person's full name would? I don't know. - Purplewowies (talk) 23:02, 7 September 2018 (UTC)
 * They're not identical?! Weird! I feel like they were certainly treated as identical. This isn't a normal bio article, though, so their full names don't have to be in the lead nor do they have to be bolded. The article title is "Dylan and Cole Sprouse" but it's essentially at this point "Dylan and Cole Sprouse's shared child actor career(s)" really. I say we either reword and start with the title and have that bolded as per normal, but not linked (as per MOS:BOLDAVOID), and leave their next mentions linked to the individual articles (whether that gets moved up or not is not really a huge deal, as long as it's in the lead) or we unbold the current wording but link to their respective articles. We could also rework the opening in that case so it reads/looks less like a biographical article i.e. remove the "(born August 4, 1992)" bit since this info could be included later and is already in the infobox.
 * It's also possible this article should just be merged into their separate articles and otherwise go the way of the do-do. I realize that wasn't the consensus around a year ago, though, which gives further ammunition to the notion this article is not a typical biographical article, but rather an article about the shared portion of their careers, and that that the title is just a convenient shorthand.
 * So something like:
 * Dylan and Cole Sprouse are twin American actors who, as children, rose to prominence and acted together in nearly all of their early projects. Often referred to as the Sprouse Brothers or the Sprouse Bros., their first major theatrical film role was in the 1999 comedy, Big Daddy, in which they co-starred with Adam Sandler.
 * could work. —Joeyconnick (talk) 01:31, 8 September 2018 (UTC)

Riverdale
Hi, i noticed Riverdale is not listed in his work? — Preceding unsigned comment added by 98.20.92.126 (talk) 21:03, 8 February 2019 (UTC)
 * Hi, 98.20.92.126. That's not included here because this article is about the period of their career in which they were frequently sharing roles. Cole Sprouse, a page just about Cole, does in fact list his work on Riverdale. - Purplewowies (talk) 22:37, 8 February 2019 (UTC)

merging of this page with their respective pages.
Hello everyone. I would like to clarify a doubt here. Has there been any discussion prior to this regarding the existence of the aforementioned actors' individual pages? This doubt has arisen in me due to the fact that the information given here seems to be somewhat similar to that of their individual pages. Please do clarify my query.

Thanking you in advance. 2409:4071:D9E:3A06:C807:CF00:1AF8:D622 (talk) 17:17, 9 March 2021 (UTC)

Correction: 2409:4071:D9E:3A06:C807:CF00:1AF8:D622 is me, TSK201911 (talk). Sorry for the mistake, for I had forgotten to sign in. TSK201911 (talk) 17:22, 9 March 2021 (UTC)
 * Take a look at Talk:Dylan and Cole Sprouse/Archive 1; there was consensus to split their separate activities into individual articles for the two of them in 2017, and there is some duplicated content to those articles in the interest of summarizing their early lives and shared career just a tad before explaining their separate careers. (I think this was done so the article didn't just abruptly start in, like, 2017 with no explanation of anything that occurred prior.) But yes, there has been discussion before about separate versus shared pages, and it is currently deliberate and in line with consensus that both of them exist. - Purplewowies (talk) 00:37, 13 March 2021 (UTC)

title: Talk:Dylan and Cole Sprouse


text:
Talk:Package management system

Mac OS X installer needs mentioning!
Mac OS X does have some package management functionality (an installer and a software update utility), which should be included here. - User:Samsara (talk • contribs) 13:04, 15 March 2006 (UTC)

Related tools
RPM is often used by another tool for handling dependencies, such as the Yellow Dog Updater Modified (yum) or the RPM-based version of the Advanced Packaging Tool (apt).

Some other package managers are
 * dpkg used with Advanced Packaging Tool (apt) in Debian GNU/Linux
 * portage used with emerge in Gentoo Linux
 * Encap Package Management System
 * cygcheck used in Cygwin

The following tools are simply front ends to RPM-based systems:
 * YaST used in SuSE
 * urpmi used in Mandriva Linux
 * yum used in Yellow Dog Linux and Fedora Core.

In addition, the advanced dependency-management system in APT has been ported to work on RPM databases as apt4rpm.

See also: Archive formats

- User:Samsara (talk • contribs) 18:44, 25 April 2006 (UTC)

Suggested merge of Package management system and Installer
Mostly I am suggesting the merge to force a clarification of what each article is about. Some of the material in Installer belongs in this article, and some material that clearly belongs in Installer is simply absent. klik would be an example of an installer mentioned in the PMS article. - User:Samsara (talk • contribs) 20:59, 4 May 2006 (UTC)

Installer != Package Management System
These two pages should not be merged. A package management system does install programs, but it also checks dependencies and installs those which are required by the program being installed, according to the preferences and command line choices made by the installing user. Most installers, on the other hand, assume that the user's system already has the required libraries or programs the program being installed requires. This is especially true in the case of Windows installers. Some well-written installers do check, usually exiting if the libraries are not found, but most will only mention what is needed. But the inclusion of the functions of checking dependencies and downloading required libraries would, in my opinion, make an installer into a package management system. It might be argued that this makes a package management system a subset of installers, but I think they should still have separate entries to avoid confusion.

 * If you'd written that as a clarification on a merged page, it would be more useful. Not that it was news to me... And, following your proposed definition, it would seem that several examples are currently misclassified. - User:Samsara (talk • contribs) 20:36, 9 May 2006 (UTC)

 * I'd have to agree with the Installer != PMS. Here is my reasoning, let's see if it's bad.  When I think installer, I think of a self contained EXE file that I can download and double-click, which will run it's included executable to move files from the executable into the directories where they need to be.  An installer contains not only the program, but all support libraries as well.  The installer checks to see if you have the support libraries installed, if not, it installs those libraries.  A Package Management System, however, is separate from the actual program being installed.  (My experience is with emerge from Gentoo and apt-get from Debian)  You use the PMS system's program to download a separate package, then follow the instructions in that separate package to install that package.  Should that package need support libraries, the PMS can download those as well;  however, the program being installed DOES NOT contain it's own copies of the libraries like a Win installer.  It depends on the PMS to get those for it.

 * So, in summary, to ME, a Installer is a program that contains within itself the program to be installed and it's support libraries. In contrast, a PMS is a Utility that gets the program to be installed as a completely separate file, and can retrieve any libraries the program to be installed needs as completely separate files.  The difference is between WinampInstall.exe and apt-get(+x) + XMMS.deb + Mp3.deb + ... Autodmc 16:42, 25 May 2006 (UTC)

 * I didn't want to get dinged for not providing sources for my statements. And I didn't have time when I made the comment to properly research it. Skreyola (talk) 04:26, 4 January 2008 (UTC)

 * Agreed. Installers are mostly stand-alone, I-don't-care-about-other-software programs. Package management systems handle installers, dependencies, etc. æle ✆ 2006-05-27t14:13z

 * Installers are mostly
 * Guys, can we have clear definitions, please?! - User:Samsara (talk • contribs) 20:25, 27 May 2006 (UTC)

 * I'm trying not to generalize, because some programs blur the line a little bit (see the Cygwin installer; it also manages Cygwin packages). æle ✆ 2006-05-28t02:19z

 * If this page is to be just a list, it should be so renamed or nominated for deletion. I think it would be a shame, because there actually are general principles to discuss here that haven't yet been touched on. - User:Samsara (talk • contribs) 08:59, 28 May 2006 (UTC)

 * Gah, I was writing that late last night. I meant "generalize too much", in the sense that there're always exceptions to any rule. æle ✆ 2006-05-28t13:02z

Comparison of package management systems
I think it would be nice to have a comparison table that outlines features of various package management systems. —The preceding unsigned comment was added by Kc8tpz (talk • contribs) 20:32, 22 January 2007 (UTC).

This is a cool idea. One issue is redundant information. Each portal wants its own specific information, e.g., the Linux portal doesn't want to see everything about Windows and Mac managers. Also, the grouping is a bit odd. The core fields would include name, platform, package formats managed, what package managers are 'under the hood' and a list of features: GUI, command line, creating packages, managing multiple machines, and so on.--Charles Merriam (talk) 21:21, 27 December 2007 (UTC)

Windows PMS

 * 1) [...] whereas the PMS of Mac OS X and Windows will only upgrade software provided by Apple and Microsoft, respectively [...]
 * What, if any exists, is the official Windows PMS? --Abdull 09:39, 5 July 2007 (UTC)
 * Windows does not, to my knowledge, have anything resembling a PMS, because Windows is designed on a single-user model, and PMSs are generally found in multi-user platforms. MacOS is an exception. Skreyola (talk) 04:22, 4 January 2008 (UTC)
 * 1) Appsnap link comment edit Gert4gt (talk) 02:22, 18 November 2007 (UTC) someone can add that back in if they can add a link to backup the "most advanced" claim. I couldn't find anything to back that up. Sorry.
 * 2) Regarding the linkfarm template in the Windows section:
 * As I note in a comment, since none of these are official systems bundled with Windows, people might not be familiar with them, and since individual software is not necessarily likely to have a Wiki page, linking to them directly does not seem unreasonable. All of these links seem appropriate to the article. I recommend removal of the linkfarm template. Skreyola (talk) 05:46, 4 January 2008 (UTC)

diagram
What does the diagram achieve that a numbered list (inline with the text) wouldn't? Is it meant to imply a cycle? Also, the "typical" manual action of requesting a reboot, is quite atypical except on Windows. (That example just perpetuates the myth that it's normal for computers to need to get rebooted every time some dumb screen saver is installed). —Fleminra 23:43, 10 October 2007 (UTC)

I agree. A screenshot of a GUI package manager, like Synaptic, might do better at conveying the core idea. --Charles Merriam (talk) 21:15, 27 December 2007 (UTC)

How about a screenshot of aptitude? (Sorry, I don't have Synaptic installed at the moment). Skreyola (talk) 05:55, 4 January 2008 (UTC)
 * Please, don't shrink it, there is no sense in unreadable text-mode screenshot --pavel.

I would like for someone to explain to me what magical advance in software engineering Linux made that reboots are not necessary after you've just overwritten half a dozen shared libraries, while running processes are using them. It is not a myth, and unless you can point out some magic I'm not aware of, you DO have to reboot a Linux system after updates to ensure a consistent state. I'm sick and tired of Linux getting credit for these incredible feats of engineering when all you do is shrug something off. Linux will someday wind up with a system similar to either Windows (files overwritten at reboot) or OpenSolaris IPS (updates installed to filesystem snapshot, snapshot promoted at next reboot) to provide consistency, and all the Linux community will do is pretend it was never an issue. Patching Solaris, Windows and other commercial systems is a little trickier than Linux, but stop pretending your Linux system does anything more advanced than blindly overwrite files. Face the issues, or you'll be left behind. Linux isn't perfect. -SMJ —Preceding unsigned comment added by 216.136.25.72 (talk) 02:21, 8 July 2008 (UTC)
 * As I understand it, it's because of the way Linux executables use libraries. You don't normally have to reboot the whole system, just the processes that use the updated libraries, and that only if those processes are going to keep running indefinitely. Linux isn't flawless, and I don't know anyone who says it is. But to pretend that Linux is not a stable system that can run for months without rebooting is silly. I only reboot my server when I install a new kernel or change hardware. But this is probably not the right place for such a discussion. Skreyola (talk) 16:31, 21 September 2010 (UTC)
 * That opinion was said more than two years ago, I think that article has already reflected the facts you're basing your point of view upon. 1exec1 (talk) 16:07, 22 September 2010 (UTC)

A cloud of articles
I spent some time cleaning up, and possibly making some sections worse. :).  There seems to be an odd cloud of related pages of varying quality, from the individual package managers, installers, and general terms like software distribution.  What would be a good 'master' article that talks about the whole system administration of installed software that can put all this in perspective to a person with only a general understanding of computers.  It just feels like the cloud is wrong.  Any ideas?--Charles Merriam (talk) 21:25, 27 December 2007 (UTC)

More sections: History; How does it works.
Does anyone know the history? It probably makes a difference.

Also, we should have some sort of How Does It Work section and diagram. The diagram might have the software repository, package manager, internals of a package, the local package database, and some directories. Showing how a user contacts a repository, selects a package from the description, gets prompted to download dependencies, downloads to local machine, unpacks into local directories, and updates the local package database might be good. Hmmm..... --Charles Merriam (talk) 21:35, 27 December 2007 (UTC)

Not an essay any more...
I looked at this, and think it doesn't look like an essay anymore. Still needs a history, and an "example of how it does it" section.

The reference updates
Hello - I've upgraded the formatting of the references. This includes verifying that the links are still active. Sometimes over time they become dead links. Standard reference syntax has the "retrieved on" date as the original viewing date. My changes have that date as the most current viewing date. This helps Wikipedia editors see, at a glance, when that page was last verified as active. E_dog95'  Hi ' 14:23, 7 April 2008 (UTC)

The Terminology table
Terms on the table are wrong. None of the Linux or *BSD package manager systems belongs to operating system. They are just like normal applications running top of operating system. The article information is wrong and is mistaken by typical conclusion and not for computer science. The package management system is just a set of tools and can be removed totally if wanted, it just comes preinstalled on software system and belongs usually to system programs -level, what is top of OS -level. This might not be the case of Windows NT, where even the browser was/is part of OS because it is integrated to it, so the package management system might be part of OS. Golftheman (talk) 11:55, 1 December 2008 (UTC)

You are right, it is just software. For instance, Gentoo is known for portage, but portage can also be used on Macs. Sockigami (talk) 19:31, 14 February 2009 (UTC)

Package management system versus package manager
I know the difference between an installer and a package management system; this does not concern that. But at the top of the article it says "a package management system is sometimes incorrectly referred to as a package manager or a system install manager." A package management system and a package manager are the same thing. RPM is called the "RPM Package Manager," and is a package management system. I'm taking the part that says it's incorrectly referred to as a package manager out. Sockigami (talk) 19:28, 14 February 2009 (UTC)

Recent revert
This edit made the article internally inconsistent, using the terms "Linux" and "GNU/Linux" interchangeably. This is confusing; we should use one or the other. It should be reverted. Chris Cunningham (not at work) - talk 18:19, 2 March 2009 (UTC)

Article name
Why does this not live at package manager? —Wiki Wikardo 19:38, 23 February 2010 (UTC)

WPM (Windows Package Manager)
please consider adding a link to http://code.google.com/p/windows-package-manager/ 62.153.127.78 (talk) 10:56, 8 July 2010 (UTC)

GNU Stow
Any reason why this has it's own special link in See Also and can it be removed to List of software package management systems, perhaps the Linux distributions section? Teh klev (talk) 14:03, 10 November 2010 (UTC)

Ian Murdock about package management
In 2006, he said it sucked, but hopefully not for much longer. His recent blog post where the "Impact" article section was taken from stated his reasoning for thinking it was a lot better now was that:
 * These days, you increasingly just “apt-get install whatever“.

Debian-based distros coming to be used more is good for standards? That's not a solution or standard, that's everyone choosing one thing. Package management still sucks in that there still isn't integration with software management systems for "third-party programs" essentially, and ISVs are still facing the exact same problem of needing to support many distros. This latest blog post of his didn't address any of the problems and points he made in those two earlier posts. Thus, I think his earlier comments about package management sucking on Linux should also be noted, or that "Impact" section completely removed. I also think a section on fragmentation and a lack of packaging standards (especially between Linux distros) is needed. Yfrwlf (talk) 01:03, 2 January 2011 (UTC)
 * Personal POV has no place in Wikipedia. 1) Package management still sucks in that there still isn't integration with software management systems for "third-party programs" - Bullshit. Noone (including Google, Oracle, Skype to name a few) has any difficulties packaging their software for Linux distributions. 2) fragmentation - According to this report more than 60-65% of desktop Linux users use Ubuntu + Debian distributions (which in turn use deb package format) and additional 10-15% use Fedora + SUSE (rpm package format). I don't see fragmentation issues here. 3) lack of packaging standards - are you living in the previous century? Making deb and rpm packages already covers more than 99% of Linux market. 1exec1 (talk) 16:04, 4 January 2011 (UTC)

You could add the comments by Tony Mobily about how software installation on GNU/Linux is still broken. Yfrwlf (talk) 01:31, 2 January 2011 (UTC)

Merger proposal with Application Packaging
Isn't Application Packaging covered under Package management system? If so, I propose a merge. A redirect could be more appropriate, if all the content is already covered here. -- Trevj (talk) 11:53, 25 November 2011 (UTC)

 * I'd say no, although from the article it's quite unclear what Application Packaging is supposed to cover (it includes Installers and some Systems/configuration management software I'm not familiar with). It seems to be wider in scope than what are traditionally considered package management systems. Perhaps Software package (installation) would be a better target? Or maybe it could be developed into a proper stand-alone article? —Ruud 12:44, 25 November 2011 (UTC)

 * Yes, package management systems are more specific. Some further thoughts:
 * "Application packaging" means building an installer. I suggest merging it to the more general article Installation (computer programs).
 * It's kind of strange Installer isn't an article.
 * The second list in Application Packaging are tools for managing deployment of packaged applications. Contrary to what the lead sentence says, managing deployment is related to application packaging, not part of it.
 * Software package (installation) is about packages in package management systems.
 * --Pnm (talk) 19:33, 25 November 2011 (UTC)

I don't agree with a merge, as an application package may or may not integrate with a package managment system. (eg. klik, RUNZ) --SF007 (talk) 05:05, 15 January 2012 (UTC)

*System*
What is this here, and what is not the relationship to SCCM (its software distribution module)? --Alien4 (talk) 12:17, 16 May 2014 (UTC)

 * Hello there! Well, "package management system" is pretty much a general term, while SCCM—I suppose—contains a Microsoft's specific implementation of such a concept. — Dsimic (talk | contribs) 02:31, 19 May 2014 (UTC)

 * So you would say, there is a connection between the two, but no obvious relationship (intrawikilinking or so) between them in the Wikipedia? There are tons of mentionings of *nx, whereas Windows just a few. Or maybe I'm confusing something; although I maybe rather would consider msi a package management technology, it is mentioned here, whereas a software (package) managment *system* like SCCM is not. Or maybe I'm just too completely confused. --Alien4 (talk) 14:59, 19 May 2014 (UTC)

 * I'm completely unfamiliar with SCCM so unfortunately I can't draw any conclusions, but I'd say that SCCM might fit better into the Systems management article, while SCCM's specific components might be mentioned in Software repository article. — Dsimic (talk | contribs) 06:47, 20 May 2014 (UTC)

 * With SCCM you can do software deployment (or software distribution, whichever expression you like best), and you can do that also with msi, App-V packages or others. In other organisations it might be different, but I know it best as that beeing the main functionality of SCCM. Which leads me to conclusion, although it does system management - S stands for "System", (CC), M stands for "Manager" - and personally I might maybe rather regard a combination of SCCM with a version control system like ClearCase as a software repository (maybe i confuse that with a Definitive Media Library), a software (package) deployment/distribution (system) (module) seems to be a lot like a "package management system" to me. But then again, do I understand the package management system article right? You know, stuff like dependencies - expressis verbis in the article introduction - is stuff you can (also) do in SCCM, although they might be more high level dependencies: if you want to install an Office plugin, MS Office must be installed, but you don't put the dependend MS Office in the plugin msi; it might be a good idea however to define that dependency in SCCM. --Alien4 (talk) 10:34, 20 May 2014 (UTC)

 * Hm, can SCCM automatically handle dependencies and install required packages? For example, when you try to install a software package which requires Visual C++'s redistributable runtime, is SCCM going to locate and install that runtime package despite the fact it isn't contained within the original software package? — Dsimic (talk | contribs) 06:42, 21 May 2014 (UTC)

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/

title: Talk:Package management system


text:
Barebone computer

A barebone computer is a partially assembled platform or an unassembled kit of computer parts allowing more customization and lower costs than a retail computer system. They are available for desktop computer, notebook (see barebook) and server purposes, and in nearly any form factor. Manufacturers are also able to produce systems of a specialized or non-standard form factor, since the system is sold as a pre-built unit, with the motherboard and power supply already installed.

Components
Assembling a barebone computer by hand is usually less expensive than buying a pre-configured computer from a retailer, and may save time and labor compared with building a system from scratch. A typical barebone desktop system consists of a CPU, a computer case (or tower), with a pre-fitted motherboard and power supply. If not already provided, the purchaser of such a platform only has to equip it with a RAM, and optionally a hard drive (in some cases, an operating system is/can be installed to a lower-cost flash drive instead). Additional input/output devices may be required depending on their needs. Sometimes, it is necessary to install an operating system if the one built into the motherboard is deemed insufficient (or not present at all). An audio adapter or network adapter may be added but this is less common as recent motherboards often already contain capable solutions.

Peripherals, such as a keyboard, mouse and monitor, almost always must be acquired separately. Barebone systems sometimes include a graphics processor or RAM, but rarely any mass storage media (hard drives), operating system or other software. Sometimes PCs with everything a normal desktop PC has except Microsoft Windows operating systems are sold as a barebone computer, but may include free software such as Linux. Refurbished and used computers may also be repackaged as barebone computers, as many computers returned for refurbishing may have missing, broken, or obsolete parts such as hard drives and peripherals.

Barebook
A barebook computer (or barebone laptop) is an incomplete notebook PC. A barebone laptop is similar to a barebone computer, but in a laptop form.

As it leaves the factory, it contains only elements strictly tied to the computer's design (case, motherboard, display, keyboard, pointing device, etc.), and the consumer or reseller has to add standardized off-the-shelf components such as CPU and GPU (when not integrated on the motherboard), memory, mass storage, WiFi card, etc. separately.

Because it is not manufactured with storage media such as harddisks or SSDs, a barebook does not typically include an operating system, which may make barebooks appealing to opposers of the bundling of Microsoft Windows.

Upgrade limitations
Future upgradeability of a barebone system may be limited, especially the motherboard component, which may have less space for extra I/O devices and fewer memory and PCI card slots than desired. The motherboard may not be compatible with faster processors and memory than those originally purchased with the barebone system. Barebones may also have limit on the maximal processor thermal design power (TDP) and not be able to support CPUs that would otherwise fit into the socket.

Manufacturers
The following companies currently manufacture barebone computers:
 * Acer Inc.
 * Advantech
 * ASUSTeK Computer Inc.
 * Biostar
 * Gigabyte Technology Co. Ltd.
 * Intel
 * Micro-Star International (MSI)
 * Shuttle Inc.
 * Supermicro (servers)
 * Systemax/Tiger Direct
 * ZOTAC

title: Barebone computer


text:
User:FRS

Welcome to my User Page v.2.1.01

About Me
Occupation: Former Rocket Scientist (FRS, get it?)

Interests: Engineering, science, law, politics and history

Nationality: US

Languages: American, but I can understand English, if you type slow enough; also, I can usually make out menus and specs in French and Russian

Age, race, gender, religion, marital status, sexual preference: Decline to state

Residence: US, but have spent time in Australia, Austria, Belgium, Canada, Denmark, England, France, Germany, Greece, India, Italy, Japan, Mexico (well, Cancún), Netherlands, Poland, Russia, Singapore, Spain, Saint Kitts and Nevis, Switzerland, Thailand and Vatican City

Pronoun preferred to be used when discussing me in the third person: he/him/his

Current Wiki Projects
Finding and correcting PoV problems

For example: | Human Radiation Experiments, | Ayat al-Akhras, |G.W. Bush & H. Katrina

Pet Peeves
My user page look much worse than practially every other one I've seen

Useful Links
(thanks to User:Pmanderson)
 * []
 * NPOV_disputes
 * Tutorial
 * Help desk
 * Policy Library
 * Utilities
 * Cite your sources
 * Verifiability
 * Wikiquette
 * Civility
 * Conflict resolution
 * Use English
 * Neutral point of view
 * Pages needing attention
 * Peer review
 * Boilerplate text
 * Articles for Deletion
 * WP:NOT
 * Don't disrupt Wikipedia to illustrate a point

User:FRS/monobook.js
 * kate's tool

Commentary
I may make some additional comments about my edits here from time to time that don't seem appropriate to link inextricably to the edited page.

Initial Itinerary
This is my initial transit through WP (reverse chronological order): Irving Langmuir Plasma (physics) solar wind Current (electricity) Steinhart-Hart equation Van der Pauw method Hall effect Hall effect thruster

Then I realized that the physics pages were too well written and NPOV (aka BOOOORRRRING) to spend much time in

Contributions
My Contributions

title: User:FRS


text:
Wikipedia:Collaboration of the week/Armenian literature

Armenian literature

 * Nominated on 16:20, 12 October 2005 (UTC); needs 3 votes by October 19.

Nothing at all. Not even a Category:Armenian literature. One of the few blanks left at Literature. I'll try to add a short stub, but this definitely needs something more to it.

Support:
 * 1) BRIAN 0918  • 2005-10-12 16:20
 * 2) Gareth Hughes 14:15, 13 October 2005 (UTC)
 * 3) GhostGirl 01:53, 15 October 2005 (UTC)
 * 4) --Revolución (talk) 20:18, 24 October 2005 (UTC)
 * 5) -- Rune Welsh | ταλκ |  Esperanza  20:36, 24 October 2005 (UTC)
 * 6) Darwinek 17:06, 25 October 2005 (UTC)


text:
Nuclear-weapon-free zone

[[File:nwfz.svg|thumb|400px|

]]

A nuclear-weapon-free zone (NWFZ) is defined by the United Nations as an agreement that a group of states has freely established by treaty or convention that bans the development, manufacturing, control, possession, testing, stationing or transporting of nuclear weapons in a given area, that has mechanisms of verification and control to enforce its obligations, and that is recognized as such by the General Assembly of the United Nations. NWFZs have a similar purpose to, but are distinct from, the Treaty on the Non-Proliferation of Nuclear Weapons to which most countries including five nuclear weapons states are a party. Another term, nuclear-free zone, often means an area that has banned both nuclear power and nuclear weapons, and sometimes nuclear waste and nuclear propulsion, and usually does not mean a UN-acknowledged international treaty.

The NWFZ definition does not count countries or smaller regions that have outlawed nuclear weapons simply by their own law, like Austria with the Atomsperrgesetz in 1999. Similarly the 2+4 Treaty, which led to German reunification, banned nuclear weapons in the new states of Germany (Berlin and former East Germany), but was an agreement only among the six signatory countries, without formal NWFZ mechanisms.

Geographic scope
Today there are five zones covering continental or subcontinental groups of countries (including their territorial waters and airspace), and three governing Antarctica, the seabed, and outer space which are not part of any state. The Antarctic, seabed, and space zones preceded all but one of the zones on national territories. Most of the Earth's oceans above the seabed are not covered by NWFZs since freedom of the seas restricts restrictions in international waters. The UN has also recognized one additional country, Mongolia, as having nuclear-weapon-free status.

NWFZs do not cover international waters (where there is freedom of the seas) or transit of nuclear missiles through space (as opposed to deployment of nuclear weapons in space).

when the African NWFZ came into force, the six land zones cover 56% of the Earth's land area of 149 million square kilometers and 60% of the 195 states on Earth, up from 34% and 30% the previous year; however, only 39% of the world's population lives in NWFZs, while the nine nuclear weapons states have 28% of the world's land area and 46% of the world population.

The Antarctic, Latin American, and South Pacific zones are defined by lines of latitude and longitude, except for the northwestern boundary of the South Pacific zone which follows the limit of Australian territorial waters, and these three zones form a contiguous area, though treaty provisions do not apply to international waters within that area. In contrast, the Southeast Asian zone is defined as the territories of its members including their Exclusive Economic Zones, and the African zone is also defined as the countries and territories considered part of Africa by the OAU (now the African Union) which include islands close to Africa and Madagascar. An AU member, Mauritius, claims the British Indian Ocean Territory where Diego Garcia is currently a US military base.

Nuclear power in NWFZ states
Four NWFZ countries have nuclear plants to generate electricity. South Africa formerly had a nuclear weapons program which it terminated in 1989.

Argentina and Brazil are known to operate uranium enrichment facilities. Countries that had enrichment programs in the past include Libya and South Africa, although Libya's facility was never operational. Australia has announced its intention to pursue commercial enrichment, and is actively researching laser enrichment.

Argentina and Brazil also have plans to build nuclear submarines.

Protocols for non-member states
Several of the NWFZ treaties have protocols under which states outside the zone that have territories within the zone can bring the provisions of the NWFZ into force for those territories. All these territories are small islands except for French Guiana. The United States has signed but not ratified Protocol I to the Treaty of Rarotonga which would apply to American Samoa and Jarvis Island. The United Kingdom does not accept that African NWFZ is applicable to the Indian Ocean island of Diego Garcia which has a U.S. military base.

Southern Hemisphere
Few prevailing winds cross the Equator and effects of nuclear explosions in the Northern Hemisphere might send less fallout to the Southern Hemisphere.

The five southern NWFZs together cover all land in the Southern Hemisphere except East Timor, still in the process of joining ASEAN, and Atlantic and Indian Ocean islands belonging to non-NWFZ countries in the box (map) bounded by 60° S, 20° W, and 115° E, which combined have less than 8000 km2 of land area:
 * St. Helena and its dependencies Ascension Island and Tristan da Cunha, a British overseas territory
 * Bouvet Island, a Norwegian territory
 * Kerguelen, Crozet, Saint Paul and Amsterdam Islands, some of the French Southern Territories
 * Chagos Islands (British Indian Ocean Territory) including Diego Garcia (disputed by Mauritius)
 * Addu and Fuvahmulah, southernmost atolls of the Maldives

In 1994 states of the South Atlantic Peace and Cooperation Zone issued a "Declaration on the Denuclearization of the South Atlantic" which the U.N. General Assembly endorsed but the U.S., U.K., and France still opposed.

Tropics
The Latin American, African, South Pacific and Southeast Asian zones also cover most land in the tropics, but not some Northern Hemisphere areas south of the Tropic of Cancer. Most tropical land outside of NWFZs is in India and the Arabian Peninsula.

Little of the land area covered by the five southern Nuclear-Weapon-Free Zones extends north of the Tropic of Cancer: only northern Mexico, northern Bahamas, northern Myanmar, and North Africa. However, the Central Asian and Mongolian zones are entirely in the North Temperate Zone.

Northern Hemisphere
The majority of non-NWS non-NWFZ states are in Europe and the North Pacific and are members of (or surrounded by) collective security alliances with nuclear weapons states dating from the Cold War and predating the NWFZ movement.

Twenty-two states are not part of a NWFZ or a collective security bloc nor nuclear weapons states, twelve in the Middle East, six in South Asia, and four in the former Soviet Union. There have been NWFZ proposals for the Middle East (e.g. Nuclear program of Iran, 2009 UN proposal, 2011 IAEA forum ), the Korean Peninsula, Central Europe, South Asia, South-east Asia, and the Arctic.

All countries without nuclear weapons, except South Sudan, are parties to the Non-Proliferation Treaty, as are the five NPT-sanctioned nuclear weapon states.

Europe
The UK, France, and the USA share a nuclear umbrella with the 29 other members of NATO, and the four European Union states not part of NATO (Austria, Cyprus, Ireland, Malta) are part of the EU's Common Security and Defence Policy.

The other European countries west of the former Soviet Union are small Western European states and surrounded by and aligned with the EU and NATO but not members (Switzerland and European microstates Liechtenstein, Monaco, San Marino, Vatican, Andorra), or Balkan states that have not yet joined the EU and NATO (Bosnia, Serbia and Kosovo).

NATO also extends to Turkey and Canada.

Former Soviet Union
Belarus and Armenia, along with some members of the Central Asian NWFZ, are allies of Russia in CSTO, the three Baltic states have joined NATO, and the GUAM states (Georgia, Azerbaijan, Ukraine, Moldova) are not party to either security treaty.

North Pacific
South Korea and Japan are American allies under its nuclear umbrella, while the three Micronesian states (Marshall Islands, Federated States of Micronesia, and Palau) are in a Compact of Free Association with the US.

South Asia
India and Pakistan are nuclear-armed states and the six other South Asian states (Afghanistan, Sri Lanka, Maldives, Bangladesh, Nepal, Bhutan) are not part of a NWFZ or security bloc.

Middle East
The six Gulf Cooperation Council states, the 5 other Arab League states outside Africa (Yemen, Jordan, Lebanon, Syria, Iraq), and Iran (see Nuclear program of Iran) are not nuclear weapons states and not part of a NWFZ. The UN General Assembly has urged establishment of a Middle East NWFZ, and NPT Review Conferences in 1995 and 2010 called for a zone free of all weapons of mass destruction in the Middle East. An International Conference For A WMD-Free Middle East was held in Haifa in December 2013 attended by citizens from all over the world concerned about the lack of progress in the official talks.

title: Nuclear-weapon-free zone


text:
Jefferson Holt

Jefferson Holt is the founder of Daniel 13 Press and manager of rock band R.E.M. from 1981 to 1996.

Under the name Vibrating Egg, Holt recorded a five-song EP on his label Dog Gone Records that included R.E.M.'s Mike Mills on bass.

In 1996, Holt and R.E.M. parted ways, allegedly due to complaints that Holt had a pattern of sexual harassment towards R.E.M.'s support staff. When asked about leaving the band, he offered this statement to Chuck Philips L. A. Times staff writer: "I've agreed to keep the terms of my agreement with R.E.M. confidential, however, 15 years is a long time, and as time passed, our friendships have changed. I think we found as time passed that we have less and less in common. I've become more interested in other things in life and wanted to spend more time pursuing those interests. I'm happier than I have been in a long time."

Representatives for R.E.M. released a statement that said the band and Holt terminated their relationship by mutual agreement. According to the statement: "The reasons for this decision and terms of the termination are private and confidential, and no further discussion of these matters will be made by any of these parties."

Holt lives with his family in North Carolina, where he collects art and memorabilia, publishes books, and pursues sundry philanthropic interests, including artistic patronage to emerging artists, photographers, musicians, and writers.

Holt is also the publisher for Daniel 13 Press, publishing photographic books by amateur and professionals.

His mother was Bertha "B" Holt, member of the North Carolina State House of Representatives. The childhood home of Jefferson Holt, the house of Bertha Holt, is featured in 509, a limited book edition by Pamela Pecchio.

References to Holt in R.E.M. songs
Holt is referenced in the song "Little America," from 1984's Reckoning album. The song's (and album's) last line, "Jefferson, I think we're lost," was changed to "Washington, I think we're lost" when the song was revived for live shows, as evidenced in a 2007 performance on the two-CD Live at The Olympia set in 2009.

title: Jefferson Holt


text: User talk:216.45.5.90

title: User talk:216.45.5.90


text:
Wikipedia:Articles for deletion/Suzie Wylie

 * The following discussion is an archived debate of the proposed deletion of the article below. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the article's talk page or on a Votes for Undeletion nomination).  No further edits should be made to this page.

The result of the debate was delete. Wikiacc (talk) 00:38, 19 October 2005 (UTC)

Suzie Wylie
Student vanity. Only claim to fame is running for president of the National Union of Students of the United Kingdom. R. fiend 16:23, 12 October 2005 (UTC)
 * Delete not yet notable enough.  Dl yo ns 493   Ta lk  16:53, 12 October 2005 (UTC)
 * No vote, I'll abstain from voting becasue she's a friend so I'm not realy neutral. I've beefed the article a bit and included some referances. On the plus side she does hold a national position in the NUS (on block of 12). On the downside so have many people who definatly don't deserve an encycopedia article. She is doing a toor with Gorgous George mabey this will be enough to push her into the relem of the political gliteriti, maby not. In defence of her modesty I don't think it was her who created the page though I can't be sure. --JK the unwise 17:10, 12 October 2005 (UTC)
 * Delete student with some activism activity. Good for her for getting involved, but it isn't the sort of thing that gets an encyclopedia article. Andrew Lenahan - St ar bli nd  17:58, 12 October 2005 (UTC)
 * Delete. Student activists who aspire to mainstream politics just ain't notable. Eddie.willers 19:22, 12 October 2005 (UTC)
 * Delete as her achievements thus far centre on student activism and peripheral political achievement. I wish her luck for the future, though. Sliggy 23:41, 12 October 2005 (UTC)
 * Delete. I have to agree with the prior justifications, including the characterizations of Ms. Wylie as someone of TREMENDOUS potential. I think she will qualify for Wikipedia one day and we will welcome her with open arms.  I just don't think she qualifies as sufficiently notable at this time. el_amante 20:40, 12 October 2005 (UTC)
 * No vote, again I know her (a bit); the article looks quite decent now and is probably verifiable, but there is the notability issue. Warofdreams talk 09:49, 13 October 2005 (UTC)
 * The above discussion is preserved as an archive of the debate. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the article's talk page or in an undeletion request). No further edits should be made to this page.


text:
Admiel Kosman

Admiel Kosman (אדמיאל קוסמן; born in 1957) is an Israeli poet and professor of Talmud.

Biography
Admiel Kosman was born in Haifa, Israel to an Orthodox Jewish family. His father hailed from a German Jewish family living in France, and his mother immigrated from Iraq. After serving in the Israel Defense Forces in an artillery unit and attending Yeshivat Hakotel in the Old City of Jerusalem, he studied graphic art and pottery at the Bezalel Academy of Art and Design. He did his Ph.D. in Talmud at Bar-Ilan University in Ramat Gan.

Kosman has four children from his first marriage.

Since relocating to Berlin, Kosman is a professor of Religious and Jewish Studies at the University of Potsdam and the academic director of Abraham Geiger Reform Rabbinical Seminary.

Kosman is the author of eight books of poetry. His poems often deal with the tension between his religious faith and artistic sensibilities. Kosman has also written three volumes of post-modern scholarship on gender in traditional Jewish texts. In 2000, he was invited by Nobel Prize–winning Polish poets Czeslaw Milosz and Wislawa Szymborska to participate in an interfaith festival in Kraków, Poetry – between Prayer and Song.

Awards
Kosman has been awarded national prizes for poetry including:
 * the Bernstein Prize (original Hebrew-language poetry category) (1991)
 * the Prime Minister's Prize (1976, 1992)
 * the Brenner Prize (2000)

Poetry

 * And Then the Act of Poetry, 1980 [Ve-Aharei Mora`ot Ma`ase Ha-Shir]
 * The Prince's Raiment, 1988 [Bigdei Nasich]
 * Soft Rags, 1991 [Smartutim Rakim]
 * What I Can, 1995 [Ma Ani Yachol]
 * We Reached God, 1998 [Higanu Le-Elohim]
 * Forty Love Poems and Two Additional Love Poems to God, 2003 [Arbaim Shirei Ahava Ve-Shnei Shirei Ahava Nosafim Le-Elohim]
 * Proscribed Prayers, Siddur Alternativi, Seventy One New Poems), Hakibutz Hameuchad, Tel Aviv 2007
 * You’re Awesome! (Ktaim Itcha), Hakibutz Hameuchad, Tel Aviv 2011
 * Approaching You in English: Selected Poems of Admiel Kosman, translated by Lisa Katz and Shlomit Naim-Naor (Zephyr Press, 2011)

Books and articles

 * Gender and Dialogue in the Rabbinic Prism (Studia Judaica; de Gruyter, New York and Berlin, 2012)
 * "The Story of a Giant Story - The Winding Way of Og King of Bashan in the Jewish Aggadic Tradition", in: HUCA 73, (2002) pp. 157–190.
 * Men’s World: Reading Masculinity in Jewish Stories in a Spiritual Context. Ergon, Würzburg 2009.
 * "Two Women Who Were Sporting with Each Other": A Reexamination of the Halakhic Approaches to Lesbianism as a Touchstone for Homosexuality in General, (with Anat Sharbat), HUCA 75, (2004), pp. 37–73
 * Men’s Tractate: Rav and the Butcher and other Stories – On Manhood, Love and Authentic Life in Aggadic and Hassidic Stories, Keter, Jerusalem 2002
 * Treading toward sanctity. Musings and meditations on close to a century's worth of discussions occasioned by Van Gogh's series of paintings of worn shoes. Was the artist's statement primarily aesthetic, or political, or was it religious? In: Ha-Aretz (19.11.2009)
 * Treading toward sanctity. Musings and meditations on close to a century's worth of discussions occasioned by Van Gogh's series of paintings of worn shoes. Was the artist's statement primarily aesthetic, or political, or was it religious? In: Ha-Aretz (19.11.2009)

title: Admiel Kosman


text: Category:People from Jalisco

title: Category:People from Jalisco


text:
Wikipedia:Articles for deletion/Electronic Music Systems

 * The following discussion is an archived debate of the proposed deletion of the article below. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the article's talk page or on a Votes for Undeletion nomination).  No further edits should be made to this page.

The result of the debate was KEEP. — J I P | Talk 16:35, 19 October 2005 (UTC)

Electronic Music Systems
Mis-named article - moved to Electronic Music Studios (London) Ltd  ajn (talk) 16:26, 12 October 2005 (UTC)

Delete, obviously. I've altered the two entries which used to link to this (the company's usually known as EMS, which is probably where the confusion arose). -- ajn (talk) 16:26, 12 October 2005 (UTC)
 * keep as a disambig I made, which points out at a possible confusion. mikka (t) 23:48, 12 October 2005 (UTC)
 * keep from me now, too. --  ajn (talk) 05:37, 13 October 2005 (UTC)

 * The above discussion is preserved as an archive of the debate. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the article's talk page or in an undeletion request). No further edits should be made to this page.


text:
User talk:Kgf0/AfD

I'm perfectly willing to discuss my rationalle for any nomnation in detail here. Please start a new section using the linked name of the nominated page as the section header, if it's not already listed.

List of sexual slang
Hey -- I voted keep because I know there's precedent for lists of words. Lots and lots of precedent. This is not really dicdef. To tell you the truth I don't like the idea of lists on Wikipedia at all, but what are you going to do? 23:29, 18 October 2005 (UTC)
 * I'm not sure I like precedent over policy - there's precedent for vanity pages too, but we WP:AFD them, and I think the same should be true wherever creeping cruft starts to take over. This will happen continuously on any slang page, but it will seem condoned, or worse encouraged, on a page called "List of slang," especially as it continues to survive calls for its death.  The continued presence, and sheer size, of such lists undermines the credibility of Wikipedia policy as a whole, and renders the rest of the policy difficult to enforce due to the same logic: there becomes a precedent for ignoring policy.  As for what to do about it, well, that's why I consider myself a Disciplined Deletionist.  YMMV.  You're right about one thing though: it's not dictdef; a closer look at WP:ISNOT will show point #3: A usage guide, or slang and idiom guide.  --Kgf0 23:57, 18 October 2005 (UTC)
 * *shrug* Sorry, my vote remains keep. If enough people vote to delete it, it'll be deleted. 00:45, 19 October 2005 (UTC)

Kgf0, I agree with you to the extent that I've put it back on AFD. And already gotten my first accusation of trying to censor wikipedia for it ;)  The Literate Engineer 00:22, 11 November 2005 (UTC)

title: User talk:Kgf0/AfD


text:
Smiths Knoll

Smiths Knoll was a poetry periodical, published in the United Kingdom. It was founded by Roy Blackman and Michael Laskey in 1991 and named after a former lightvessel station off the Norfolk coast, near Haisborough Sands.

It was edited by Roy Blackman until 2002 when Joanna Cutts began to serve in the post. Issue 50, published on 2 November 2012, was the final issue of the magazine.

title: Smiths Knoll


text:
Tocotrienol

The vitamin E family comprises four tocotrienols (alpha, beta, gamma, delta) and four tocopherols (alpha, beta, gamma, delta). The critical chemical structural difference between tocotrienols and tocopherols is that tocotrienols have unsaturated isoprenoid side chains with three carbon-carbon double bonds versus saturated side chains for tocopherols (see Figure).

Tocotrienols are compounds naturally occurring at higher levels in some vegetable oils, including palm oil, rice bran oil, wheat germ, barley, saw palmetto, annatto, and certain other types of seeds, nuts and grains, and the oils derived from them.

Chemically, different analogues of vitamin E all show some activity as a chemical antioxidant, but do not all have the same vitamin E equivalence. Tocotrienols demonstrate activity depending on the type of antioxidant performance being measured. All tocotrienols have some physical antioxidant activity due to an ability to donate a hydrogen atom (a proton plus electron) from the hydroxyl group on the chromanol ring, to free radical and reactive oxygen species. Historically studies of tocotrienols account for less than 1% of all research into vitamin E.

Health effects
A number of health benefits of tocotrienols have been proposed, included decreased risk of heart disease and cancer. The Food and Nutrition Board of the Institute of Medicine of the United States National Academy of Sciences does not define a Recommended Dietary Allowance or Adequate Intake for tocotrienols.

Brain
A review of human studies in middle-aged and elderly stated "Evidence from prospective and case-control studies suggested that increased blood levels of tocotrienols were associated with favorable cognitive function outcomes." The review qualified this statement by noting that randomized, controlled clinical trials were needed to evaluate these observations.

Heart disease
Tocotrienols have been linked to improved markers of heart disease.

Skin
Tocotrienols have been linked to improve atopic eczema.

Side effects
Tocotrienols are generally well tolerated and without significant side effects.

History
The discovery of tocotrienols was first reported by Pennock and Whittle in 1964, describing the isolation of tocotrienols from rubber. The biological significance of tocotrienols was clearly delineated in the early 1980s, when its ability to lower cholesterol was first reported by Asaf Qureshi and Elson in the Journal of Medicinal Chemistry. During the 1990s, the anti-cancer properties of tocopherols and tocotrienols began to be delineated. The current commercial sources of tocotrienol are rice and palm. Other natural tocotrienol sources include rice bran oil, coconut oil, cocoa butter, barley, and wheat germ. Tocotrienols are safe and human studies show no adverse effects with consumption of 240 mg/day for 48 months. Tocotrienol rich fractions from rice, palm, or annatto, used in nutritional supplements, functional foods, and anti-aging cosmetics, are available in the market at 20%, 35%, 50%, and 70% total vitamin E content.

Etymology
Tocotrienols are named by analogy to tocopherols (from Greek words meaning to bear a pregnancy (see tocopherol); but with this word changed to include the chemical difference that tocotrienols are trienes, meaning that they share identical structure with the tocopherols except for the addition of the three double bonds to their side chains.

Comparison to tocopherols
Tocotrienols have only a single chiral center—the 2' carbon on the chromanol ring, which is where the isoprenoid tail is attached. Unlike the tocopherols, which have additional chiral centers along their saturated tail chain, the unsaturated chain of the tocotrienols instead have double-bonds at this sites. Tocotrienols extracted from plants are always dextrorotatory stereoisomers, signified as d-tocotrienols. In theory, (levorotatory; l-tocotrienol) forms of tocotrienols could exist as well, which would have a 2S rather than 2R configuration at the molecules' single chiral center, but unlike synthetic, dl-alpha-tocopherol, the marketed tocotrienol dietary supplements are all d-tocotrienol extracts from palm or annatto oils.

Tocotrienol studies confirm anti-oxidation, anti-inflammatory potentials and suggest anti-cancer effects better than the common forms of tocopherol due to their chemical structure. Scientists have suggested tocotrienols are better antioxidants than tocopherols. It has been proposed that the unsaturated side-chain in tocotrienols causes them to penetrate tissues with saturated fatty layers more efficiently than tocopherol. Lipid ORAC values are highest for δ-tocotrienol. However that study also says: "Regarding α-tocopherol equivalent antioxidant capacity, no significant differences in the antioxidant activity of all vitamin E isoforms were found."

Absorption and distribution
Tocotrienols are primarily administered orally and, due to their lipophilic nature, their absorption is significantly enhanced when taken with a fat-rich diet. These compounds are mainly absorbed in the small intestine, with absorption depending on adequate pancreatic function, bile secretion, and micelle formation in the intestines. Upon administration, tocotrienols are distributed throughout the body, with higher concentrations observed in plasma and adipose tissues.

Bioavailability factors
The short half-lives of tocotrienols are attributed to their low binding affinity for α-TTP, which maintains plasma levels of tocopherols. Specifically, α-tocopherol has a significantly higher binding affinity for α-TTP compared to tocotrienols. Relative to α-tocopherol's affinity, α-tocotrienol has about 9%, δ-tocotrienol 12%, and ɤ-tocotrienol 2% affinity for α-TTP. Consequently, δ-tocotrienol remains in plasma for a longer duration, offering greater bioavailability and slower biotransformation compared to other isomers. Human studies have indicated that δ-tocotrienol has a bioavailability of 28%, while ɤ- and α- isomers exhibit 9%.

Metabolism and excretion
Tocotrienols are primarily metabolized in the liver, undergoing ω-hydroxylation by the enzymes CYP3A4 and CYP4F2, followed by β-oxidation. The final metabolites, carboxyethyl-hydroxychromanols (CEHC) and carboxymethylbutyl hydroxychroman (CMBHC), are readily excreted in urine.

Radiation countermeasures
Following exposure to gamma radiation, hematopoietic stem cells (HSCs) in the bone marrow, which are important for producing blood cells, rapidly undergo apoptosis (cell death). There are no known treatments for this acute effect of radiation. Two studies conducted by the U.S. Armed Forces Radiobiology Research Institute (AFRRI) found that treatment with γ-tocotrienol or δ-tocotrienol enhanced survival of hematopoietic stem cells, which are essential for renewing the body's supply of blood cells. Based on these successful results of studies in mice, γ-tocotrienol is being studied for its safety and efficacy as a radioprotective measure in nonhuman primates. No human trials have yet been completed.

title: Tocotrienol


text:
Public transport accessibility level

The public transport accessibility level (PTAL) is a method sometimes used in United Kingdom transport planning to assess the access level of geographical areas to public transport.

PTAL is a simple, easily calculated approach that hinges on the distance from any point to the nearest public transport stop, and service frequency at those stops. The result is a grade from 1–6 (including sub-divisions 1a, 1b, 6a and 6b), where a PTAL of 1a indicates extremely poor access to the location by public transport, and a PTAL of 6b indicates excellent access by public transport.

Background
The PTAL calculation was originally developed by the Borough of Hammersmith and Fulham in 1992, and was later adopted by Transport for London in 2004 as the standard method for calculation of public transport access in London. It is not commonly used outside Greater London or the south east of England.

Method
The first stage in PTAL calculation is to calculate the walking distance from the site (known as the point of interest (POI)) to the nearest bus stops and rail stations (where rail can be taken to also include London Underground, DLR and trams). These stops and stations are known as service access points (SAPs). Only SAPs within a certain distance of the POI are included (640m for bus stops and 960m for rail stations, which correspond to a walking time of 8 minutes and 12 minutes respectively at the standard assumed walking speed of 80m/min).

The next stage is to determine the service level during the morning peak (defined as 0815–0915) for each route serving a SAP. Where service levels differ in each direction on a route, the highest frequency is taken. On railways, a route is generally defined as a service with a particular calling pattern – for example, services on the Piccadilly line from Hammersmith could be divided into two "routes": Cockfosters to Heathrow and Cockfosters to Uxbridge.

A total access time for each route is then calculated by adding together the walking time from the POI to the SAP and the average waiting time for services on the route (i.e. half the headway). This is converted to an equivalent doorstep frequency (EDF) by dividing 30 (minutes) by the total access time, which is intended to convert total access time to a "notional average waiting time, as though the route were available at the doorstep of the POI".

A weighting is applied to each route to simulate the enhanced reliability and attractiveness of a route with a higher frequency over other routes. For each mode (e.g. bus, Tube, DLR, tram, rail), the route with the highest frequency is given a weighting of 1.0, with all other routes in that mode weighted at 0.5.

Finally, the EDF and the weighting are multiplied to produce an accessibility index for each route, and the accessibility indices for all routes are summed to produce an overall accessibility index for the POI.

This accessibility index (AI) can then be converted to a PTAL grade (1–6) through a banding system (where AIs 0.00–5.00 are PTAL 1, 5.01–10.00 are PTAL 2, etc. up to PTAL 6 for scores of 25 and above).

TfL introduced the WebCAT automatic calculator in 2015.

Uses
The PTAL is used as a development planning tool in London, to determine both permitted parking standards and development densities. Large site developments (those the London boroughs refer to the Greater London Authority) must follow planning guidelines that allow more parking in areas with low PTALs (i.e., poor public transport) and vice versa—and that also relate the allowed density of development to PTAL (i.e., areas with better public transport may have higher density housing or offices).

TfL also have software to calculate PTALs across wide areas using GIS and timetable data, the typical result being a map with coloured bands relating to PTAL grades.

Ahmedabad
The London PTAL method was first applied in the Indian context to Ahmedabad in 2014 (see figure Ahmedabad PTAL 2014) by Bhargav Adhvaryu and Jay Shah. PTAL mapping for other Indian cities if under progress. In the London method, points of interest (POIs) were considered by the actual development (e.g., buildings). However, in Ahmedabad, given the lack of availability of building footprint data at the time of the study, the method deviated by construing POIs as centroids of a 1 km2 grid. Given that the purpose of the study was to explore implications of PTAL at a macro-scale (i.e., development/ master plan level – the study area being 465 km2) and the data constraints, the grid-cell approach seemed justified (comparison for which is discussed in the section on Surat application). In addition, it made the computations much faster.

The others adaptation of London method to Ahmedabad included revisiting walk speed and public transport service reliability assumptions. Most of the roads in Ahmedabad do not have footpaths and, if any, are usually occupied by street vendors and parking. Therefore, people are forced to walk on the road (the black-top surface), which creates unsafe and potentially hazardous situations, such that walking is avoided as much as possible, even for short trips. To account for this discomfort walk speed was decreased to 60m/min (based on a few samples) as against 80m/min used in London. The reliability factor added in case of London (to allow for additional wait times) were 2 minutes and 0.75 minutes for buses and rail services, respectively. In Ahmedabad, this was changed to 2.5 minutes for city buses (AMTS) and 1 minute for BRTS (based on empirical observations), and 0.75 minutes was not changed for the proposed metrorail – Ahmedabad Metro (a section of which started operation in March 2019). Lastly, in London 8 minutes (i.e., 640m) and 12 minutes (i.e., 960m) were used as the threshold walk distances to bus and rail SAPs, respectively; SAPs beyond these distances are rejected. However, in Ahmedabad, surveys to determine willingness to walk for public transport were not carried out. Therefore, the farthest SAP from a POI (not accounted for in any other POI) was measured, which turned out to be 993m. At 60m/min, this give as willingness to walk at about 16 minutes, which seemed reasonable.

The Ahmedabad study discussed several uses of PTAL mapping:

 * 1) Improving existing public transport systems by recognizing areas with poor accessibility, thereby enabling decision makers to prioritize investments in public transport systems and support non-motorized transport infrastructure.
 * 2) Formulating parking policies, e.g. park-and-ride facilities could be provided to supplement areas with low and medium PTAL and parking may be restricted or charged at a higher rate in areas with high PTAL.
 * 3) Integrating land use zoning with public transport accessibility. By allowing future transport improvements to be incorporated into PTAL calculations, a future PTAL map becomes an important tool in supporting land use and zoning decisions for local authorities, including introduce transit-oriented development (TOD), as PTALs already incorporate walkability criteria from POIs – an important D (distance to transit) in the 6Ds of TOD. It can also be useful in testing "what if" scenarios using land use – transport interaction models.
 * 4) PTAL maps could be used by households to inform their residential location choices, especially low-income households that are captive public transport users. Real estate developers (who supply housing and commercial spaces) could use PTAL maps (both existing and future) for locating potential projects (especially low-income housing and industrial), while government agencies could use PTAL maps to locate social housing projects.

Surat
Building from the Ahmedabad case study, PTAL was applied for Surat by Bhargav Adhvaryu, Abhay Chopde, and Lalit Dashora. This application goes beyond the Ahmedabad study in two ways. First, it overlays population density map on PTAL maps (see figure Surat PTAL 2016 overlaid with population density) demonstrating a better way to use PTAL maps to inform public transport investment decisions. Second, it demonstrates the use of PTAL for evaluating future transport investment options. PTAL maps for year 2021 (see figure Surat PTAL 2016 v. 2021 (future)) were generated based on information on future (and committed) proposals to demonstrate PTAL's strategic use to create "what-if" scenarios. The Surat study also explicitly justified the use of 1 km2 grid for PTAL mapping in data and resource constrained situation by showing changes in PTAL map resolutions for grid sizes for comparison (see figure Comparison of PTAL map for various grid sizes (Surat)). Of course, smaller grid micro-PTAL maps can be prepared for specific areas of the city which could be used to fine-tuning public transport infrastructure provision at local area level. The Surat study discussed several uses of PTAL mapping such as: [1] prioritising public transport investments [2] Integrating transport in development/master plan [3] informing the parking policy [4] improving residential location choice and optimizing supply of affordable housing, and [5] understanding the mobility needs of the urban poor, which is based on another study in Ahmedabad. It argues that living in high PTAL areas may not necessarily translate to high accessibility to destination by public transport, especially those urban poor with variable job destination by month and season (e.g., construction workers, casual labourers, street vendors, etc.). Superimposing housing location of the urban poor on the PTAL map allows identifying specific areas for enhancing the mobility (see figure Ahmedabad PTAL 2017 superimposed with slum and chawl location).

Lucknow
The PTAL analysis of Indian cities continued with the application of PTAL to Lucknow. The methodology adopted for the PTAL analysis of Ahmedabad and Surat was used to prepare the PTAL map of Lucknow. The maps of the baseline and the tentatively committed scenarios formed the basis for further research on its applications to improve the urban plan-making process. The first application of PTAL was to enhance the statutory development plan. The PTAL map was superimposed over the proposed development plan to validate the congruity of the land use and transport proposals (see figure Lucknow PTAL 2020 (baseline scenario) overlaid on population density). A new public transport network was recommended to improve PTAL in areas most likely to develop in the near future. The second application was to improve the zoning for transit-oriented development. The third application is aimed at making public transport more inclusive. The study found that the proposed public affordable housing projects are in areas having poor PTAL, which could hamper the occupancy in these projects; the slums, on the contrary, were in high-PTAL areas. Recommendations included proposing affordable housing projects in areas having high-PTAL. The fourth application explored was to enhance micro-level plans. An area of 1 km2 was assessed using 100 m2 grids. The PTAL analysis revealed which areas have poor PTAL. Improvement in the quality of pedestrian infrastructure and street connectivity was recommended; the new PTAL map, thus, generated demonstrated improved PT accessibility (see figure Lucknow PTAL: Macro v. Micro). The authors also proposed combining this tool to develop a holistic dashboard; this could be used by the stakeholders in taking more informed decisions, focused on land use transport integration.

Hubli-Dharwad
The PTAL analysis of Indian cities continued with the application of PTAL to Hubli-Dharwad, a twin-city region that is one of fastest-growing cities in Karnataka State. The analysis was based on the methodology adopted for Ahmedabad and Surat, with new methodological innovations (explain below). The city follows a Master Plan 2031 Revision–II (made in 2017 and approved in 2019), which has opened new areas for development. This established the need to analyse the accessibility of the public transport network in relation to the planned future developments that builds on the analysis of the current situation. The mapping provides a visual representation of the existing accessibility levels (see figure Hubli-Dharwad PTAL 2020 (base year) overlaid on 2011 Census population density) that can further be used to facilitate the decision-making process in master plan preparation and guide future public transport investments, rationalise land use distribution, help decide sites for affordable housing locations, and support the demarcation of transit-oriented development (TOD) zone demarcation. The base year PTAL is also important to compare the PTALs with future year.

In the study, the PTAL map was superimposed with the proposed Master Plan 2031 which envisions Hubli-Dharwad to grow as a compact and equitable city. A key methodological step was to start with the base year PTAL map and overlay layers of existing land use, job density, development and demand potential, PT improvement leading to a robust public-transport centric development plan for 2031 (see figure Methodology to arrive at a robust PT-centric future plan (2031)). Considering this future (2031) PT improvements, the PTAL was then prepared (see figure Hubli-Dharwad PTAL 2031 (future year) with bus rapid transit and mini-bus feeder systems). As can bee seen the average accessibility index in the base year (2020) is 3.6 (buses/hour), which improves to 5.5 buses/hour for 2031.

Recommendations were made to improve public transport infrastructure to ensure synchronisation with the existing job centers and proposed development. The PTAL map was also superimposed on proposed affordable housing locations in the Master Plan to assess accessibility to public transport and hence recommendations were made to improve connectivity to these zones. The proposed TOD zone demarcation along the BRT corridor was also overlaid on the PTAL map to validate accessibility levels in the zone.

Greater Manchester

 * Transport for Greater Manchester developed the Greater Manchester Accessibility Level (GMAL) method. This is similar to the PTAL calculation but uses "crow flies" distances to Service Access Points. It also includes an additional score for "Local Link" demand responsive transport services.

New South Wales
Transport for New South Wales also uses an adapted version of the PTAL method.

Advantages & disadvantages
Whilst PTAL is a simple calculation (easily performed by a spreadsheet) that offers an obvious indication of the density of public transport provision in an area, it suffers two key problems:

 * It does not take into account where services actually go to – for example, a bus that runs every ten minutes to the bottom of the road is considered better than a bus that runs every twelve minutes to the city centre.
 * The use of arbitrary cut-offs to exclude more distant service access points underestimates the ability to access locations just outside those cut-off distances. For example, a point 960m from King's Cross could have a PTAL of 6, whilst a point 961m from the same station could have a PTAL of 1 or 2.

Accessibility modelling has been proposed as a solution to these problems. It uses GIS to calculate door-to-door travel times by public transport to a grid of points around the point of interest, resulting in a set of isochrone maps – journey time contours – within which the number of workplaces, households or residents can be calculated using census data. This method takes into account many more factors than PTAL, but is much more time-consuming and requires a level of expertise with GIS software and methodologies.

title: Public transport accessibility level


text:
File:David-C-H.JPG

Summary
Author = David.c.h Source = David.c.h

title: File:David-C-H.JPG


text: Template:Redox indicator template

title: Template:Redox indicator template