Alexander: You have really pissed me off. That kind of response was not professional, kind, or even intelligent. Do YOU realize that people subscribe through digest? I wrote that email LONG before I saw your responses. Now who is the ignorant one? Besides, personal flames should not be done through mailing lists. If you want to look stupid, do it through private email. > Date: Fri, 02 Apr 2004 19:43:29 +0200 > From: Alexander Dalloz <alexander.dalloz@xxxxxxxxxxxxxxxx> > Subject: Re: Fedora core 2 torrent for DVD iso doesn't do mediacheck > To: For users of Fedora Core releases <fedora-list@xxxxxxxxxx> > Message-ID: <1080927809.17327.448.camel@xxxxxxxxxxxxxxxxxxxxx> > Content-Type: text/plain; charset="utf-8" > > Am Fr, den 02.04.2004 schrieb Brian Bober um 19:30: > > > I believe that the Fedora 2 core 2 DVDs available through bittorrent should > do > > Are you just ignorant? > > Please go to fedora-test-list@xxxxxxxxxx for test release discussions. > > Alexander > > > -- > Alexander Dalloz | Enger, Germany | GPG key 1024D/ED695653 1999-07-13 > Fedora GNU/Linux Core 1 (Yarrow) on Athlon CPU kernel 2.4.22-1.2174.nptl > Sirendipity 19:42:32 up 14 days, 3:24, load average: 0.05, 0.07, 0.09 > [ Î?νÏ?θι Ï?'αÏ?Ï?ον - gnothi seauton ] > my life is a planetarium - and you are the stars > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: not available > Type: application/pgp-signature > Size: 189 bytes > Desc: Dies ist ein digital signierter Nachrichtenteil > Url : /archives/fedora-list/attachments/20040402/5608e4f4/attachment.bin > > ------------------------------ > > Message: 6 > Date: Fri, 02 Apr 2004 10:02:00 -0800 > From: "Michael A. Peters" <mpeters@xxxxxxx> > Subject: Re: new upgrade FC2x2, up2date? > To: For users of Fedora Core releases <fedora-list@xxxxxxxxxx> > Message-ID: <1080928920.16909.5.camel@xxxxxxxxxxxxxxxxxxxxxx> > Content-Type: text/plain > > On Fri, 2004-04-02 at 06:32, Bob Barnes wrote: > > According to up2date I have 170 updates with 0 ignored. Don't > > mind that at all if it's correct. BUT when I get around to the "fetching > > rpmheader cdrdao-1.1.8-3" in the progress dialog it hangs. > > up2date is having issues. > You should use yum - even that is having some issues, though it has been > more successful for me. > > Some have complained about FC2 stuff on this list and they *may* right - > this is a busy list and the other list isn't quite as busy (close) and > discusses FC2 exclusively. > > However - the "reply to" does use releases in the plural - core releases > ;) > > -- > Cheap Linux CD's - http://mpeters.us/linux/ > > > > > ------------------------------ > > Message: 7 > Date: Fri, 2 Apr 2004 20:38:16 +0200 > From: "Tobias Glasow" <tobias@xxxxxxxxxxxxxxxxx> > Subject: Fedora Core 1 Installation via NFS / no Fedora Core > Installation Tree > To: <fedora-list@xxxxxxxxxx> > Message-ID: <FNEGKCNICCDHNAKCPFEPEEHBEAAA.tobias@xxxxxxxxxxxxxxxxx> > Content-Type: text/plain; charset="iso-8859-1" > > hi list, > > i am trying to install a Fedora Core 1 on a Cobalt Raq3 via NFS. The install > kernel and initrd from the boot.iso is loaded via nfs and the installer is > starting up correctly. > > i can choose my preferred language and the installation method. now, when i > choose nfs and give my server and nfs path (/var/fedora1) it says "That > directory does not seem to contain a Fedora Core installation tree". > > in the logs of the nfs server i just see the authenticated nfs request and > no further errors. in the nfspath (var/fedora1) there is even the unpacked > content of the 3 cds and also the 3 isoimages (permissions are all 777). > > any more ideas what is going wrong? > > thanks, > tobias > > > > > > ------------------------------ > > Message: 8 > Date: Fri, 02 Apr 2004 18:33:24 +0000 > From: "John Walsh" <dear_grommet@xxxxxxxxxxx> > Subject: Re: kmail lost old folders/emails > To: fedora-list@xxxxxxxxxx > Message-ID: <Law10-F40mOuf0fLCBT000291a3@xxxxxxxxxxx> > Content-Type: text/plain; format=flowed > > > Alexander, > > Thanks for the help. > > > > > Then yesterday I got all the latest packages through up2date: > > > >Please use a mirror. The main Redhat server has already enough traffic. > > OK, I've switched to a UK mirror (mirror.ac.uk). > > > >Doing an XFree and KDE update while having X running is not the best > >idea. Better switch to init 3, run up2date-nox -u there and when > >finished switch back to init 5. > > OK - thanks for the tip. > > > >root? You mean you are running X and KDE as root? This would be very > >bad. If you did not mean that please explain what the permissions are. > > Yes, I confess, I do over use the root account, and run Gnome desktop as > root. > > I do know its bad, but I'm happy to do it. > > Should it be a case of NEVER do this ? > > > > > So I closed kmail and re-opened it - now it only has the default folders > >and > > > all the existing ones don't show up. > > > >If you use IMAP you might need to resubscribe the additional folders. > > Not sure what that is. > > I run sendmail, and use Kmail to read the /var/spool/USER mail boxes. > > > > > ps. after the up2date, I don't use the latest kernel because it does not > >see > > > the mouse, so I'm still running the original FC1.0 kernel > >2.4.22-1.2115.nptl > > > >Which mouse do you have? There should be no issue with the mouse and > >latest FC1 kernel .2174 as far as I know. > > Its a Logitech 3 button mouse - quite standard. > > As the system boots, it flashes the LED's, five times. > > It does this at two stages of booting. > > I searched for what the 5xLED flash means, but I can't find anything (any > url's ?). > > I assume it is linked to the mouse, as everything else works/boots fine > (keyboard is OK), > just the mouse does not respond. > > John. > > _________________________________________________________________ > Express yourself with cool new emoticons http://www.msn.co.uk/specials/myemo > > > > > ------------------------------ > > Message: 9 > Date: Fri, 02 Apr 2004 12:53:11 -0600 > From: "Rodolfo J. Paiz" <rpaiz@xxxxxxxxxxxxxx> > Subject: Re: new upgrade FC2x2, up2date? > To: For users of Fedora Core releases <fedora-list@xxxxxxxxxx> > Message-ID: <6.0.3.0.0.20040402124922.02561008@xxxxxxxxxxxxxxxxxxx> > Content-Type: text/plain; charset="us-ascii"; format=flowed > > At 12:02 4/2/2004, you wrote: > >However - the "reply to" does use releases in the plural - core releases > > Note that "FC2 Test 2" is not a core release... it is a *testing* release > in preparation for the actual FC2. The "core" releases are those which do > not bear the "test" designation. Once FC2 is released, then both FC1 and > FC2 topics will be valid on this list. > > A large part of the (good and valid) reason for this is that the bugs and > issues encountered in core releases vs. testing releases are entirely > different, so it makes sense so show those comments and questions to > different groups of people, those who are actually *using* the program and > OS versions with which someone is having problems. It makes the chances of > actually getting help much better. > > If you ask about an up2date problem in FC2 Test 2 on this list, very few > people will be using that program... most (nearly all) of us are on FC1. So > you are not likely to get as much help, and maybe some people will waste > their time (and yours) giving you answers which do not apply to you at all. > > Cheers, > > > -- > Rodolfo J. Paiz > rpaiz@xxxxxxxxxxxxxx > http://www.simpaticus.com > > > > > ------------------------------ > > Message: 10 > Date: Fri, 02 Apr 2004 12:04:23 +0000 > From: BFD <bfd@xxxxxxxxxx> > Subject: Re: new upgrade FC2x2, up2date? > To: For users of Fedora Core releases <fedora-list@xxxxxxxxxx> > Message-ID: <406D56C7.1060306@xxxxxxxxxx> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Rodolfo J. Paiz wrote: > > > Note that "FC2 Test 2" is not a core release... it is a *testing* > > release in preparation for the actual FC2. > > > There is a mailing list specifically for the Fedora test releases at > > http://www.redhat.com/mailman/listinfo/fedora-test-list > > You might want to join it and ask your question there. > > BFD > > > > > ------------------------------ > > Message: 11 > Date: Fri, 02 Apr 2004 14:14:59 -0500 > From: James Kosin <jkosin@xxxxxxxxxxxxxxxxxx> > Subject: Email Client.... > To: fedora-list@xxxxxxxxxx > Message-ID: <406DBBB3.9040101@xxxxxxxxxxxxxxxxxx> > Content-Type: text/plain; charset=us-ascii; format=flowed > > Everyone, > > I found a really cool/free email client for Windows... Before eveyone > jumps on me... I'm using it to read the list and it does not have the > problems with GPG signed messages as OutLook does. > > In fact, it has free Junk mail scanning and everything. > > It is Mozilla Thunderbird 0.5 for Windows. > You can get it here: http://www.mozilla.org/projects/thunderbird/ > > It was able to import all my OutLook mail and everything. Works > wonders... I've now fully retired Microsoft OutLook on my machine. > > Everyone using Windows to check this mail list... Check out this FREE > email client. > > Sorry to Plug MOZILLA so hard.... > James Kosin > > > > > ------------------------------ > > Message: 12 > Date: Fri, 2 Apr 2004 21:06:16 +0100 (BST) > From: Jeroen Van Goey <peak_freak@xxxxxxxxx> > Subject: Re: Determining IP information for eth0 failed > To: fedora-list@xxxxxxxxxx > Message-ID: <20040402200616.21198.qmail@xxxxxxxxxxxxxxxxxxxxxxx> > Content-Type: text/plain; charset=iso-8859-1 > > Nigel Wade wrote: > >It may well be that you can't get DHCP direct from your ISP because of other > hardware in > the way. > and Keven Ring wrote: > >Is the switch/hub [pick one, they are different.... :) ] really a Cable > Modem/DSL ROUTER > > >[that is, on the original box, did it say either Cable Modem Router or DSL > Router, or > >both?]. > Where the fibre-cable enters my house, I've three boxes on the wall. First it > enters a > box, model NIU-2D4TB from Dinh-Telecom (I couldn't find much info about it, > except for > the fact that Dinh-Telecom is a Belgian company). Where there is a label > "-5dB/1dB", a > coax cable exits and goes to a Motorola SB4200E SURFboard Cable Modem > http://broadband.motorola.com/catalog/productdetail.asp?ProductID=180). From > there a > cable goes to a "5 Port Mini-Hub" (no model or vendor visible on the box). > From there, 2 > cables exit, one to PC1, the other to PC2. > > >Is [the Windows] PC1 getting an IP address from your ISP? > Using the command "winipcfg" I get this information: > adaptoradress: 00-03-E1-40-35-90 > IP-address: 81.83.45.35 > subnetmask: 255.255.254.0 > Standard Gateway: 81.83.44.1 > > >How many leases have you purchased from your ISP? > Have no clue... I subscribe to a service that allows me to have 2 PCs > connected to the > internet, each one with their own IP-address. For those who understand dutch, > the product > info page is: > http://www.telenet.be/producten/internet/telenet_internet/duo/index.php > ,and the installation layout is at > http://www.telenet.be/producten/internet/installatie/installatie_duo_quattro/index.php > It > mentions that you only need a hub and no router, but no word about leases. > > >Did you purchase the cable modem? > My ISP installed it, so I guess I lease it from them. > > So it seems that what you said (that my hub won't do Network Address > Translation [NAT] > and/or that my cable modem only allows for exactly 1 network card MAC address > and > completely IGNORES other requests) is happening. > > IF this is the case, I will likely go for option 2 you suggested (purchasing > a 2nd > Network Interface Card [NIC] (~$10-20 US) for PC2, connect the cable modem to > the machine > that has 2 network cards , connect the other card to the hub, set up NAT, > install a > Firewall, and possibly reset my cable modem.) > > Before I do this, are there any other checks that I can perform to know for > certain that > this is the case. And can somebody tell me in detail what this lease thing > is. If we're > positive, I will install the second NIC and tell how it goes, > > Thanks for the good support until now, and looking forward to the feedback, > Jeroen > > PS: St0rM wrote: > >However one line that is missing from his file that is in mine by default is > " > > ONBOOT='yes' " This tells the system to activate the interface at boot > time. > Sorry, my fault. It is in there, but I somehow didn't copy it. > > > > > > ___________________________________________________________ > WIN FREE WORLDWIDE FLIGHTS - nominate a cafe in the Yahoo! Mail Internet Cafe > Awards www.yahoo.co.uk/internetcafes > > > > > ------------------------------ > > Message: 13 > Date: Sat, 3 Apr 2004 06:07:17 +1000 > From: Norman Gaywood <norm@xxxxxxxxxxxxxxxxx> > Subject: Re: Latest FC kernel still have SMP bugs? > To: For users of Fedora Core releases <fedora-list@xxxxxxxxxx> > Message-ID: <20040402200716.GA5344@xxxxxxxxxxxxxxxxx> > Content-Type: text/plain; charset=us-ascii > > On Fri, Apr 02, 2004 at 10:57:11AM +0100, WipeOut wrote: > > I personally don't think it has anything to do with NFS mounts, I don't > > have any but the still have the lockup's on my HT desktop.. No problem > > with a vanilla SMP kernel.. > > Actually, the trigger for the bug is a umount not a mount. It also seems > to be be any type of umount. The test script mentioned earlier in the > thread does a loop-back mount/umount. > > There may be other ways to trigger it other than umount. > > -- > Norman Gaywood, Systems Administrator > School of Mathematics, Statistics and Computer Science > University of New England, Armidale, NSW 2351, Australia > > norm@xxxxxxxxxxxxxxxxx Phone: +61 (0)2 6773 2412 > http://turing.une.edu.au/~norm Fax: +61 (0)2 6773 3312 > > Please avoid sending me Word or PowerPoint attachments. > See http://www.fsf.org/philosophy/no-word-attachments.html > > > > > ------------------------------ > > Message: 14 > Date: Sat, 3 Apr 2004 06:11:30 +1000 > From: Norman Gaywood <norm@xxxxxxxxxxxxxxxxx> > Subject: Re: Latest FC kernel still have SMP bugs? > To: For users of Fedora Core releases <fedora-list@xxxxxxxxxx> > Message-ID: <20040402201130.GB5344@xxxxxxxxxxxxxxxxx> > Content-Type: text/plain; charset=us-ascii > > On Fri, Apr 02, 2004 at 11:31:06AM +0100, Nigel Wade wrote: > > I guess I'm back to square one. The system won't operate in SMP with the FC > > > kernel and won't operate at all without a FC kernel. So it looks like > > Fedora is snafu'd. > > > > Unfortunately, RH9/RHEL3 don't have the version of LDAP I require, and when > > > I tried an upgrade to openldap I started getting FUTEX locking problems. > > Install the RHEL3 kernel on FC1. I installed: > > kernel-smp-2.4.21-9.0.1.EL > kernel-smp-unsupported-2.4.21-9.0.1.EL > > from mirror.physics.ncsu.edu:/pub/whitebox/3.0/en/updates/i686 > > This has been working well for me. You need to use the rpm switches: > > rpm --oldpackage -i kernel* > > -- > Norman Gaywood, Systems Administrator > School of Mathematics, Statistics and Computer Science > University of New England, Armidale, NSW 2351, Australia > > norm@xxxxxxxxxxxxxxxxx Phone: +61 (0)2 6773 2412 > http://turing.une.edu.au/~norm Fax: +61 (0)2 6773 3312 > > Please avoid sending me Word or PowerPoint attachments. > See http://www.fsf.org/philosophy/no-word-attachments.html > > > > > ------------------------------ > > Message: 15 > Date: Fri, 2 Apr 2004 23:03:03 +0200 > From: "Rolf Berkenbosch" <rolf@xxxxxxxxxxxxxx> > Subject: Again problems with shell users > To: <fedora-list@xxxxxxxxxx> > Message-ID: <00fe01c418f5$e395dc80$1a00a8c0@rolf> > Content-Type: text/plain; charset="us-ascii" > > Here is my output. > I had have this problem earlier but somehow the reinstall of ssh won't > work this time. > Now I have realy a big problem? Is this a bug in Fedora??? > > ssh -v -v -l testtest 213.196.8.10 > OpenSSH_3.6.1p2, SSH protocols 1.5/2.0, OpenSSL 0x0090701f > debug1: Reading configuration data /etc/ssh/ssh_config > debug1: Applying options for * > debug1: Rhosts Authentication disabled, originating port will not be > trusted. > debug2: ssh_connect: needpriv 0 > debug1: Connecting to 213.196.8.10 [213.196.8.10] port 22. > debug1: Connection established. > debug1: identity file /root/.ssh/identity type -1 > debug1: identity file /root/.ssh/id_rsa type -1 > debug1: identity file /root/.ssh/id_dsa type -1 > debug1: Remote protocol version 1.99, remote software version > OpenSSH_3.6.1p2 > debug1: match: OpenSSH_3.6.1p2 pat OpenSSH* > debug1: Enabling compatibility mode for protocol 2.0 > debug1: Local version string SSH-2.0-OpenSSH_3.6.1p2 > debug1: SSH2_MSG_KEXINIT sent > debug1: SSH2_MSG_KEXINIT received > debug2: kex_parse_kexinit: > diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1 > debug2: kex_parse_kexinit: ssh-rsa,ssh-dss > debug2: kex_parse_kexinit: > aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-c > bc,rijndael-cbc@xxxxxxxxxxxxxx > debug2: kex_parse_kexinit: > aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-c > bc,rijndael-cbc@xxxxxxxxxxxxxx > debug2: kex_parse_kexinit: > hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@xxxxxxxxxxx,hmac-sha1-9 > 6,hmac-md5-96 > debug2: kex_parse_kexinit: > hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@xxxxxxxxxxx,hmac-sha1-9 > 6,hmac-md5-96 > debug2: kex_parse_kexinit: none,zlib > debug2: kex_parse_kexinit: none,zlib > debug2: kex_parse_kexinit: > debug2: kex_parse_kexinit: > debug2: kex_parse_kexinit: first_kex_follows 0 > debug2: kex_parse_kexinit: reserved 0 > debug2: kex_parse_kexinit: > diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1 > debug2: kex_parse_kexinit: ssh-rsa,ssh-dss > debug2: kex_parse_kexinit: > aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-c > bc,rijndael-cbc@xxxxxxxxxxxxxx > debug2: kex_parse_kexinit: > aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-c > bc,rijndael-cbc@xxxxxxxxxxxxxx > debug2: kex_parse_kexinit: > hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@xxxxxxxxxxx,hmac-sha1-9 > 6,hmac-md5-96 > debug2: kex_parse_kexinit: > hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@xxxxxxxxxxx,hmac-sha1-9 > 6,hmac-md5-96 > debug2: kex_parse_kexinit: none,zlib > debug2: kex_parse_kexinit: none,zlib > debug2: kex_parse_kexinit: > debug2: kex_parse_kexinit: > debug2: kex_parse_kexinit: first_kex_follows 0 > debug2: kex_parse_kexinit: reserved 0 > debug2: mac_init: found hmac-md5 > debug1: kex: server->client aes128-cbc hmac-md5 none > debug2: mac_init: found hmac-md5 > debug1: kex: client->server aes128-cbc hmac-md5 none > debug1: SSH2_MSG_KEX_DH_GEX_REQUEST sent > debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP > debug2: dh_gen_key: priv key bits set: 126/256 > debug2: bits set: 1568/3191 > debug1: SSH2_MSG_KEX_DH_GEX_INIT sent > debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY > debug2: no key of type 0 for host 213.196.8.10 > debug2: no key of type 2 for host 213.196.8.10 > The authenticity of host '213.196.8.10 (213.196.8.10)' can't be > established. > RSA key fingerprint is 71:88:ac:c8:ee:f0:d6:af:a0:3b:dc:2a:be:ab:5b:b9. > Are you sure you want to continue connecting (yes/no)? yes > Warning: Permanently added '213.196.8.10' (RSA) to the list of known > hosts. > debug2: bits set: 1568/3191 > debug1: ssh_rsa_verify: signature correct > debug2: kex_derive_keys > debug2: set_newkeys: mode 1 > debug1: SSH2_MSG_NEWKEYS sent > debug1: expecting SSH2_MSG_NEWKEYS > debug2: set_newkeys: mode 0 > debug1: SSH2_MSG_NEWKEYS received > debug1: SSH2_MSG_SERVICE_REQUEST sent > debug2: service_accept: ssh-userauth > debug1: SSH2_MSG_SERVICE_ACCEPT received > debug1: Authentications that can continue: > publickey,password,keyboard-interactive > debug1: Next authentication method: publickey > debug1: Trying private key: /root/.ssh/identity > debug1: Trying private key: /root/.ssh/id_rsa > debug1: Trying private key: /root/.ssh/id_dsa > debug2: we did not send a packet, disable method > debug1: Next authentication method: keyboard-interactive > debug2: userauth_kbdint > debug2: we sent a keyboard-interactive packet, wait for reply > debug1: Authentications that can continue: > publickey,password,keyboard-interactive > debug2: we did not send a packet, disable method > debug1: Next authentication method: password > testtest@xxxxxxxxxxxx's password: > debug2: we sent a password packet, wait for reply > debug1: Authentication succeeded (password). > debug1: channel 0: new [client-session] > debug2: channel 0: send open > debug1: Entering interactive session. > debug2: callback start > debug2: ssh_session2_setup: id 0 > debug1: channel 0: request pty-req > debug1: channel 0: request shell > debug2: callback done > debug1: channel 0: open confirm rwindow 0 rmax 32768 > debug1: channel_free: channel 0: client-session, nchannels 1 > Connection to 213.196.8.10 closed by remote host. > Connection to 213.196.8.10 closed. > debug1: Transferred: stdin 0, stdout 0, stderr 87 bytes in 0.0 seconds > debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 10187.3 > debug1: Exit status -1 > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: /archives/fedora-list/attachments/20040402/3c384a5c/attachment.htm > > ------------------------------ > > -- > fedora-list mailing list > fedora-list@xxxxxxxxxx > http://www.redhat.com/mailman/listinfo/fedora-list > > > End of fedora-list Digest, Vol 2, Issue 17 > ******************************************
