-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
15.02.2012 17:45, "Jóhann B. Guðmundsson" wrote:
> Thomas Woerner has been working on a more user friendly firewall
> solution for Fedora so firewall solution is in a bit of state of flux in
> Fedora at this point in time and explains why things are a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
drago01 wrote:
>> I also against making it global by default. But this can be done
>> in separate folder, not to standard /usr/bin, and then added for
>> users who want it just add it into PATH.
Yep, of course. This idea unobtrusive and don't hard for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Frank Murphy wrote:
> Bookmark this: http://ss64.com/bash/
I know about :) This idea just try for standartization of command
names... I know about posix and LSB, but these standards don't make
logic in the names of commands. Okay, as I see, this idea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi folk,
I want to propose new idea about names of command line utilites...
For example, all present utilites have sence just for guru's (ls, rm,
fsck etc), but for novies it's hard to use. Is good idea to symlink'ing
(shell aliasing) these and much
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Сергей Варюхин wrote:
> What are reaction time at bugzilla?
- From few second to few years...
> I was write some commentaries at
> https://bugzilla.redhat.com/show_bug.cgi?id=557010 and wait for
> developers reaction. About one week already. Does i d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bill Nottingham wrote:
> My bikeshedding opinion is /lib/init/state might be better. But if
> it's just to be temporary, why isn't /dev/.initramfs OK?
+1.
After starting udev daemon old content of /dev catalog will be hidden
(/dev/.initramfs too). S