Re: what has 'yum update' done?

[Joe Zeff]

On 07/11/2013 11:38 PM, Heinz Diehl wrote:

Only speaking for myself: I always try to upgrade first, having a
complete backup, of course. If it doesn't work, I reinstall. There's
nothing to loose, since I'm expecting to reinstall anyway.


I've had an update fail too, once.  Being retired and having both a 
laptop and a desktop, I've always made sure my laptop gets upgraded 
first and is working properly before upgrading my desktop.  It took me 
several days of work, but I eventually had the satisfaction of getting 
my desktop upgraded without a clean install.  Of course, if I were in a 
production environment, I'd have bitten the bullet, done a fresh install 
(/home is always on its on partition and wasn't affected by the bad 
upgrade.) and started putting things back together, because the work I 
did cleaning things up simply wouldn't have been cost effective.  And, 
probably, if I were working and I had this issue at home, I'd have ended 
up with a new install because there's only so many hours per day and so 
much Copious Free Time to spend cleaning up.  It's a trade-off.  For me, 
the time spent getting things working were paid for in the satisfaction 
of a difficult job well done.  Not everybody can afford to think that way.

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Mailing List Etiquette (was Re: can't run sshd on 23456 in Fedora 19)

[Timothy Murphy]

Joe Zeff wrote:

>> that i should set my focus to a perfect english and political correctness
>> instead technical facts? sorry, my day has only 24 hours
> 
> No.  Some of the people who didn't grow up speaking English are better
> at it than you, but you're quite understandable.  Not only that, there
> are a few on this list who I presume grew up with it that aren't as good
> as it as you are.  Don't worry about it.
> 
> And, to answer another question, the word "I" in English does mean
> "ich," but in English, proper nouns are always capitalized.

I agree with you completely re Reindl.
But I don't agree with your grammatical advice.
"I" is always capitalized, but not "you", "he", etc.
I don't believe there is any logical reason for this,
as indeed for much english grammar.
"It just growed."
I find my German friends (could equally well be "german friends"?)
all know far more about english grammar than I do,
believing that English is a dialect of German,
rather than a random mixture of incompatible languages.

-- 
Timothy Murphy  
e-mail: gayleard /at/ eircom.net
tel: +353-86-2336090, +353-1-2842366
School of Mathematics, Trinity College, Dublin 2, Ireland


-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: NEW RANT OF THE DAY: anaconda is ....

[François Patte]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Le 11/07/2013 02:21, Rahul Sundaram a écrit :
> Hi
> 
> 
> On Wed, Jul 10, 2013 at 5:40 PM, François Patte
>  > wrote:
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> This message follows my previous ones
> 
> When you enter in "troubleshooting" section you can enter in rescue
> mode. GREAT!!!
> 
> ONLY with a default QWERTY keyboard!
> 
> 
> 
> Bugzilla #?

983872

But is it a bug? Or conceptors of anaconda have lost their brain somewhere?


- -- 
François Patte
UFR de mathématiques et informatique
Laboratoire MAP5 --- UMR CNRS 8145
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. +33 (0)1 8394 5849
http://www.math-info.univ-paris5.fr/~patte
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAlHfuqsACgkQdE6C2dhV2JVwIACfX9gq5dYpNPeffQ9S+13CU7If
bTkAoMHWB1kEne6g0C2GH0N6hANcxq2o
=KtVe
-END PGP SIGNATURE-
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

F18 to F19: shutdown doesn't work in LXDE

[antonio.montagn...@alice.it]

Fedup worked fine also on a small old laptop.

We have   a minor issue, when we try to switch off from the menu, machine 
doesn't shut down and we have to use the power button to poweroff

But if we issue poweroff or reboot when logged as root in text mode with 
Ctrl+Alt+F2 poweroff or reboot works fine.
We had such an issue in F18.

Any idea??

Tnx

Antonio Montagnani



Fedora 19 Schroedinger's cat (Linux)

http://www.campingmonterosa.com

Delivered by Alice webmail
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

R: F18 to F19: shutdown doesn't work in LXDE

[antonio.montagn...@alice.it]

https://bugzilla.redhat.com/show_bug.cgi?id=981738

here we are :-)


Messaggio originale

Da: antonio.montagn...@alice.it

Data: 12-lug-2013 10.58

A: 

Ogg: F18 to F19: shutdown doesn't work in LXDE





Fedup worked fine also on a small old laptop.

We have   a minor issue, when we try to switch off from the menu, machine 
doesn't shut down and we have to use the power button to poweroff

But if we issue poweroff or reboot when logged as root in text mode with 
Ctrl+Alt+F2 poweroff or reboot works fine.
We had such an issue in F18.

Any idea??

Tnx

Antonio Montagnani



Fedora 19 Schroedinger's cat (Linux)

http://www.campingmonterosa.com

Delivered by Alice webmail




-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Middle mouse button paste

[Ian Chapman]

On 11/07/13 22:31, Ranjan Maitra wrote:


Would be nice to figure out a long-term solution.

Of course, this may not all be helpful to you (in which case, sorry).


No problem, thanks Ranjan. At first I thought it was a feature that 
might have been removed to 'improve' the experience but the two boxes 
that were affected seem to work now and I don't what changed. It was 
bizarre because it wouldn't paste on a VT or in X so at first I thought 
it was (maybe even two) faulty mice but xev was showing the middle clicks.


--
Ian Chapman.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Fedup 17->18 won't boot, all partitions are GPT

[Ian Chapman]

On 12/07/13 10:20, Rick Walker wrote:


I did a fedup from F17 to F18 on my work desktop.  Now I get an infinite
boot loop.  Fdisk can't look at the partition table of /dev/sda because
it has been coverted to GPT format (who did that?).

As near as I can tell, the boot process fails after about 1 page of
output near where "/" should be mounted.  I can't see the error message
because it reboots too quickly.

Doing a rescue with an F17 bootable flash drive allows me to at least
mount my /boot and / partitions, so I guess F17 understands the GPT
conversion.  It won't however, recognize the new system to do a boot
sector repair.  Should I try with an F18 bootable flash drive?

Under the F17 debug prompt /dev/sda2 (boot) and /dev/sda4 (root)
both give clean fsck checks.

I appreciate any suggestions.


When dealing with GPT partition tables, parted is probably the tool you 
want use as fdisk doesn't understand them. Somebody correct me if I'm 
wrong, but I think a non UEFI system cannot normally boot directly from 
a GPT partition, so often in addition to a GPT partition table, an 
MS-DOS (fdisk style) partition table is created which masks out the rest 
of the disk as being in use to avoid non-GPT aware software from 
stomping over your partitions. Providing your bootloader and OS 
understand GPT, then the system should boot.


What does the output of "fdisk -l /dev/sda" show? I would expect it to 
look something like


   Device Boot  Start End  Blocks   Id  System
/dev/sda1   1   625142447   312571223+  ee  GPT

Compare that to the output of "parted /dev/sda print". Mine for example is:

Disk /dev/sda: 320GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number  Start   End SizeFile system  Name  Flags
 1  1049kB  2097kB  1049kB bios_grub
 2  2097kB  526MB   524MB   ext4 ext4  boot
 3  526MB   320GB   320GB  lvm




--
Ian Chapman.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

how to set up IP forwarding on linux machines?

[Norah Jones]

Hi, 

I have a IP configured which is not visible for another network (suppose IP: A).
I have a common machine/switch which is in between two networks, now need to 
set up IP forwarding such a way that the packets coming to IP: A should be 
forwarded to that machine correctly.

Thanks,
Norah Jones


-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: crypted partition

[Jorge Fábregas]

On 07/11/2013 06:53 PM, Patrick Dupre wrote:
> How can I know what is the physical partition ?

You'll find it in /etc/crypttab

