Re: New Maintainer for MC Project
Pavel, Below is your note posted today. Below that the full text of the letter, and response, to which you refer, with key sections highlighted and numbered. Programmers can read - I'll let them draw their own conclusions. A conversation is proposed regarding the project, the Midnight Commander project. The project your quoted comment was discussing. I clearly state that the Krew does not agree with some of the remarks on the Lists and elswhere that Midnight Commander be scrapped, and an entirely new program be written. The we feel Midnight Commander is just fine and can have a bright future with the right leadership. Again, the offer is reiterated, with the sole goal of keeping the MC Project viable. This is the only thing we ever proposed. My note of June 4, 2005, posted in full on this list, reiterated yet again this fact, and asked specifically if you understood that we were not interested in writing a new application, or a branch of the existing MC, but were offering help to the existing MC Team to continue to work on their project in a pleasant and stable environment. Why you now try and say we were, in essence, trying to scavange MC Developers away from the existing project to create a new one I cannot know - but the message traffic shows this in just not so. In my next note, I underscored this fact (note already posted in full below) saying: Regarding a fresh start, if it was our desire to compete with MC, we would have already released our product - this is not our wish. Our wish is to try and save a distressed project that we all regard highly and support. We are MC users, too. From what I see in your forums, you don't need new developers, your developers just need to see their work used by MC users. New developers are not the answer, new leadership is the answer. My note of June 1st also emphasizes that point, full message below. In the sentence marked 1), you acknowledge that you understand that we are talking about giving the current MC Project a home, and no other. No new project, No fork, THE MC Project. That was the offer from the start, and nothing else. Please stop mis-characterizing what I communicated in my messages. The notes speak for themselves. Terry Subject: Re: Awaiting your replyFrom: Pavel Roskin [EMAIL PROTECTED]To: Fudoki [EMAIL PROTECTED]In-Reply-To: [EMAIL PROTECTED]References: [EMAIL PROTECTED]Content-Type: text/plain Content-Transfer-Encoding: 7bitDate: Wed, 01 Jun 2005 20:38:34 -0400Message-Id: [EMAIL PROTECTED]Mime-Version: 1.0X-Mailer: Evolution 2.2.2 (2.2.2-5) Hello, Terry!On Wed, 2005-06-01 at 13:52 -0400, Fudoki wrote: Pavel, The leaders of the Krusader Krew have decided that we should wait a few days before directly posting our offer on the Midnight Commander Forums to give you an opportunity to respond to my last letter. I see the wisdom of this, and will not be posting to the MC Forums until you have had time to get back to us with your position on the MC Team becoming a part of the Krusader Project.1) *Sorry, I didn't realize that the question was about MC Team becoming a part of the Krusader Project. I cannot answer on behalf of anyoneexcept myself. I may join if I have time, but I'm not very optimistic.*If you are going to create a mailing list, please feel free to subscribe me. I'll unsubscribe if I have to.Our leadership wants to be certain that your feelings on this matter receive the consideration they deserve. Please let me know when you get a chance. Thanks! My feeling is that it would be nice to have a file manager with amaintainable codebase. I don't think anyone would object (maybe exceptcompeting projects).-- Regards,Pavel Roskin From: Pavel Roskin proski gnu orgTo: Fudoki sekhmet_616 yahoo comCc: mc-devel gnome orgSubject: Re: New Maintainer for MC Project Date: Tue, 07 Jun 2005 17:57:53 -0400 Hello!Sorry, I should have answered this long ago.On Sat, 2005-06-04 at 05:58 -0700, Fudoki wrote: Greetings All! My name is Terry Wilkinson and I am on the Docs Team and also am the Public Relations Coordinator for the Krusader File Manager Project (http://krusader.sourceforge.net/index.php). Our Team has been watching this list closely because most of us are regular MC users. I have also been talking to our leadership, and to Pavel Roskin, about offering to become the new Maintainer of the Midnight Commander Project, and Pavel has encouraged me to do so. This is not true. In fact, it tried to discourage you from attempts totake over the existing project.That's what I wrote you:Fresh start needs developers. If you have developers, you don't need to talk to me. Just start coding and show me your existing code if youwant me in your team.From another message:By the way, I think the new project shouldn't be called Midnight Commander.Either you misunderstood me or you are misrepresenting my words. Ineither case, I don't think you should take over the existing project.If you
Fwd: New Maintainer for MC Project
Part 2 of 2 Original Message Subject: Re: A new day for MC? Date: Thu, 26 May 2005 15:01:32 -0400 From: Pavel Roskin [EMAIL PROTECTED] To: Fudoki [EMAIL PROTECTED] References: [EMAIL PROTECTED] Hello! On Tue, 2005-05-24 at 19:01 -0400, Fudoki wrote: Dear Pavel, I am a longtime MC user and fan. I am also the PR Coordinator for the Krusader Krew. We are the project that makes the Krusader File Manager, so we understand all the issues and concerns you raise, firsthand. Been there, and are doing that. 1) *In reply to your suggestion that If someone else can take the responsibility for the project and make a release, I'm fine with it; the Krew has discussed your Project's current dilemma. All of us are MC users, and many of us use MC as much as we use our own Krusader (they have different areas of usefulness) - so we say this as not only as co-developers, but also as avid supporters, and loyal MC users: We would be willing to have a conversation with you, and your lead developers, about allowing your team to find a home in the Krusader Krew's project.* I'm not sure you really understand the problem. The problem is not with hosting or having a home. The problem is that I don't have enough time to deal with the project properly. This problem exists since January 2003. I'm struggling to reply to all personal e-mail I'm getting regarding the project. Right now, there are about 20 e-mails to reply in my queue. As for the mailing lists, there are hundreds e-mails I haven't seen since the last prerelease. This sort of defeats the purpose of prerelease because the feedback gets ignored. There are other developers doing some work, but I don't see anybody who could take over the project. Maybe we need more decentralization, but I don't think I could be the leading maintainer even in this case unless working on mc becomes my full-time job. The project requires a lot of expertize. Somehow I'm supposed to be able to evaluate Python syntax highlighting or issues with Tamil translation. Or I need people whose judgment I can trust. In any case, I need to be able to be reachable almost every day, and it's something I cannot promise. I cannot see how your project can help here. We can make your infrastructure and marketing problems go away literally overnight, and provide an environment where your team can focus on their work in a supportive and positive environment. Marketing problems? What do you mean? Maybe I just wasted my time explaining you the real problem? Best of all, we are all about file management and developing innovative new ways to deal with file management, so your needs and challenges are already well understood by us. 2) *Trying to forge a new project from the old, as some have suggested on your forums would only introduce further problems and, by itself, solve none. Yet some positive, affirmative, action must be taken for the good of all concerned.* Let's stick to technical terms here. What is forge? Do you mean rewriting the whole codebase or gradual cleaning of the existing code? 3) *If you feel that a fresh start would keep the MC Project viable, and facilitate the development process and morale of your team, let's talk. I believe you will find we have a lot in common, and a lot to offer.* Fresh start needs developers. If you have developers, you don't need to talk to me. Just start coding and show me your existing code if you want me in your team. We are deeply committed to the Open Source Movement, and would normally have posted this offer in open forum, but for several reasons, our leadership felt I should direct this offer to you first, to ensure fairness and as a courtesy. Please understand that we are in no way being secretive or using back channels. It's just that no useful purpose would be served by putting you on the spot; we want to help, not fuel the fire. I'll appreciate if you post in mc-devel@gnome.org. Please be more detailed in your proposal. The Krew extends it's support, encouragement, and if it is desired and would be helpful, our material assistance to keep what we consider a very worthy and worthwhile program that we value and use alive for years to come. I'm on H-1 visa in the USA until November 2005, and it doesn't allow me to be paid by anyone except my employer. You may be more successful hiring other developers in the meantime. --Regards, Pavel Roskin -- Original Message Subject: Re: A new day for MC? Date: Wed, 01 Jun 2005 03:29:24 -0400 From: Fudoki [EMAIL PROTECTED] To: Pavel Roskin [EMAIL PROTECTED] References: [EMAIL PROTECTED] [EMAIL PROTECTED] Dear Pavel, Thanks for the prompt
Re: New Maintainer for MC Project
Fudoki Wilkinson ! Hey, buddy, calmdown and move your ass away from this list, don't botherMC developers. With all your postings here Ican see that your behavior like a hysteric woman, which do not want to hear that ppl talking to her. Iloathe toppl which can't understand that others says to him. You got an answer - NO, so shut up and silently run away, if you still have remains of your self-respect of course ... ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [patch] avoiding casts of function pointers
Hello, On Tue, 7 Jun 2005, Oswald Buddenhagen wrote: On Tue, Jun 07, 2005 at 05:12:59PM +0200, Roland Illig wrote: This patch fixes the gcc warning about incompatible pointer types in widget.c. I is much more complicated than Jindrich's patch, but in return it is fully ISO C compliant. :) what an effort ... the simplest solution is making the functions that don't need a pointer just have a dummy parameter. that's typical for callbacks. Good point. Let's not fix warnings blindly. ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
RE: File exists: duplicate key accel; and a feature request
Beware of this, please. If you change it now you may break translations. --- On Wed 06/08, wwp < [EMAIL PROTECTED] > wrote: From: wwp [mailto: [EMAIL PROTECTED] To: mc@gnome.org Date: Wed, 8 Jun 2005 08:03:23 +0200 Subject: File exists: duplicate key accel; and a feature request Hi there!I've noticed a long standing duplicate accel when mc asks if a copied filehas to override an already existing one.The dialog's title is: File existsThe questions: Overwrite this target ? Y N A Overwrite all targets? A U N ISee how 'A' is twice possible.. but pressing A does the second one.BTW I would like to submit a feature request..When a file I/O error is encountered (several possible reasons as forinstance: not being able to set permissions when copying a file from ext2 tovfat, but it could be any read or write error), we get a Skip/Retry/Abortdialog. Would it be possible to add a [skip All] that would skip all furthererrors that match this one? That would be really user-friendly, IMO.Regards,-- wwp___Mc mailing listhttp://mail.gnome.org/mailman/listinfo/mcJoin Excite! - http://www.excite.comThe most personalized portal on the Web! ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Announcement of mc-4.6.1-pre4
Hello MC, I've created a new cvs tag MC_4_6_1_pre4 and deleted MC_4_6_1_PRE5A since it had a wrong version nunmber. I've created a new tarball based on MC_4_6_1_pre4 - it can be found here: http://pavelsh.pp.ru/mc/ Now, we need to inform all interested parties (translators, maintainers and news sites). -- Best regards, Pavel mailto:[EMAIL PROTECTED] ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
FW: RE: Announcement of mc-4.6.1-pre4
Ooops, sorry for the previous mail... I made a mess.. ___ Join Excite! - http://www.excite.com The most personalized portal on the Web! ---BeginMessage--- I recently localized a device numbers label which was left in src/info.c. Is it worth applying it (porting from HEAD to PRE4) to this release? It's already translated in HEAD for es.po and it.po. I could post the patch tonight from home. For the rest I tried yesterday and the Spanish translations seems to be up-to-date in the release tag. ___ Join Excite! - http://www.excite.com The most personalized portal on the Web! ---End Message--- ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Announcement of mc-4.6.1-pre4
Hi, On Wed, 2005-06-08 at 13:24, Pavel Shirshov (pchel) wrote: I've created a new cvs tag MC_4_6_1_pre4 and deleted MC_4_6_1_PRE5A since it had a wrong version nunmber. I've created a new tarball based on MC_4_6_1_pre4 - it can be found here: http://pavelsh.pp.ru/mc/ Now, we need to inform all interested parties (translators, maintainers and news sites). Could one of the maintainers please release this tarball as a release candidate? Give it a week or maybe to so downstream can verify their patch sets and we can stamp out the newly introduced bugs ;) . I think some of you would just want this to be released as 4.6.1 final immediately. I think that's a bad idea as it is bad practice. I would like to be sure no new bugs have been introduced in the frenzy of last week. Having a release candidate before the final release is also just good practice and having waited for half a year 1 or 2 weeks won't hurt that much :) . In the mean time we could work a little on the homepage(s). Are we going to use the wiki that Miguel set up? If so don't we need some style changes (nice sunflower, but hey, we're not wikipedia). And do we need to point Savannah and the Ibiblio homepage to the new home? Things like that. Leonard. -- mount -t life -o ro /dev/dna /genetic/research ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
RE: New Maintainer for MC Project
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fudoki WilkinsonSent: Tuesday, June 07, 2005 11:42 PMTo: MC Devel ListSubject: Re: New Maintainer for MC Project From: Fudoki Wilkinson [EMAIL PROTECTED]Date: Jun 8, 2005 12:32 AMSubject: Re: New Maintainer for MC Project To: Pavel Roskin [EMAIL PROTECTED]Greetings Pavel, On 6/7/05, Pavel Roskin [EMAIL PROTECTED] wrote: Hello!Quoting Fudoki Wilkinson [EMAIL PROTECTED]: This message was not answered by Pavel until until 6 June, after the offer of help had been withdrawn. Still, you didn't have my endorsement that you claimed you had."Go ahead" meant "post whatever you want to the list", not "take over theproject". All I have ever said is we were posting our offer to the mailing list with your permission amd blessing. I have never said you approved or did not approve of the offer itself. How could I - you never said? If you believe there is an example of me claiming you advocated approval of our offer, show it to me. It is not there, and you deliberately misrepresented what I said using two out of context lines. Not fair, or right. How about this quote from your June 4 2005 09:05:32 -0400 posting [quote] I have also been talking to our leadership, and to Pavel Roskin, about offering to become the new Maintainer of the Midnight Commander Project, and Pavel has encouraged me to do so. Pavel only wants what is best for Midnight Commander to be successful. [/quote] This clearly seems that you are saying that Pavel has already approved of your proposal. If you can't remember what you've written, please read the archives. That's what they are there for. Thanks, Ryan ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
cons.saver not suid root
moin, for some time now, cons.saver is not installed suid root any more, making the whole thing sort of pointless. the attached patch makes it useful for me. comments? -- Hi! I'm a .signature virus! Copy me into your ~/.signature, please! -- Chaos, panic, and disorder - my work here is done. --- Makefile.am.orig2005-06-08 16:30:58.0 +0200 +++ Makefile.am 2005-06-08 16:29:13.0 +0200 @@ -75,6 +75,8 @@ if USE_EDIT $(MAKE) install_mcedit endif + chown root:root $(pkglibdir)/cons.saver + chmod u+s $(pkglibdir)/cons.saver # # Make relative symlinks, but do the right thing if LN_S is `ln' or `cp'. ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: cons.saver not suid root
On Wed, Jun 08, 2005 at 04:35:16PM +0200, Oswald Buddenhagen wrote: moin, for some time now, cons.saver is not installed suid root any more, making the whole thing sort of pointless. the attached patch makes it useful for me. comments? cons.saver should not be setuid root, it should be setuid to whatever user owns /dev/vcsa* devices. Ideally there is a vcsa user that just owns these devices and cons.saver. Jakub ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: cons.saver not suid root
On Wed, Jun 08, 2005 at 04:40:14PM +0200, Jakub Jelinek wrote: On Wed, Jun 08, 2005 at 04:35:16PM +0200, Oswald Buddenhagen wrote: for some time now, cons.saver is not installed suid root any more, making the whole thing sort of pointless. the attached patch makes it useful for me. comments? cons.saver should not be setuid root, it should be setuid to whatever user owns /dev/vcsa* devices. Ideally there is a vcsa user that just owns these devices and cons.saver. yes, i'm aware of this. anyway, we have no portable (even across linuxes) way to create a vcsa user, so there is no other option than root. actually, this is what many other programs do. and if packagers can do better, i won't complain. i just want something that works out of the box. -- Hi! I'm a .signature virus! Copy me into your ~/.signature, please! -- Chaos, panic, and disorder - my work here is done. ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: cons.saver not suid root
Hi Jakub, Oswald, On Wed, 2005-06-08 at 16:40, Jakub Jelinek wrote: On Wed, Jun 08, 2005 at 04:35:16PM +0200, Oswald Buddenhagen wrote: for some time now, cons.saver is not installed suid root any more, making the whole thing sort of pointless. cons.saver should not be setuid root, it should be setuid to whatever user owns /dev/vcsa* devices. Ideally there is a vcsa user that just owns these devices and cons.saver. Please compare http://mail.gnome.org/archives/mc-devel/2005-January/msg00049.html . Leonard. -- mount -t life -o ro /dev/dna /genetic/research ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: cons.saver not suid root
Hello Oswald, On Wed, 2005-06-08 at 16:49, Oswald Buddenhagen wrote: yes, i'm aware of this. anyway, we have no portable (even across linuxes) way to create a vcsa user, so there is no other option than root. I'd rather have the downstream packagers fixing the device permissions and the accompanying user than suid-ing cons.saver root. That's just ugly. Leonard. -- mount -t life -o ro /dev/dna /genetic/research ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: cons.saver not suid root
On Wed, Jun 08, 2005 at 05:13:00PM +0200, Leonard den Ottolander wrote: On Wed, 2005-06-08 at 17:03, Oswald Buddenhagen wrote: and punish the upstream users, including ourselves? interesting. This issue can be easily fixed with package builds. suppose i prefer configure make stow ... I'd assume people that don't use a form packaging on their systems should be knowledgeable enough to read the docs and fix this issue by hand. How much effort is it to suid root the binary anyway if you really don't want to figure out how to setup the device access? are you kidding? do you really expect every new user to do a bughunt as the first thing? also, don't underestimate the usage rate of the upstream build system. it is the de-facto standard of installing 3rd-party unix software. ugly is this paranoia wrt just making it suid root. What about the concept of least necessary access? what about the concept of user friendliness? yes, there is a tradeoff. well, everywhere is. You ignore the possibility of eventualities in the future. what type of eventualities do you talk about? -- Hi! I'm a .signature virus! Copy me into your ~/.signature, please! -- Chaos, panic, and disorder - my work here is done. ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: cons.saver not suid root
On Wed, Jun 08, 2005 at 05:23:42PM +0200, Egmont Koblinger wrote: On Wed, Jun 08, 2005 at 04:35:16PM +0200, Oswald Buddenhagen wrote: --- Makefile.am.orig2005-06-08 16:30:58.0 +0200 +++ Makefile.am 2005-06-08 16:29:13.0 +0200 @@ -75,6 +75,8 @@ if USE_EDIT $(MAKE) install_mcedit endif + chown root:root $(pkglibdir)/cons.saver + chmod u+s $(pkglibdir)/cons.saver Seems to lack destdir support... indeed. well, i didn't propose the patch for commit, only for comments for now. i'm not sure about the correct location for the commands. -- Hi! I'm a .signature virus! Copy me into your ~/.signature, please! -- Chaos, panic, and disorder - my work here is done. ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: cons.saver not suid root
On Wed, Jun 08, 2005 at 04:49:11PM +0200, Oswald Buddenhagen wrote: we have no portable (even across linuxes) way to create a vcsa user, so there is no other option than root. How about not creating a user or group, but observing the installed system? IMHO if all the vcsa devices are owned by the same user or same group whose uid/gid is below 100, then we could assume that that one is a vcsa-like user or group, and install mc setgid or setuid to that particular gid or uid. If this is not the case, that is, the user or group varies or is greater than 100 (which might mean that a real user is logged in on all the ttys), then we could still fallback to setuid root. bye, Egmont ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: cons.saver not suid root
On Wed, Jun 08, 2005 at 05:42:07PM +0200, Koblinger Egmont wrote: On Wed, Jun 08, 2005 at 04:49:11PM +0200, Oswald Buddenhagen wrote: we have no portable (even across linuxes) way to create a vcsa user, so there is no other option than root. How about not creating a user or group, but observing the installed system? IMHO if all the vcsa devices are owned by the same user or same group whose uid/gid is below 100, then we could assume that that one is a vcsa-like user or group, and install mc setgid or setuid to that particular gid or uid. the number 100 is 100% arbitrary when looking at the linux landscape. also, i loathe putting anything more intelligent than stat(/dev/vcsa0).group == vcsa in the detection logic - _this_ might become a real security hole. -- Hi! I'm a .signature virus! Copy me into your ~/.signature, please! -- Chaos, panic, and disorder - my work here is done. ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: cons.saver not suid root
On Wed, Jun 08, 2005 at 05:43:05PM +0200, Leonard den Ottolander wrote: On Wed, 2005-06-08 at 17:23, Oswald Buddenhagen wrote: suppose i prefer configure make stow ... Patch is your friend. Or just chown and chmod afterwards. you needn't to educate _me_. now that i identified the problem and patched my checkout i could not care less. do you really expect every new user to do a bughunt as the first thing? I'd expect most new users to use a distro that sets this up properly for them. you shouldn't. particularly, you should not force them to do so by making either way of installation harder in unexpected ways. IMO this is more of a documentation issue than a build issue. Maybe we should add a note to the README. readmes are only read when the installation is non-obvious in the first place or when a problem suggesting a user fault occurs. personally, i'd assume it's a bug or the feature is missing alltogether. also, don't underestimate the usage rate of the upstream build system. it is the de-facto standard of installing 3rd-party unix software. Any statistics on this? i don't think percentages matter in this case. there is a non-trivial amount of users that use this method, even if it is only 1% of the total number. but the other 99% are outright irrelevant to that matter. By the way, afaik cons.saver is only used on Linux. i think freebsd was discussed some time ago. anyway, what's the point? what type of eventualities do you talk about? Possible introduction of bugs when somebody should start touching this code. oh, c'mon, the idiot that touches a suid/sgid program without thoroughly considering the consequences should be stoned anyway. maybe the blob at the top of the file should be made more explicit to protect against roland^Wpeople that tend to commit faster than they think. ;) -- Hi! I'm a .signature virus! Copy me into your ~/.signature, please! -- Chaos, panic, and disorder - my work here is done. ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: cons.saver not suid root
On Wed, Jun 08, 2005 at 06:06:03PM +0200, Tomasz Koczko wrote: BTW: in case Linux now I don' see cons.saver usage. $ strace -o out mc; grep cons.saver out with few times ctrl-o during strace show nothing (?). Q: is in case Linux cons.saver is still neccessary ? Yes. In case mc's running on text console you need raw read-write access to vcsa* in order to get ctrl-o working. There are two approches for this situation, one is the setuid/setgid cons.saver wrapper, the other is granting access for the user to the vcsa devices, e.g. make vcsa owned by the user. The problem with the latter one is that there's no way to revoke this from the user under Linux, once you open it you can hold it open as long as the system is up and hence you can watch other people's data there if someone else logs in there... -- Egmont ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Announcement of mc-4.6.1-pre4
On Wed, 8 Jun 2005, Pavel Shirshov (pchel) wrote: Hello MC, I've created a new cvs tag MC_4_6_1_pre4 and deleted MC_4_6_1_PRE5A since it had a wrong version nunmber. I've created a new tarball based on MC_4_6_1_pre4 - it can be found here: http://pavelsh.pp.ru/mc/ Now, we need to inform all interested parties (translators, maintainers and news sites). Can you say something more why this is not relased as 4.6.2 ? Last regular release was more than two years ago. It will be good to see more releases (like in time when Miguel was maintainer) even without looking is it just released tar ball contain more or less bugs (remember in OSS projects more importand than bugs count is avange time of fixing bug .. more than two years it is very long/bad time). kloczek -- --- *Ludzie nie maj problemw, tylko sobie sami je stwarzaj* --- Tomasz Koczko, sys adm @zie.pg.gda.pl|*e-mail: [EMAIL PROTECTED] ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: cons.saver not suid root
Hi Jakub, On Wed, 2005-06-08 at 16:40, Jakub Jelinek wrote: cons.saver should not be setuid root, it should be setuid to whatever user owns /dev/vcsa* devices. Ideally there is a vcsa user that just owns these devices and cons.saver. Could you maybe go into the details if and if how a setuid-ed root cons.saver could be abused? Leonard. -- mount -t life -o ro /dev/dna /genetic/research ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Localize dev numbers label for 4.6.1-pre4
I've just tweaked it to latest CVS 4.6.1-pre4 ___ Join Excite! - http://www.excite.com The most personalized portal on the Web! diff -ur /home2/dmartin/cvs/mc/po/es.po ./mc/po/es.po --- /home2/dmartin/cvs/mc/po/es.po 2005-06-08 22:01:37.395194320 +0200 +++ ./mc/po/es.po 2005-06-08 22:17:09.558483960 +0200 @@ -2438,6 +2438,11 @@ msgid Created: %s msgstr Cambiado: %s +#: src/info.c:155 +#, c-format +msgid Dev. type: major %lu, minor %lu +msgstr Dispositivo major: %lu, minor: %lu + #: src/info.c:163 #, c-format msgid Size: %s diff -ur /home2/dmartin/cvs/mc/po/it.po ./mc/po/it.po --- /home2/dmartin/cvs/mc/po/it.po 2005-06-08 22:01:37.591164528 +0200 +++ ./mc/po/it.po 2005-06-08 22:17:26.600893120 +0200 @@ -2449,6 +2449,11 @@ msgid Created: %s msgstr Creato: %s +#: src/info.c:155 +#, c-format +msgid Dev. type: major %lu, minor %lu +msgstr Tipo dis.: major %lu, minor %lu + #: src/info.c:163 #, c-format msgid Size: %s diff -ur /home2/dmartin/cvs/mc/src/info.c ./mc/src/info.c --- /home2/dmartin/cvs/mc/src/info.c 2005-06-08 02:29:36.0 +0200 +++ ./mc/src/info.c 2005-06-08 22:17:46.348890968 +0200 @@ -152,7 +152,7 @@ #if 0 #ifdef HAVE_STRUCT_STAT_ST_RDEV if (st.st_rdev) - printw (Inode dev: major: %d, minor: %d, + printw (_(Dev. type: major %lu, minor %lu), st.st_rdev 8, st.st_rdev 0xff); else #endif ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
RE: Localize dev numbers label for 4.6.1-pre4
Ooops, the code in info.c is there, but it's disabled with an if 0 :)) ... in such case ... the localization is slightly useless ___ Join Excite! - http://www.excite.com The most personalized portal on the Web! ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
RE: Localize dev numbers label for 4.6.1-pre4
Hi David, On Wed, 2005-06-08 at 22:39, David Martin wrote: Ooops, the code in info.c is there, but it's disabled with an if 0 :)) Roland has reenabled that code in HEAD. The translation can thus be committed to HEAD. Not sure if we should enable this for PRE at this point. Leonard. -- mount -t life -o ro /dev/dna /genetic/research ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
RE: Localize dev numbers label for 4.6.1-pre4
Hi David, On Wed, 2005-06-08 at 22:39, David Martin wrote: ... in such case ... the localization is slightly useless Looking at the info panel I doubt if we actually *want* localization in that view. Especially if we are going to support large device numbers we can't use large strings very well, especially on an 80 char wide screen. We'll probably even have to abbreviate major and minor. Leonard. -- mount -t life -o ro /dev/dna /genetic/research ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
RE: Localize dev numbers label for 4.6.1-pre4
Hi, On Wed, 2005-06-08 at 23:24, Leonard den Ottolander wrote: Looking at the info panel I doubt if we actually *want* localization in that view. Especially if we are going to support large device numbers we can't use large strings very well, especially on an 80 char wide screen. We'll probably even have to abbreviate major and minor. Please disregard this remark. As the other strings are also being translated there is no reason to make an exception for this one. Where is my brain? Leonard. -- mount -t life -o ro /dev/dna /genetic/research ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Localize dev numbers label for 4.6.1-pre4
David Martin wrote: I've just tweaked it to latest CVS 4.6.1-pre4 Please just commit it to HEAD. Roland ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Localize dev numbers label for 4.6.1-pre4
Done. It's been there for a couple of weeks. Thanks. David --- On Wed 06/08, Roland Illig [EMAIL PROTECTED] wrote: From: Roland Illig [mailto: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: mc-devel@gnome.org Date: Wed, 08 Jun 2005 23:53:06 +0200 Subject: Re: Localize dev numbers label for 4.6.1-pre4 David Martin wrote:br I've just tweaked it to latest CVS 4.6.1-pre4brbrPlease just commit it to HEAD.brbrRolandbr ___ Join Excite! - http://www.excite.com The most personalized portal on the Web! ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
