[no subject]
Hi -I am trying to install an adobe flash plugin to my ubuntu program but a window keeps coming up saying that I need a password to grant administrative rights.How do I get this password??? Chris Jackson -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Announcing the Next Ubuntu Hug Day! - Thursday 25 June 2009
unsuscribe From: Pedro Villavicencio Garrido To: ubuntu-bugsq...@lists.ubuntu.com; ubuntu-devel-annou...@lists.ubuntu.com Sent: Tuesday, June 23, 2009 11:38:11 PM Subject: Announcing the Next Ubuntu Hug Day! - Thursday 25 June 2009 Fellow Ubuntu Triagers! This week's HugDay target is *drum roll please* Banshee! * 29 New Bugs need a hug * 21 Incomplete Bugs need a status check * 19 Confirmed Bugs need a review * 1 Bug with Patch to be checked * 2 Bugs to be forwarded upstream Bookmark it, add it to your calendars, turn over those egg-timers! * Thursday 25 June 2009 * https://wiki.ubuntu.com/UbuntuBugDay/20090625 Can't stress it enough: everyone can help! Have some time? Triage boogz! I won't be upset if you get a headstart~ ;) Have a blog? Blog about Hugday! Have some screen space? Open #ubuntu-bugs and keep an eye out for newcomers in need. Have minions? Teach THEM to triage for you! :) Wanna be famous? Is easy! remember to use 5-A-day so if you do a good work your name could be listed at the top 5-A-Day Contributors in the Ubuntu Hall of Fame page! Make a difference; we will be in #ubuntu-bugs (FreeNode) all day and night, and will be ready to answer your questions about how to help. If you're new to all this, head to http://wiki.ubuntu.com/Bugs Have a nice day, pedro. -- ubuntu-devel-announce mailing list ubuntu-devel-annou...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Ubuntu Studio meeting 26 of June 09 (01:00am UTC)
On Tue, Jun 23, 2009 at 1:46 PM, Luis de Bethencourt wrote: > Hello everybody, > > We are holding a Ubuntu Studio meeting the Thursday 26 of June 2009, > at 01:00am UTC (that is the night of the 25 to the 26). > Everybody is invited. > > Members and Developers of the Ubuntu Studio team _must_ attend. > Users are suggest to do so :) > > Luis de Bethencourt > > -- > Luis de Bethencourt Guimerá > luisbg > > GPG: B0ED1326 > Luis, I believe you've forgotten to mention where. If I recall, you had mentioned it's going to be in the #ubuntu-meeting IRC chat room. -Eric -- ___ http://greyrockstudio.blogspot.com -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
How to make non-interactive kernel packages using make-kpkg?
[ubuntu-devel-discuss bcc'd]
Hello everyone,
I am interested in doing some kernel development and testing, which means a
lot of patching and packaging of kernels. I'm pretty used to the manual way
of patching a kernel, configuring, and installing it but for my current
project this process must be 100% non-interactive. For the most part
make-kpkg (from kernel-package) has made this a breeze, but I still seem to
be getting some undesired interactions (nag screens) when I try to install a
kernel that is rolled with make-kpkg.
Before I go on with details about my make-kpkg endeavors, I'm also
interested in knowing more about how Ubuntu does this, since it could be
that I'm simply going about this the wrong way. I was unable to find
thorough documentation on Ubuntu or Debian's release process for kernels, so
any pointers would be greatly appreciated.
Here's an example how my simple shell script calls make-kpkg:
cd /usr/src
apt-get source linux-source-2.6.30
cp test.config linux-2.6.30/.config
cd linux-2.6.30
make-kpkg clean
MAKEFLAGS="CONCURRENCY_LEVEL=2" \
setarch i386 make-kpkg \
--append-to-version="-custom" --revision="123" \
--arch="i386" \
--rootcmd fakeroot \
--config oldconfig \
--initrd --bzImage kernel_image
...and off it goes. Eventually a .deb file appears in the parent directory.
And then I try to install it (using dpkg -i) and am prompted to abort due to
pre-existing modules for my kernel version (in spite of clobber_modules =
yes and silent_modules = yes) or installation of an initrd/initramfs kernel
(in spite of do_initrd = yes and warn_initrd = no) or lack of a vmlinuz link
in a pristine environment (in spite of do_symlinks = yes). I have my
/etc/kernel-{img,pkg}.conf files below for further scrutiny, but needless to
say I am a bit confused as to why I am prompted when I explicitly configure
make-kpkg to package the kernel in such a way as to omit those kinds of
warnings.
I should also note that I do not have a ~/.kpackage directory or any special
environment variables that would override the settings in the .conf files.
My /etc/kernel-img.conf:
# Kernel image management overrides
# See kernel-img.conf(5) for details
link_in_boot = yes
do_symlinks = yes
minimal_swap = yes
clobber_modules = yes
warn_reboot = no
silent_modules = yes
silent_loader = yes
# don't try to update the bootloader
do_bootloader = no
# prevent any warnings about installing an initrd kernel
do_initrd = yes
warn_initrd = no
My /etc/kernel-pkg.conf:
# Kernel package management overrides
# See kernel-pkg.conf(5) for details
# This file is used by kernel-package (>2.0) to provide a means of the site
# admin to over-ride settings in the distributed debian/rules. Typically
# this is used to set maintainer information, as well as the priority
# field. However, one may hack a full makefile in here (you should
# really know what you are doing here if you do that, though)
# Please change the maintainer information, as well as the Debian version
# below, (and maybe the priority as well, especially if you are uploading
# an official package)
# The maintainer information.
maintainer := Nobody
email := nob...@nowhere
# Priority of this version (or urgency, as dchanges would call it)
priority := Low
link_in_boot = yes
kimage = bzImage
root_cmd = fakeroot
do_clean = yes
I'd appreciate any advice on using make-kpkg to make kernel packages which
are non-interactive. If there are some example configurations out there, I'd
love to know. Thanks!
--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re:
On gio, 2009-06-25 at 19:33 +1000, chris jackson wrote: > > > > > Hi -I am trying to install an adobe flash plugin to my ubuntu program > but a window keeps coming up saying that I need a password to grant > administrative rights.How do I get this password??? Chris Jackson > > Hi Chris this is the wrong mailing list, the support mailing list is ubuntu-users, not ubuntu-devel-discuss. However the solution to your problem is simple: you need to use *your own* password; this will work if your user is an administrator of the machine, which surely happens for the user you create during installation. If you did not install ubuntu just ask who installed it. You can also install flash only for your user if the administrator can't be contacted, just go to the adobe web site and follow instructions for linux instead of using the automated system for firefox, which tries to install flash for all users. Vincenzo -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: That upstart Upstart
On Mon, 2009-06-29 at 16:11 -0500, Patrick Goetz wrote: > Everyone knows the canonical (no pun intended) unix interview question, > namely > > Q: how many processes does the kernel start on boot? > A: Only one -- init > > Apparently this isn't necessarily true any more, or soon won't be? > In the literal sense, it's still true. Once the kernel initialisation has completed, it runs the /sbin/init executable on the root filesystem. It's up to this executable to run all of the other processes on the system. When using System V init, this /sbin/init binary is provided by the sysvinit package. When using Upstart, this binary is provided by the upstart package. While they have different configuration and operation, they are still fundamentally a single binary from which all other processes are spawned. Now, I said literal sense, because on a modern system that's not entirely true. This has nothing to do with Upstart, but simply the way that Linux has evolved. Firstly the root filesystem's /sbin/init is rarely the first process started these days. Instead the /init executable inside a boot-loaded supplied "initial ram filesystem" (initramfs) is actually run; this is then responsible for mounting to the root filesystem, and the final thing it does is exec /sbin/init itself. Thus the new /sbin/init on the root filesystem still has pid #1. Secondly, the kernel isn't just a monolithic processes these days but has many threads of operation. These threads are effectively processes being run inside kernel space, some are even userspace from all effective points of view other than the fact they were spawned by the kernel. Many of these are spawned before init is actually started, but the kernel takes care to assign them pids beginning 2. Thirdly the kernel itself will spawn userspace processes directly itself; the original example of this is that the kernel will execute /sbin/modprobe itself if you open a device node that has no attached driver (passing a magic alias along the lines of char-major-123-4). Other examples are the defunct /sbin/hotplug tool, and apport which is run when a process core dumps. Since these are executed out the kernel, they fall outside of the "everything is run by init" model. > So, this brings us to upstart, the init replacement. After a couple of > days of looking through both the on-line documentation I could find > (http://upstart.ubuntu.com/getting-started.html) and the actual > installed files I find that I still have more than a number of > questions about how this is supposed to work currently and in the > future, as alluded to in this snippet from something posted to one of > the ubuntu devel lists: > > > > Date: Fri, 26 Jun 2009 14:55:16 -0500 > > From: Robbie Williamson > > Subject: Debian/Ubuntu Boot Performance Sprint Summary > > Scott James Remnant stated that he expects to have the > entire Ubuntu boot sequence transitioned over to upstart > by 10.04, with some work already planned for the 9.10 cycle. > - > Great! Always happy to answer any questions about it! :-) > Questions: > 1. the previously referenced site says that jobs files are placed in > /etc/init/jobs.d; actually, they seem to be in /etc/event.d -- what's up > with that? > Upstart is in heavy development, and things are subject to change until 1.0 is out. Once that happens, it'll all be stable and compatible, but up to that point I would rather get things right than be bound to not change things. The document you're reading is from the upstream site, and thus actually documents a later version of Upstart (0.5) than is currently in Ubuntu (0.3) I should probably point out that the next version (0.6) uses a different location again. These location changes generally come with a job format change, so it does actually make migration easier. Why the change at all? /etc/event.d was causing a lot of confusion, people started to think that jobs were events - when the two are quite different. The original reason for using /etc/event.d was that it fitted the /etc/dbus-1/event.d naming for "things run on events". Future versions will just use /etc/init > 2. > lizard:~~$ which init > /sbin/init > lizard:~~$ dpkg -S /sbin/init > upstart: /sbin/init > > So, I'm confused: is init still being used, or what? > Yes. Upstart is an implementation of /sbin/init, thus the binary it installs is still called /sbin/init (since that's what the kernel runs). --version reveals all here: 8<8<8<8<8<8<8< littlebigplanet scott% /sbin/init --version init (upstart 0.6.0) Copyright (C) 2009 Canonical Ltd. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. >8>8>8>8>8>8>8 > /etc/inittab no longer exists in 9.04/9.10, and the job
Re: That upstart Upstart
On Tue, 2009-06-30 at 02:56 +0100, Colin Watson wrote: > On Mon, Jun 29, 2009 at 04:11:53PM -0500, Patrick Goetz wrote: > > Doesn't this mean that rcS is stopped before /etc/init.d/rcS is ever > > exec'd, since the runlevel is set before the script is run? In > > particular, when exactly does the runlevel event stop the script? > > I think the 'stop on runlevel' is actually just there to make sure rcS > doesn't keep on trying to start, but Scott could clarify that. > The rcS script might run a root shell (sulogin, usually) in cases of error - the filesystem check failing is a good example here. The user might type "shutdown" at this shell. Or the user might simply press Ctrl-Alt-Delete while rcS is running. The "stop on" therefore makes sure it's all killed so the system can run the shutdown scripts. > (For the avoidance of doubt, this isn't me arguing that the job format > shouldn't be better documented, but rather that if you're searching for > documentation because you want to write Upstart jobs and use them in > production rather than because you want to help with development, you > may be on the wrong track just now.) > Indeed, the lack of detailed documentation is /slightly/ deliberate ;-) Scott -- Scott James Remnant sc...@canonical.com signature.asc Description: This is a digitally signed message part -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Mono Position Statement
The Ubuntu Technical Board has been asked for a position statement on the use of C#, specifically the Mono implementation, by applications in Ubuntu. These applications, as well as the Mono stack, were proposed for inclusion like any other application and underwent the same review process that all new applications and platforms undergo before being accepted into the archive. With specific regard to the default installed application set, applications have been reviewed and compared against each other on merit and features. These often take place during the Ubuntu Developer Summits, most recently over the default media player. A common concern cited about Mono is the patent position, largely it seems due to the originator of the C# language and associated ECMA standards. The Ubuntu Project takes patent issues seriously, and the Ubuntu Technical Board is the governance body that handles allegations of patent infringement. The Ubuntu Technical Board strives to engage with rights holder openly in terms of the code that we ship. If a rights holder claims a patent infringement applies to said code, the Technical Board will commit to a review of the claim. The Ubuntu Technical Board has received no claims of infringement against the Mono stack, and is not aware of any such claims having been received by other similar projects. It is common practice in the software industry to register patents as protection against litigation, rather than as an intent to litigate. Thus mere existence of a patent, without a claim of infringement, is not sufficient reason to warrant exclusion from the Ubuntu Project. (While the Ubuntu project wishes to be responsive to patent infringement claims, we cannot commit to the assessment and review of claims made by anyone other than the registered rights holder.) Given the above, the Ubuntu Technical Board sees no reason to exclude Mono or applications based upon it from the archive, or from the default installation set. Since the Mono stack is already a dependency of the default installation set for many remixes of Ubuntu, including the Desktop Edition, there is no reason to consider a dependency on Mono as an issue when suggesting applications for the default set. (Other remixes may obviously consider the CD Size implications if an application would introduce the Mono platform to the set.) Scott on behalf of the Ubuntu Technical Board -- Scott James Remnant sc...@ubuntu.com signature.asc Description: This is a digitally signed message part -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: gparted, ubiquity and other packages left behind by karmic a2 installer
On Mon, Jun 29, 2009 at 8:39 PM, Colin Watson wrote: > (It's surprising that you apparently didn't see a dialog informing you > that the installer had crashed. It must have gone down pretty hard.) Yup. I had no idea that it crashed until you just told me :) the same thing occurred both times I installed alpha 2 on this machine. By the way, is it preferred, in general, that I ask on this list prior to reporting perceived bugs (in the dev branch)? Or, is it better to enter things as bugs and keep the noise off the list? -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: gparted, ubiquity and other packages left behind by karmic a2 installer
On Tue, Jun 30, 2009 at 11:27:02AM -0400, Nathan Dorfman wrote: > On Mon, Jun 29, 2009 at 8:39 PM, Colin Watson wrote: > > (It's surprising that you apparently didn't see a dialog informing you > > that the installer had crashed. It must have gone down pretty hard.) > > Yup. I had no idea that it crashed until you just told me :) Interesting. That's a rather curious bug in itself. > By the way, is it preferred, in general, that I ask on this list prior > to reporting perceived bugs (in the dev branch)? Or, is it better to > enter things as bugs and keep the noise off the list? It's OK to ask here, but really, if you reckon something is a bug it's best to cut out the middle man and just report it as a bug. Which of them gets quicker attention depends a bit on the habits of the developers involved, but if it's a bug then chances are somebody is going to suggest that you file it anyway. -- Colin Watson [cjwat...@ubuntu.com] -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