-- 
Jorge
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Mailing List Etiquette (was Re: can't run sshd on 23456 in Fedora 19)

[Patrick O'Callaghan]

On Wed, 2013-07-10 at 16:24 +0200, Reindl Harald wrote:
> and if you think here that "i" should be "I", sorry it does
> not bother me because there are *a lot* of words in the
> german language beginning with uppercase letters while
> at the same time in context of internet communication
> it is often ignored and does not matter

I have nothing to say about German practice, but in English it does
matter, even if a tiny minority of people sometimes forget it. The fact
that you think it doesn't matter is exactly my point, but as you clearly
aren't able to listen to a different view even from a native speaker of
English, there's no point in continuing this. I didn't make the comment
hoping from a positive response from you, I made it in reply to someone
else.

Have a nice life.

poc

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: how to set up IP forwarding on linux machines?

[fedora]

sysctl -a |grep forward
and then set the needed parameters to 1 for
- ipv4/ipv6
- the interface you want

using sysctl -w parameter
and you will have a router

suomi

On 2013-07-12 12:19, Norah Jones wrote:

Hi,

I have a IP configured which is not visible for another network (suppose IP: A).
I have a common machine/switch which is in between two networks, now need to 
set up IP forwarding such a way that the packets coming to IP: A should be 
forwarded to that machine correctly.

Thanks,
Norah Jones



--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: [GW-C] [ECOTONE] Re: rant of the day: installing fedora

[Patrick O'Callaghan]

On Thu, 2013-07-11 at 22:11 -0400, D. Hugh Redelmeier wrote:
> Anaconda's screens need to be more wordy to make things clearer
> and less scary to the user.

Agreed. I found several things confusing about it, especially the
partitioning screen, though I finally managed it. However it's worth
noting that the first screen has a button (lower right) clearly
indicating "We won't touch your disks until you click here".

poc

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: [GW-C] [ECOTONE] Re: rant of the day: installing fedora

[Patrick O'Callaghan]

On Thu, 2013-07-11 at 23:45 -0400, Rahul Sundaram wrote:
> Hi
> 
> 
> On Thu, Jul 11, 2013 at 10:11 PM, D. Hugh RedelmeierAnaconda's screens
> need to be more wordy to make things clearer
> and less scary to the user.
> 
> 
> Perhaps you can file a bug report?  It appears in this thread, noone
> yet has done this

Like most people I tend to use the installer only once per new release,
so if it isn't straightforward it can be difficult, in the relief of
managing to get past it, to remember the exact sequence of failures and
retries one has gone through, in order to formulate a useful bug report.
> 
A poor excuse, but my own.

poc

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: crypted partition

[Todor Petkov]

On 12/07/2013 01:53 AM, Patrick Dupre wrote:

Hello,

I have a luks partition which is mount at boot time:
in /etc/fstab:
/dev/mapper/luks-21e00840-01b6-4ba1-8ab2-d4cfe70430e8 /home

How can I know what is the physical partition ?
df gives:
/dev/dm-16   /home
blkid gives:
/dev/mapper/luks-21e00840-01b6-4ba1-8ab2-d4cfe70430e8:
UUID="85da123b-7dcc-403e-b28b-2bd16cd6d504" TYPE="ext4"

Thank.



Hello,

try with "cryptsetup status luks-21e00840-01b6-4ba1-8ab2-d4cfe70430e8"


Regards,


--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

psmouse-alps-1.3 and f19

[Robson Roberto Souza Peixoto]

Hi,

anybody here has success on compile the psmouse-alps on Fedora 19? I
getting this error:

*#* cd /
# tar xaf /root/psmouse-alps-1.3-alt.tbz
*#* cd /usr/src/psmouse-alps-1.3/
# cat dkms.conf
# $Id: dkms.conf 742 2013-02-11 17:15:05Z dturvene $

PACKAGE_NAME="psmouse"
PACKAGE_VERSION="alps-1.3"
CLEAN="rm -f *.*o"

BUILT_MODULE_NAME[0]="psmouse"
MAKE[0]="make -C $kernel_source_dir
M=$dkms_tree/$PACKAGE_NAME/$PACKAGE_VERSION/build/src psmouse.ko"
BUILT_MODULE_LOCATION[0]="src"
DEST_MODULE_LOCATION[0]="/updates"

AUTOINSTALL="yes"
# dkms add -m psmouse -v alps-1.3

Creating symlink /var/lib/dkms/psmouse/alps-1.3/source ->
 /usr/src/psmouse-alps-1.3

DKMS: add completed.
# dkms build -m psmouse -v alps-1.3

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area
make KERNELRELEASE=3.9.9-301.fc19.x86_64 -C
/lib/modules/3.9.9-301.fc19.x86_64/build
M=/var/lib/dkms/psmouse/alps-1.3/build/src psmouse.ko.
Error!  Build of psmouse.ko failed for: 3.9.9-301.fc19.x86_64 (x86_64)
Consult the make.log in the build directory
/var/lib/dkms/psmouse/alps-1.3/build/ for more information.


Installed kernel packages:
# rpm -qa | grep ^kernel
kernel-headers-3.9.9-301.fc19.x86_64
kernel-devel-3.9.9-301.fc19.x86_64
kernel-modules-extra-3.9.5-301.fc19.x86_64
kernel-3.9.5-301.fc19.x86_64
kernel-3.9.9-301.fc19.x86_64
kernel-modules-extra-3.9.9-301.fc19.x86_64


Thanks,
-- 
Robson Roberto Souza Peixoto
Robinho http://robsonpeixoto.com/
Master in Computer Science, University of Campinas
Linux Counter #395633
IRC: robsonpeixoto
Twitter: http://twitter.com/rrspba
github: https://github.com/robsonpeixoto
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: psmouse-alps-1.3 and f19

[Carlos "casep" Sepulveda]

On 12 July 2013 09:06, Robson Roberto Souza Peixoto
 wrote:
> Consult the make.log in the build directory
> /var/lib/dkms/psmouse/alps-1.3/build/ for more information.


And what's the content of that?


--
"My name is Ozymandias, king of kings:
Look on my works, ye Mighty, and despair!"
Percy Bysshe Shelley
http://sites.google.com/site/carlossepulveda
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: psmouse-alps-1.3 and f19

[Robson Roberto Souza Peixoto]

On Fri, Jul 12, 2013 at 10:09 AM, Carlos "casep" Sepulveda <
ca...@fedoraproject.org> wrote:

> On 12 July 2013 09:06, Robson Roberto Souza Peixoto
>  wrote:
> > Consult the make.log in the build directory
> > /var/lib/dkms/psmouse/alps-1.3/build/ for more information.
>
>
> And what's the content of that?
>

Sorry, I forget to copy it. =D

# cat /var/lib/dkms/psmouse/alps-1.3/build/make.log
DKMS make.log for psmouse-alps-1.3 for kernel 3.9.9-301.fc19.x86_64 (x86_64)
Sex Jul 12 09:59:56 BRT 2013
make: Entrando no diretório `/usr/src/kernels/3.9.9-301.fc19.x86_64'
  CC  /var/lib/dkms/psmouse/alps-1.3/build/src/psmouse-base.o
  CC  /var/lib/dkms/psmouse/alps-1.3/build/src/synaptics.o
  CC  /var/lib/dkms/psmouse/alps-1.3/build/src/alps.o
  CC  /var/lib/dkms/psmouse/alps-1.3/build/src/elantech.o
  CC  /var/lib/dkms/psmouse/alps-1.3/build/src/logips2pp.o
  CC  /var/lib/dkms/psmouse/alps-1.3/build/src/lifebook.o
  CC  /var/lib/dkms/psmouse/alps-1.3/build/src/sentelic.o
  CC  /var/lib/dkms/psmouse/alps-1.3/build/src/trackpoint.o
  LD  /var/lib/dkms/psmouse/alps-1.3/build/src/psmouse.o
  MODPOST 0 modules
make: Saindo do diretório `/usr/src/kernels/3.9.9-301.fc19.x86_64'



>
>
> --
> "My name is Ozymandias, king of kings:
> Look on my works, ye Mighty, and despair!"
> Percy Bysshe Shelley
> http://sites.google.com/site/carlossepulveda
> --
> users mailing list
> users@lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
>



-- 
Robson Roberto Souza Peixoto
Robinho http://robsonpeixoto.com/
Master in Computer Science, University of Campinas
Linux Counter #395633
IRC: robsonpeixoto
Twitter: http://twitter.com/rrspba
github: https://github.com/robsonpeixoto
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Disabling ipv6

[Fernando Lozano]

Hi Tim,

Many ISPs will, also, have to buy new equipment. For some of them, at 
great expense. They're not going to do that unless they have to. Some 
have been avoiding it just because the technicalities of it are a new 
nightmare that they don't want to have to deal with (new security 
issues, new network configuring, new customer support issues). 
I don't know there, but here ISPs are not well known for investing in 
human resources. :-( I'd guess some big corporations will really adopt 
IPv6 before most ISPs. I just don't think it's time for SMBs to work 
(fight) with IPv6, they should wait for product to mature and best 
practives to be agreed to.



The interim solution has been to grab back already allocated, but 
currently un-used, IPv4 addresses. This solution will be short-lived, 
but I haven't seen an predictions for when it'll run out of available 
IPv4 addresses. If manufacturers and software programmers don't pull 
their fingers out, we'll be faced with even more ISPs subjecting their 
clients to NAT.

It seems the first test is very simple,
seeing if there is an  DNS record.
Then there is a second test which I did not understand.
But no site that failed the  test came good in the second.

If there is no IPv6 IP address for something, then there can be no IPv6
type of connection to it.



--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: [GW-C] [ECOTONE] Re: rant of the day: installing fedora

[Ian Malone]

On 12 July 2013 12:23, Patrick O'Callaghan  wrote:
> On Thu, 2013-07-11 at 23:45 -0400, Rahul Sundaram wrote:
>> Hi
>>
>>
>> On Thu, Jul 11, 2013 at 10:11 PM, D. Hugh RedelmeierAnaconda's screens
>> need to be more wordy to make things clearer
>> and less scary to the user.
>>
>>
>> Perhaps you can file a bug report?  It appears in this thread, noone
>> yet has done this
>
> Like most people I tend to use the installer only once per new release,
> so if it isn't straightforward it can be difficult, in the relief of
> managing to get past it, to remember the exact sequence of failures and
> retries one has gone through, in order to formulate a useful bug report.
>>
> A poor excuse, but my own.
>

Nailed it, not many people will go through the installer enough times
to work out how it actually works and how it should work. I've done
various live installs for testing, but by the time you've done that
you're familiar enough with what's going on that it doesn't occur to
you anymore.

-- 
imalone
http://ibmalone.blogspot.co.uk
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

new rant of the day: anaconda and fedup are...

[Fernando Lozano]

GREAT

;-)


Thanks a lot Fedora developers.


[]s, Fernando Lozano

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: R: F18 ti F19: can't create a Java virtual machine

[Fernando Lozano]

Hi,

Please see bug

https://bugzilla.redhat.com/show_bug.cgi?id=983677

for a description of the same issue and a workaround.

The default java configured on alternatives doesn't exists. Just change 
the default to the openjdk entrey ending in ".i386"



[]s, Fernando Lozano


Computer n.1 says

alternatives --config java

Ci sono 3 programmi che forniscono 'java'.

  SelezioneComando
---
*+ 1   /usr/lib/jvm/jre-1.7.0-openjdk/bin/java
   2   /usr/lib/jvm/jre-1.5.0-gcj/bin/java
   3   /usr/lib/jvm/jre-1.7.0-openjdk.i386/bin/java

Invio per mantenere l'attuale selezione[+], o inserire il numero di 
selezione:




Computer n.2 says

Ci sono 2 programmi che forniscono 'java'.

  SelezioneComando
---
   1   /usr/lib/jvm/jre-1.5.0-gcj/bin/java
*+ 2   /usr/lib/jvm/jre-1.7.0-openjdk.x86_64/bin/java

Invio per mantenere l'attuale selezione[+], o inserire il numero di 
selezione:




Computer n.3 says

Ci sono 2 programmi che forniscono 'java'.

  SelezioneComando
---
*+ 1   /usr/lib/jvm/jre-1.7.0-openjdk/bin/java
 2   /usr/lib/jvm/jre-1.7.0-openjdk.i386/bin/java


Computer n.3 cannot open the Java virtual machine...


Messaggio originale
Da: antonio.montagn...@alice.it
Data: 12-lug-2013 6.44
A: "Community support for Fedora users"
Ogg: F18 ti F19: can't create a Java virtual machine

We made un update to a laptop, fedup worked very well but now user
when
starts arduino gets a message (we can see it in a terminal) that
can't
create a Java virtual machine. Same Arduino worked fine in F18

Any idea???
-- 
Antonio M

Skype: amontag52

Linux Fedora F19(Schroedinger's cat) on Acer 5720

http://lugsaronno.altervista.org
http://www.campingmonterosa.com




-- 
users mailing list

users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org






-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: [GW-C] [ECOTONE] Re: rant of the day: installing fedora

[François Patte]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Le 12/07/2013 05:45, Rahul Sundaram a écrit :
> Hi
> 
> 
> On Thu, Jul 11, 2013 at 10:11 PM, D. Hugh RedelmeierAnaconda's screens
> need to be more wordy to make things clearer
> 
> and less scary to the user.
> 
> 
> Perhaps you can file a bug report?  It appears in this thread, noone yet
> has done this

File a bug report on what? So many problems with this "new" anaconda!
the partitionning problem, the lack of keyboard selection in rescue
mode

And now: backward compatibility to upgrade old fedora install which
seems to be not recognised by f18 installer: I installed an f10 on two
disks in a raid array using lvm.

I tried to install f18 using the previous raid config and partitionning:
f18 installer is unable to do anything: it sees the raid, but I cannot
reuse it (nor the partitions): everything is gray and you cannot access
to anything.

awkward compatibility!

F.P.


- -- 
François Patte
UFR de mathématiques et informatique
Laboratoire CNRS MAP5, UMR 8145
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. +33 (0)1 8394 5849
http://www.math-info.univ-paris5.fr/~patte
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAlHgCIoACgkQdE6C2dhV2JXEoACfYYJQNhSBrQKf3skcqIwhQpUU
cNQAn1fIByrP2TRnImeTLRE4G3S7B1mK
=Fb9q
-END PGP SIGNATURE-
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Disabling ipv6

[Chris Adams]

Once upon a time, Fernando Lozano  said:
> I don't know there, but here ISPs are not well known for investing
> in human resources. :-( I'd guess some big corporations will really
> adopt IPv6 before most ISPs. I just don't think it's time for SMBs
> to work (fight) with IPv6, they should wait for product to mature
> and best practives to be agreed to.

The best practices have largely been agreed to (as much as any best
practices ever are).  IPv6 is as mature as it can get until a billion
end-users get on it.  Large ISPs around the world have rolled it out in
production.  Major OSes support it out-of-the-box.

If you don't even try to understand it, you are being left behind
already.
-- 
Chris Adams 
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: [OT] Seth Vidal, creator of "yum" killed in bike accident

[Jatin K]

On Wednesday 10 July 2013 01:59 AM, staticsafe wrote:

http://durham.io/2013/07/09/seth-vidal-creator-of-yum-open-source-software-killed-in-bike-accident-off-hillandale-rd/

May he rest in peace.



RIP ...

condolences to his family


--
   _
  °v°
 /(_)\
  ^ ^  Jatin Khatri
RHCSA,RHCE,CCNA
Registerd Linux user No #501175
www.linuxcounter.net
No M$

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Disabling ipv6

[Chris Adams]

Once upon a time, Tim  said:
> How is your firewall set up?  When you allow something for IPv4, does it
> make a corresponding rule for IPv6, at the same time.  Likewise, for if
> you block something.  And I mean that in two ways, dealing with ports,
> and addresses.  I may decide to block all port 80 traffic, and I'd hope
> my firewall doesn't just put a block on IPv4 traffic, requiring me to
> separately set up another rule for the IPv6.  Or, I may find out that
> I'm seeing unwanted traffic from www.example.com, I'll probably have to
> find out their IPv4 and IPv6 IPs and individually block them.

Except for trying to block things by hostname (which is always a
problem, since DNS changes all the time), yes.  My firewall does all of
that.  As far as I know, the CPE advertising IPv6 support does that.
I'm pretty sure the Windows software firewall does that (don't know
anything about Mac OS X).

Does _every_ firewall that claims IPv4 and IPv6 support do that
correctly?  I don't know, probably not.  But at the same time, does
every firewall that claims IPv4 support handle all of the above
correctly, 100% of the time?  Probably not.  There will always be bugs,
design flaws, etc.

> Then there's address range types.  With IPv4 it's easy enough to have a
> demarcation point between one side of my LAN and the WWW, and set rules
> about it.  IPv6 uses a different technique of addressing/subnetting, and
> in some of my earlier readings of it, doesn't really work in a similar
> way that you can do that kind of demarcation.  There's not that level of
> distinction between LAN and WAN.

Yes, IPv4 and IPv6 addresses are different (that's kind of the point).
The whole idea that somehow RFC1918 space is "magic" (I hear people call
it "unroutable" all the time, which is flat wrong) came in with NAT and
is bad, as anybody who has dealt with enterprise networks (and
especially when companies merge, interconnect, etc.) can tell you.

If you want something similar to RFC1918 space with IPv6, you can use
ULA, but you really shouldn't.

> So there's those basic levels of security, before anybody even worries
> about flaws in IPv6, itself.

I don't see anything here much other than "it is different and different
is bad"; certinaly not any of the supposed "security flaws".
-- 
Chris Adams 
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Disabling ipv6

[Fernando Lozano]

Hi,

You keep talking about IPv6 security risks (over IPv4), but haven't
cited any.

While I don't know of security risks of IPv6, itself, there is this:
If you follow IPv6 on the net you should have found lots of articles 
about this, and how it affects specially home users and SMBs. Here are 
some introductory links:


http://thepcsecurity.com/ipv6-security-issues-concerns-transition/
http://searchsecurity.techtarget.com/tip/Analysis-Vast-IPv6-address-space-actually-enables-IPv6-attacks
http://searchsecurity.techtarget.com/tip/IPv6-myths-Debunking-misconceptions-regarding-IPv6-security-features

Most vendors and ISPs won't talk about his -- IPv6 is a selling point -- 
but here's buried inside an AT&T white paper:


http://www.webtorials.com/main/resource/papers/att/paper28/IPv6_impact_network.pdf

"According to the National Institute of Standards and Technology (NIST):
Prevention of unauthorized access to IPv6 networks will likely be
more difficult in the early years of IPv6 deployments. IPv6 adds more
components to be filtered than IPv4, such as extension headers,
multicast addressing, and increased use of ICMP. These extended
capabilities of IPv6, as well as the possibility of an IPv6 host
having a number of global IPv6 addresses, potentially provides an
environment that will make network-level access easier for attackers
due to improper deployment of IPv6 access controls. Moreover,
security related tools and accepted best practices have been slow
to accommodate IPv6. Either these items do not exist or have not
been stress tested in an IPv6 environment"

For more techinical content, you can visit

http://www.gont.com.ar/

which is Fernando Gont home page (author of some IETF RFCs), and see 
theslides at


http://www.si6networks.com/presentations/ipv6kongress/mhfg-ipv6-kongress-ipv6-security-assessment.pdf



How is your firewall set up?
That's not the question. I am an experienced sysadmin and networking 
expert, I know where to search for information and what to look for. But 
today most computer users, not just Fedora users, do not have this 
expertise and won't spend enough time researching. They expect to get 
minimally secure default from vendors and open source projects. 
something most DO NOT provide currenty, regarding IPv6. :-(


The fact is: today, even most experienced network admins do not know 
enough about IPv6 security. Most ones I talked to still believe "IPv6 is 
more secure by design" which it isn't.



[]s, Fernando Lozano

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: psmouse-alps-1.3 and f19

[Robson Roberto Souza Peixoto]

Maybe I founded the problem:

$ fgrep MOUSE_PS2 /usr/src/kernels/3.9.9-301.fc19.x86_64/.config
CONFIG_MOUSE_PS2=y
CONFIG_MOUSE_PS2_ALPS=y
CONFIG_MOUSE_PS2_LOGIPS2PP=y
CONFIG_MOUSE_PS2_SYNAPTICS=y
CONFIG_MOUSE_PS2_CYPRESS=y
CONFIG_MOUSE_PS2_LIFEBOOK=y
CONFIG_MOUSE_PS2_TRACKPOINT=y
CONFIG_MOUSE_PS2_ELANTECH=y
CONFIG_MOUSE_PS2_SENTELIC=y
# CONFIG_MOUSE_PS2_TOUCHKIT is not set


The CONFIG_MOUSE_PS2 need be a module, because after the compilation, I'll
need to remove the old psmouse module e use the newer.

So, unfortunately I'll need to recompile the kernel =/

Thanks


On Fri, Jul 12, 2013 at 10:17 AM, Robson Roberto Souza Peixoto <
robsonpeix...@gmail.com> wrote:

>
>
>
> On Fri, Jul 12, 2013 at 10:09 AM, Carlos "casep" Sepulveda <
> ca...@fedoraproject.org> wrote:
>
>> On 12 July 2013 09:06, Robson Roberto Souza Peixoto
>>  wrote:
>> > Consult the make.log in the build directory
>> > /var/lib/dkms/psmouse/alps-1.3/build/ for more information.
>>
>>
>> And what's the content of that?
>>
>
> Sorry, I forget to copy it. =D
>
> # cat /var/lib/dkms/psmouse/alps-1.3/build/make.log
> DKMS make.log for psmouse-alps-1.3 for kernel 3.9.9-301.fc19.x86_64
> (x86_64)
> Sex Jul 12 09:59:56 BRT 2013
> make: Entrando no diretório `/usr/src/kernels/3.9.9-301.fc19.x86_64'
>   CC  /var/lib/dkms/psmouse/alps-1.3/build/src/psmouse-base.o
>   CC  /var/lib/dkms/psmouse/alps-1.3/build/src/synaptics.o
>   CC  /var/lib/dkms/psmouse/alps-1.3/build/src/alps.o
>   CC  /var/lib/dkms/psmouse/alps-1.3/build/src/elantech.o
>   CC  /var/lib/dkms/psmouse/alps-1.3/build/src/logips2pp.o
>   CC  /var/lib/dkms/psmouse/alps-1.3/build/src/lifebook.o
>   CC  /var/lib/dkms/psmouse/alps-1.3/build/src/sentelic.o
>   CC  /var/lib/dkms/psmouse/alps-1.3/build/src/trackpoint.o
>   LD  /var/lib/dkms/psmouse/alps-1.3/build/src/psmouse.o
>   MODPOST 0 modules
> make: Saindo do diretório `/usr/src/kernels/3.9.9-301.fc19.x86_64'
>
>
>
>>
>>
>> --
>> "My name is Ozymandias, king of kings:
>> Look on my works, ye Mighty, and despair!"
>> Percy Bysshe Shelley
>> http://sites.google.com/site/carlossepulveda
>> --
>> users mailing list
>> users@lists.fedoraproject.org
>> To unsubscribe or change subscription options:
>> https://admin.fedoraproject.org/mailman/listinfo/users
>> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
>> Have a question? Ask away: http://ask.fedoraproject.org
>>
>
>
>
> --
> Robson Roberto Souza Peixoto
> Robinho http://robsonpeixoto.com/
> Master in Computer Science, University of Campinas
> Linux Counter #395633
> IRC: robsonpeixoto
> Twitter: http://twitter.com/rrspba
> github: https://github.com/robsonpeixoto
>



-- 
Robson Roberto Souza Peixoto
Robinho http://robsonpeixoto.com/
Master in Computer Science, University of Campinas
Linux Counter #395633
IRC: robsonpeixoto
Twitter: http://twitter.com/rrspba
github: https://github.com/robsonpeixoto
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Disabling ipv6

[Fernando Lozano]

Hi Chris,

The best practices have largely been agreed to (as much as any best 
practices ever are). IPv6 is as mature as it can get until a billion 
end-users get on it. Large ISPs around the world have rolled it out in 
production. Major OSes support it out-of-the-box. If you don't even 
try to understand it, you are being left behind already. 


IPv6 has alot of "under the carpet" issues because vendors fear too much 
discussion about this will delay large-scale use even more. Every sane 
person agree the world needs to move to IPv6, but IMHO this is not being 
done in the most responsible manner.


I propose we let the billion dollars companies do the hard work, but at 
the same protect SMBs from IPv6. The Fedora Project could do their part 
by disabling IPv6 by default.


Please see my message providing links about IPv6 security threats, 
including recent slides (this year!) from IETF members. I do my homework 
before making statements on the net.



[]s, Fernando Lozano

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Disabling ipv6

[Chris Adams]

Once upon a time, Fernando Lozano  said:
> IPv6 has alot of "under the carpet" issues because vendors fear too
> much discussion about this will delay large-scale use even more.

Again: citation needed.  Without any actual issues sited, you are just
spreading FUD.

> I propose we let the billion dollars companies do the hard work, but
> at the same protect SMBs from IPv6. The Fedora Project could do
> their part by disabling IPv6 by default.

Again, you are years too late.  Fedora would be greatly regressing (and
falling far behind mainstream OSes) by disabling IPv6.

> Please see my message providing links about IPv6 security threats,
> including recent slides (this year!) from IETF members. I do my
> homework before making statements on the net.

I took a look at a couple, but just saw more FUD and stopped.
-- 
Chris Adams 
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: [389-users] problems with dsgw

[Barton, Joseph B.]

>Date: Thu, 11 Jul 2013 14:55:01 -0600
>From: Rich Megginson 
>To: 389-us...@lists.fedoraproject.org
>Subject: Re: [389-users] problems with dsgw
>Message-ID: <51df1ba5.5010...@redhat.com>
>Content-Type: text/plain; charset=UTF-8; format=flowed

>On 07/11/2013 02:32 PM, Barton, Joseph B. wrote:
>> Hi,
>>
>> I am just starting to work with 389 on centos 6.3 , and run into a
bit 
>> of a snag on a test install of 389.  Everything seems to work fine 
>> with the basic install.  I am able to  access the 
>> /usr/bin/389-console, run commands from a prompt, plus I am able to 
>> access the 389 administration express page from the web server
running on port 9830.
>>
>> We need to be able to utilize the directory server gateway web 
>> interface.  After verifying the 389-dsgw-1.1.10-1.el6_3.x86_64 was 
>> installed along with the rest of the 389 packages, I then ran the 
>> setup-ds-admin.pl script.  This seemed to complete without error, and

>> I was then able to go to the web server running on port 9830 and 
>> notice that the directory server express, directory server org charts

>> and (most
>> importantly) directory server gateway links were now added to the
page.

>I'm assuming you meant "ran setup-ds-admin.pl first, then ran
setup-ds-dsgw"?
Yes!
>>
>>
>> The problems are that I get a "Not Found" error for each of the newly

>> added links.
>> 1. If I click on directory server gateway I get:
>> Not Found
>> The requested URL /clients/dsgw/bin/lang was not found on this
server.
>>
>> 2. If I click on directory server gateway I get:
>> Not Found
>> The requested URL /clients/dsgw/bin/lang was not found on this
server.
>>
>> 3. If I click on the Directory Server Org Charts link, I get:
>> Not found
>> The requested URL /clients/orgchart/html/index.html was not found on 
>> this server.
>>
>> All documentation seems to point that this should be working.
>>
>> I would appreciate it if someone could point me in the right
direction 
>> to get this fixed.
>>
>> Thanks!
>>
>> Joe
>> --
--
389 users mailing list
389-us...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users

Re: [OT] Seth Vidal, creator of "yum" killed in bike accident

[Jatin K]

On Friday 12 July 2013 04:29 AM, Ranjan Maitra wrote:

I liked the suggestions of Biker Yum or Yummy Cycles as names for F20.
Perhaps could use one of these or similar and have the dedication to
him also.

Ranjan


FREE 3D EARTH SCREENSAVER - Watch the Earth right on your desktop!
Check it out at http://www.inbox.com/earth



+1 for Yummy Cycles

--
   _
  °v°
 /(_)\
  ^ ^  Jatin Khatri
RHCSA,RHCE,CCNA
Registerd Linux user No #501175
www.linuxcounter.net
No M$

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Disabling ipv6

[Fernando Lozano]

Hi,


Tim:

If manufacturers and software programmers don't pull their fingers
out, we'll be faced with even more ISPs subjecting their clients to
NAT.

Fernando Lozano:

Would this be so bad? Most people at work have been working using NAT
for years. NAT increases security. Most internet users don't need to
run servers.

Yes it would.  NAT doesn't really increase security.  It gives the
illusion of doing so, because it usually breaks networking, but not
always (just one reason why you shouldn't pretend it's a firewall).
IMHO globaly-addressable client devices increase security risks. NAT 
make some things more complicated, but I'd rather improve NAT 
technologies and application protocols to work with then. Many experts 
argue in favor of NAT even for IPv6 networks, see for example:


http://searchenterprisewan.techtarget.com/tip/Why-IPv6-wont-rid-the-Internet-of-Network-Address-Translation


Users do things that act like servers, and require connections to get
through to them.
IMHO they shouldn't. End users will never know enough to implement 
proper network security. Cloud services would provide better 
alternatives to most "server-like" things users would want to do, with 
cheap and free options.



Just a few things that become nightmarish with NAT:

   Using some FTP servers.
It's a protocol broken by design, with connection call-back connections. 
I'd eliminate FTP altogether.




   Sending files through instant messenger clients.
Put Dropbox, Google Drive or the like suppport in IM clients. Push for a 
standard REST API for this kind of services, so IM developers don't have 
to write code for a myriad different services.




   Voice over IP.
Improve VoIP protocols. Most VoIP users will anyway depend on 
centralized servers for realiability (like Skype supernodes), presence, 
authentication, or interoperability with POTS and cell services.




   Using any type of peer-to-peer software.
IMHO peer-to-peer in general is a boken concept. It's nice for 
experimentation, good for politics (you won't depend on a big 
corporation) but increases network security risk. There are technical 
alternatives to peer-to-peer designs that IMHO lend to better security 
and QoS. On the political side, standards and ONGs should prevent 
dominance by big corporations.


Cloud VPN services would allow end-users to get connections to their 
home machines if they want, at the same without exposing them to scans 
and attacks from the whole Internet. I'd focus on improving those offering.



[]s, Fernando Lozano

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Fedup from 17 -> 19 okay?

[Fernando Lozano]

Me also, except for the Java issue (which is easy to fix using 
alternatives).



If anyone is interested, it worked fine.

On Thu, Jul 11, 2013 at 1:59 PM, Robert Arkiletian  wrote:

Can I skip 18 and upgrade from 17 to 19 with fedup?
Has anyone tried this with success or failure?


--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: [OT] Seth Vidal, creator of "yum" killed in bike accident

[Sylvia Sánchez]

+1 to Yummy Cycles


LAILAH
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: [389-users] problems with dsgw

[Rich Megginson]

On 07/12/2013 08:33 AM, Barton, Joseph B. wrote:

Date: Thu, 11 Jul 2013 14:55:01 -0600
From: Rich Megginson 
To: 389-us...@lists.fedoraproject.org
Subject: Re: [389-users] problems with dsgw
Message-ID: <51df1ba5.5010...@redhat.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
On 07/11/2013 02:32 PM, Barton, Joseph B. wrote:

Hi,

I am just starting to work with 389 on centos 6.3 , and run into a

bit

of a snag on a test install of 389.  Everything seems to work fine
with the basic install.  I am able to  access the
/usr/bin/389-console, run commands from a prompt, plus I am able to
access the 389 administration express page from the web server

running on port 9830.

We need to be able to utilize the directory server gateway web
interface.  After verifying the 389-dsgw-1.1.10-1.el6_3.x86_64 was
installed along with the rest of the 389 packages, I then ran the
setup-ds-admin.pl script.  This seemed to complete without error, and
I was then able to go to the web server running on port 9830 and
notice that the directory server express, directory server org charts
and (most
importantly) directory server gateway links were now added to the

page.


I'm assuming you meant "ran setup-ds-admin.pl first, then ran

setup-ds-dsgw"?
Yes!


Did you restart admin server?



The problems are that I get a "Not Found" error for each of the newly
added links.
1. If I click on directory server gateway I get:
Not Found
The requested URL /clients/dsgw/bin/lang was not found on this

server.

2. If I click on directory server gateway I get:
Not Found
The requested URL /clients/dsgw/bin/lang was not found on this

server.

3. If I click on the Directory Server Org Charts link, I get:
Not found
The requested URL /clients/orgchart/html/index.html was not found on
this server.

All documentation seems to point that this should be working.

I would appreciate it if someone could point me in the right

direction

to get this fixed.

Thanks!

Joe
--

--
389 users mailing list
389-us...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users


--
389 users mailing list
389-us...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users

Re: [Samba] About NAS versus Samba

[Fernando Lozano]

Hi Andrew,

I work on a NAS product myself, and at this vendor and my previous 
vendor Samba 4.0 as an AD DC was all I ever needed to use to test the 
AD integration features of the NAS. Thanks, Andrew Bartlett 
Please tell me which product this is, so I can contact the local 
reseller. :-) You can send me in pvt if you think it would not be 
ethical to advertise your employee on the list.


Sales people here (and their "technical" consultants) don't know / don't 
care about Samba. Every time I ask about samba compatibility they try to 
sell me Windows and VmWare licenses. They even lie trying to make my 
employee buy those licenses and ditch Linux altogether.


I am only saved because of some previous incidents where I told my boss 
"either they are lying or they don't know", showing technical references 
from vendors themselves and standards bodies, but was overruled. Later 
my boss found I was right the had way: products didn't worked as 
expected, company lost money.


Most non-IT people, even many IT people, wrongly believe the vendor 
people should be the better experts and so any conflict of opinion they 
should be right. When it fails, the IT manager or the business area 
manager hide it, so they don't take blame for the wrong decision 
consequences. :-(


If I someone tell me "this product works" I can by knowing if something 
bad happens it's something I can solve. Sometimes the management 
interface for a product won't let you do things the embebed software 
could do, so I don't want to risk a product without someone telling me 
"this one worked for me".



[]s, Fernando Lozano
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

idea for F20 release name to honor Seth

[Matthew Miller]

On Fri, Jul 12, 2013 at 11:48:00AM -0300, Sylvia Sánchez wrote:
> +1 to Yummy Cycles

The F20 name nomination period is officially over, but we haven't had the
vote yet. I suppose this should be a ticket with FESCO or the Fedora Board
if people are really interested in making this happen.

https://fedorahosted.org/fesco/
https://fedorahosted.org/board/

It's also worth remembering that Seth was in favor of dropping the naming
process altogether --
https://lists.fedoraproject.org/pipermail/advisory-board/2012-March/011419.html
but didn't really _hate_ them  --
https://lists.fedoraproject.org/pipermail/advisory-board/2012-March/011427.html
.

This makes Jef Spatela's tweet on the subject
https://twitter.com/jspaleta/status/354740898371862529
ring particulary true. I think it's the kind of joke that Seth would have
rolled his eyes at and secretly appreciated.

I wish I could ask him.


-- 
Matthew Miller  ☁☁☁  Fedora Cloud Architect  ☁☁☁  
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Disabling ipv6

[Fernando Lozano]

Hi,


NAT is a fact today, has been for years, and people have been using
Bittorrent and Skype regardless.

And sometimes they (and other applications) don't work, because of
things like layered NAT.

Fix NAT issues instead of ditch it altogether.


For home users and SMBs, NAT is something that was taken care of.
IPv6 is a whole new bunch of risks. I am not against IPv6 per se. I
am against wide use of IPv6 right now. Let it mature.

How will it "mature" if nobody tries it?  Fedora is a leading-edge
operating system, and full IPv6 support is part of that.
Fedora servers many different kinds of users, some of then are not 
network people and would be hurt by current IPv6 problems. The network 
people can enable IPv6, other should't have to disable it. That's the 
same principle as don't let TCP ports open by default on iptables.



As IPv4 runs out, some ISPs are turning to "Carrier Grade NAT", which
adds layers of NAT that break things like P2P applications and IPSec.

I'll happily trade IPSec for OpenVPN. ;-)

That's nice, but in the real world, users have to connect to VPNs
configured by others (and many businesses need hardware VPN
concentrators, which OpenVPN won't work with).
In the real world, ISPs should fix their Carrier Grande NAT. There are 
lots of ways wrong network configs can 0impact apps.



To just use the network they need only IPv4.

That is not true in some places (and the number of such places is
increasing all the time).
Defaults should focus most users, not the exceptions. When most users 
need IPv6, it's ok to have it enabled by default.


Plese note I ain't proposing removing IPv6 support from the Fedora Linux 
Kernel. I'm just proposing the default network configurations should 
have IPv6 disabled, and those who want to use it should have to take 
action (just click a checkbox) to enable.



They don't need the
security risks that current IPv6 implementation and default
configurations adds. Today, IPv6 is far from "just works". You are
advocating using all end users as guiena pigs for IPv6 evolution. I
advocate evolving IPv6 before exposing end users to ti.

You are several years behind the curve on IPv6.

You keep talking about IPv6 security risks (over IPv4), but haven't
cited any.
Please see my other message about them, won't repeat the links here. You 
could just google "IPv6 security risks" to see articles from the current 
year about then. And follow IETF RFCs to see how many proposals about 
them are in Draft and not implement by most products yet. PLease don't 
assume people who disagree with you no clue what they are talking about.




IPv6 does "just work" in many places; there are a lot of people that are
using IPv6 and don't even know it
And those are exposed to the security risks. We haven't see a 
high-profile (media coverage) IPv6 attach yet just because so few peple 
actually use it that it's not very attractive to hackers. But as ISPs 
move on implements proper IPv6 support (without tunnels internally) 
those ISP users are becoming so vulnerable.




Whether you like it or not, IPv6 is here today and is here to stay.
There is no practical alternative.  Will there be bugs?  Yes, of course;
people are still finding IPv4 bugs as well.
Will tell again: I'm bot against IPv6 per se. I agree it has to be 
deployed. But I can't agree using end users and SMBs as guinea pigs, 
waiting to see how hackers use it to create new attacks. Let the big 
companies work this before giving IPv6 enabled by default in Fedora, 
Windows, Mac and other OSes.



[]s, Fernando Lozano

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: idea for F20 release name to honor Seth

[Bruno Wolff III]

When this came up in reference to Dennis Ritchie's death during the F16 
development cycle, the decision was made to do a dedication rather 
than naming the release after him. This isn't identical to the situation 
with Seth since he was a community member, but I still think the reasoning 
applies. If people want to see what was done, take a look at: 
http://fedoraproject.org/wiki/F16_release_announcement

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: idea for F20 release name to honor Seth

[Clive Hills]

+1 to do what we did re Dennis.


On Fri, Jul 12, 2013 at 4:21 PM, Bruno Wolff III  wrote:

> When this came up in reference to Dennis Ritchie's death during the F16
> development cycle, the decision was made to do a dedication rather than
> naming the release after him. This isn't identical to the situation with
> Seth since he was a community member, but I still think the reasoning
> applies. If people want to see what was done, take a look at:
> http://fedoraproject.org/wiki/**F16_release_announcement
>
> --
> users mailing list
> users@lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.**org/mailman/listinfo/users
> Guidelines: 
> http://fedoraproject.org/wiki/**Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
>



-- 
Clive
 -- 077222971491
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: [GW-C] [ECOTONE] Re: rant of the day: installing fedora

[Rahul Sundaram]

Hi


On Fri, Jul 12, 2013 at 9:45 AM, François Patte <
francois.pa...@mi.parisdescartes.fr> wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Le 12/07/2013 05:45, Rahul Sundaram a écrit :
>
>
> File a bug report on what? So many problems with this "new" anaconda!
> the partitionning problem, the lack of keyboard selection in rescue
> mode 


For any or all the problems one might have.   You could do it in a VM just
to test and report the problems as well.   Feel free to post the links here
so that others can provide their feedback as well.   If you want to discuss
it first, use the Anaconda devel list.   I don't think any of the installer
developers are in this list.

Rahul
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Fedup 17->18 won't boot, all partitions are GPT

[Rick Walker]

Hi Ian,

> > I did a fedup from F17 to F18 on my work desktop.  Now I get an
> > infinite boot loop.  Fdisk can't look at the partition table of
> > /dev/sda because it has been coverted to GPT format (who did that?). 

Ian Chapman  writes:
> When dealing with GPT partition tables, parted is probably the tool you 
> want use as fdisk doesn't understand them. 
> 
> What does the output of "fdisk -l /dev/sda" show? I would expect it to 
> look something like
> 
> Device Boot  Start End  Blocks   Id  System
> /dev/sda1   1   625142447   312571223+  ee  GPT

Thanks for the comments, Ian.  I checked with parted and have the
same disk setup as you.  I also can see my old partitions using
the "parted /dev/sda print" command.

I guess my grub setup got hosed somehow, and the GPT conversion is a
red-herring. 

I'm downloading an F18 live image to try a rescue on the boot
setup.  An f17 image was unable to cope with the GPT conversion.
After saying that it identified and mounted the old root
partition (but "may have had some problems"), the mount point was
null.  Maybe F18 can fix itself.

--
Rick Walker


-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Proposal: Fedora should install with IPv6 disabled by default [was: Re: Disabling ipv6]

[Fernando Lozano]

Hi Chris,

[As I changed the subject, let me clear: IPv6 still compiled in the 
kernel. Just the network interfaces configs that should come with IPv6 
disabled by default, if the user wants it should be easy to enable]



Once upon a time, Fernando Lozano  said:

IPv6 has alot of "under the carpet" issues because vendors fear too
much discussion about this will delay large-scale use even more.

Again: citation needed.  Without any actual issues sited, you are just
spreading FUD.
Works both ways. You can't claim I'm just spreading FUD withou evidence 
to corroborate your claim.


Anyway I've alread sent to the list evidence that the IPv6 security 
issues are real. As for "vendors fear too much discussion" it's really 
my personal interpretation of their silence, fell free to disagree. But 
please don't deny anymore there are IPv6 security issues, this is a hard 
fact.



I propose we let the billion dollars companies do the hard work, but
at the same protect SMBs from IPv6. The Fedora Project could do
their part by disabling IPv6 by default.

Again, you are years too late.  Fedora would be greatly regressing (and
falling far behind mainstream OSes) by disabling IPv6.
Fedora should take the lead and be more responsible to their users. It 
would be an improvement, not a regression.



Please see my message providing links about IPv6 security threats,
including recent slides (this year!) from IETF members. I do my
homework before making statements on the net.

I took a look at a couple, but just saw more FUD and stopped.
Fell free to ignore reallity when it doesn't agree with your personal 
opinion. But be warned reallity will hurt you anyway.


Or will you tell me that IETF people don't know what they are talking 
about? See for example:


http://tools.ietf.org/html/draft-ietf-v6ops-ra-guard-implementation-07
http://tools.ietf.org/html/draft-gont-6man-flowlabel-security-03
http://tools.ietf.org/html/draft-ietf-6man-nd-extension-headers-05

Papers from them, and even very recent RFCs on the security issues, can 
be foud if you take the time to follow my links and the links contained 
in them.



[]s, Fernando Lozano

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: idea for F20 release name to honor Seth

[Ranjan Maitra]

I agree, but we are not suggesting naming the release after him, but
something that some of us think would be a good but indirect way of
honoring him.

Of course, I would not mind dropping the naming process altogether

Ranjan

On Fri, 12 Jul 2013 16:31:03 +0100 Clive Hills 
wrote:

> +1 to do what we did re Dennis.
> 
> 
> On Fri, Jul 12, 2013 at 4:21 PM, Bruno Wolff III  wrote:
> 
> > When this came up in reference to Dennis Ritchie's death during the F16
> > development cycle, the decision was made to do a dedication rather than
> > naming the release after him. This isn't identical to the situation with
> > Seth since he was a community member, but I still think the reasoning
> > applies. If people want to see what was done, take a look at:
> > http://fedoraproject.org/wiki/**F16_release_announcement
> >
> > --
> > users mailing list
> > users@lists.fedoraproject.org
> > To unsubscribe or change subscription options:
> > https://admin.fedoraproject.**org/mailman/listinfo/users
> > Guidelines: 
> > http://fedoraproject.org/wiki/**Mailing_list_guidelines
> > Have a question? Ask away: http://ask.fedoraproject.org
> >
> 
> 
> 
> -- 
> Clive
>  -- 077222971491


-- 
Important Notice: This mailbox is ignored: e-mails are set to be
deleted on receipt. For those needing to send personal or professional
e-mail, please use appropriate addresses.


GET FREE SMILEYS FOR YOUR IM & EMAIL - Learn more at 
http://www.inbox.com/smileys
Works with AIM®, MSN® Messenger, Yahoo!® Messenger, ICQ®, Google Talk™ and most 
webmails


-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: [389-users] 389 directory server crash

[Rich Megginson]

On 07/12/2013 08:22 AM, Mitja Mihelič wrote:

On 07/09/2013 03:34 PM, Rich Megginson wrote:

On 07/09/2013 06:43 AM, Mitja Mihelič wrote:

Hi!

We are having problems with some our 389-DS instances. They crash 
after receiving an update from the provider.


After looking at the stack trace, I think this is 
https://fedorahosted.org/389/ticket/47391


The crash happened twice after about a week of running without 
problems. The crashes happened on two consumer servers but not at 
the same time.
The servers are running CentOS 6x with the following 389DS packages 
installed:

389-ds-console-doc-1.2.6-1.el6.noarch
389-console-1.1.7-1.el6.noarch
389-adminutil-1.1.15-1.el6.x86_64
389-dsgw-1.1.10-1.el6.x86_64
389-ds-base-debuginfo-1.2.11.15-14.el6_4.x86_64
389-admin-1.1.29-1.el6.x86_64
389-ds-console-1.2.6-1.el6.noarch
389-admin-console-doc-1.1.8-1.el6.noarch
389-ds-1.2.2-1.el6.noarch
389-ds-base-1.2.11.15-14.el6_4.x86_64
389-ds-base-libs-1.2.11.15-14.el6_4.x86_64
389-admin-console-1.1.8-1.el6.noarch

We are in the process of replacing the Centos 5x base 
consumer+provider setup with a CentOS 6x base one. For the time 
being, the CentOS 6 machines are acting as consumers for the old 
server. They run for a while and then the replicated instances crash 
though not at the same time.

One of the servers did not want to start after the crash,


Can you provide the error messages from the errors log?
I have attached error logs from the provider 
(2013-06-27-provider_error) and the consumer 
(2013-06-27-server_two_error) in question.


so I have run db2index on its database. It's been running for four 
days and it has still not finished. 


Try exporting using db2ldif, then importing using ldif2db.

The export process hangs. After an hour strace still shows:
futex(0x7f5822670ed4, FUTEX_WAIT, 1, NULL
The error log for this is attached as 
2013-07-10-server_two-ldif_import_hangs.


Are you using db2ldif or db2ldif.pl?  If you are using db2ldif, is the 
server running?  If not, please try first shutting down the server and 
use db2ldif.


If db2ldif still hangs, then please follow the instructions at 
http://port389.org/wiki/FAQ#Debugging_Hangs to get a stack trace of the 
hung process.







All I get from db2index now are these outputs:
[09/Jul/2013:13:29:11 +0200] - reindex db: Processed 65095 entries 
(pass 1104) -- average rate 53686277.5/sec, recent rate 0.0/sec, hit 
ratio 0%


How many entries do you have in your database?
The number revolves around 65400. It varies perhaps 2 user del/add 
operations a month and 20 attribute changes per week, if that.




The other instance did start up, but the replication process did not 
work anymore. I disabled the replication to this host and set it up 
again. I chose "Initialize consumer now" and the consumer crashed 
every time.


Can provide a stack trace of the core when the server crashes? This 
may be different than the stack trace below.
The last provided stack trace was produced at the last server crash. I 
will provide another stack trace when CONSUMER_ONE crashes again. 
Currently it refuses to crash at initialization time and keeps running.



I have enabled full error logging and could find nothing.
I have read a few threads (not all, I admit) on this list and 
http://directory.fedoraproject.org/wiki/FAQ#Debugging_Crashes and 
tried to troubleshoot.


The crash produced the attached core dump and I could use your help 
with understanding it. As well as any help with the crash. If more 
info is needed I will gladly provide it.


Regards, Mitja



--
389 users mailing list
389-us...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users






--
389 users mailing list
389-us...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users

Re: Disabling ipv6

[Fernando Lozano]

Hi,

I took me time to recover this one, another more techinical content 
about IPv6 security:


http://w3.antd.nist.gov/iip_pubs/Montgomery-ipv6-security-findings.doc


[]s, Fernando Lozano


Hi,

You keep talking about IPv6 security risks (over IPv4), but haven't
cited any.

While I don't know of security risks of IPv6, itself, there is this:
If you follow IPv6 on the net you should have found lots of articles 
about this, and how it affects specially home users and SMBs. Here are 
some introductory links:


http://thepcsecurity.com/ipv6-security-issues-concerns-transition/
http://searchsecurity.techtarget.com/tip/Analysis-Vast-IPv6-address-space-actually-enables-IPv6-attacks 

http://searchsecurity.techtarget.com/tip/IPv6-myths-Debunking-misconceptions-regarding-IPv6-security-features 



Most vendors and ISPs won't talk about his -- IPv6 is a selling point 
-- but here's buried inside an AT&T white paper:


http://www.webtorials.com/main/resource/papers/att/paper28/IPv6_impact_network.pdf 



"According to the National Institute of Standards and Technology (NIST):
Prevention of unauthorized access to IPv6 networks will likely be
more difficult in the early years of IPv6 deployments. IPv6 adds more
components to be filtered than IPv4, such as extension headers,
multicast addressing, and increased use of ICMP. These extended
capabilities of IPv6, as well as the possibility of an IPv6 host
having a number of global IPv6 addresses, potentially provides an
environment that will make network-level access easier for attackers
due to improper deployment of IPv6 access controls. Moreover,
security related tools and accepted best practices have been slow
to accommodate IPv6. Either these items do not exist or have not
been stress tested in an IPv6 environment"

For more techinical content, you can visit

http://www.gont.com.ar/

which is Fernando Gont home page (author of some IETF RFCs), and see 
theslides at


http://www.si6networks.com/presentations/ipv6kongress/mhfg-ipv6-kongress-ipv6-security-assessment.pdf 





How is your firewall set up?
That's not the question. I am an experienced sysadmin and networking 
expert, I know where to search for information and what to look for. 
But today most computer users, not just Fedora users, do not have this 
expertise and won't spend enough time researching. They expect to get 
minimally secure default from vendors and open source projects. 
something most DO NOT provide currenty, regarding IPv6. :-(


The fact is: today, even most experienced network admins do not know 
enough about IPv6 security. Most ones I talked to still believe "IPv6 
is more secure by design" which it isn't.



[]s, Fernando Lozano



--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

RE: Proposal: Fedora should install with IPv4/6 disabled by default [was: Re: Disabling ipv6]

[J.Witvliet]

If you got scared, why not keep the entire network down?
If you want it, sure you can enable it ;-)

Enjoy your weekend.

-Original Message-
From: users-boun...@lists.fedoraproject.org 
[mailto:users-boun...@lists.fedoraproject.org] On Behalf Of Fernando Lozano
Sent: Friday, July 12, 2013 5:50 PM
To: users@lists.fedoraproject.org
Subject: Proposal: Fedora should install with NETWORK [was IPv6] disabled by 
default [was: Re: Disabling ipv6]

Hi Chris,

[As I changed the subject, let me clear: NETWORK [was: IPv6] still compiled in 
the 
kernel. Just the network interfaces configs that should come with NETWORK 
[was:IPv6] 
disabled by default, if the user wants it should be easy to enable]


__
Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet 
de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u 
verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat 
aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband 
houdt met risico's verbonden aan het electronisch verzenden van berichten.

This message may contain information that is not intended for you. If you are 
not the addressee or if this message was sent to you by mistake, you are 
requested to inform the sender and delete the message. The State accepts no 
liability for damage of any kind resulting from the risks inherent in the 
electronic transmission of messages.
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: what has 'yum update' done?

[Eddie G. O'Connor Jr.]

On 07/12/2013 03:19 AM, Joe Zeff wrote:

On 07/11/2013 11:38 PM, Heinz Diehl wrote:

Only speaking for myself: I always try to upgrade first, having a
complete backup, of course. If it doesn't work, I reinstall. There's
nothing to loose, since I'm expecting to reinstall anyway.


I've had an update fail too, once.  Being retired and having both a 
laptop and a desktop, I've always made sure my laptop gets upgraded 
first and is working properly before upgrading my desktop.  It took me 
several days of work, but I eventually had the satisfaction of getting 
my desktop upgraded without a clean install.  Of course, if I were in 
a production environment, I'd have bitten the bullet, done a fresh 
install (/home is always on its on partition and wasn't affected by 
the bad upgrade.) and started putting things back together, because 
the work I did cleaning things up simply wouldn't have been cost 
effective.  And, probably, if I were working and I had this issue at 
home, I'd have ended up with a new install because there's only so 
many hours per day and so much Copious Free Time to spend cleaning 
up.  It's a trade-off.  For me, the time spent getting things working 
were paid for in the satisfaction of a difficult job well done.  Not 
everybody can afford to think that way.
See?...it's stuff like the stories above that make me hesitant to go 
from 18 to 19I mean can I backup my entier system andf install a 
frssh copy?then put all my stuff back? Sure. But isn't the whole 
purpose of an "upgrade' so that you can do just what it says.."upgrade" 
without fear of losing your valuable data or anything not working 
properly?...I can always just wait for F20 to come out and then move on 
from therebut I might have to ride the F18 wave a bit longer.



EGO II
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: services vs firewall

[Ian Pilcher]

On 07/11/2013 10:41 PM, Amadeus W.M. wrote:
> On Fri, 12 Jul 2013 11:09:15 +0800, Ed Greshko wrote:
>>
>> One question.  Is the nfs server running?
>>
> 
> Thanks, good catch! I too figured it wasn't running because nmap reports 
> closed if the port is open, but nothing's listening on it. So I guess the 
> firewall configuration survived a reboot, but starting nfs didn't. So 
> this is needed:
> 
> systemctl enable nfs-server.service
> 

On Fedora 19, you also need to do:

  systemctl enable nfs.target

See https://bugzilla.redhat.com/show_bug.cgi?id=769879.

-- 

Ian Pilcher arequip...@gmail.com
Sometimes there's nothing left to do but crash and burn...or die trying.


-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

RE: Proposal: Fedora should install with IPv4/6 disabled by default [was: Re: Disabling ipv6]

[Michael Hennebry]

On Fri, 12 Jul 2013, j.witvl...@mindef.nl wrote:


If you got scared, why not keep the entire network down?
If you want it, sure you can enable it ;-)


That is what I do.
If I'm using my computer and need internet access,
I just click on the start-listening icon.
Said icon then becomes a stop-listening icon.

--
Michael   henne...@web.cs.ndsu.nodak.edu
"SCSI is NOT magic. There are *fundamental technical
reasons* why it is necessary to sacrifice a young
goat to your SCSI chain now and then."   --   John Woods
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Proposal: Fedora should install with IPv4/6 disabled by default [was: Re: Disabling ipv6]

[Fernando Lozano]

Hi,


If you got scared, why not keep the entire network down?
If you want it, sure you can enable it ;-)

By your reasoning, Fedora doesn't need to provide secure installation 
defaults. Anyone could craft their own iptables rules and selinux 
policies if they feed a need for better security. And by the way, why 
having trouble provinding services pre-packaged using chroot?



[]s, Fernando Lozano

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Proposal: Fedora should install with IPv6 disabled by default [was: Re: Disabling ipv6]

[Fernando Lozano]

Hi,


[As I changed the subject, let me clear: IPv6 still compiled in the kernel. 
Just the network interfaces configs
that should come with IPv6 disabled by default, if the user wants it should be 
easy to enable]
exactly *that* is my point

it is ridiculous that i bave a clearly static ipv4 config
using network.service as well as "ipv6disable=1" as kernel
param and on a F19 machine with 3.10.0-1.fc20.x86_64 eth0
comes up with "inet6 fe80::20c:29ff:fe30:82b9"

this is not a matter of ipv6 security / yes / no / don't know
it is a matter of if ipv6 would make sense for the network
and would enable and *properly* configure it but this is
not the case because the gateway is for sure not ipv6 capable

i do not need to see any ip-address (ipv4 or ipv6) on a
statically interface which was not explicitly configured
Having a smarter ifconfig / ip tool or ethernet device driver would be a 
way to implement my proposal.


But, by the IPv6 RTFs, just having IPv6 enabled means there is an IPv6 
address for that interface. IPv6 provides local auto-configuration for 
network intefaces, without DHCP or any other infrastrucure being present.


That's one thing that creates security risks: you don't know you could 
be reached by that address.


So, ifconfig or ip or whatever would have to disable IPv6 for any 
interface that does not having an explicit IPv6 address. I'd think it 
would be easier to have the default eth*-cfg files and Network Manager 
disable IPv6 unless the user tells them to enable.



[]s, Fernando Lozano

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

F19 nouveau corrupted graphics

[Jon Dufresne]

Hello,

I am currently running F17. As it is nearing end of life, I am anxious to
upgrade. Around kernel 3.7, I started to experience very heavy graphics
slowdown and corruption. I reported a bug around the time I experienced it <
https://bugzilla.redhat.com/show_bug.cgi?id=912459>. Because F17 has a
version of the 3.6 kernel, I can continue using the desktop without
interruption.

In preparations for upgrading I tested out F19 Beta, Alpha, and final live
CD. All versions show the same bug, creating an unusable desktop.

At this point I'm stuck between F19 which has corrupted graphics; unusable
desktop and F17 which is EOL and will not receive security updates (not to
mentioned outdated).

Any thoughts on what to do?
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: F19 nouveau corrupted graphics

[Kevin Martin]

On 07/12/13 11:56, Jon Dufresne wrote:
> Hello,
> 
> I am currently running F17. As it is nearing end of life, I am anxious to 
> upgrade. Around kernel 3.7, I started to experience very
> heavy graphics slowdown and corruption. I reported a bug around the time I 
> experienced it
> . Because F17 has a 
> version of the 3.6 kernel, I can continue using the desktop
> without interruption.
> 
> In preparations for upgrading I tested out F19 Beta, Alpha, and final live 
> CD. All versions show the same bug, creating an unusable
> desktop.
> 
> At this point I'm stuck between F19 which has corrupted graphics; unusable 
> desktop and F17 which is EOL and will not receive
> security updates (not to mentioned outdated).
> 
> Any thoughts on what to do?
> 
> 
I experienced the same thing and had to set

Option "ShadowFB" "1"

in the Device section of xorg.conf to get nouveau to be usable.  Try that and 
see if things work better.

Kevin

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Disabling ipv6

[Fernando Lozano]

Hi,

hence it would be enough if "ifup" would respect the configuration
i can not see "just having IPv6 enabled means there is an IPv6 address"
below - where is there ipv6 enabled? there is even a "IPV6INIT=no"
I have overlooked that. I'm not a Fedora developer, have to check if 
IPV6INIT means what me and you think it means, but I guess this is a bug.


Have you checked https://bugzilla.redhat.com/show_bug.cgi?id=982740 ?


[]s, Fernando Lozano

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Computer blocked because of error smpboot CPU2: Not responding

[Paul Smith]

Dear All,

I am experiencing the following problem while booting Fedora 19:

smpboot: CPU2: Not responding.

The computer seems to be blocked. Is there some way of rebooting it
without having to power off the computer?

Thanks in advance,

Paul
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Problems running emacs under Fedora-19

[Jonathan Ryshpan]

On Fri, 2013-07-12 at 09:01 +0800, Ed Greshko wrote:
> On 07/12/13 08:35, Jonathan Ryshpan wrote:
> > When I attempt to run emacs it fails:
> >
> > $ emacs
> > emacs: error while loading shared libraries: libgnutls.so.26:
> > cannot open shared object file: No such file or directory
> > $ rpm -q emacs
> > emacs-24.2-19.fc18.x86_64
> >
> > It appears that emacs hasn't been updated to the Fedora-19 libraries,
> > which are on my computer:
> >
> > $ locate libgnutls.so
> > /usr/lib/libgnutls.so.28
> > /usr/lib/libgnutls.so.28.19.0
> > /usr/lib64/libgnutls.so
> > /usr/lib64/libgnutls.so.28
> > /usr/lib64/libgnutls.so.28.19.0
> >
> > libgnutls.so.26 isn't available in the standard Fedora-19 distro, nor
> > can I find emacs-24.2-19.fc19.x86_64 .
> >
> > System is Fedora-19 with all upgrades running on a 4 processor x86_64
> > system.
> >
> > Ideas?  Build from source?
> 
> Are you sure you're fully updated?
> 
> [root@f18x ~]# rpm -q emacs
> emacs-24.2-18.fc19.x86_64
>  
> yum distro-sync  ??

My system was only too well updated.  Note:

On my system:   emacs-24.2-19.fc18.x86_64
On yours:   emacs-24.2-18.fc19.x86_64

Fedora-18 uses a more recent version of emacs than Fedora-19 
so yum and fedup don't upgrade emacs properly.  

yum distro-sync fixes this.

Thanks - jon






-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: F19 nouveau corrupted graphics

[poma]

On 12.07.2013 18:56, Jon Dufresne wrote:
> Hello,
> 
> I am currently running F17. As it is nearing end of life, I am anxious to
> upgrade. Around kernel 3.7, I started to experience very heavy graphics
> slowdown and corruption. I reported a bug around the time I experienced it <
> https://bugzilla.redhat.com/show_bug.cgi?id=912459>. Because F17 has a
> version of the 3.6 kernel, I can continue using the desktop without
> interruption.
> 
> In preparations for upgrading I tested out F19 Beta, Alpha, and final live
> CD. All versions show the same bug, creating an unusable desktop.
> 
> At this point I'm stuck between F19 which has corrupted graphics; unusable
> desktop and F17 which is EOL and will not receive security updates (not to
> mentioned outdated).
> 
> Any thoughts on what to do?

lspci -nn | grep VGA
yum install
http://kojipkgs.fedoraproject.org/packages/kernel/3.11.0/0.rc0.git6.1.fc20/x86_64/kernel-3.11.0-0.rc0.git6.1.fc20.x86_64.rpm
If doesn't work,
https://bugs.freedesktop.org/
https://bugs.freedesktop.org/buglist.cgi?product=xorg&component=Driver%2Fnouveau
http://lists.freedesktop.org/mailman/listinfo/nouveau


poma

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Proposal: Fedora should install with IPv6 disabled by default [was: Re: Disabling ipv6]

[David G . Miller]

Fernando Lozano  lozano.eti.br> writes:

> 
> Hi,
> 
> > [As I changed the subject, let me clear: IPv6 still compiled in the 
kernel. Just the network interfaces configs


Perhaps Fedora is the wrong distribution for you. 

The whole idea behind Fedora is for it to be an "engineering proving 
ground" where new technologies (like IPv6) are rolled out for real world 
use.  In the case of IPv6, this includes hopefully providing the tools 
required for users to be able to securely run a Fedora system with IPv6 
enabled.  If there is a problem with the tools provided then the answer is 
to fix the tools and/or provide additional tools; not pull back from a 
technology that IS coming.

Cheers,
Dave

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Computer blocked because of error smpboot CPU2: Not responding

[Paul Smith]

On Fri, Jul 12, 2013 at 6:49 PM, Paul Smith  wrote:
> I am experiencing the following problem while booting Fedora 19:
>
> smpboot: CPU2: Not responding.
>
> The computer seems to be blocked. Is there some way of rebooting it
> without having to power off the computer?

I believe that the cause of this problem was the fact that I had an
external disk connected to the computer. I have meanwhile unplugged
it, but the booting process is totally blocked and I do not know how
to resume it.

Paul
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Proposal: Fedora should install with IPv6 disabled by default [was: Re: Disabling ipv6]

[poma]

On 12.07.2013 18:44, Fernando Lozano wrote:
…
> So, ifconfig or ip or whatever would have to disable IPv6 for any
> interface that does not having an explicit IPv6 address. I'd think it
> would be easier to have the default eth*-cfg files and Network Manager
> disable IPv6 unless the user tells them to enable.

Looks like you're reading a lot of documents, so it wouldn't be bad to
also read these[1] quite simple guidelines.
Take into consideration that some of distro binaries are built with an
IPv6 on mind.


poma


[1] https://www.kernel.org/doc/Documentation/networking/ipv6.txt


-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: how to pxe boot using Fedora 19 live CDs

[Jonathan Dieter]

On Thu, 2013-07-11 at 13:09 -0700, Jerome Yanga wrote:
> On Thu, Jul 11, 2013 at 1:04 PM, Jerome Yanga wrote:
> 
> > I have tried many configs and have failed to pxe boot a live Fedora 19 cd.
> >  I need help in the boot parameters.  Here is my current one.
> >
> > LABEL fedora_x86_64_19
> >  MENU LABEL ^1) Fedora 19 x86_64 Live
> >  MENU INDENT 1
> >  KERNEL knl/vmlinuz_fedora_19_x86_64_live_desktop
> >  APPEND initrd=img/initrd_fedora_19_x86_64_live_desktop root=live:
> > http://192.168.0.100/repo/linux/fedora/x86_64/19/LiveOS/squashfs.imgroot=live:http://192.168.0.100/repo/linux/fedora/x86_64/19/LiveOS/squashfs.img
> >
> > I am getting the error below.
> >
> > dracut: FATAL: Don't know how to handle 'root=live:
> > http://192.168.0.100/repo/linux/fedora/x86_64/19/LiveOS/squashfs.img'
> >
> > regards,
> > j
> >
> 
> 
> I forgot to mention that the Live CD ISO is mounted via loop and published
> via the URL.
> 
> regards,
> j

Have you tried using livecd-iso-to-pxeboot, available from livecd-tools
in the repositories?  This tool will extract the disk image and kernel
from the iso and create a proper config file for it.

Jonathan



-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Fwd: Touchpad is not working anymore

[Diego Vargas]

Hello All,

I just wanted to let you know that I fixed my problem. Finally.
It seems Windows unactivated the touchpad with something like the Fn+F5.
So, after 4 days of research, many many people said that using a fedora
live cd and then pressing the Fn+F5 there it will activate it. Even that
solution was posted here.
The thing is that I've tried that but without other live cds (Mint, Ubuntu)
and not exactly live cds (Fedora 19 anaconda and Fedora 18 anaconda) but
the graphical installation section. How ever, I had a fedora 16 live cd, in
which after booted I've tried that key combination: then Problem Solved.

Feels the same happiness as the first time I had internet in home...


Thanks all for your responses and help,
Diego


On Wed, Jul 10, 2013 at 10:59 AM, poma  wrote:

> On 07.07.2013 22:30, Diego Vargas wrote:
> > Hello All!
> >
> > I've been playing with fedora a little bit and I just love it! I've have
> > the gnome GDM and the Cinnamon Desktop.
> …
> > Since the first Update, the touchpad have stopped working.
> > The pointer is not being displayed and, if I connect an usb mouse I
> cannot
> > move it with the touchpad. (obviously, the usb mouse works perfectly).
> >
> > I have this on /var/log/Xorg.0.log
> >
> > [37.148] (II) config/udev: Adding input device SynPS/2 Synaptics
> > TouchPad (/dev/input/event4)
> …
>
> systemctl isolate multi-user.target
> startxfce4
>
>
> poma
>
>
>
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: what has 'yum update' done?

[Joe Zeff]

On 07/12/2013 09:10 AM, Eddie G. O'Connor Jr. wrote:

See?...it's stuff like the stories above that make me hesitant to go
from 18 to 19


Why?  Something went wrong.  Once.  I spent several days, off and on, 
cleaning up cruft and duplicate packages from a CLI, got the GUI working 
and all was well.  Tish happens.  With every gain, there's a risk.  For 
me, going from 17 to 18 had too many risks; jumping right to 19 looks 
much safer.  YMMV and all that, but as long as you have /home on its own 
partition, and that's backed up, there's no reason to be afraid.

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Why should one upgrade Fedora whenever a new version is released?

[Paul Smith]

Dear All,

Why should one upgrade Fedora whenever a new version is released? What
are the main reasons?

Thanks in advance,

Paul
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Why should one upgrade Fedora whenever a new version is released?

[Digimer]

On 12/07/13 15:45, Paul Smith wrote:

Dear All,

Why should one upgrade Fedora whenever a new version is released? What
are the main reasons?

Thanks in advance,

Paul


Access to newer versions of software and the features they add. In 
general, it's personal preference. How "bleeding edge" do you wish to 
be? If you are somewhat more risk averse, then staying on older, still 
supported Fedora versions is just fine, too.


--
Digimer
Papers and Projects: https://alteeve.ca/w/
What if the cure for cancer is trapped in the mind of a person without 
access to education?

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: what has 'yum update' done?

[Eddie G. O'Connor Jr.]

On 07/12/2013 03:33 PM, Joe Zeff wrote:

On 07/12/2013 09:10 AM, Eddie G. O'Connor Jr. wrote:

See?...it's stuff like the stories above that make me hesitant to go
from 18 to 19


Why?  Something went wrong.  Once.  I spent several days, off and on, 
cleaning up cruft and duplicate packages from a CLI, got the GUI 
working and all was well.  Tish happens.  With every gain, there's a 
risk.  For me, going from 17 to 18 had too many risks; jumping right 
to 19 looks much safer.  YMMV and all that, but as long as you have 
/home on its own partition, and that's backed up, there's no reason to 
be afraid.
Well I've just finished backing up not only the /home...but 
/usr.../tmp../etc as well...(as I was able to do a "fresh" install from 
17 to 18.I didn't quite know what to "save"so I took it 
ALL!).And now for.."fedup-cli --network 19"...and I'll keep my 
fingers crossedbut what's the time frame?like an 
hour?2?...2+1/2?I mean could I possibly make it from the 
community where I live to the Piza Hut "in town" for three large 
"Meat-zza's" and back before its done?...LOL!



EGO II
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Why should one upgrade Fedora whenever a new version is released?

[Steven Stern]

On 07/12/2013 02:45 PM, Paul Smith wrote:
> Dear All,
> 
> Why should one upgrade Fedora whenever a new version is released? What
> are the main reasons?
> 

Assuming you're on a version that still gets support, patches, and updates:

1.  If you've chosen Fedora, it's because you like living near the edge.
 Face  it, it's fun. Things break, things get fixed, hurdles are jumped.
It shows you are superior to people who use Windows or OS/X, even if
you're the only one who appreciates that. If you don't like the Fedora
life but like the Red Hat environment, switch to CentOS.  Stable,
strong, boring. :-)

2.  Skipping versions (e.g., using only odd-number versions) complicates
the upgrade processes.  It will *probably* work, but it's less certain
than upgrading with each bump.



-- 
-- Steve
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Why should one upgrade Fedora whenever a new version is released?

[Temlakos]

On 07/12/2013 03:45 PM, Paul Smith wrote:

Dear All,

Why should one upgrade Fedora whenever a new version is released? What
are the main reasons?

Thanks in advance,

Paul


Today we have an upgrade tool that makes the upgrade process almost 
seamless. That is, as long as you upgrade every time. Miss a version, 
and you're in trouble. Miss two or three versions, and any major change 
will force you to do a complete, wipe-your-drive re-installation.


As to why it matters: software is always subject to updates. Some of 
this is required for security reasons. And any version of an operating 
system must come to the end of its life, or else you have no time to 
invent anything new.


Temlakos
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Why should one upgrade Fedora whenever a new version is released?

[Eddie G. O'Connor Jr.]

On 07/12/2013 03:45 PM, Paul Smith wrote:

Dear All,

Why should one upgrade Fedora whenever a new version is released? What
are the main reasons?

Thanks in advance,

Paul
As far as it was explained to me: you're not REALLY required to upgrade, 
if the version you're using suits your purposes. The upside to NOT 
upgrading is you won't have to worry about anything "new" breaking 
something that's "always worked before in the old version of Fedora". 
But the downside is you won't be exposed to cutting edge technology 
either. It's comparable to the sticking your head in the sand vs. 
exploring the island you've just crash landed on!...LOL! At least that's 
how the guy explained it to me when I asked a similar question...



EGO II
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Why should one upgrade Fedora whenever a new version is released?

[Joe Zeff]

On 07/12/2013 12:51 PM, Temlakos wrote:

Today we have an upgrade tool that makes the upgrade process almost
seamless. That is, as long as you upgrade every time. Miss a version,
and you're in trouble. Miss two or three versions, and any major change
will force you to do a complete, wipe-your-drive re-installation.


No.  I've skipped versions when I've seen more trouble with fresh 
installs and upgrades reported than I think reasonable.  The only time I 
ever had a problem with an upgrade it was because the upgrade program 
hung, leaving things in an unstable state.  It's safe to skip one 
version, but more than one can be very, very problematic.

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Computer blocked because of error smpboot CPU2: Not responding

[Paul Smith]

On Fri, Jul 12, 2013 at 8:54 PM, Reindl Harald  wrote:
>> I am experiencing the following problem while booting Fedora 19:
>>
>> smpboot: CPU2: Not responding.
>>
>> The computer seems to be blocked. Is there some way of rebooting it
>> without having to power off the computer?
>
> https://www.kernel.org/doc/Documentation/kernel-parameters.txt
>
> nosmp   [SMP] Tells an SMP kernel to act as a UP kernel,
> and disable the IO APIC.  legacy for "maxcpus=0"
>
>
> however, if one CPU or core doe snot respond
> all the time assume your hardware is dying

Thanks, Reindl. The issue was caused by the fact that I rebooted the
computer without having disconnected the external disk before. Since a
hard power off, the computer has worked just fine. But I was keen to
avoid the hard power off, as someone told me that it is maleficent for
the hard drive. However, it seems that that opinion is not unanimous
according to the discussions I have consulted meanwhile -- many claim
that a hard power off is pretty safe regarding hardware.

Paul
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: F19 nouveau corrupted graphics

[Jon Dufresne]

> lspci -nn | grep VGA

01:00.0 VGA compatible controller [0300]: nVidia Corporation G80 [GeForce
8800 GTX] [10de:0191] (rev a2)

> yum install
>
http://kojipkgs.fedoraproject.org/packages/kernel/3.11.0/0.rc0.git6.1.fc20/x86_64/kernel-3.11.0-0.rc0.git6.1.fc20.x86_64.rpm

Should I be able to test this on FC17 before upgrading to FC19 to test this
works before re-installing the system?

yum install
http://kojipkgs.fedoraproject.org/packages/kernel/3.11.0/0.rc0.git6.1.fc20/x86_64/kernel-3.11.0-0.rc0.git6.1.fc20.x86_64.rpm

Loaded plugins: fastestmirror, langpacks, merge-conf, presto,
refresh-packagekit
kernel-3.11.0-0.rc0.git6.1.fc20.x86_64.rpm
|  31 MB  00:00:19
Examining
/var/tmp/yum-root-Ewg5mq/kernel-3.11.0-0.rc0.git6.1.fc20.x86_64.rpm:
kernel-3.11.0-0.rc0.git6.1.fc20.x86_64
Marking /var/tmp/yum-root-Ewg5mq/kernel-3.11.0-0.rc0.git6.1.fc20.x86_64.rpm
as an update to kernel-3.6.11-1.fc17.x86_64
Marking /var/tmp/yum-root-Ewg5mq/kernel-3.11.0-0.rc0.git6.1.fc20.x86_64.rpm
as an update to kernel-3.6.11-5.fc17.x86_64
Marking /var/tmp/yum-root-Ewg5mq/kernel-3.11.0-0.rc0.git6.1.fc20.x86_64.rpm
as an update to kernel-3.7.3-101.fc17.x86_64
Marking /var/tmp/yum-root-Ewg5mq/kernel-3.11.0-0.rc0.git6.1.fc20.x86_64.rpm
as an update to kernel-3.7.6-102.fc17.x86_64
Marking /var/tmp/yum-root-Ewg5mq/kernel-3.11.0-0.rc0.git6.1.fc20.x86_64.rpm
as an update to kernel-3.7.9-101.fc17.x86_64
Marking /var/tmp/yum-root-Ewg5mq/kernel-3.11.0-0.rc0.git6.1.fc20.x86_64.rpm
as an update to kernel-3.7.9-104.fc17.x86_64
Marking /var/tmp/yum-root-Ewg5mq/kernel-3.11.0-0.rc0.git6.1.fc20.x86_64.rpm
as an update to kernel-3.8.3-103.fc17.x86_64
Marking /var/tmp/yum-root-Ewg5mq/kernel-3.11.0-0.rc0.git6.1.fc20.x86_64.rpm
as an update to kernel-3.8.4-102.fc17.x86_64
Marking /var/tmp/yum-root-Ewg5mq/kernel-3.11.0-0.rc0.git6.1.fc20.x86_64.rpm
as an update to kernel-3.8.8-100.fc17.x86_64
Marking /var/tmp/yum-root-Ewg5mq/kernel-3.11.0-0.rc0.git6.1.fc20.x86_64.rpm
as an update to kernel-3.8.11-100.fc17.x86_64
Marking /var/tmp/yum-root-Ewg5mq/kernel-3.11.0-0.rc0.git6.1.fc20.x86_64.rpm
as an update to kernel-3.8.12-100.fc17.x86_64
Marking /var/tmp/yum-root-Ewg5mq/kernel-3.11.0-0.rc0.git6.1.fc20.x86_64.rpm
as an update to kernel-3.8.13-100.fc17.x86_64
Marking /var/tmp/yum-root-Ewg5mq/kernel-3.11.0-0.rc0.git6.1.fc20.x86_64.rpm
as an update to kernel-3.9.8-100.fc17.x86_64
Resolving Dependencies
--> Running transaction check
---> Package kernel.x86_64 0:3.11.0-0.rc0.git6.1.fc20 will be installed
--> Processing Dependency: systemd >= 203-2 for package:
kernel-3.11.0-0.rc0.git6.1.fc20.x86_64
Loading mirror speeds from cached hostfile
 * fedora: mirror.its.sfu.ca
 * remi: mirrors.mediatemple.net
 * rpmfusion-free: mirror.web-ster.com
 * rpmfusion-free-updates: mirror.web-ster.com
 * updates: mirror.web-ster.com
--> Processing Dependency: dracut >= 027 for package:
kernel-3.11.0-0.rc0.git6.1.fc20.x86_64
--> Processing Dependency: systemd >= 200 for package:
kernel-3.11.0-0.rc0.git6.1.fc20.x86_64
--> Finished Dependency Resolution
Error: Package: kernel-3.11.0-0.rc0.git6.1.fc20.x86_64
(/kernel-3.11.0-0.rc0.git6.1.fc20.x86_64)
   Requires: systemd >= 200
   Installed: systemd-44-24.fc17.x86_64 (@updates)
   systemd = 44-24.fc17
   Available: systemd-44-8.fc17.i686 (fedora)
   systemd = 44-8.fc17
Error: Package: kernel-3.11.0-0.rc0.git6.1.fc20.x86_64
(/kernel-3.11.0-0.rc0.git6.1.fc20.x86_64)
   Requires: dracut >= 027
   Installed: dracut-018-105.git20120927.fc17.noarch (@updates)
   dracut = 018-105.git20120927.fc17
   Available: dracut-018-35.git20120510.fc17.noarch (fedora)
   dracut = 018-35.git20120510.fc17
Error: Package: kernel-3.11.0-0.rc0.git6.1.fc20.x86_64
(/kernel-3.11.0-0.rc0.git6.1.fc20.x86_64)
   Requires: systemd >= 203-2
   Installed: systemd-44-24.fc17.x86_64 (@updates)
   systemd = 44-24.fc17
   Available: systemd-44-8.fc17.i686 (fedora)
   systemd = 44-8.fc17
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Fwd: Touchpad is not working anymore

[poma]

On 12.07.2013 21:27, Diego Vargas wrote:
> Hello All,
> 
> I just wanted to let you know that I fixed my problem. Finally.
> It seems Windows unactivated the touchpad with something like the Fn+F5.
> So, after 4 days of research, many many people said that using a fedora
> live cd and then pressing the Fn+F5 there it will activate it. Even that
> solution was posted here.
> The thing is that I've tried that but without other live cds (Mint, Ubuntu)
> and not exactly live cds (Fedora 19 anaconda and Fedora 18 anaconda) but
> the graphical installation section. How ever, I had a fedora 16 live cd, in
> which after booted I've tried that key combination: then Problem Solved.
> 
> Feels the same happiness as the first time I had internet in home...
> 
> 
> Thanks all for your responses and help,
> Diego


p. 149 - Disabling or enabling the touch pad
http://cdgenp01.csd.toshiba.com/content/support/manuals/userguides/su3495682/GMAD00335011_Sat-SatPro-U900_12Dec14.pdf#page=149
http://support.toshiba.com/support/staticContentDetail?contentId=3495682


poma


-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

TPM for rngd

[Ian Pilcher]

Anyone know how to use rngd with a TPM?  I've checked that the TPM is
turned on in my BIOS, and I'm able to load the tpm module, but rngd
still fails, because /dev/tpm0 doesn't exist.

Any pointers appreciated.  Thanks!

-- 

Ian Pilcher arequip...@gmail.com
Sometimes there's nothing left to do but crash and burn...or die trying.


-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Proposal: Fedora should install with IPv6 disabled by default [was: Re: Disabling ipv6]

[dave]

>
>
> Am 12.07.2013 20:24, schrieb David G.Miller:
>> Fernando Lozano  lozano.eti.br> writes:
 [As I changed the subject, let me clear: IPv6 still compiled in the
>> kernel. Just the network interfaces configs
>> 
>>
>> Perhaps Fedora is the wrong distribution for you.
>>
>> The whole idea behind Fedora is for it to be an "engineering proving
>> ground" where new technologies (like IPv6) are rolled out for real world
>> use.  In the case of IPv6, this includes hopefully providing the tools
>> required for users to be able to securely run a Fedora system with IPv6
>> enabled.  If there is a problem with the tools provided then the answer
>> is
>> to fix the tools and/or provide additional tools; not pull back from a
>> technology that IS coming
>
> why this polemic answer?
>
> it is legit and recommended to disable ipv6 link-local on
> machines inside a network with a ipv4-only gateway because
> it is not needed, makes no sense and you should *never*
> enable network capabilities which are not used
>
> the main problem is not be able to *disable* it if
> you know what you are doing and know why therese
> is no need for ipv6 in your environment
> https://bugzilla.redhat.com/show_bug.cgi?id=982740
>
>
I don't consider my response to be "polemic."  Just pointing out that
Fedora tends to be a "bleeding edge", development distribution.  As an
example, you might review the commentary regarding the new installer that
appeared in FC-18.  The same can be said for any number of new features
such as systemctl instead of System V init scripts and firewalld as well
as many others.

That being said, you and Fernando might wish to explore how to submit a
feature request to make enabling/disabling IPv6 easier and more intuitive.
 Such a feature would be more in keeping with Fedora's goal of being a
technology incubator for what eventually becomes RHEL.  Simply turning off
a new technology that some people find inconvenient but that will move
from optional to required in the foreseeable future is contrary to what
Fedora is all about.

Cheers,
Dave
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Computer blocked because of error smpboot CPU2: Not responding

[Rick Stevens]

On 07/12/2013 01:00 PM, Paul Smith issued this missive:

On Fri, Jul 12, 2013 at 8:54 PM, Reindl Harald  wrote:

I am experiencing the following problem while booting Fedora 19:

smpboot: CPU2: Not responding.

The computer seems to be blocked. Is there some way of rebooting it
without having to power off the computer?


https://www.kernel.org/doc/Documentation/kernel-parameters.txt

nosmp   [SMP] Tells an SMP kernel to act as a UP kernel,
 and disable the IO APIC.  legacy for "maxcpus=0"


however, if one CPU or core doe snot respond
all the time assume your hardware is dying


Thanks, Reindl. The issue was caused by the fact that I rebooted the
computer without having disconnected the external disk before. Since a
hard power off, the computer has worked just fine. But I was keen to
avoid the hard power off, as someone told me that it is maleficent for
the hard drive. However, it seems that that opinion is not unanimous
according to the discussions I have consulted meanwhile -- many claim
that a hard power off is pretty safe regarding hardware.


Power cycling (more specifically thermal cycling) is harder on the
hardware than simply leaving it on. In my 35+ years in electronics,
generally if a piece of equipment is going to die, it's going to do so
during power up or a really big swing in temperatures (such as the loss
of aircon in a data center). I will say this observation is completely
empirical and I can't back it up with hard numbers, but it is my
experience.

The occasional hard, poweroff boot shouldn't be a big deal and you may
never experience a failure because of it. I have, which is one reason
my systems at home never get powered off other than when I perform
maintenance on them. I do turn off monitors and the like, but they're
cheap to replace if they croak compared with my computers and the data
contained thereon (and yes, I back up religiously).
--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 22643734Yahoo: origrps2 -
--
- "Daddy, why doesn't this magnet pick up this floppy disk?" -
--
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: how to pxe boot using Fedora 19 live CDs

[Jerome Yanga]

On Fri, Jul 12, 2013 at 11:58 AM, Jonathan Dieter  wrote:

>
> On Thu, 2013-07-11 at 13:09 -0700, Jerome Yanga wrote:
> > On Thu, Jul 11, 2013 at 1:04 PM, Jerome Yanga  >wrote:
> >
> > > I have tried many configs and have failed to pxe boot a live Fedora 19
> cd.
> > >  I need help in the boot parameters.  Here is my current one.
> > >
> > > LABEL fedora_x86_64_19
> > >  MENU LABEL ^1) Fedora 19 x86_64 Live
> > >  MENU INDENT 1
> > >  KERNEL knl/vmlinuz_fedora_19_x86_64_live_desktop
> > >  APPEND initrd=img/initrd_fedora_19_x86_64_live_desktop root=live:
> > >
> http://192.168.0.100/repo/linux/fedora/x86_64/19/LiveOS/squashfs.imgroot=live:http://192.168.0.100/repo/linux/fedora/x86_64/19/LiveOS/squashfs.img
> > >
> > > I am getting the error below.
> > >
> > > dracut: FATAL: Don't know how to handle 'root=live:
> > > http://192.168.0.100/repo/linux/fedora/x86_64/19/LiveOS/squashfs.img'
> > >
> > > regards,
> > > j
> > >
> >
> >
> > I forgot to mention that the Live CD ISO is mounted via loop and
> published
> > via the URL.
> >
> > regards,
> > j
>
> Have you tried using livecd-iso-to-pxeboot, available from livecd-tools
> in the repositories?  This tool will extract the disk image and kernel
> from the iso and create a proper config file for it.
>
> Jonathan
>
>
>
> --
> users mailing list
> users@lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
>

Jonathan,

Yup.  I have tried that.  I get an out of memory error or the connection
times out.

regards,
j
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Computer blocked because of error smpboot CPU2: Not responding

[Joe Zeff]

On 07/12/2013 01:43 PM, Rick Stevens wrote:

Power cycling (more specifically thermal cycling) is harder on the
hardware than simply leaving it on. In my 35+ years in electronics,
generally if a piece of equipment is going to die, it's going to do so
during power up or a really big swing in temperatures (such as the loss
of aircon in a data center). I will say this observation is completely
empirical and I can't back it up with hard numbers, but it is my
experience.


This is why an incandescent lightbulb is much more likely to fail when 
you turn it on than at any other time.  I've read stories about bulbs 
that have been working for decades because they've never been turned 
off.  I have two reasons for leaving my desktop on 24/7: first, because 
Linux is designed to be run that way[1] and that allows me to use my 
uptime[2] as an example of how stable Linux is and second, I have BOINC 
installed and even when I'm away at a convention, or house sitting, it's 
doing useful work.


[1]i.e., "because I can."
[2]Normally, I only reboot for kernel upgrades.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: F18 to F19: shutdown doesn't work in LXDE

[poma]

On 12.07.2013 10:58, antonio.montagn...@alice.it wrote:
> 
> 
> Fedup worked fine also on a small old laptop.
> 
> We have   a minor issue, when we try to switch off from the menu, machine 
> doesn't shut down and we have to use the power button to poweroff
> 
> But if we issue poweroff or reboot when logged as root in text mode with 
> Ctrl+Alt+F2 poweroff or reboot works fine.
> We had such an issue in F18.
> 
> Any idea??

http://lxde.git.sourceforge.net/git/gitweb.cgi?p=lxde/lxsession;a=commit;h=eadab747cd597ddf64d147289aa98f847f4b7ab5


poma

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: R: F18 to F19: shutdown doesn't work in LXDE

[poma]

On 12.07.2013 11:12, antonio.montagn...@alice.it wrote:
> 
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=981738
> 
> here we are :-)

https://bugzilla.redhat.com/show_bug.cgi?id=800658


poma


-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: how to pxe boot using Fedora 19 live CDs

[Joe Zeff]

On 07/12/2013 01:44 PM, Jerome Yanga wrote:

Yup.  I have tried that.  I get an out of memory error or the connection
times out.


That doesn't sound right.  How much RAM and swap do you have?
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Proposal: Fedora should install with IPv6 disabled by default [was: Re: Disabling ipv6]

[Fernando Lozano]

Hi,
>> Perhaps Fedora is the wrong distribution for you.
>>
>> The whole idea behind Fedora is for it to be an "engineering proving
>> ground" where new technologies (like IPv6) are rolled out for real world
>> use.
Not all Fedora users work in the networking fields. Many are developers
who doesn't care about networking. Even most web, client-server and
mobile developers are not close to being security experts and would
configure a very insecure system if left by thenselves. This does not
exclude them from being superb C, Java, PHP, Python, etc developers.

I don't think it's a good policy to exclude some users because of
others. And I don't thing people are understanding how real and serious
are current IPv6 vulnerabilities.

Biut I ask: would it be so hard for networking people to click once on
anaconda or Network Manager to enable IPv6 if? I think it's harder for
non-networking people to understand they should disable IPv6 else know
how to configure IPv6 in a secure way.


>> the main problem is not be able to *disable* it if
>> you know what you are doing and know why therese
>> is no need for ipv6 in your environment
>> https://bugzilla.redhat.com/show_bug.cgi?id=982740
IMHO those are two distinct issue, although related:

1. Users should be able to disable IPv6. Today they can't and this is a
bug that hopefully will be solved soon. I think no one ever intended
IPv6 to be mandatory. ;-)

2. The secure installation default should be IPv6 disabled. That's my
proposal.


[]s, Fernando Lozano

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: F19 nouveau corrupted graphics

[poma]

On 12.07.2013 22:05, Jon Dufresne wrote:
>> lspci -nn | grep VGA
> 
> 01:00.0 VGA compatible controller [0300]: nVidia Corporation G80 [GeForce
> 8800 GTX] [10de:0191] (rev a2)
> 
>> yum install
>>
> http://kojipkgs.fedoraproject.org/packages/kernel/3.11.0/0.rc0.git6.1.fc20/x86_64/kernel-3.11.0-0.rc0.git6.1.fc20.x86_64.rpm
> 
> Should I be able to test this on FC17 before upgrading to FC19 to test this
> works before re-installing the system?

Isn't it obvious? :)
Keep in mind neither the upgrade doesn't guarantee anything regarding.

…
> --> Finished Dependency Resolution
> Error: Package: kernel-3.11.0-0.rc0.git6.1.fc20.x86_64
> (/kernel-3.11.0-0.rc0.git6.1.fc20.x86_64)
>Requires: systemd >= 200
>Installed: systemd-44-24.fc17.x86_64 (@updates)
>systemd = 44-24.fc17
>Available: systemd-44-8.fc17.i686 (fedora)
>systemd = 44-8.fc17
> Error: Package: kernel-3.11.0-0.rc0.git6.1.fc20.x86_64
> (/kernel-3.11.0-0.rc0.git6.1.fc20.x86_64)
>Requires: dracut >= 027
>Installed: dracut-018-105.git20120927.fc17.noarch (@updates)
>dracut = 018-105.git20120927.fc17
>Available: dracut-018-35.git20120510.fc17.noarch (fedora)
>dracut = 018-35.git20120510.fc17
> Error: Package: kernel-3.11.0-0.rc0.git6.1.fc20.x86_64
> (/kernel-3.11.0-0.rc0.git6.1.fc20.x86_64)
>Requires: systemd >= 203-2
>Installed: systemd-44-24.fc17.x86_64 (@updates)
>systemd = 44-24.fc17
>Available: systemd-44-8.fc17.i686 (fedora)
>systemd = 44-8.fc17
…

F19:
- dracut Version: 029-1.fc19
- systemd 204


poma


-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Disabling ipv6

[Fernando Lozano]

Hi,

>> Have you checked https://bugzilla.redhat.com/show_bug.cgi?id=982740?
> yes i have "NETWORKING_IPV6=no" since virtually forever
> in "/etc/sysconfig/network" as well as "IPV6INIT=false"
> in the interface configurations
>
> this was most time ignored
I wasn't aware this bug was so serious. Please add your findings to the
bug, so Fedora developers can test all scenarios when releasing a fix.


> since this also does not work in recent environments my simple
> question by starting the thread was "which magic is now the best"
> and i was *not* interested in evangelists explaining how
> superiour ipv6 is as answer because it is *off-topic* for networks
> behind gateways which are not ipv6 capable and opens only *security
> problems* in LAN environments
>
> you need not a security hole in the protocl - the simple presence of
> it is one in environments where it is not needed is a security
> problem and violates best practices "disable anything which is
> not actively used" - period
That's the reason I proposed IPv6 disabled by default.

Sorry for mixing it up with your question.


[]s, Fernando Lozano

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

[389-users] Accessing TCP options data in 389ds Hello,

[Justin Kinney]

Hello,

I'm investigating the possibility of logging client IP address where 389ds
is deployed behind a load balancer. Today, we lose the true client IP
address as the source IP is replaced with the load balancer's before the
packet hits the 389 host. Has anybody solved this issue before?

For HTTP based services, this problem is trivial to overcome by grokking
the X-Forwarded-For header from the request, but obviously this doesn't
work with a service like LDAP deployed behind a TCP based load balancing
instance.

One option is to use a direct server return (DSR) configuration with our
load balancer and host, but that adds a lot of overhead to our environment
in terms of configuration complexity, so I'd like to avoid that.

Another option is using an interesting capability of our load balancer (and
I'm not sure how unique this feature is - I'd be interested in hearing if
anyone else has run across it). It can insert the client IP address into
the TCP stream, as arbitrary data in the options field of the TCP header.
Existence of an address is also indicated by a magic number (which can
uniquely identify the VIP on the load balancer).

What would it take to modify 389 to access the raw TCP header, parse the
options field to get the true client IP, and then associate it with the
request? Ideally, the client IP would be accessible in the access log.

Thanks in advance,
Justin
--
389 users mailing list
389-us...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users

Re: [389-users] Accessing TCP options data in 389ds Hello,

[Rich Megginson]

On 07/12/2013 03:25 PM, Justin Kinney wrote:

Hello,

I'm investigating the possibility of logging client IP address where 
389ds is deployed behind a load balancer. Today, we lose the true 
client IP address as the source IP is replaced with the load 
balancer's before the packet hits the 389 host. Has anybody solved 
this issue before?


For HTTP based services, this problem is trivial to overcome by 
grokking the X-Forwarded-For header from the request, but obviously 
this doesn't work with a service like LDAP deployed behind a TCP based 
load balancing instance.


One option is to use a direct server return (DSR) configuration with 
our load balancer and host, but that adds a lot of overhead to our 
environment in terms of configuration complexity, so I'd like to avoid 
that.


Another option is using an interesting capability of our load balancer 
(and I'm not sure how unique this feature is - I'd be interested in 
hearing if anyone else has run across it). It can insert the client IP 
address into the TCP stream, as arbitrary data in the options field of 
the TCP header. Existence of an address is also indicated by a magic 
number (which can uniquely identify the VIP on the load balancer).


What would it take to modify 389 to access the raw TCP header, parse 
the options field to get the true client IP, and then associate it 
with the request? Ideally, the client IP would be accessible in the 
access log.


I don't know - what are the TCP/IP/socket API calls that are required to 
get this data?




Thanks in advance,
Justin


--
389 users mailing list
389-us...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users


--
389 users mailing list
389-us...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users

Re: Proposal: Fedora should install with IPv6 disabled by default [was: Re: Disabling ipv6]

[Joe Zeff]

On 07/12/2013 02:17 PM, Fernando Lozano wrote:

1. Users should be able to disable IPv6. Today they can't and this is a
bug that hopefully will be solved soon. I think no one ever intended
IPv6 to be mandatory. ;-)


Actually, they can, but they have to take the time to configure the 
connection instead of just accepting the defaults.  When you use Network 
Manager, if you edit the connection there's a tab for IPv6 and you can 
set it to Ignore, as I have.  Easy, simple, clear, but as I said, you 
have to look for it.  Should Ignore be the default?  I don't know, honestly.

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Proposal: Fedora should install with IPv6 disabled by default [was: Re: Disabling ipv6]

[Fernando Lozano]

Hi joe,
> On 07/12/2013 02:17 PM, Fernando Lozano wrote:
>> 1. Users should be able to disable IPv6. Today they can't and this is a
>> bug that hopefully will be solved soon. I think no one ever intended
>> IPv6 to be mandatory. ;-)
>
> Actually, they can, but they have to take the time to configure the
> connection instead of just accepting the defaults.  When you use
> Network Manager, if you edit the connection there's a tab for IPv6 and
> you can set it to Ignore, as I have.  Easy, simple, clear, but as I
> said, you have to look for it.  Should Ignore be the default?  I don't
> know, honestly.

If you see the bug cited earlier current Fedora (19) has a bug where
settings to disable IPv6 are ignored. But IMHO that's a different
question, a simple bug that can (will) be fixed.

IMHO "have to look" should not be required by most users. IPv6 today
serves networing people. Fedora is not only for networking people, and I
from my experience most Fedora users are not networking people. Do we
have data about Fedora user demographics?


[]s, Fernando Lozano

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

possibly OT: finding the right plugins for Firefox on F19

[Fred Smith]

Hi all!

I've got F19 on one of my netbooks, and F17 on the other. the F17 netbook
has no trouble playing itunes movie trailers, while the F19 one displays
a black window with the video controls, but won't actually play anything.

I've just spent over an hour comparing the FF plugins on the two machines,
and AFAICS they are identical, except that the F17 machine has citrix
receiver (which I can't see being related, at all) as well as "gnome
shell integration", while I don't believe either is necessary on the
F19 machine--it doesn't have GNOME installed, it's a purely MATE system.
(And the F17 machine, while it has gnome installed, also always is used
as a MATE desktop.)

the only other oddity is that on the F19 machine FF shows two versions
of "shockwave flash", 11.2.r202 and 11.1.r102. if I disable either,
the other becomes disabled too. and I can find only one instance of
libflashplayer.so on the machine.

So, has anyone else either had similar problems, or perhaps actually
made it work? If so, I'd appreciate a hint or two.

thanks!

Fred

-- 
 Fred Smith -- fre...@fcshome.stoneham.ma.us -
   I can do all things through Christ 
  who strengthens me.
-- Philippians 4:13 ---
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: TPM for rngd

[Ian Pilcher]

On 07/12/2013 03:14 PM, Ian Pilcher wrote:
> Anyone know how to use rngd with a TPM?  I've checked that the TPM is
> turned on in my BIOS, and I'm able to load the tpm module, but rngd
> still fails, because /dev/tpm0 doesn't exist.

Had to install kernel-modules-extra to get tpm_tis.ko.

-- 

Ian Pilcher arequip...@gmail.com
Sometimes there's nothing left to do but crash and burn...or die trying.


-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: [389-users] Accessing TCP options data in 389ds Hello,

[Grzegorz Dwornicki]

That is true but load balancer iptables see incoming requests as they are.
I'm not sure that this is what you need. What information you wish to
receive? Besides the real client IP?
12 lip 2013 23:48, "Justin Kinney"  napisał(a):

>
>
>
> On Fri, Jul 12, 2013 at 2:32 PM, Grzegorz Dwornicki wrote:
>
>> Are you doing this on loadbalancer? You can use iptables with log target
>> but if this is not sufficient, then some kind of sniffer like tcpdump might
>> be helpful
>>
>
> The loadbalancer will add the client ip address to the TCP options field
> of the client request prior to passing to the servicing node behind the LB.
>
>
>> 12 lip 2013 23:27, "Rich Megginson"  napisał(a):
>>
>>  On 07/12/2013 03:25 PM, Justin Kinney wrote:
>>>
>>>  Hello,
>>>
>>>  I'm investigating the possibility of logging client IP address where
>>> 389ds is deployed behind a load balancer. Today, we lose the true client IP
>>> address as the source IP is replaced with the load balancer's before the
>>> packet hits the 389 host. Has anybody solved this issue before?
>>>
>>>  For HTTP based services, this problem is trivial to overcome by
>>> grokking the X-Forwarded-For header from the request, but obviously this
>>> doesn't work with a service like LDAP deployed behind a TCP based load
>>> balancing instance.
>>>
>>>  One option is to use a direct server return (DSR) configuration with
>>> our load balancer and host, but that adds a lot of overhead to our
>>> environment in terms of configuration complexity, so I'd like to avoid that.
>>>
>>>  Another option is using an interesting capability of our load balancer
>>> (and I'm not sure how unique this feature is - I'd be interested in hearing
>>> if anyone else has run across it). It can insert the client IP address into
>>> the TCP stream, as arbitrary data in the options field of the TCP header.
>>> Existence of an address is also indicated by a magic number (which can
>>> uniquely identify the VIP on the load balancer).
>>>
>>>  What would it take to modify 389 to access the raw TCP header, parse
>>> the options field to get the true client IP, and then associate it with the
>>> request? Ideally, the client IP would be accessible in the access log.
>>>
>>>
>>> I don't know - what are the TCP/IP/socket API calls that are required to
>>> get this data?
>>>
>>>
>>> Thanks in advance,
>>> Justin
>>>
>>>
>>> --
>>> 389 users mailing 
>>> list389-users@lists.fedoraproject.orghttps://admin.fedoraproject.org/mailman/listinfo/389-users
>>>
>>>
>>>
>>> --
>>> 389 users mailing list
>>> 389-us...@lists.fedoraproject.org
>>> https://admin.fedoraproject.org/mailman/listinfo/389-users
>>>
>>
>> --
>> 389 users mailing list
>> 389-us...@lists.fedoraproject.org
>> https://admin.fedoraproject.org/mailman/listinfo/389-users
>>
>
>
> --
> 389 users mailing list
> 389-us...@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/389-users
>
--
389 users mailing list
389-us...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users

Re: Proposal: Fedora should install with IPv6 disabled by default [was: Re: Disabling ipv6]

[Joe Zeff]

On 07/12/2013 02:38 PM, Fernando Lozano wrote:

IMHO "have to look" should not be required by most users. IPv6 today
serves networing people. Fedora is not only for networking people, and I
from my experience most Fedora users are not networking people. Do we
have data about Fedora user demographics?


I agree.  That's why I made a point out of the fact that you have to 
take the time and effort to find the right place.  Not that it's hard, 
but it either should be disabled by default, or you should be asked when 
the connection's set up, probably with disabled as the default, so that 
inexperienced users won't end up with something the don't need, 
especially as waiting for IPv6 to come up or time out when your ISP 
doesn't provide it just slows your boot down.

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Proposal: Fedora should install with IPv6 disabled by default [was: Re: Disabling ipv6]

[Fernando Lozano]

Hi,
> On 12.07.2013 18:44, Fernando Lozano wrote:
> …
>> So, ifconfig or ip or whatever would have to disable IPv6 for any
>> interface that does not having an explicit IPv6 address. I'd think it
>> would be easier to have the default eth*-cfg files and Network Manager
>> disable IPv6 unless the user tells them to enable.
> Looks like you're reading a lot of documents, so it wouldn't be bad to
> also read these[1] quite simple guidelines.
> Take into consideration that some of distro binaries are built with an
> IPv6 on mind.
>
> [1] https://www.kernel.org/doc/Documentation/networking/ipv6.txt
Your "guidelines" are none at all. Those are docs for a kernel module,
their options. Important docs, but just "command reference", not guidelines.

Unfortunately those module options are currently not being honored (bug
already opened). Changing those defaults (specifically, disabled=1 being
the new default) would be a way to implement what I propose. But I guess
it would not be easy for NetworkManager to change this and reload ipv6
module. Maybe I'm wrong abou that.

About binaries requiring ipv6, that's like expecting a package that
needs a database to create the database as part of its install. Most
ones I tried won't -- they will depend on the database client package,
but will need the user/sysadmin to setup the database before starting
the software included on the package. IPv6 disabled would be just like
that: whoever installs something that requires IPv6 enabled would simply
have to enable it.

Defaults should suit most users. Not a minority that requires IPv6
enabled and how how to manage it.


[]s, Fernando Lozano

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: F19 nouveau corrupted graphics

[Jon Dufresne]

> > Should I be able to test this on FC17 before upgrading to FC19 to test
> this
> > works before re-installing the system?
>
> Isn't it obvious? :)
> Keep in mind neither the upgrade doesn't guarantee anything regarding.
>
>
I see.

In that case how could I verify if an updated kernel fixes the bug or not?
Will I need to build an updated custom kernel from scratch?
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Cannot login into home directory

[Paul Smith]

Dear All,

When I login, I get the following problem:

-- psmith: /home/psmith: change directory failed: Permission denied

I have the following:

drwx--. 191 psmith psmith 12288 Jul 12 23:13 psmith

Any ideas?

Thanks in advance,

Paul
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: F19 nouveau corrupted graphics

[poma]

On 12.07.2013 23:55, Jon Dufresne wrote:
>>> Should I be able to test this on FC17 before upgrading to FC19 to test
>> this
>>> works before re-installing the system?
>>
>> Isn't it obvious? :)
>> Keep in mind neither the upgrade doesn't guarantee anything regarding.
>>
>>
> I see.
> 
> In that case how could I verify if an updated kernel fixes the bug or not?
> Will I need to build an updated custom kernel from scratch?

That's only a kernel part, no matter which method you use to build it.
There's also a Xorg part, so I recommend don't waste your time, but at
least upgrade to F18.


poma


-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Disabling ipv6

[David Beveridge]

On Fri, Jul 12, 2013 at 4:43 AM, Joe Zeff  wrote:
>
> Can you give a practical example, please.  I've no reason to disbelieve you,
> but I've also never run across such a case and would like to see one.
>
This kind of depends on what iptables or firewall rules you have,
but for a moment lets assume that you allow "related" connections on your input.

What this means is to allow anything you connect outbound to to be
trusted to make a reverse connection back to you.

So you are therefore trusting everything you connect to.  Doesn't
sound very "Secure" to me.

dave
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Cannot login into home directory

[Steven Stern]

On 07/12/2013 05:27 PM, Paul Smith wrote:
> Dear All,
> 
> When I login, I get the following problem:
> 
> -- psmith: /home/psmith: change directory failed: Permission denied
> 
> I have the following:
> 
> drwx--. 191 psmith psmith 12288 Jul 12 23:13 psmith
> 
> Any ideas?
> 
> Thanks in advance,
> 
> Paul
> 

I had this happen to me the other day.  As root, I thought I was
somewhere else and mistakenly changed the permissions on /home itself.

Check "ls -ld /home".

It should be 755.

-- 
-- Steve
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Disabling ipv6

[James Hogarth]

> This kind of depends on what iptables or firewall rules you have,
> but for a moment lets assume that you allow "related" connections on your
input.
>
> What this means is to allow anything you connect outbound to to be
> trusted to make a reverse connection back to you.
>
> So you are therefore trusting everything you connect to.  Doesn't
> sound very "Secure" to me.
>

That's not what related means...

Related refers to the returning flow for a given session (sequence numbers
need to match etc) or in the case of ftp with the appropriate ftp conntrack
module then the data channel related to the control channel TCP session
currently open not that the destination can then connect willy nilly back
to the source...
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org