Re: Testing test releases: do not update
by Jef Spaleta
Sandy Pond wrote:
> Well here's one bugzilla change that may benefit both. I'd be
> nice to be able to peruse just the recently filed bugs against FC2 >
but I haven't found a way to list bugs submitted later than a
> certain date. This is different than those recently changed.
bugs created against fc test1 from 2004-02-26 till now...so basically
since yesterday
http://tinyurl.com/3x6ur
and similar for fc devel:
http://tinyurl.com/2admj
Created using...
https://bugzilla.redhat.com/bugzilla/query.cgi
specifically the fields at the bottom of the page...
Only bugs where any of the fields: [Bug creation]
were changed between: 2004-02-26 and NOW
The one thing i would change..to make this query easier to do
would be to allow the from date to be relative to NOW, instead of
needing to be YYYY-MM-DD. So i can build a canned query that does
this from saying NOW-7days to get a weeks worth of new bugs.
CannedQueries are useful...
http://www.fedora.us/wiki/CannedQueries
just need people willing to create them so they can be easily found.
Oh yeah...and i need a good play to put them so they are easily found.
Other than finding manhours to create them..and finding a place to put
them...they work pretty well.
-jef
20 years, 1 month
cifs really got me, where is smb?
by Jim Bevier
I have all the lastest updates as of this morning. OS is
2.6.3-1.110smp. I mounted a smb share exported from a FC1
machine using "mount -t cifs -o rw,user=xxx,password=yyyy,
workgroup=WORKGROUP //gateway/src /src". I edited
a file with vi (wierd chars at eol are now fixed) and saved
it. I had used file name "FIle.cpp" so I went to the gateway
machine and renamed the file. "mv FIle.cpp File.cpp". I
went back to the FC2T1 system and did vi file.cpp and it
is the original file unedited??? Went to gateway machine and
the mods are in the file meaning it was written properly, but
I can not get back the modified file. Is this some sort of caching
problem? I saw this yesterday, but I did not know what was
the sequence that caused the failure. I had to unmount the
filesystem and remount it to be able to see the modified file.
Where is my samba support again?
Jim
20 years, 1 month
Really strange problem with the 2.6.x kernels
by Paul F. Johnson
Hi,
Up to last night, I was happily running a version of the 2.6.2 kernel
I'd compiled myself. It worked well.
I attempted to run the 2.6.3-109 kernel. X wouldn't fire up as /dev/
psaux couldn't be found. Damn, says I, and tried to go back to the 2.6.2
kernel. For some reason, the keyboard locked immediately after selecting
the 2.6.2 kernel from grub. X started fine, but with no mouse or
keyboard.
Reset and moved back to the 2.4.24 kernels and all is well again.
Any ideas on what could be causing this?
TTFN
Paul
--
"Logic, my dear Zoe, is merely the ability to be wrong with authority"
Dr Who
20 years, 1 month
Software Suspend
by Giuseppe Cavallo
Hi all,
I installed Fedora Core 2 trest1 in my laptop. I meant to qualify the software
suspend but I see that in the default kernel 2.6.2-1.65 (in the acpi option)
is not qualified in default. Why? And in the final release of Fedora Core 2
will it bequalified in default?
--
[--Saluti Giuseppe Cavallo /*ICQ=94835351*/--]
20 years, 1 month
php problems
by Mike old
Am I right in thinking that php lacks pg support?
this is what I get from php <db access file>
PHP Fatal error: Call to undefined function: pg_connect() in /home/
www/html/contact_list.php on line 4
phpinfo shows (extract)
Configure Command './configure' '--host=i386-redhat-linux' '--
build=i386-redhat-linux' '--target=i386-redhat-linux-gnu' '--program-
prefix=' '--prefix=/usr' '--exec-prefix=/usr' '--bindir=/usr/bin' '--
sbindir=/usr/sbin' '--sysconfdir=/etc' '--datadir=/usr/share' '--
includedir=/usr/include' '--libdir=/usr/lib' '--libexecdir=/usr/libexec'
'--localstatedir=/var' '--sharedstatedir=/usr/com' '--mandir=/usr/share/
man' '--infodir=/usr/share/info' '--cache-file=../config.cache' '--with-
config-file-path=/etc' '--with-config-file-scan-dir=/etc/php.d' '--
enable-force-cgi-redirect' '--disable-debug' '--enable-pic' '--disable-
rpath' '--enable-inline-optimization' '--with-bz2' '--with-db4=/usr' '--
with-curl' '--with-exec-dir=/usr/bin' '--with-freetype-dir=/usr' '--
with-png-dir=/usr' '--with-gd' '--enable-gd-native-ttf' '--with-gdbm'
'--with-gettext' '--with-ncurses' '--with-gmp' '--with-iconv' '--with-
jpeg-dir=/usr' '--with-openssl' '--with-png' '--with-pspell' '--with-
regex=system' '--with-xml' '--with-expat-dir=/usr' '--with-dom=shared,/
usr' '--with-dom-xslt=/usr' '--with-dom-exslt=/usr' '--with-
xmlrpc=shared' '--with-pcre=/usr' '--with-zlib' '--with-layout=GNU' '--
enable-bcmath' '--enable-exif' '--enable-ftp' '--enable-magic-quotes'
'--enable-safe-mode' '--enable-sockets' '--enable-sysvsem' '--enable-
sysvshm' '--enable-track-vars' '--enable-trans-sid' '--enable-yp' '--
enable-wddx' '--with-pear=/usr/share/pear' '--with-kerberos' '--with-
ldap=shared' '--with-mysql=shared,/usr' '--with-pgsql=shared' '--with-
snmp=shared,/usr' '--with-snmp=shared' '--enable-ucd-snmp-hack' '--with-
unixODBC=shared' '--enable-memory-limit' '--enable-bcmath' '--enable-
shmop' '--enable-calendar' '--enable-dbx' '--enable-dio' '--enable-mcal'
'--enable-mbstring' '--enable-mbstr-enc-trans' '--enable-mbregex' '--
with-apxs2=/usr/sbin/apxs'
But no sign of any pgsql.so files (all postgres rpms are installed)
20 years, 1 month
Re: Fedora Core 2 Test 2 - delayed
by Stephen Smalley
On Fri, 2004-02-27 at 13:19, James Harrison wrote:
> Can we have two kernels - one with SELinux and one without.
Boot with selinux=0, and the SELinux code is disabled.
> Anaconda should install it by default, but there should be an option to not
> install SELinux.
>
> Its up to the user how secure he/she wants to make their systems.
>
> I read the wonderful news article about SELinux and how the NSA have inserted
> their "security" code into Linux, but I cant see any technical detail.
>
> Maybe if someone were to explain what they actually did then I might change my
> mind or point me in the right direction.
http://www.nsa.gov/selinux. Technical reports and published papers
available under http://www.nsa.gov/selinux/docs.cfm.
--
Stephen Smalley <sds(a)epoch.ncsc.mil>
National Security Agency
20 years, 1 month
missing "fdomain" module in 2.6.3-1.109 kernel
by G.Wolfe Woodbury
The latest kernel would not install on my machine due to a missing
"fdomain" SCSI module that caused the mkinitrd step (under up2date and
yum) to fail.
Specifications of "tembo":
AMD K6-2 @ 333.MHz
320M RAM
ATI Rage XL (Mach 64)
IDE drives and CD-RW
CMI8331 sound chipset on mobo
Tulip NIC on mobo
3c509 NIC on PCI
AHA-2920A (fdomain) SCSI on ISA (Syquest EZ135)
PS/2 keyboard and mouse (trackball)
--
Gregory G. "Wolfe" Woodbury `-_-' Owner/Admin: wolves.durham.nc.us
ggw at wolves.durham.nc.us U RHCT August 2003
"The Line Eater is a boojum snark." Hug your wolf.
20 years, 1 month
FC2-test1 and ipv6
by Doncho N. Gunchev
Is there any way to completly disable ipv6 support in FC2-test1 and
how? I looked a bit inside the network scripts and tryed to add any option
i've found there but I still get ipv6 addresses with 'ip address list' or
ifconfig. I even did 'service network stop' but ipv6 module indicates being
used by 6 times and I could not rmmod it.
Also is there any sort of ipv6 related documentation shipped with
FC2-test1 or is it planed to be?
--
Regards,
Doncho N. Gunchev Registered Linux User #291323 at counter.li.org
GPG-Key-ID: 1024D/DA454F79
Key fingerprint = 684F 688B C508 C609 0371 5E0F A089 CB15 DA45 4F79
20 years, 1 month
Fedora Core 2 Test 2 - delayed
by Bill Nottingham
We're encountering various issues that are causing us to delay
the release of test2. We'd like to get as much exposure to SELinux
as possible, and this means shipping test2 with SELinux in
enforcing mode. However, there are still some subsystems that
aren't quite ready for this, so we need to slide the release
date some.
The *current* projection is that the freeze will be on March 12,
for availability on March 22. This date is only preliminary at
this point, and may change. The schedule at:
http://fedora.redhat.com/participate/schedule/
will be updated shortly.
Bill
20 years, 1 month
Re: Testing test releases: do not update
by Jef Spaleta
Mike A. Harris wrote:
> as Jef Spaleta puts it "rawhide might kill babies"
EAT BABIES
not KILL
totally different...totally....yeesh
And you slyly glossed over the one valid point in the thread...
shmuel siegel wrote:
>> I think that a lot of the confusion comes form a lack of a
>> public test plan and the lack of guidelines for testers
If i would agree with anything..i would agree...that a lot of
potentially useful testers, enthusiastic users who want to contribute in
some way, are unduly confused about what is really expected of them
during different phases of the testing process.
Or if not confused...just completely unaware, and don't really have a
good idea of where to start. And I'm warning you, trying to build some
sort of communication mechanism(s) to provide better guidance during
testing is own my personal agenda....which means I'm going to poke
developers in the eye and see if I can get a few crusty nuggets of
useful wisdom out of them, in a effort to cobbling together something
aimed at the potential tester, to get them started with less overall
emotional trauma. And just to be mean...i'm not going to give you my
personal timescale to start the attack....but you've been
warned....start watching the skies.
And i could probably argue, that people who have been involved with
previous rhl beta processes, probably are carrying some misguided
expectations about how the testing is going to work for FC as well
(though i think yer post addresses these old hats to a large extent.) I
think everyone really needs to come to the table with an understanding
of where the real development bottlenecks are. In my opinion, the
biggest bottleneck is utilization of developer time...developer time is
the scarce resource. Building a testing process thats most convenient
for the testers but puts an undue burden on the developers isn't a
process based on the realities of the resource economics involved. We
can argue till we are blue in the face about the reality value of having
an extra tree, from the testers point of view, but there is no getting
around the fact that how much really gets done between releases in terms
of building the bits is choked by how many developer manhours there are
to burn on the innumerable priorities. Let's put it this way....no one
can honestly argue that developers are sitting playing games waiting for
actionable bug reports to roll-in. But i also think, in the new world
order of the more open Fedora process, there is a place to make an
effort to recognize the contributions being made from outstanding
testers. I'm not talking about bending the testing process to their
will, but a considerate way to give testers recognition for letting
test1 releases meltdown their boxen..for the good of mankind.
-jef"you will pay for misquoting me..pay..dearly"spaleta
20 years, 1 month
