Latest Server Release Expands Ubuntu Enterprise Profile


 
Thread Tools Search this Thread
Special Forums Cybersecurity Security Advisories (RSS) Latest Server Release Expands Ubuntu Enterprise Profile
# 1  
Old 04-21-2008
Latest Server Release Expands Ubuntu Enterprise Profile

[h2]Latest Server Release Expands Ubuntu Enterprise Profile[/h2]
Ubuntu 8.04 LTS Server Edition Combines Advanced Functionality With Five Years of Maintenance and Support
LONDON, April 21, 2008 - Canonical Ltd. announced the upcoming availability of Ubuntu 8.04 LTS Server Edition for free download on Thursday 24 April. In related news, Canonical also announced the simultaneous release of Ubuntu 8.04 LTS Desktop Edition.
read more


More...
Login or Register to Ask a Question

Previous Thread | Next Thread

5 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Special characters automatically gets returned - Red Hat Enterprise Linux Server release 7.0

Dear experts, We are using Linux OS i.e Red Hat Enterprise Linux Server release 7.0 I log to the server using putty & default shell is -bash4.2$ echo $SHELL /bin/bash special character automatically gets returned in my putty. -bash-4.2$ ~ Also this special... (4 Replies)
Discussion started by: dba1981
4 Replies

2. Red Hat

Special characters automatically gets returned - Red Hat Enterprise Linux Server release 7.0

Dear experts, We are using Linux OS i.e Red Hat Enterprise Linux Server release 7.0 I log to the server using putty & default shell is Code: -bash4.2$ echo $SHELL /bin/bash special character automatically gets returned in my putty. Code: -bash-4.2$ ~ Also this... (0 Replies)
Discussion started by: dba1981
0 Replies

3. Red Hat

To download mod_ssl for Red Hat Enterprise Linux Server release 5.6 Beta (Tikanga)

Hi, Anyone know how and where to download mod_ssl package into Red Hat Enterprise Linux Server release 5.6 Beta (Tikanga) ? could you also show what's the procedure to apply the mod_ssl into the server and how to apply the digital cert into apache server and so on. Thanks. (1 Reply)
Discussion started by: ckwan
1 Replies

4. Debian

Upgrading Ubuntu Server (10.04) using do-release-upgrade

I have a small server in work, essentially a desktop with Ubuntu Server 10.04 LTS. For the first time in it's life, I've started to get errors when running scripts involving large files. So before I give up on it, I was thinking of maybe getting the newer version of Ubuntu Server 14.04. I was... (4 Replies)
Discussion started by: Cludgie
4 Replies

5. Ubuntu

Installing latest Ubuntu on my desktop

I wish to install the latest ubuntu on my desktop. How do I go about doing this ? Also how do I create the superuser or admin once the installation is done ? (3 Replies)
Discussion started by: sundaresh
3 Replies
Login or Register to Ask a Question
REQUESTSYNC(1)						      General Commands Manual						    REQUESTSYNC(1)

NAME
requestsync - helper to file sync requests for Ubuntu SYNOPSIS
requestsync [-d distro] [-nse] [-k keyid] <source package> [target release] [base version] requestsync --lp [-nse] <source package> <target release> [base version] requestsync -h DESCRIPTION
requestsync looks at the versions of <source package> in Debian and Ubuntu and prompts for an explanation of why the Ubuntu changes (if there are any) should be dropped. The changelog entry is then downloaded from packages.debian.org, and the sync request bug is filed in launchpad. Alternatively, the sync request can be filed by GPG-signed email (option --email). requestsync checks if you have the permissions to request the sync from the archive administrators directly by checking if you have upload permissions for that package through package set permissions or component permissions. If you don't have upload permissions, the script will subscribe the necessary team with approval rights to the bug report for you. This check is only performed if requestsync is allowed to use the LP API (not email submission). In the other case requestsync relies on that you answer the question about upload permissions honestly to determine if a team with approval rights is to be subscribed to the bug. If you have permission to upload the package directly, then you may prefer to use syncpackage instead to copy the package using the Launch- pad API. At some future point, requestsync will be changed to do this automatically. requestsync uses launchpadlib authentication to file its requests. OPTIONS
Listed below are the command line options for requestsync: -h Display a help message and exit. -d Specifies which Debian distribution a package should be synced from. Default is testing in LTS cycles, otherwise unstable. -n Specifies that the package is a new package, and requestsync should not attempt to look it up in Ubuntu since it will not exist. -k <keyid> Specifies your GPG key. This is only used if the sync request is mailed to Launchpad. --email Use GPG-signed email to file the bug, rather than launchpadlib. -s Specifies that you require sponsorship. You need this option if you don't have upload permissions for that package. This disables the upload permissions check described above. -C Allow changelog to be manually filled in when missing. requestsync gets Debian changelogs from packages.debian.org, which isn't in sync with the Debian archive. To request a sync before the changelog is available, pass this option, and provide the changelog entries yourself. -e Use this flag after FeatureFreeze for non-bug fix syncs. requestsync will subscribe ubuntu-release team instead of sponsorship team. -l INSTANCE, --lpinstance=INSTANCE Use the specified instance of Launchpad (e.g. "staging"), instead of the default of "production". --no-conf Do not read any configuration files, or configuration from environment variables. <source package> This is the source package that you would like to be synced from Debian. <target release> This is the release that you would like the source package to be synced into. This should always be the latest development release of Ubuntu. [base version] In some cases, the base version (where the Ubuntu package started differing from the Debian package) cannot be automatically deter- mined. Specify this option in this case. ENVIRONMENT
requestsync uses the following variables which should be set in your shell's configuration by adding export VARIABLE= lines, where VARIABLE is one of the following: UBUMAIL, DEBEMAIL Specifies which email should be used when sending to Launchpad. All of the CONFIGURATION VARIABLES below are also supported as environment variables. Variables in the environment take precedence to those in configuration files. CONFIGURATION VARIABLES
REQUESTSYNC_SMTP_SERVER Set which SMTP server to use when sending mail. If unspecified this defaults to launchpad's SMTP servers (the eventual destina- tion). REQUESTSYNC_SMTP_PORT Sets which port of the SMTP server to use. Default is 25. REQUESTSYNC_SMTP_USER and REQUESTSYNC_SMTP_PASS Sets the username and password to use when authenticating to the SMTP server. REQUESTSYNC_USE_LPAPI Setting this to no is equivalent to running with --email. REQUESTSYNC_LPINSTANCE, UBUNTUTOOLS_LPINSTANCE The default value for --lpinstance. REQUESTSYNC_KEYID, UBUNTUTOOLS_KEYID The default value for -k. SEE ALSO
rmadison(1), syncpackage(1), ubuntu-dev-tools(5) AUTHOR
requestsync and this manual page were written by the Ubuntu MOTU Team. Both are released under the GNU General Public License, version 2. ubuntu-dev-tools 19 January 2008 REQUESTSYNC(1)