I know I can log in (locally) to my FC8 system, and enable the
remote desktop, walk to another machine and use vnc to pull it up.
However, how can I make it so it's done automatically without me having
to manually do it each time (and it remains persistent across reboots as
well). Basically this will be a headless machine, and I'll be using vnc
elsewhere to access it's desktop.
W | It's not a bug - it's an undocumented feature.
Ashley M. Kirchner <mailto:firstname.lastname@example.org> . 303.442.6410 x130
IT Director / SysAdmin / Websmith . 800.441.3873 x130
Photo Craft Imaging . 3550 Arapahoe Ave. #6
http://www.pcraft.com ..... . . . Boulder, CO 80303, U.S.A.
|Daniel B. Thurman wrote:
|> I tried:
|>> echo "\e[5;31mHello World"
|> and the red "Hello World" does not blink.
|try echo -e.
|No idea on blinking text, but your example above, combined
|with echo -e
|turned my terminal text red.
Yes, the color red worked - what you were supposed to
get is BLINKING red - that is where the problem is!
So it seems that ansi escape sequence for BLINKING is
broken. Remember when we had broken symbolic links?
The BLINKED red. This does not work.
Try creating a bogus symbolic link like this:
ln -s /foo/goo hoo
ls -l hoo
You will see a RED "hpp", but not BLINKING RED "hoo".
Me thinks there is a problem... ;)
No virus found in this outgoing message.
Checked by AVG.
Version: 7.5.524 / Virus Database: 269.23.7/1408 - Release Date: 4/30/2008 6:10 PM
Now I'd like to see if another annoying thing can be removed - getting
rid of the prompt for the keyring password. Since my machines are not
used publicly, I have no desktop security issues to worry about and
would like to know how I can keep it from prompting me for it in the
first place. Any ideas how to automate or remove this?
I do the not-so-rare "trick" of having two X sessions running, allowing
ctrl-alt-f7 / ctrl-alt-f8 to be a very painless fast-user-switch.
In order for this to work, I want more lax permissions on the sound devices.
(All members of group "sndshare" get access.) Previously, this was
accomplished by changing the settings for the <sound> device class in a file
That device class no longer exists in that file. I assume this is because
there is some new special modern udev way of accomplishing the same goal.
But, since all of the udev .rules files contain the line "# do not edit this
file, it will be overwritten on update", I'm not quite sure where is proper.
Plus, the 40-alsa-rules doesn't seem to be quite comprehensive -- some of
the devices must be created via defaults somewhere else.
So, what's the Right Thing To Do? (I'm using F9beta but I think the same
thing applies to F8, which I skipped.)
Matthew Miller mattdm(a)mattdm.org <http://mattdm.org/>
Boston University Linux ------> <http://linux.bu.edu/>
I wonder if anyone can give me any pointers to the following issues:
1) Dell D610 seems to go into screensaver mode far sooner than the kde
screensaver settings should allow. This happens maybe three or four times
and then it settles down and behaves normally after moving the mouse cursor
to get out of the screensaver each time it happens.
2) Another Dell this time a desktop Dimension 5150 - if I don't have
firefox running then the screensaver kicks in at the prescribed time,
and then the monitor goes into powersave at the prescribed timeout.
(There is no power management set in control center - if I set it then
X seems to crash at strange times). If firefox is running then the
screensaver comes in as normal but the monitor fails to enter powersave mode.
Both systems are fully updated F8 and running KDE 3.5 - these "features"
have been present for pretty for quite some time now and I wondered if
anyone has seen anything similar, or who might know a workaround?
I didn't specify at the outset of this discussion, but I have only two complaints regarding this issue and neither of them have to do with software patents, GPL, multimedia and related issues. Those things are insignificant from my perspective. What I hate to see is Redhat going down. Whether any of you believe it or not, Goliath comments aside, they have given themselves a black eye in the minds of many loyal supporters over the past couple of years. For me personally, the #2 issue is system stability. In their quest to be bleeding edge or whatever you want call it, I think we have sacrificed way too much in reliability and stability. I understand the devlopment schedule, testing methodology etc, as justifiable reasons therein. Initially I thought it was a great thing and eagerly awaited every release looking forward to the things I would be able to see and test for the first time. However, lately that has degeneratde into a situation I cannot
accept as the seeming recklesss abandon with which thay've gone about it.
That's really all there is to it. I can easily deal with these issues and that's why you don't see me posting here asking for help. But it has reached the threshold for me that I am not really enjoying it any more. I don't use my PCs for anything unusual or complex, just ordinary home office servers and workstations, with pretty much last generation plain vanila hardware. Despite that, I have lost count of the number of times and hours I've spent in the last two years fixing really dumb stuff like having the network just stop working after an update. Sure it's easy enough to run the previous kernel for a few days or a week until the fix appears, but that gets tiring after awhile when it becomes a continuous ongoing fear of loading new kernels. Sorry, but to me, things like that (and there are MANY more), and the frequency whith which they are ocurring just don't cut it for something being offered to the public, I don't care what justification for
software philosophy you offer. Some of it just seems like sloppy work to me
So I'll cross my fingers and take another step into F9. If things don't improve, I suppose I'll just sigh and continue being a disgruntled Fedora user. But fewer of my machines are running it these days, and that trend seems likely to continue.
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
I need to set up simple authenticated ftp access to a Fedora system
(running F9 beta).
I tried both proftpd and pure-ftpd and could not get either one to work
over a local connection (i.e. ftp localhost). proftpd would allow me log
in, but would not display any directory listing, or transfer any files;
pure-ftpd would not accept anything except anonymous logins.
Can anyone point me to a clear step-by-step startup guide for either of
these (or something else)?
Can anyone explain the reason why F8, by default, does not
include /usr/local/lib in its working pathlist?
I just had to add another file naming it in /etc/ld.so.conf.d
I don't recall ever having to do that in any previous incarnations of fedora,
it was always there.
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Superstition, idolatry, and hypocrisy have ample wages, but truth goes
-- Martin Luther