Re: openssh-server and cman with only 3y support??
On Fri, Mar 26, 2010 at 11:12:32AM +0100, Nicolas Barcet wrote: > > Nick, can you check into this and confirm if this is accurate? > > Copying the reply I got from Michael Vogt on the subject: > > Thanks for raising that. The mainteance check that runs on launchpad > is written by me and a extensive seeds review was done by Kees to make > sure the stuff is in the right seeds. > > There is currently a bug (and a pending merge request) in LP that adds > server-ship to the 5y support seed, this is currently not the case and > most likely causing a lot of the problems you see. > > In the meantime you can check the updated script outout via: > $ bzr get lp:~mvo/ubuntu-maintenance-check/python-apt > and run "maintenance-check.py". Add --with-seeds if you are > interessted in what seeds the packages are in. For those of us watching at home, the above URL should be lp:~mvo/ubuntu-maintenance-check/python-port (Michael's fingers are too used to typing "python-apt" ;-) ). -- - mdz -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: RFC: redhat-cluster-suite demotion to universe
On Mon, Jan 04, 2010 at 06:59:04PM -0500, Scott Kitterman wrote: > "Mathias Gug" wrote: > > >Pros for universe demotion: > > * extremely difficult to test > > * earlier versions were very painful to get security updates applied > > I think these are better arguments for removal than demotion. If it's too > hard for Canonical to maintain, punting it to the community isn't likely > to end well. I don't think there was any implication in Mathias' email that this is about Canonical or the community, only main vs. universe. -- - mdz -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: Reporting bugs with the Ubuntu EC2 images
On Fri, Sep 11, 2009 at 10:42:53AM -0700, Brian Murray wrote: > On Thu, Sep 10, 2009 at 05:45:33PM -0700, Matt Zimmerman wrote: > > Bugs should be reported using the ubuntu-bug tool, following the > > instructions at https://help.ubuntu.com/community/ReportingBugs > > > > Bugs should be reported from the running instance where the problem exists > > wherever possible, as ubuntu-bug will automatically collect the relevant > > information and submit it to Launchpad to aid in diagnosis. > > > > Doing this does not yet automatically tag the bug with ec2-images, but but > > this is something we intend to do. > > Additionally, if there is some item in apport output that would show up > in the bug description that would identify these as coming from an ec2 > image (like the kernel version?) we could then go back and tag these > appropriately. I think there are very few bugs reported from this environment at present; in fact, ubuntu-bug may or may not presently be installed in the images. If it isn't, we should seriously consider adding it for the benefit of improved bug management. It's not large. > > We will make this happen automatically when using ubuntu-bug. Until then, > > it's also possible to craft a +filebug URL which pre-fills the tags field. > > I don't have an example to hand, but Brian should be able to help with this. > > A +filebug url with field.tags=ec2-images appended will do the trick. For > example: > > https://bugs.launchpad.net/ubuntu/+source/zpkg/+filebug?field.tags=ec2-images > > will have the tag ec2-images added to it. Thanks. > > Extending the above resource would be the best way to do this. > > I'm somewhat concerned about making the ReportingBugs wiki page longer > than it already is and possibly discouraging people from reading it. I defer to your judgement, then. If there's a better place to put this information, please help the team to organize the instructions appropriately. -- - mdz -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: Reporting bugs with the Ubuntu EC2 images
Background for Marjo and Brian: We had been tracking bugs relating to our EC2 images on an "ubuntu-on-ec2" project, and are moving away from that to file them on the appropriate Ubuntu packages instead, with a tag to group them (very similar to the migration we did for UNR recently). On Wed, Sep 09, 2009 at 08:18:09PM -0700, Eric Hammond wrote: > > I used to send folks here to report bugs running Ubuntu on EC2: > > https://bugs.launchpad.net/ubuntu-on-ec2/+bugs > > Where should they go in the new bug structure? Bugs should be reported using the ubuntu-bug tool, following the instructions at https://help.ubuntu.com/community/ReportingBugs Bugs should be reported from the running instance where the problem exists wherever possible, as ubuntu-bug will automatically collect the relevant information and submit it to Launchpad to aid in diagnosis. Doing this does not yet automatically tag the bug with ec2-images, but but this is something we intend to do. > It seems unlikely that EC2 users will know what package is causing their > problem. There is a guide linked from the above which helps identify which package is at fault. I don't think it covers EC2-specific infrastructure yet, but it probably should. > How do I find all bugs tagged with "ec2-images' no matter what package > they are assigned to? This doesn't work: > > https://bugs.launchpad.net/+bugs?field.tag=ec2-images https://bugs.launchpad.net/ubuntu/+bugs?field.tag=ec2-images > Should all Ubuntu on EC2 bugs be filed against "ubuntu"? > > https://bugs.launchpad.net/ubuntu/+bugs?field.tag=ec2-images Wherever possible, they should be filed against the appropriate package. If that cannot be determined, then filing > It seems more complicated to have to tell people reporting bugs to open > the "Extra Options" and add a tag of "ec2-images". We will make this happen automatically when using ubuntu-bug. Until then, it's also possible to craft a +filebug URL which pre-fills the tags field. I don't have an example to hand, but Brian should be able to help with this. > Perhaps we should have a wiki page with complete instructions on how to > file a problem with Ubuntu on EC2 including things like "Report the AMI > id of the image you are running". Extending the above resource would be the best way to do this. -- - mdz -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: UEC Karmic Kernel status update meetings.
On Wed, Sep 09, 2009 at 07:05:48AM -0400, Pete Graner wrote: > John Johansen wrote: > >The kernel team will be holding UEC Karmic Kernel status updates/discussion > >on > >#ubuntu-kernel daily @16:00 GMT until the current kernel status stabilizes. > > > >Any and all who are interested are welcome to participate. > > > >john > > > > I added this to the Platform Team Calendar & The Ubuntu Kernel Team > Calendar in Google Calendar as well. This is a good idea, thanks for setting it up. I've asked Scott Moser to attend on behalf of the server team going forward. -- - mdz -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Apport for servers?
I like to install and enable apport on my servers, so that if a daemon crashes, it leaves behind a crash file with the relevant state which I can use for analysis and reporting the bug. I think this functionality should continue to be disabled by default in stable releases, but what do you think about including apport in the server install so that 1) we get the benefits of crash reporting for pre-release development, and 2) administrators can trivially enable it? -- - mdz -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: Moving w3m out of standard
On Thu, Jun 26, 2008 at 09:57:07AM +0100, Matt Zimmerman wrote: > > patch > > This doesn't seem to be in standard, though I'm somewhat surprised that > nothing in there pulls it in through a dependency. > > I think it's a good candidate for the server seed. > [...] > > screen > > This is in desktop, not standard. A good candidate for the server seed. I've added both of these to the server seed now that it exists. -- - mdz -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Degraded RAID UI (Re: Server Team 20080812 meeting minutes)
On Tue, Aug 12, 2008 at 05:19:32PM -0700, Mathias Gug wrote: > Boot Support for Degraded RAID > > kirkland has been working on adding RAID support to grub-install. His patch is > waiting for sponsoring. He hopes it will make it for alpha4 scheduled to be > released on Thursday. If so mathiaz suggested that this new feature should be > documented in the Release Notes in order to get more testing. > > The last item he's working on is adding a question during the installation on > whether the system should be set to boot from a degraded array (defaulting to > No, which matches the current behaviour). It appears from that if this feature is not enabled, the system will fail hard to an initramfs shell. Instead, how about giving the user the option to continue? Waiting for root file system... ** WARNING: The root filesystem was found on a degraded RAID array! ** The system may have suffered a hardware fault, such as a disk drive failure. You may attempt to start the system anyway, or stop now and attempt manual recovery operations. If you choose to continue, the system may start normally, but performance may be degraded, and a further hardware fault could result in permanent data loss. If you abort now, you will be provided with a recovery shell. Do you wish to continue? [y/N] This should present no more risk than dropping to a shell, and gives the user the guidance to make an informed decision. -- - mdz -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: unexpected output vmstat -s
On Mon, Aug 11, 2008 at 04:24:24PM +0200, Sander van Vugt wrote: > Thanks for your feedback. From it (and my ignorance ;-) follows another > question. For performance measuring purposes, I think it is useful to > compare interrupts and CPU context switches in a non tickless kernel. Why? Are you using the number of interrupts as a measure of uptime? Of workload? There are better metrics for those. -- - mdz -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: Accepted: initramfs-tools 0.92bubuntu9 (source)
On Sun, Aug 03, 2008 at 09:40:15PM -, Ben Collins wrote: > Format: 1.8 > Date: Sun, 03 Aug 2008 17:34:22 -0400 > Source: initramfs-tools > Binary: initramfs-tools > Architecture: source > Version: 0.92bubuntu9 > Distribution: intrepid > Urgency: low > Maintainer: Ubuntu Kernel Team <[EMAIL PROTECTED]> > Changed-By: Ben Collins <[EMAIL PROTECTED]> > Description: > initramfs-tools - tools for generating an initramfs > Changes: > initramfs-tools (0.92bubuntu9) intrepid; urgency=low > . >* Default update-initramfs.conf to not keep backups. With latest > last-good-boot, we don't need to any more. > TODO: LILO probably wants .bak's since it doesn't do last-good-boot > stuff. > Should we worry about this? I believe LILO is still used for some cases in the installer (volume management?), though I'm not sure which. The server team should know. -- - mdz -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: Moving w3m out of standard
On Wed, Jun 25, 2008 at 07:55:28AM -0400, Rich Kulawiec wrote: > As an die-hard old-school (err, make that, "ancient school") 'nix admin > I applaud the idea of trying to keep installs minimal, both for space > and security reasons. > > On the other hand, I recognize the value of having some basic utilities > handy to administer services, test them, debug them, and fix them. > Like many other people, I've got a favorite set that I often find > useful. I try to keep that set restricted to those that I can run > on a low-bandwidth ssh connection, because that's often exactly > what I have to do, and I try to avoid overlapping tools (although > arguably two of my choices, curl and wget, at least partially do so). > > My suggestion is that discussion take place over (a) whether it makes > sense or not to bundle a collection of such tools for easy installation, > and (b) what tools might be good candidates for inclusion. Here are > the ones that I've used across a variety of 'nix systems; I don't > claim that this list is the best or most inclusive or anything, it > just happens to be the toolset that I've found lets me deal with > most of the things I've had to deal with. > > curl We ship wget in standard, which is close enough in functionality that I don't think two tools make sense. > dig (part of the BIND distribution) We ship both dig (dnsutils) and host (bind9-host) in standard. > lslk This sounds potentially useful, but is in universe and abandoned upstream. Doesn't lsof provide this functionality? > lsof > mutt Both in standard. > nmap This is in main, but we don't install it by default. A scanner probably doesn't belong in every installation. > patch This doesn't seem to be in standard, though I'm somewhat surprised that nothing in there pulls it in through a dependency. I think it's a good candidate for the server seed. > rsync standard > screen This is in desktop, not standard. A good candidate for the server seed. > surfraw (I *said* I was ancient-school) No comment. :-) > tcpdump > top Both standard. > traceroute We ship tracepath by default, which isn't setuid. traceroute is in main, though, since so many folks are more familiar with it. > w3m Currently in standard, and the subject of this thread. > wget Standard. -- - mdz -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: Moving w3m out of standard
On Tue, Jun 17, 2008 at 02:05:09PM -0400, Bud Roth wrote: > I agree with Dustin's point. When an install goes flawlessly, a text > web browser may be superfluous, but when things go crunch and your > laptop is not handy, a text web browser is a quick way to find solutions > on the Internet. Sometimes, it can be as simple a need as looking up a > VMWARE key or making sure that the server's Apache server is serving > pages. Wget doesn't really fit the bill. Some form of text web browser > should be easily apt-gettable... This discussion has no bearing at all on whether a text web browser is apt-gettable. There are already three of them in main (w3m, links, elinks), and even if w3m were moved out of main, it would still be apt-gettable. My proposal has only to do with removing it from the default installation on desktops. -- - mdz -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: Moving w3m out of standard
On Mon, Jun 16, 2008 at 09:38:41PM -0700, Steve Beattie wrote: > On Mon, Jun 16, 2008 at 03:31:46PM +0100, Matt Zimmerman wrote: > > * w3m# we need some text-based html presenter > > > > I'd like to formally cast doubt on this statement from the standard seed. > > This was originally added a long time ago in order to provide a text-based > > browser for use on servers, at a time when the default server installation > > was a strict subset of the desktop. It is completely superfluous on a > > modern desktop. > > > > Now that this is becoming possible with the new server seed[1], I'd like to > > propose that it move to the server seed instead (or even be removed, if the > > server team doesn't feel it's appropriate). > > > > Note that wget, which is much smaller, simpler and more generally useful > > (e.g. in scripts) is already in standard. > > I have no opinion as to where in the seeds w3m exists, so long as I can > apt-get install it somehow on my apparently archaic desktop, where it > is not superfluous at all. The seed lists determine which packages are included in the 'main' component, from which the official CDs and other end products are built. They don't affect which packages are available for download, and I'm certainly not suggesting that w3m should be removed from Ubuntu. > But do note that wget, curl et al serve slightly different purposes > than w3m, lynx, elinks et al in that the latter do interpretation and > presentation of html, not merely just pulling it from the network. For > example, I use a text based email client and I use "w3m --dump" in my > mailcap entry[0] to handle html email, so that I can read and respond to > the processed output, not the raw html. It's particularly effective for > handling html email that contains tables in it, especially if you need > to address in your reply to said email specific elements within tables > and wish to comment inline. I use both regularly and understand the difference; again, no one will prevent you from using w3m regardless of its seed status. :-) -- - mdz -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: Moving w3m out of standard
On Mon, Jun 16, 2008 at 10:30:01AM -0500, Dustin Kirkland wrote: > But I do see a distinct difference between w3m/lynx/elinks and > wget/curl. The latter are useful for scripting the downloading of > files/content and then acting on it. The former are more interactive, > and allow for web searching, following links, reading pages. Since you're the second person to respond this way, I must not have been clear enough in my original email. I did not mean to say that wget provides the same functionality as w3m. I only wanted to remind everyone that, even if w3m is removed from the default install, there are other tools which implement the relevant protocols for accessing web content non-interactively, and I don't think that should change. > We can debate whether an interactive text browser belongs in the > default server seed, or if we simply document how to install and use > it in the Server Guide. I'd like to see an interactive web browser > remain on the server, though. I defer to the server team on this point; my main concern is with removing it from standard. Note that this saves a megabyte or so on the CDs, and every bit helps. -- - mdz -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Moving w3m out of standard
* w3m# we need some text-based html presenter I'd like to formally cast doubt on this statement from the standard seed. This was originally added a long time ago in order to provide a text-based browser for use on servers, at a time when the default server installation was a strict subset of the desktop. It is completely superfluous on a modern desktop. Now that this is becoming possible with the new server seed[1], I'd like to propose that it move to the server seed instead (or even be removed, if the server team doesn't feel it's appropriate). Note that wget, which is much smaller, simpler and more generally useful (e.g. in scripts) is already in standard. [1] https://wiki.ubuntu.com/UDS-Intrepid/Report/Server#head-27b6797bcec023c8714310edd0947ee48caaa8f2 -- - mdz -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
