Resident Evil Playthrough (Chris) Part 10
- Length: 7:47
- Rating: ( ratings)
- Views:
- Author: Davemeyo
there was a error at the end of this video but I fixed it in Part 11 and I will be starting on the way to the guard house
It's not slap
- Length: 0:42
- Rating: ( ratings)
- Views:
- Author: gmhgb
It's mostly snap with finger and mute with palm plus added errors - I don't get time to practice! Poor sound due to small point and squirt camera
Mookilla Rajyathe (1991) 3
- Length: 10:1
- Rating: ( ratings)
- Views:
- Author: dalydalos
Tags: bharath cinema classic comedy dalydalus film india indian Jagathy kerala malayalam malayali malayaly mallu mallus movie Mukesh Siddique Thilakan thriller
Mookilla Rajathe is a good comedy film from Taha Four mental patients (Thilakan, Mukesh, Siddique & Jagathy) escape from the mental hospital and begin their life in the city. Comedy of errors that happen to them makes up the story
MadTV - Coach Hines (Part 1) (High Quality version)
- Length: 4:41
- Rating: ( ratings)
- Views:
- Author: Animan25
Tags: Coach Hines Jeff MadTV Probst
Coach Hines gets in trouble at the confessional!! (Please excuse the multiple uploads of this same video to my channel. I Sincerely Apologize for this, but two consecutive uploads prior to this one resulted in the normal version of the video getting corrupted into losing audio syncronization with the video datas after a graphic pixelization error ocurred apparently caused by some sort of glitch in the video convertion process that YouTube uses to convert uploaded videos to .FLV format, and I have been trying to get a 100% fully funtional version available for everyone to view in spite of this. Here's a new, freshly digitized version of the video that I have now uploaded. I hope it ends up better than the last one. Thanks for understanding, everyone!!) ;)
dbdvrf #50 Debian Developer's Reference
- Length: 7:35
- Rating: ( ratings)
- Views:
- Author: h4ck3rm1k3
Tags: debian developers reference
http://packages.debian.org/sid/developers-reference - - essential for any Debian maintainer. A.1.2.**debconf debconf provides a consistent interface to configuring packages interactively. It is user interface independent, allowing end-users to configure packages with a text-only interface, an HTML interface, or a dialog interface. New interfaces can be added as modules. You can find documentation for this package in the debconf-doc package. Many feel that this system should be used for all packages which require interactive configuration; see Section**6.5, ***Configuration management with debconf*** . debconf is not currently required by Debian Policy, but that may change in the future. A.1.3.**fakeroot fakeroot simulates root privileges. This enables you to build packages without being root (packages usually want to install files with root ownership) . If you have fakeroot installed, you can build packages as a regular user: dpkg-buildpackage -rfakeroot. A.2.**Package lint tools According to the Free On-line Dictionary of Computing (FOLDOC), `lint' is a Unix C language processor which carries out more thorough checks on the code than is usual with C compilers. Package lint tools help package maintainers by automatically finding common problems and policy violations in their packages. A.2.1.**lintian lintian dissects Debian packages and emits information about bugs and policy violations. It contains automated checks for many aspects of Debian policy as well as some checks for common errors. You should periodically get the newest lintian from unstable and check over all your packages. Notice that the -i option provides detailed explanations of what each error or warning means, what its basis in Policy is, and commonly how you can fix the problem. Refer to Section**5.3, ***Testing the package* ** for more information on how and when to use Lintian. You can also see a summary of all problems reported by Lintian on your packages at http: //lintian.debian.org/ . These reports contain the latest lintian output for the whole development distribution (unstable). A.2.2.**debdiff debdiff (from the devscripts package, Section**A.6.1, ***devscripts*** ) compares file lists and control files of two packages. It is a simple regression test, as it will help you notice if the number of binary packages has changed since thelast upload, or if something has changed in the control file. Of course, some of the changes it reports will be all right, but it can help you prevent various accidents. You can run it over a pair of binary packages: debdiff package_1-1_arch.deb package_2-1_arch.deb Or even a pair of changes files: debdiff package_1-1_arch.changes package_2-1_arch.changes For more information please see debdiff(1) . A.3.**Helpers for debian/rules Package building tools make the process of writing debian/rules files easier. See Section* *6.1.1, ***Helper scripts* ** for more information about why these might or might not be desired. A.3.1.**debhelper debhelper is a collection of programs which can be used in debian/rules to automate common tasks related to building binaryDebian packages. debhelper includes programs to install various files into your package, compress files, fix file permissions, and integrate your package with the Debian menu system. Unlike some approaches, debhelper is broken into several small, simple commands which act in a consistent manner. As such, it allows more fine-grained control than some of the other debian/ rules tools. There are a number of little debhelper add-on packages, too transient to document. You can see the list of most of them by doing apt-cache search ^dh-. A.3.2.**debmake debmake, a precursor to debhelper, is a more coarse-grained debian/rules assistant. It includes two main programs: deb-make, which can be used to help a maintainer convert a regular (non-Debian) source archive into a Debian source package; and debstd, which incorporates in one big shot the same sort of automated functions that one finds in debhelper. The consensus is that debmake is now deprecated in favor of debhelper. It is a bug to use debmake in new packages. New packages using debmake will be rejected from the archive. A.3.3.**dh-make The dh-make package contains dh_make, a program that creates a skeleton of files necessary to build a Debian package out of a source tree. As the name suggests, dh_make is a rewrite of debmake and its template files use dh_* programs from debhelper. While the rules files generated by dh_make are in general asufficient basis for a working package, they are still just the groundwork: the burden still lies on the maintainer to finely tune the generated files and make the package entirely functional and Policy-compliant. A.3.4.**yada yada is another packaging helper tool. It uses a debian/packages file to auto-generate debian/rules and other necessary files in the debian/ subdirectory.
dbdvrf #49 Debian Developer's Reference
- Length: 7:14
- Rating: ( ratings)
- Views:
- Author: h4ck3rm1k3
Tags: debian developers reference
http://packages.debian.org/sid/developers-reference - - is a good idea to send the document to the corresponding l10n mailing list, asking for a review. Once it has been done, you should feel more confident in the quality of the translation, and feel safe to include it in your package. 8.2.3.**How to get a given translation updated If you have some translations of a given text lying around, each time you update the original, you should ask the previous translator to update the translation with your new changes. Keep in mind that this task takes time; at least one week to get the update reviewed and all. If the translator is unresponsive, you may ask for help on the corresponding l10n mailing list. If everything fails, don'tforget to put a warning in the translated document, stating that the translation is somehow outdated, and that the reader should refer to the original document if possible. Avoid removing a translation completely because it is outdated. Old documentation is often better than no documentation at all for non-English speakers. 8.2.4.**How to handle a bug report concerning a translation The best solution may be to mark the bug as forwarded to upstream, and forward it to both the previous translator and his /her team (using the corresponding debian-l10n-XXX mailing list). 8.3.**I18N & L10N FAQ for translators While reading this, please keep in mind that there is no general procedure within Debian concerning these points, and that in any case, you should collaborate with your team and the package maintainer. 8.3.1.**How to help the translation effort Choose what you want to translate, make sure that nobody is already working on it (using your debian-l10n-XXX mailing list), translate it, get it reviewed by other native speakers on your l10n mailing list, and provide it to the maintainer of the package (see next point). 8.3.2.**How to provide a translation for inclusion in a package Make sure your translation is correct (asking for review on your l10n mailing list) before providing it for inclusion. It will save time for everyone, and avoid the chaos resulting in having several versions of the same document in bug reports. The best solution is to file a regular bug containing thetranslation against the package. Make sure to use the 'PATCH' tag, and to not use a severity higher than 'wishlist', since the lack of translation never prevented a program from running. 8.4.**Best current practice concerning l10n * As a maintainer, never edit the translations in any way (even to reformat the layout) without asking on the corresponding l10n mailing list. You risk for example breaksing the encoding of the file by doing so. Moreover, what you consider an error can be right (or even needed) in the given language. * As a translator, if you find an error in the original text, make sure to report it. Translators are often the most attentive readers of a given text, and if they don't report the errors they find, nobody will. * In any case, remember that the major issue with l10n is that it requires several people to cooperate, and that it is very easy to start a flamewar about small problems because of misunderstandings. So if you have problems with your interlocutor, ask for help on the corresponding l10n mailing list, on debian-i18n, or even on debian-devel (but beware, l10n discussions very often become flamewars on that list :) * In any case, cooperation can only be achieved with mutual respect. Appendix**A.**Overview of Debian Maintainer Tools This section contains a rough overview of the tools available to maintainers. The following is by no means complete or definitive, but just a guide to some of the more popular tools.Debian maintainer tools are meant to aid developers and free their time for critical tasks. As Larry Wall says, there's more than one way to do it. Some people prefer to use high-level package maintenance tools and some do not. Debian is officially agnostic on this issue; any tool which gets the job done is fine. Therefore, this section is not meant to stipulate to anyone which tools they should use or how they should go about their duties of maintainership. Nor is it meant to endorse any particular tool to the exclusion of a competing tool. Most of the descriptions of these packages come from the actual package descriptions themselves. Further information can be found in the package documentation itself. You can also see more info with the command apt-cache show [package-name]. A.1.**Core tools The following tools are pretty much required for any maintainer. A.1.1.**dpkg-dev dpkg-dev contains the tools (including dpkg-source) required to unpack, build, and upload Debian source packages. These utilities contain the fundamental, low-level functionality required to create and manipulate packages; as such, they are
easy fake virus notepad trick with codes (vbs script useign notepad)
- Length: 5:59
- Rating: ( ratings)
- Views:
- Author: miutubevids
Tags: (vbs codes computer easy fake funny hack miutubevids notepad notepad) prank script thing trick tutorial useign virus vsb with
A miutubevids production Music: The day that never comes by Metallica Please visit my channel for more vids comment with suggestion and suscribe and rate Just copy the code below into notepad, saveit as whateveryouwant.vbs ---------------------------------------------------------------------- Dim userInput, box userInput = ("Self destruct sequece of C drive initiated in 5 4 3 2 1") Set Sapi = Wscript.CreateObject("SAPI.SpVoice") Sapi.speak userinput box=msgbox("Your C drive has been erased by a unknown cause, click OK to romove the virus from your system (recomended)), click Cancel to abort romoving virus)",1,"Anti-Virus") if box=2 then box=msgbox("Aborted successfully",48,"Anti-Virus") Else if box=1 then box=msgbox("Removing virus...",48,"Anti-Virus") box=msgbox("Removing virus...",48,"Anti-Virus") box=msgbox("Error",48,"Anti-Virus") box=msgbox("Error",48,"Anti-Virus") box=msgbox("Error",48,"Anti-Virus") box=msgbox("Your C drive has been erased by a unknown cause",48,"Anti-Virus") box=msgbox("This was made by miutubevids go to http://au.youtube.com/user/miutubevids for hit utube account",48,"Anti-Virus") end if end if ---------------------------------------------------------------------- to da its done
dbdvrf #45 Debian Developer's Reference
- Length: 7:29
- Rating: ( ratings)
- Views:
- Author: h4ck3rm1k3
Tags: debian developers reference
http://packages.debian.org/sid/developers-reference - - to the original filename. Note that you don't need to depend on sharutils to get the uudecode program if you use perl's pack function. The code could look like uuencode-file: perl -ne 'print(pack "u", $$_);' $(file) ] $(file).uuencoded uudecode-file: perl -ne 'print(unpack "u", $$_);' $(file).uuencoded ] $(file) Chapter**7.**Beyond Packaging Debian is about a lot more than just packaging software and maintaining those packages. This chapter contains information about ways, often really critical ways, to contribute to Debian beyond simply creating and maintaining packages. As a volunteer organization, Debian relies on the discretion of its members in choosing what they want to work on and in choosing the most critical thing to spend their time on. 7.1.**Bug reporting We encourage you to file bugs as you find them in Debian packages. In fact, Debian developers are often the first line testers. Finding and reporting bugs in other developers' packages improves the quality of Debian. Read the instructions for reporting bugs in the Debian bug tracking system. Try to submit the bug from a normal user account at which you are likely to receive mail, so that people can reach you if they need further information about the bug. Do not submit bugs as root. You can use a tool like reportbug(1) to submit bugs. It can automate and generally ease the process. Make sure the bug is not already filed against a package. Each package has a bug list easily reachable at http:// bugs.debian.org/packagename Utilities like querybts( 1) can also provide you with this information (and reportbug will usually invoke querybts before sending, too). Try to direct your bugs to the proper location. When for example your bug is about a package which overwrites files from another package, check the bug lists for both of those packages in order to avoid filing duplicate bug reports. For extra credit, you can go through other packages, merging bugs which are reported more than once, or tagging bugs `fixed' when they have already been fixed. Note that when you are neither the bug submitter nor the package maintainer, you should not actually close the bug (unless you secure permission fromthe maintainer). From time to time you may want to check what has been going on with the bug reports that you submitted. Take this opportunity to close those that you can't reproduce anymore. To find out all the bugs you submitted, you just have to visit http:// bugs.debian.org/from:[your-email-addr]. 7.1.1.**Reporting lots of bugs at once (mass bug filing) Reporting a great number of bugs for the same problem on a great number of different packages *** i.e., more than 10 *** is a deprecated practice. Take all possible steps to avoid submitting bulk bugs at all. For instance, if checking for the problem can be automated, add a new check to lintian so that an error or warning is emitted. If you report more than 10 bugs on the same topic at once, it is recommended that you send a message to [ debian-devel@lists.debian.org] describing your intention before submitting the report, and mentioning the fact in the subject of your mail. This will allow other developers to verify that the bug is a real problem. In addition, it will help prevent a situation in which several maintainers start filing the same bug report simultaneously. Please use the programms dd-list and if appropriate whodepends (from the package devscripts) to generate a list of all affected packages, and include the output in your mail to [ debian-devel@lists.debian.org]. Note that when sending lots of bugs on the same subject, you should send the bug report to [maintonly@bugs.debian.org] so that the bug report is not forwarded to the bug distribution mailing list. 7.2.**Quality Assurance effort 7.2.1.**Daily work Even though there is a dedicated group of people for Quality Assurance, QA duties are not reserved solely for them. You can participate in this effort by keeping your packages as bug-free as possible, and as lintian-clean (see Section**A.2.1, ***lintian*** ) as possible. If you do not find that possible, then you should consider orphaning some of your packages (see Section**5.9.4, ***Orphaning a package* ** ). Alternatively, you may ask the help of other people in order to catch up with the backlog of bugs that you have (you can ask for help on [debian-qa@lists.debian.org] or [debian-devel@lists.debian.org]) . At the same time, you can look for co-maintainers (see Section**5.12, * **Collaborative maintenance*** ). 7.2.2.**Bug squashing parties From time to time the QA group organizes bug squashing parties to get rid of as many problems as possible. They are announced on [debian-devel-announce@ lists.debian.org] and the announcement explains which area will be the focus of the party: usually they focus on release critical bugs but it may happen
dbdvrf #40 Debian Developer's Reference
- Length: 7:38
- Rating: ( ratings)
- Views:
- Author: h4ck3rm1k3
Tags: debian developers reference
http://packages.debian.org/sid/developers-reference - - per se, this datatype indicates a note that can be displayed to the user. It should be used only for important notes that the user really should see, since debconf will go to great pains to make sure the user sees it; halting the install for them to press a key, and even mailing the note to them in some cases. 6.5.3.1.7.**text: This type is now considered obsolete: don't use it. 6.5.3.1.8.**error: This type is designed to handle error messages. It is mostly similar to the note type. Frontends may present it differently (for instance, the dialog frontend of cdebconf draws a red screen instead of the usual blue one). It is recommended to use this type for any message that needs user attention for a correction of any kind. 6.5.3.2.**Description: short and extended description Template descriptions have two parts: short and extended. The short description is in the Description: line of the template. The short description should be kept short (50 characters or so) so that it may be accomodated by most debconf interfaces. Keeping it short also helps translators, as usually translations tend to end up being longer than the original. The short description should be able to stand on its own. Some interfaces do not show the long description by default, or only if the user explicitely asks for it or even do not show it at all. Avoid things like What do you want to do?The short description does not necessarily have to be a full sentence. This is part of the keep it short and efficient recommendation. The extended description should not repeat the short description word for word. If you can't think up a long description, then first, think some more. Post to debian-devel. Ask for help. Take a writing class! That extended description is important. If after all that you still can't come up with anything, leave it blank. The extended description should use complete sentences. Paragraphs should be kept short for improved readability. Do not mix two ideas in the same paragraph but rather use another paragraph. Don't be too verbose. User tend to ignore too long screens. 20lines are by experience a border you shouldn't cross, because that means that in the classical dialog interface, people will need to scroll, and lot of people just don't do that. The extended description should never include a question. For specific rules depending on templates type (string, boolean, etc.), please read below. 6.5.3.3.**Choices This field should be used for Select and Multiselect types. It contains the possible choices which will be presented to users. These choices should be separated by commas. 6.5.3.4.**Default This field is optional. It contains the default answer for string, select and multiselect templates. For multiselect templates, it may contain a comma-separated list of choices. 6.5.4.**Templates fields specific style guide 6.5.4.1.**Type field No specific indication except: use the appropriate type by referring to the previous section. 6.5.4.2.**Description field Below are specific instructions for properly writing the Description (short and extended) depending on the template type. 6.5.4.2.1.**String/password templates * The short description is a prompt and not a title. Avoid question style prompts (IP Address?) in favour of opened prompts (IP address: ). The use of colons is recommended. * The extended description is a complement to the short description. In the extended part, explain what is being asked, rather than ask the same question again using longer words. Use complete sentences. Terse writing style is strongly discouraged. 6.5.4.2.2.**Boolean templates * The short description should be phrased in the form of a question which should be kept short and should generally end with a question mark. Terse writing style is permitted and even encouraged if the question is rather long (remember that translations are often longer than original versions) * Again, please avoid referring to specific interface widgets. A common mistake for such templates is if you answer Yes-type constructions. 6.5.4.2.3.**Select/Multiselect * The short description is a prompt and not a title. Do not use useless Please choose... constructions. Users are clever enough to figure out they have to choose something...:) * The extended description will complete the short description. It may refer to the available choices. It may also mention that the user may choose more than one of the available choices, if the template is a multiselect one (although the interface often makes this clear) . 6.5.4.2.4.**Notes * The short description should be considered to be a *title*. * The extended description is what will be displayed as a more detailed explanation of the note. Phrases, no terse writing style.
Page: 1 of 6421