On Freitag 02 Oktober 2009, Arthur D. wrote:
You appear to be demonstrating that you don't fully understand the
problem:
828 ~ $ grep nano /usr/portage/app-admin/sudo/sudo-1.7.2_p1.ebuild
# XXX: /bin/vi may not be available, make nano visudo's default.
Am 02.10.2009 07:29, schrieb Arthur D.:
I repeat once more.
Every user who has VIM installed on theirs systems is forced to do extra
configuration, to make sudo work as expected, just because someone prefer
other editor and thinks that vanilla choice is bad. Isn't that just stupid?
I have
On Fri, 2009-10-02 at 08:06 +0200, Volker Armin Hemmann wrote:
why is it always vim users who get their panties in a knot about
nothing?
You are likely wrong about this. I'm willing to bet that a lot of
people, even people responding to this thread, are vim users. However
most of us know how
I really don't see your problem.
All that was needed here on my box was setting VIM as my editor of
choice (I preferer to do that per-user so no setting of anything in rc
or /etc/env.d) and VISUDO accepted it. No magic involved.
Sebastian, I already fixed the problem for my local host. But I
2009/10/2 Arthur D. spinal...@mail.ru:
You appear to be demonstrating that you don't fully understand the
problem:
828 ~ $ grep nano /usr/portage/app-admin/sudo/sudo-1.7.2_p1.ebuild
# XXX: /bin/vi may not be available, make nano visudo's default.
--with-editor=/bin/nano
On Fri, Oct 2, 2009 at 2:30 AM, Joshua Murphy poiso...@gmail.com wrote:
2009/10/2 Arthur D. spinal...@mail.ru:
You appear to be demonstrating that you don't fully understand the
problem:
828 ~ $ grep nano /usr/portage/app-admin/sudo/sudo-1.7.2_p1.ebuild
# XXX: /bin/vi may not be
Daniel Troeder schrieb:
ALSA is not a service (it's just drivers and API). There is nothing
running. It just loads your configuration (modules and volume levels).
PA on the other hand does not have hardware drivers - it relies on ALSA
or OSS for that.
thanks, already activated it
Go to LFS, build it all, build emacs, set EDITOR to emacs, and run
sudo visudo. Please. I have a rather good guess that you'll be,
amazingly, using the default that was set at build time for the sane
default editor, in LFS's case vim (whether called by that or the vi
symlink to it), that the
2009/10/2 Arthur D. spinal...@mail.ru:
Go to LFS, build it all, build emacs, set EDITOR to emacs, and run
sudo visudo. Please. I have a rather good guess that you'll be,
amazingly, using the default that was set at build time for the sane
default editor, in LFS's case vim (whether called by
if I
run a server with 50 users, 48 of which use emacs, one of which uses
vim, and I choose to use pico, why should I be forced to use vi for it
by default just because I have vim to satisfy someone else's desires?
That's really funny, Joshua. Do you provide 50 users of your company with
access
Joshua Murphy poiso...@gmail.com писал(а) в своём письме Fri, 02 Oct
2009 09:58:33 +0300:
every Gentoo system has vi, there just isn't a direct
symlink with that name to busybox.
Wow, that's a really great problem.
$ ln `which busybox` vi
$ ./vi
--
Best regards, Spinal
On Fri, 02 Oct 2009 08:29:30 +0300, Arthur D. wrote:
I repeat once more.
Every user who has VIM installed on theirs systems is forced to do extra
configuration, to make sudo work as expected, just because someone
prefer other editor and thinks that vanilla choice is bad. Isn't that
just
On Thu, 1 Oct 2009 19:34:25 -0500, forgottenwizard wrote:
So instead it should set a non-existant editor to the configured
default?
Nano is not non-existent by default.
Another variable in make.conf may be a reasonable fix for this though
I'm sure someone will bitch about having to set
On Fri, 02 Oct 2009 09:44:26 +0300, Arthur D. wrote:
That's right. But there are some reasons why visudo called so (do you
see that short VI?),
What are those reasons?
Do they apply to Gentoo?
Is it possible that this is simply because the original coder used vi? Or
perhaps to maintain the
On Fri, 02 Oct 2009 10:17:26 +0300, Arthur D. wrote:
I remind you, that an admin restricted the access to that ticket after
users started to vote for it.
Unless the reason for restriction was stated, your implication of
causality is invalid.
--
Neil Bothwick
Plagarism prohibited. Derive
A more sensible approach would be for the ebuild to check which ebuild
satisfies the virtual/editor dependency and set that.
Not clever. What if there are several editors installed?
And, yes, I prefer VIM. And I don't like when the package which
vanilla defaults were always to be using vim as
On Fri, 02 Oct 2009 11:15:09 +0300, Arthur D. wrote:
A more sensible approach would be for the ebuild to check which ebuild
satisfies the virtual/editor dependency and set that.
Not clever. What if there are several editors installed?
Choose the most appropriate from a defined list.
Neil Bothwick n...@digimed.co.uk писал(а) в своём письме Fri, 02 Oct
2009 11:23:38 +0300:
This problem could also be fixed by USE flags. Instead of whining why
not submit a patch that has the ebuild respect the vanilla USE flag?
Thanks for the idea. I will try this.
--
Best regards, Spinal
On Fri, Oct 02, 2009 at 09:07:20AM +0100, Neil Bothwick wrote:
On Thu, 1 Oct 2009 19:34:25 -0500, forgottenwizard wrote:
So instead it should set a non-existant editor to the configured
default?
Nano is not non-existent by default.
It isn't always on the users sytem. Providing a
Am 02.10.2009 08:25, schrieb Arthur D.:
I really don't see your problem.
All that was needed here on my box was setting VIM as my editor of
choice (I preferer to do that per-user so no setting of anything in rc
or /etc/env.d) and VISUDO accepted it. No magic involved.
Sebastian, I already
Once again, try running sudo visudo as unprivileged user (that's
right,
sudo is used to make root stuff without logging with root ;-) )
Ok, I comment out
%wheel ALL=(ALL) ALL
so that my user could use sudo visudo.
Hey.. Great.. It started visudo with VIM.
So again.. What are you complaining
On Fri, Oct 02, 2009 at 09:23:38AM +0100, Neil Bothwick wrote:
On Fri, 02 Oct 2009 11:15:09 +0300, Arthur D. wrote:
And, yes, I prefer VIM. And I don't like when the package which
vanilla defaults were always to be using vim as editor is overwritten
without any notifications and causing
Am 02.10.2009 10:52, schrieb forgottenwizard:
On Fri, Oct 02, 2009 at 09:07:20AM +0100, Neil Bothwick wrote:
On Thu, 1 Oct 2009 19:34:25 -0500, forgottenwizard wrote:
So instead it should set a non-existant editor to the configured
default?
Nano is not non-existent by default.
It isn't
Arthur D. wrote:
Once again, try running sudo visudo as unprivileged user (that's
right,
sudo is used to make root stuff without logging with root ;-) )
Ok, I comment out
%wheel ALL=(ALL) ALL
so that my user could use sudo visudo.
Hey.. Great.. It started visudo with VIM.
So again..
On Fri, Oct 02, 2009 at 11:08:08AM +0200, Sebastian Be?ler wrote:
Am 02.10.2009 10:52, schrieb forgottenwizard:
It isn't always on the users sytem. Providing a non-existent default
seems quite broken to me.
By DEFAULT it is on EVERY Gentoo-system.
If you CHOOSE to remove the default then
Am 02.10.2009 11:04, schrieb forgottenwizard:
The number of USE flags would be quite impressive for such a small
package.
a vanilla-flag could be possible that disables every changes to the
upstream-package.
It even exists atm for a number of packages
metat...@darkstation ~ $ euse -i vanilla
On Fri, 2 Oct 2009 04:04:30 -0500, forgottenwizard wrote:
This problem could also be fixed by USE flags. Instead of whining
why not submit a patch that has the ebuild respect the vanilla USE
flag?
USE flags is nice, except ls /usr/portage/app-editors/ | wc -l returns
76 packages (give
On Fri, 2 Oct 2009 03:52:24 -0500, forgottenwizard wrote:
Nano is not non-existent by default.
It isn't always on the users sytem. Providing a non-existent default
seems quite broken to me.
That's true of every editor, so you have to choose the one that is most
likely to be there, the one
On Fri, Oct 02, 2009 at 11:21:08AM +0200, Sebastian Be?ler wrote:
Am 02.10.2009 11:04, schrieb forgottenwizard:
The number of USE flags would be quite impressive for such a small
package.
a vanilla-flag could be possible that disables every changes to the
upstream-package.
It even
On Fri, Oct 02, 2009 at 10:29:08AM +0100, Neil Bothwick wrote:
On Fri, 2 Oct 2009 03:52:24 -0500, forgottenwizard wrote:
Nano is not non-existent by default.
It isn't always on the users sytem. Providing a non-existent default
seems quite broken to me.
That's true of every editor,
Am 02.10.2009 11:29, schrieb forgottenwizard:
insert emacs user whining
Thats an option, but seems to be a poor one. All that will do is let you
use either vi(m) or nano for the default, which for emacs users will be
no diffrent than the current problem.
joke
If you use emacs then you are
Thanks. Depmod yielded no results. At least as far as I can tell. I tried
with ...
Code:
# depmod -a ; depmod -e -F
As I recall Note: the kernel developers warn that you should not configure or
compile your kernel as root.
-http://forums.gentoo.org/viewtopic-t-539024.html And that that
Am 02.10.2009 11:40, schrieb Sebastian Beßler:
Am 02.10.2009 11:29, schrieb forgottenwizard:
insert emacs user whining
Thats an option, but seems to be a poor one. All that will do is let you
use either vi(m) or nano for the default, which for emacs users will be
no diffrent than the
On Freitag 02 Oktober 2009, forgottenwizard wrote:
On Fri, Oct 02, 2009 at 10:29:08AM +0100, Neil Bothwick wrote:
On Fri, 2 Oct 2009 03:52:24 -0500, forgottenwizard wrote:
Nano is not non-existent by default.
It isn't always on the users sytem. Providing a non-existent default
OK. Now the latest update.
1) Here's a copy (just a copy, all links are useless) of bug report done
by me.
I was forced to copy that page to hosting because package maintainer
restricted
access to users who began to vote for this bug.
On Fri, Oct 02, 2009 at 11:40:33AM +0200, Sebastian Be?ler wrote:
Am 02.10.2009 11:29, schrieb forgottenwizard:
insert emacs user whining
Thats an option, but seems to be a poor one. All that will do is let you
use either vi(m) or nano for the default, which for emacs users will be
On Fri, 2 Oct 2009 04:36:47 -0500, forgottenwizard wrote:
It isn't always on the users sytem. Providing a non-existent default
seems quite broken to me.
That's true of every editor, so you have to choose the one that is
most likely to be there, the one that is installed for the stage
This thread is really out of control, I doubt anything useful can be born
here, we are just running circles around a chair.
On Fri, 2 Oct 2009 04:54:42 -0500, forgottenwizard
phrexianrea...@hushmail.com wrote:
On Fri, Oct 02, 2009 at 11:40:33AM +0200, Sebastian Be?ler wrote:
Am 02.10.2009
On Fri, 02 Oct 2009 12:09:23 +0200, Jesús Guerrero wrote:
The USE flag idea is non-viable and doesn't make sense.
Why not? The flag already exists for the very purpose the OP raised.
--
Neil Bothwick
PC DOS Error #01: Windows loading, come back tomorrow
signature.asc
Description: PGP
On Thu, 01 Oct 2009 23:12:36 +0300, Arthur D. spinal...@mail.ru wrote:
James Ausmus james.aus...@gmail.com писал(а) в своём письме Thu, 01
Oct
2009 22:04:38 +0300:
VI.
Maybe it's called VIsudo because VIM is better alternative for VANILLA,
hah?
Maybe we should stick to the old devfs
Volker Armin Hemmann wrote:
then the more sensible one should be used by default.
Lets see:
nano, built in help, easy to use, small, good enough for most edits.
vim, whatthefuckisthatcrap? how do I quit this monstrum? what happened now?
MODES?
nano wins, hands down. Because every idiot
Oh, and your ebuild patch doesn't even bother to check the vim
dependency.
The vanilla USE flag is not global, it's local, man.
And it doesn't force user to install vim.
You may want to make symlink /usr/bin/vi - /bin/busybox instead.
--
Best regards, Spinal
On Fri, 2 Oct 2009 11:21:53 +0100, Neil Bothwick n...@digimed.co.uk
wrote:
On Fri, 02 Oct 2009 12:09:23 +0200, Jesús Guerrero wrote:
The USE flag idea is non-viable and doesn't make sense.
Why not? The flag already exists for the very purpose the OP raised.
Oh, you meant vanilla, sorry, I
On Fri, 02 Oct 2009 13:35:47 +0300, Arthur D. spinal...@mail.ru wrote:
Oh, and your ebuild patch doesn't even bother to check the vim
dependency.
The vanilla USE flag is not global, it's local, man.
That's irrelevant. Each ebuild should sort its dependencies. The scope of
the use flags is
So, if it can't find vim, we should go
fix that ourselves and that is acceptable, but if it can't find nano then
that's unacceptable for you, did I get it right?
Did you visit
http://www.rootshell.be/~spinal/gentoo_bug_report/286017.html ?
I was forced to offer the maintainer to respect at
On Fri, 02 Oct 2009 13:57:44 +0300, Arthur D. spinal...@mail.ru wrote:
So, if it can't find vim, we should go
fix that ourselves and that is acceptable, but if it can't find nano
then
that's unacceptable for you, did I get it right?
Did you visit
I recompiled my kernel again with built-in e1000e support. No good. Maybe
it's udev?
_
Get your FREE, LinuxWaves.com Email Now! -- http://www.LinuxWaves.com
Join Linux Discussions! -- http://Community.LinuxWaves.com
On Fri, Oct 02, 2009 at 12:09:23PM +0200, Jes??s Guerrero wrote:
On Fri, 2 Oct 2009 04:54:42 -0500, forgottenwizard
phrexianrea...@hushmail.com wrote:
How about a custom_editor flag, as you suggested, then an EDITOR
variable in make.conf? Thats the only way I could see being able to
solve
On 10/2/2009 1:29 AM, Arthur D. wrote:
Agree. There's no need in making vim as depends. But in other hand in
vanilla sudo
package there's VI hardcoded by default. And MOST if not ALL users who
have VIM
So basically, you're entire silly argument boils down to I
don't like nano, make it go
On Friday 02 October 2009 10:53:37 Arthur D. wrote:
=+ 3) And now the most interesting. I was banned by maintainer. Now I cannot
access the ticket too.
Strange, uh?
On 10/02/2009 04:20 AM, Cinder wrote:
I recompiled my kernel again with built-in e1000e support. No good. Maybe
it's udev?
Oops, by grepping through the kernel sources I see that you need the e1000
driver, not e1000e.
From your pastebin lspci: Intel Corporation 82547EI Gigabit Ethernet
2009/10/2 Mike Edenfield kut...@kutulu.org:
On 10/2/2009 1:29 AM, Arthur D. wrote:
Agree. There's no need in making vim as depends. But in other hand in
vanilla sudo
package there's VI hardcoded by default. And MOST if not ALL users who
have VIM
So basically, you're entire silly argument
This is an interesting thread to analyze, even though 90.9% of it is
basically BS and flaming.
I actually can side a little bit with the OP. But as a user of Gentoo,
vi and sudo.
If it were all up to me, I'd have visudo look at EDITOR and fail if it
doesn't exist. But this is likely not the
I asked this before without any response (smile).
Kworldclock 3.5.10 is a useful little app, but is absent from 4.3.1 .
I've found 2 versions of the problem :
KDE bug 184088 , which suggests the problem is Gentoo packaging ;
Gentoo forum
On 2009-10-02, Albert Hopkins mar...@letterboxes.org wrote:
It's a distribution where you have to choose your own system
logger and compile your own kernel, but when it comes to the
text editor they decide to hold your hand with nano?
Some of us who are vimpaired think of it more as they
Er, what the heck is this one:
emerge -av1 x11-libs/libXScrnSaver
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild N] x11-proto/scrnsaverproto-1.2.0 49 kB
[ebuild N] x11-libs/libXScrnSaver-1.1.3 USE=-debug 0 kB
[blocks B ]
Does anyone know of a self-powered external video card (USB, Firewire,
ExpressCard) that has composite/RCA output and works in Gentoo? I'd
like to use it to connect my laptop (VGA output only) to TVs while I'm
travelling.
Something like this?
091002 Nikos Chantziaras wrote:
Er, what the heck is this one:
emerge -av1 x11-libs/libXScrnSaver
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild N] x11-proto/scrnsaverproto-1.2.0 49 kB
[ebuild N]
Am Freitag, 2. Oktober 2009 schrieb Nikos Chantziaras:
Er, what the heck is this one:
emerge -av1 x11-libs/libXScrnSaver
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild N] x11-proto/scrnsaverproto-1.2.0 49 kB
[ebuild N]
091002 Philip Webb wrote in too much haste:
Faced with that, I would do
emerge -Cp libXScrnSaver
emerge -C libXScrnSaver
emerge -pv libXScrnSaver
emerge -1 libXScrnSaver
Sorry, I thought the new version was 1.3 , but of course it's 1.1.3 ,
so the block is a bit bizarre. Someone else
On Fri, 2009-10-02 at 19:17 +0300, Nikos Chantziaras wrote:
Er, what the heck is this one:
emerge -av1 x11-libs/libXScrnSaver
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild N] x11-proto/scrnsaverproto-1.2.0 49 kB
[ebuild N]
1. FYI, There is a short, direct upgrade guide that should be referenced
before upgrading to 1.6:
http://www.gentoo.org/proj/en/desktop/x/x11/xorg-server-1.6-upgrade-guide.xml
It refers to another, short upgrade guide that should definitely be
reviewed before proceeding:
2. The second guide uses a lot of one-shot emerges; could anyone
please explain why I'd use a one-shot?
ISTM that if a package is on my system, I'd want it routinely updated.
If I need it only once, then instruct me to unmerge it after it's done!?
The basic idea of --oneshot is to avoid
On Fri, Oct 2, 2009 at 2:40 AM, Cinder cin...@linuxwaves.com wrote:
Thanks. Depmod yielded no results. At least as far as I can tell. I tried
with ...
Code:
# depmod -a ; depmod -e -F
As I recall Note: the kernel developers warn that you should not
configure or compile your kernel as
On 10/02/2009 07:17 PM, Nikos Chantziaras wrote:
Er, what the heck is this one:
emerge -av1 x11-libs/libXScrnSaver
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild N ] x11-proto/scrnsaverproto-1.2.0 49 kB
[ebuild N ] x11-libs/libXScrnSaver-1.1.3
On Fri, Oct 2, 2009 at 11:17 AM, Nikos Chantziaras rea...@arcor.de wrote:
Er, what the heck is this one:
emerge -av1 x11-libs/libXScrnSaver
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild N] x11-proto/scrnsaverproto-1.2.0 49 kB
Seems like an awful lot of hoops to jump through just to get a facility
that
comes out of the box in 3.5. Maybe I'll give it a try anyway, so thanks.
Yeah, right? I was thinking of making the switch, but I was convinced there
must be infinite tricks hidden.
~daid
Grant Edwards wrote:
SNIP
and my brain just doesn't
work the way vi does.
I'm with you Grant. Mine doesn't work that way either.
Dale
:-) :-)
2009/10/2 Arthur D. spinal...@mail.ru:
Joshua Murphy poiso...@gmail.com писал(а) в своём письме Fri, 02 Oct 2009
09:58:33 +0300:
every Gentoo system has vi, there just isn't a direct
symlink with that name to busybox.
Wow, that's a really great problem.
$ ln `which busybox` vi
$ ./vi
--
Do we have tools other than Konqueror that are aware of smb/UNK
addressing?
Before you answer please note that:
I know about ssh
I know about fuse
I know about mount -tcifs
I'd really like to be able to use UNK addressing from the cmd line.
cd //host/share
I don't now how many of you have
Hello, Walt:
I had Browse removable media when inserted checked. Sure enough, when
unchecked, a nautilus window opens. I also notice that two options are
checked. I don't understand what the difference between them would be:
Mount removeable drives when hot-plugged
and
Mount removable
Dale rdalek1...@gmail.com writes:
Grant Edwards wrote:
SNIP
and my brain just doesn't
work the way vi does.
I'm with you Grant. Mine doesn't work that way either.
You guys do know that Bill Joy was lopsided drunk when he wrote the
bulk of vi ... right? (or so it is said by oldtimers)
On 2009-10-02, Harry Putnam rea...@newsguy.com wrote:
Dale rdalek1...@gmail.com writes:
Grant Edwards wrote:
SNIP
and my brain just doesn't work the way vi does.
I'm with you Grant. Mine doesn't work that way either.
You guys do know that Bill Joy was lopsided drunk when he
wrote the
Daniel:
just a note to follow up for you guys. i managed to flash the bios on my tyan
S5393G2NR to v1.06 and now the vmx flag shows up in /proc/cpuinfo along with
about a half a dozen others. so now the kvm device is created at boot and kvm
works like a charm with no modules whatsoever. so
On 10/02/2009 02:10 PM, Alan E. Davis wrote:
Hello, Walt:
I had Browse removable media when inserted checked. Sure enough,
when unchecked, a nautilus window opens. I also notice that two options
are checked. I don't understand what the difference between them would be:
Mount removeable
On 10/02/2009 01:56 PM, Harry Putnam wrote:
Do we have tools other than Konqueror that are aware of smb/UNK
addressing?
Before you answer please note that:
I know about ssh
I know about fuse
I know about mount -tcifs
I'd really like to be able to use UNK addressing from the cmd line.
cd
Volker Armin Hemmann writes:
On Dienstag 29 September 2009, Alex Schuster wrote:
Philip Webb writes:
I've added to a number of KDE bugs relating to problems with 4.3.1 .
Thanks for doing so! Hopefully this will improve KDE.
I also have a huuuge list of KDE bugs, but I am still at
Nikos Chantziaras realnc at arcor.de writes:
Well, actually one thing that stands out is that I'm using newer
versions of most of the dependencies.
I might have found my problem:
# xdriinfo
Xlib: extension XFree86-DRI missing on display :0.0.
Screen 0: not direct rendering capable.
Alex Schuster writes:
And then... some days ago I wanted to try ati-drivers-9.8, and had to
upgrade 6 packages, xorg-1.6 and such. I quickpkg'd them, tried the new
drivers (no success of course), downgraded with --usepkg, and still I
cannot get it to work again. I am using the radeon drivers
walt w41...@gmail.com writes:
On 10/02/2009 01:56 PM, Harry Putnam wrote:
Do we have tools other than Konqueror that are aware of smb/UNK
addressing?
Before you answer please note that:
I know about ssh
I know about fuse
I know about mount -tcifs
I'd really like to be able to use UNK
81 matches
Mail list logo
