Re: Bugs for NM 0.7
On Mon, Sep 08, 2008 at 10:44:49AM +0100, Matthew Garrett wrote: On Mon, Sep 08, 2008 at 11:31:07AM +0200, Alexander Sack wrote: On Mon, Sep 08, 2008 at 12:26:50AM +0100, Matthew Garrett wrote: To be fair to NM, this is a Debian/Ubuntu integration issue. System-wide configuration is present but requires a system-specific backend. NetworkManager has a distro independent system-wise backend called keyfile. And thats enabled by default in ubuntu. What isnt enabled by default yet is the legacy backend for /etc/network/interfaces, but that isnt the problem this is about afaict. The thread was discussing the removal of network-admin - doesn't that modify /etc/network/interfaces? Yes it does that atm. But if network-admin is still wanted in the long run - it could also write keyfile system configurations. - Alexander -- 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: Bugs for NM 0.7
On Mon, Sep 08, 2008 at 11:51:59AM +0200, Alexander Sack wrote: On Mon, Sep 08, 2008 at 10:44:49AM +0100, Matthew Garrett wrote: The thread was discussing the removal of network-admin - doesn't that modify /etc/network/interfaces? Yes it does that atm. But if network-admin is still wanted in the long run - it could also write keyfile system configurations. Right, but I believe the issue is that without network-admin there's no graphical means of configuring the legacy networking interface. -- Matthew Garrett | [EMAIL PROTECTED] -- 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: Bugs for NM 0.7
On Mon, Sep 08, 2008 at 10:53:42AM +0100, Matthew Garrett wrote: On Mon, Sep 08, 2008 at 11:51:59AM +0200, Alexander Sack wrote: On Mon, Sep 08, 2008 at 10:44:49AM +0100, Matthew Garrett wrote: The thread was discussing the removal of network-admin - doesn't that modify /etc/network/interfaces? Yes it does that atm. But if network-admin is still wanted in the long run - it could also write keyfile system configurations. Right, but I believe the issue is that without network-admin there's no graphical means of configuring the legacy networking interface. The upload hopefully coming today will have a more or less well working /e/n/i backend, which is read-only. You can enable it by enabling the ifupdown plugin in /etc/NetworkManager/nm-system-settings.conf So please test that and report network-admin managed use-cases that dont work. - Alexander -- 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 Ubuntu Manpage Repository
Olá Dustin e a todos. On Saturday 06 September 2008 01:10:43 Dustin Kirkland wrote: * http://manpages.ubuntu.com It is funny to find kernel man in games http://manpages.ubuntu.com/search.py?title=kernel man pages dapper 6.06 LTSfeisty 7.04gutsy 7.10hardy 8.04 LTSintrepid 8.10 . . . . . (1) - Executable programs or shell commands . . . . . (2) - System calls (functions provided by the kernel) . . . . . (3) - Library calls (functions within program libraries) . . . . . (4) - Special files (usually found in /dev) . . . . . (5) - File formats and conventions eg /etc/passwd kernel(6) kernel(6) kernel(6) kernel(6) kernel(6) (6) - Games -- BUGabundo :o) (``-_-´´) http://LinuxNoDEI.BUGabundo.net Linux user #443786GPG key 1024D/A1784EBB My new micro-blog @ http://BUGabundo.net ps. My emails tend to sound authority and aggressive. I'm sorry in advance. I'll try to be more assertive as time goes by... 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: Bugs for NM 0.7
On Mon, Sep 08, 2008 at 11:31:07AM +0200, Alexander Sack wrote: On Mon, Sep 08, 2008 at 12:26:50AM +0100, Matthew Garrett wrote: To be fair to NM, this is a Debian/Ubuntu integration issue. System-wide configuration is present but requires a system-specific backend. NetworkManager has a distro independent system-wise backend called keyfile. And thats enabled by default in ubuntu. What isnt enabled by default yet is the legacy backend for /etc/network/interfaces, but that isnt the problem this is about afaict. The thread was discussing the removal of network-admin - doesn't that modify /etc/network/interfaces? -- Matthew Garrett | [EMAIL PROTECTED] -- 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: Boot sequence profiling on first boot
Am 08.09.2008 um 01:05 schrieb Marcin 'Qrczak' Kowalczyk: 2008/9/8 Wouter Stomp [EMAIL PROTECTED]: I just tried the effect of profiling the boot sequence by adding profile to the kernel line in grub, and the effects were amazing! From 1:21 (average of 3 boots) to 58 seconds (again average of 3). I tried it and the speedup was only from 0:37 to 0:34. The system has a month and a half. I don't know much about the boot profiler, but likely, it can influence the time between kernel loading and starting X11 only. On my machine, a fairly recent dual core desktop, most time is used on the other parts: the vendor's BIOS screen, Grub waiting a few seconds for possible user input, X11 and Gnome launching. Nevertheless, a gain of a few seconds is great, considering the boot sequence (hopefully) remains stable and it's a gain on each of millions of computers. MarKus - - - - - - - - - - - - - - - - - - - Dipl. Ing. Markus Hitter http://www.jump-ing.de/ -- 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: Bugs for NM 0.7
On Mon, Sep 08, 2008 at 12:26:50AM +0100, Matthew Garrett wrote: On Sun, Sep 07, 2008 at 10:27:10PM +0300, Peteris Krisjanis wrote: Btw, I haven't seen that system wide configuration on OpenSUSE and Fedora. I would like to see it in action. So far I am very nervous about ditching network-admin, because no matter how it was stuck in development, or it lacked features, it worked, it had over the distros feel and so far Network Manager has been let's repeat PulseAudio all over the place. There should be very good network-admin and NM integration or at least NM should heavily improve their configuration dialogs and menus. Otherwise I still suggest to leave network-admin and work on NM to improve it to get it finally worthy to ditch good old g-s-t tool for good. To be fair to NM, this is a Debian/Ubuntu integration issue. System-wide configuration is present but requires a system-specific backend. NetworkManager has a distro independent system-wise backend called keyfile. And thats enabled by default in ubuntu. What isnt enabled by default yet is the legacy backend for /etc/network/interfaces, but that isnt the problem this is about afaict. - Alexander -- 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-devel-discuss Digest, Vol 22, Issue 5
i got the same situtation with you,when i want to compile the kernel of ubuntu server 8.04, i found that #apt-get install source-code cannot fetch the kernel source-code. so i download the kernel from www.kernel.org, i just cannot find the compared version of kernel,i compile it anyway.and i have my new kernel ,which is unable to start the system. 在2008-09-03 19:00:[EMAIL PROTECTED] 写道： Send Ubuntu-devel-discuss mailing list submissions to ubuntu-devel-discuss@lists.ubuntu.com To subscribe or unsubscribe via the World Wide Web, visit https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss or, via email, send a message with subject or body 'help' to [EMAIL PROTECTED] You can reach the person managing the list at [EMAIL PROTECTED] When replying, please edit your Subject line so it is more specific than Re: Contents of Ubuntu-devel-discuss digest... Today's Topics: 1. Re: PackageKit: Call for testing (Sebastian Heinlein) 2. Re: Bugs marked incomplete (Sarah Hobbs) 3. Re: Intrepid compatibility with C3 CPUs (( ``-_-?? ) -- Fernando) -- Message: 1 Date: Wed, 03 Sep 2008 08:08:42 +0200 From: Sebastian Heinlein-- 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: Re:Ubuntu-devel-discuss Digest, Vol 22, Issue 5
On Mon, 2008-09-08 at 22:49 +0800, mydebian wrote: i got the same situtation with you,when i want to compile the kernel of ubuntu server 8.04, i found that #apt-get install source-code cannot fetch the kernel source-code. so i download the kernel from www.kernel.org, i just cannot find the compared version of kernel,i compile it anyway.and i have my new kernel ,which is unable to start the system. When replying from a digest, it helps if you specify (or quote) which topic you're replying to, but anyway... apt-get source linux should, I think, get the kernel source -- Mackenzie Morgan http://ubuntulinuxtipstricks.blogspot.com apt-get moo 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: feedback on new wiki theme
On Mon, Sep 08, 2008 at 05:45:42PM -0500, Matthew Nuzum wrote: I disagree - the problem with fixed width is that at some point we have to make assumptions as to the screen size used to access as well as how the reader wants to read the information. I feel that these both should be left to the reader not pre-defined by the writer. snip Sometimes I see a fixed-width page and I just feel like it looks so lonely sitting there in the middle of such wide margins to either side. Especially on a single column site like this one. But when I stop looking at the design of the site and just start using it I like it much better. The narrow column width really pulls you into the site's content. (and seriously, its not that narrow with a content width of 820px and a column width of 875px) I've used this theme for a bit now and browsed many different pages and feel that the it works very nicely on a content-heavy page. I've maximized my browser window (1280x800) to hopefully get a taste of the pain experienced by people who use their browser this way typically and honestly I think that overall its an improvement. It is common to focus on a fixed width design as narrow, but for many users the big issue is that it is fixed. On a wide page it looks narrow, but on a narrow page it is nearly unusable since it is wider than the window, and requires using the horizontal scroll bar to read each line. As others have mentioned, the fact that the user can't control the width of the content is the real issue, and the reason fluid designs are very popular. This is of course famously a problem for folks with narrow screens (e.g. handheld computers). But it is also often a problem for folks with big screens. E.g. I often use the very practical info in a wiki interactively, looking back and forth between a narrow web page on the left and a terminal window on the right, and wanting as much material, and page height, as I can get. A fixed design thwarts that plan. So as earlier posters have said, what is wrong with keeping the fluidity of the current design, letting the user choose how wide to make their browser window, and thus how long their lines of text should be? The rest of the design can match ubuntu.com, where graphics and other design considerations can be an issue, but for a wiki, I think fixed-width is the wrong choice. Neal McBurnett http://mcburnett.org/neal/ -- 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
The Case For Re-Evaluating Our Release Approach To FFMPEG
Gday everyone, It was suggested to me on IRC that I should discuss this matter on this mail list. Summary : I think we need to have regular snapshots of svn ffmpeg, libavcodec and so forth released in both the current development build and as backports to production builds. User's expect to have video experiences atleast as good as Windows and Mac, and this is necessary for actually delivering that. My argument : To be honest my original approach with meeting my video needs on Ubuntu was to turf out the default apps and do my own custom compiles of mplayer, mencoder and gnome-mplayer. This continues to work well and frankly is still superior to what I can do under gstreamer and totem (such as deinterlacing and other video filters). However I felt guilty about doing this because I was not supporting the Ubuntu principle of having one standard method for doing things and I was restricting the value of my testing work I do on Ubuntu by not using default applications in all circumstances. So some time ago I bit the bullet, committed myself to using default apps and leaving mplayer for any related tests. I am thankful for Sebastien's updates to the gstreamer good and ugly plugins recently, as well as the updates Intrepid has received with Totem. However, the ffmpeg gstreamer plugin is a key plugin for most user's multimedia experiences. It provides to gstreamer: * 256 elements * 39 types Of particular note amongst these many features is that some very common video formats are used by gstreamer, such as AVC / H.264 decoding. AVC is one of the formats that is gaining much momentum with it being widely used in BluRay, HDDVD, some Digital Video Broadcasters and as an efficient backup format for personal media. As a subscriber to the ffmpeg commit mailing list I know that in the past months there has been substantial improvement to the code for AVC decoding and the resolution of many related bugs. AVC is just one decoder that ffmpeg handles out of many decoders that has had many bug fixes in the past months. Since gstreamer released a new ffmpeg plugin I have been enthusiastic to see this arrive into Ubuntu and have Intrepid enjoy the more reliable video experience this would offer our users. I'm advised though that what is needed is to upgrade ffmpeg and related libraries across the board to deliver the new gstreamer plugin. Upgrading ffmpeg across the board would also give benefits to more advanced Ubuntu users, whom for example maybe conducying video transcoding via libavcodec. They wont need to suffer known bugs with old ffmpef builds. I want to note how the FFMPEG project manages releases: * They dont do them * Their standard response in reporting bugs is to compile SVN and retest. What seems to happen in practice for FFMPEG in Ubuntu is that it rarely is updated - Intrepid's packages are currently seven months old. On an upstream project that has numerous commits daily. I feel bad for our users because I see bug reports on Launchpad that I know is never going to go anywhere because ffmpeg currently isnt kept up to date and is not backported for their build. Anyone who has a passing observation of the situation has to agree this is not ideal. I contend the risk of having old binaries in the repos and all the problems that brings with poor user experiences outweighs the risk that new code will bring new problems. My practical experience of doing my own compiles of SVN head has consistently been things are fixed and enhanced. On one occasion I had a problem where the code would not compile and on another a bad commit occurred, which effected functionality, but that was fixed in half a day and I simply recompiled. Upstream strive for the SVN build to be fully functional and in my experience thats meet on nearly all occasions. My skills are not in packaging, but I can certainly assist with testing and helping construct a freeze exception rationale for Intrepid. Please consider. -- 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
