Re: [SLUG] ftp servers with packages

2004-06-16 Thread Jeff Waugh
quote who=Mike MacCana

 ASSHAT

(Good choice.)

- Jeff

-- 
GVADEC 2004: Kristiansand, Norwayhttp://2004.guadec.org/
 
Whatcha wanna be when you grow up?
Eight and a half.
-- 
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html


[SLUG] Kernel exploit for all kernels 2.4.18

2004-06-16 Thread Paul Robinson



Evening Sluggers,

Saw this on overclockers.com.au tonight : http://reviewed.homelinux.org/news/2004-06-11_kernel_crash/

and a lil googling showed :

http://www.gossamer-threads.com/lists/linux/kernel/403593

Certainly looks nasty. Any one heard more on this? 

Cheers,
Paul
-- 
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html


Re: [SLUG] Kernel exploit for all kernels 2.4.18

2004-06-16 Thread Gonzalo Servat
On Thu, 2004-06-17 at 00:16 +1000, Paul Robinson wrote:
 Evening Sluggers,
  
 Saw this on overclockers.com.au tonight :
 http://reviewed.homelinux.org/news/2004-06-11_kernel_crash/
  
 and a lil googling showed :
  
 http://www.gossamer-threads.com/lists/linux/kernel/403593
  
 Certainly looks nasty. Any one heard more on this? 

Here's a URL explaining it a bit further in detail:

  http://linuxreviews.org/news/2004-06-11_kernel_crash/index.html

Pretty nasty indeed. Scary to think a bug this serious didn't get picked
up :)

Regards,
Gonzalo

-- 
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html


Re: [SLUG] Kernel exploit for all kernels 2.4.18

2004-06-16 Thread Paul Robinson
That's actually the same site as the first url (prob just aliased domain
name). :)

Damn nasty indeed. Time to build a testing box to see if our production
servers are affected (looks like some customised kernels handle it ok (not a
blanket 2.4.18 and up problem. just the majority.)

Paul
- Original Message - 
From: Gonzalo Servat [EMAIL PROTECTED]
To: Paul Robinson [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Thursday, June 17, 2004 12:25 AM
Subject: Re: [SLUG] Kernel exploit for all kernels  2.4.18


 On Thu, 2004-06-17 at 00:16 +1000, Paul Robinson wrote:
  Evening Sluggers,
 
  Saw this on overclockers.com.au tonight :
  http://reviewed.homelinux.org/news/2004-06-11_kernel_crash/
 
  and a lil googling showed :
 
  http://www.gossamer-threads.com/lists/linux/kernel/403593
 
  Certainly looks nasty. Any one heard more on this?

 Here's a URL explaining it a bit further in detail:

   http://linuxreviews.org/news/2004-06-11_kernel_crash/index.html

 Pretty nasty indeed. Scary to think a bug this serious didn't get picked
 up :)

 Regards,
 Gonzalo



-- 
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html


Re: [SLUG] souces.list for packages stored locally

2004-06-16 Thread Richard Hayes
On Tue, 15 Jun 2004 08:22 am, Alexander Samad wrote:
 On Tue, Jun 15, 2004 at 02:30:18PM +1000, Roger Barnes wrote:
   On Tue, 15 Jun 2004, Roger Barnes wrote:
I think you need to point at a directory, not a particular

 package apt-move setups up the right structure

  The debian-user thread below may provide some clues:
  http://lists.debian.org/debian-user/2003/11/msg00617.html
 
  Short of running dpkg-scanpackages, you may be stuck with using dpkg -i
  instead of apt-get install



To set up a local debian cache of deb files that you've created or downloaded 
separately:

  # mkdir -p /usr/local/cache/dists/local/local/binary-i386
  # cp *.deb /usr/local/cache/dists/local/local/binary-i386
  # cd /usr/local/cache
  # dpkg-scanpackages dists/local/local/binary-i386 /dev/null \
  $ dists/local/local/binary-i386/Packages

Then add the following line to /etc/apt/sources.list:

  deb file:/usr/local/cache local local

http://www.togaware.com/linux/survivor/Cache_Packages.shtml
-- 
Richard Hayes
Nada Marketing 
2/713 Pacific Hwy Gordon Australia 2072
Phone:+(61-2) 9418 4545 Fax:+(61-2) 9418 4348 Mob:+(61) 0414 618 425
http://www.nada.com.au 
-- 
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html


[SLUG] Microsoft loses Munich

2004-06-16 Thread Stuart Guthrie

Just hitting lists here and there. 

After initial successful Linux pilots -

MS just lost the final battle for Munich. The first 14,000 user Linux
install is up for grabs...



-- 
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html


[SLUG] Printing with Morphix

2004-06-16 Thread heracles
Hi all,
Installed Morphix (a Debian distro) recently on an older machine and can't
find the command to set up the printer. It is on a win2003 server network,
but the printer hangs off one of the machines. In SuSE I'd just use YAST2,
but what is available in Debian?

Stay well and happy
Heracles

PS Not converted (SuSE 9.1 on main machine) but wanted to give Debian another
go.

Stay well  happy
Ashley

-- 
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html


[SLUG] Fedora Core 2 Blues Sound/Mouse

2004-06-16 Thread woodgrove
I tried to upgrade to Fedora Core 2 from Redhat 9, as I 
needed to upgrade to the latest GTK2.

The result was that the sound card would not work, 
there was nothing on the desktop (except those items I 
moved there from the link), X complained about not 
being able to activate the XKB configurator, Mozilla 
disappears in a puff of smoke after the starting has 
finished (no explanation offered), a number of other X 
applications behave similarly, it seems not to support 
firewire, and I have not been able to get the LIRC 
(Linux Remote Control) driver to work with it (though 
not seeing a light at the end of the tunnel in any 
other direction I have not tried too hard.

Much of this does not overly concern me, but I do need 
the sound card and LIRC to work. I tried the Soundcard 
detection under X, which identified the sound card, but 
could not play the test signal on it.

So I rebooted Redhat 9 only to find that the mouse did 
not work (note: the X desktop now advertises Fedora 
Core 2), and there were no longer icons for the Desktop 
items (Home, Trash, Computer). I've managed to add 
appropriate icons for Home and Computer via the 
properties, but this option does not exist for Trash. I 
can live with this, but must have a working mouse.

In summary, can anyone help me to either get sound 
working under Core 2, or the mouse working when I boot 
RedHat 9, having upgraded to Core 2.

Any advice to assist in any of the other problems 
alluded to would also be appreciated.

Thanks,
Greg Wood.
-- 
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html


Re: [SLUG] Fedora Core 2 Blues Sound/Mouse

2004-06-16 Thread James Gregory
On Thu, 2004-06-17 at 13:14 +1000, [EMAIL PROTECTED] wrote:
 I tried to upgrade to Fedora Core 2 from Redhat 9, as I 
 needed to upgrade to the latest GTK2.

Now *that's* a fun upgrade. Can you tell us how you did it? did you just
put the CD in the drive and use the installer, or did you try using yum
or up2date or something?

 [lots of broken stuff]

first of all, take a look in ~/.xsession-errors. There's probably a
bunch of messages about broken libraries. Upgrading those libraries to
their FC2 versions will probably solve the various application level
problems. The XKB thing is GNOME 2.6. There's a dialog that lets you do
XKB stuff, but XKB has been disabled (I think). At any rate, it's a
harmless error in most cases.

 In summary, can anyone help me to either get sound 
 working under Core 2, or the mouse working when I boot 
 RedHat 9, having upgraded to Core 2.

There's a tool called system-config-soundcard - it's the one you should
be using. Is it possible you used the redhat-config-soundcard app?
Anyway, try system-config-soundcard, and see how that goes. Are you
running the 2.6 kernel that ships with FC2, or the kernel from RH9
still?

I don't know anything about LIRC I'm afraid, so I can't offer any help
there. It's probably a case of migrating your /etc/modules.conf file
though.

HTH,

James.
-- 
James Gregory [EMAIL PROTECTED]


signature.asc
Description: This is a digitally signed message part
-- 
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html


Re: [SLUG] GNOME panel segfaulting

2004-06-16 Thread Matthew Davidson
Jeff Waugh wrote:
quote who=Matthew Davidson
'Application gnome-panel (process ) has crashed due to a fatal 
error (segmentation fault)'

It should provide a button to report a bug - that will give you a really
simple UI to get a gdb backtrace and report it. If you want, I can take a
quick look at the backtrace independently of your bug report.
It's been added as Bug 144511.  Not very detailed, I'm afraid.  I had to 
use the web interface, as I don't have sendmail or another MTA installed 
on this system.  Backtrace attached.

If you're not at all fussed about losing configuration temporarily, you
might want to run a recursive unset on all the panel settings, like this:
  gconftool-2 --recursive-unset /apps/panel
Try that, let us know how it goes. :-)
No luck.
Matthew.
--
0419 242 316 ... (02) 6658 1607
--
Please avoid sending me Word or PowerPoint attachments.
See http://www.fsf.org/philosophy/no-word-attachments.html
From: Matthew Davidson [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
X-Mailer: bug-buddy 2.4.2
Subject: gnome-panel crashes on login

Distribution: Debian testing/unstable
Package: gnome-panel
Severity: normal
Version: GNOME2.4.1 2.4.x
Gnome-Distributor: Debian
Synopsis: gnome-panel crashes on login
Bugzilla-Product: gnome-panel
Bugzilla-Component: Panel
Bugzilla-Version: 2.4.x
BugBuddy-GnomeVersion: 2.0 (2.4.0.1)
Description:
Description of the crash:
Gnome-panel segfaults on login.  On closing the panel, it starts up
again and immediately segfaults.  User has no idea what caused it, and
claims not to have changed the panel configuration in any way.

Steps to reproduce the crash:
Only happens for one user, who can't give any account of what was done
to cause it.

Expected Results:


How often does this happen?
Every time gnome-panel starts.

Additional Information:



Debugging Information:

Backtrace was generated from '/usr/bin/gnome-panel'

(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...[New Thread 16384 (LWP 1773)]
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...0x4095abd8 in waitpid () from
/lib/libpthread.so.0
#0  0x4095abd8 in waitpid () from /lib/libpthread.so.0
#1  0x400cba94 in ?? () from /usr/lib/libgnomeui-2.so.0
#2  0x40091884 in libgnomeui_module_info_get () from
/usr/lib/libgnomeui-2.so.0
#3  0x40959815 in __pthread_sighandler () from /lib/libpthread.so.0
#4  signal handler called
#5  0x40aaab5f in strlen () from /lib/libc.so.6
#6  0xb728 in ?? ()

Thread 1 (Thread 16384 (LWP 1773)):
#0  0x4095abd8 in waitpid () from /lib/libpthread.so.0
No symbol table info available.
#1  0x400cba94 in ?? () from /usr/lib/libgnomeui-2.so.0
No symbol table info available.
#2  0x40091884 in libgnomeui_module_info_get () from
/usr/lib/libgnomeui-2.so.0
No symbol table info available.
#3  0x40959815 in __pthread_sighandler () from /lib/libpthread.so.0
No symbol table 

[SLUG] sudoers

2004-06-16 Thread Simon Bryan
Hi all,
Can someone give me the syntax to put in the sudoers file to allow all
users to be able to mount (in particular samba homes if that is relevant).
I don't seem to be able to get the EBNF right!


-- 
Simon Bryan
IT Manager
OLMC Parramatta
-- 
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html


Re: [SLUG] sudoers

2004-06-16 Thread Rick Welykochy
Simon Bryan wrote:
Hi all,
Can someone give me the syntax to put in the sudoers file to allow all
users to be able to mount (in particular samba homes if that is relevant).
I don't seem to be able to get the EBNF right!
An untested stab in the dark:
ALL ALL=(ALL) /path/to/smbmount blah blah blah
Safer: only allow users in the group smb:
%smbALL=(ALL) /path/to/smbmount blah blah blah
DISCALIMER:
   Configuring sudo incorrectly can result in severe attacks
   on your system. Ensure you really do understand the consequences
   of implementing the above configuriation. I take no responsibility
   for the information provided, which originates from a sample sudoers
   file and the 'man sudoers' command.

cheers
rick

--
_
Rick Welykochy || Praxis Services
For years, Microsoft has had a policy of announcing products that don't
exist yet, to cause customers to stop buying a competitor's product.
That's Vapourware.  Is it really any shock that they would want to prevent
customers from using more robust OSs and tools, by offering Vapoursecurity?
 -- David Maxwell on Full Disclosure
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html