[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

UNSUBSCRIBE




debian-user-digest-request@lists.debian.org wrote:

> To UNSUBSCRIBE, send email to debian-user-digest-request@lists.debian.org with
> a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
> debian-user-digest Digest                               Volume 2003 : Issue 775
>
> Today's Topics:
>   Re: ssh and X---where do I switch th  [ "David Gaudine" <david@annette.conc ]
>   RE: Network config help needed        [ "deFreese, Barry" <Barry.deFreese@n ]
>   Re: lost X... non valid arg: tcp ...  [ bboett@bboett.dyndns.org (Bruno Boe ]
>   RE: Working with WAV files            [ "David Turetsky" <davidturetsky@ear ]
>   Re: Patched sendmail? testing?        [ Joey Hess <joeyh@debian.org> ]
>   Re: Network config help needed        [ Patrick Wiseman <pwiseman@mindsprin ]
>   Re: The Very Verbose Guide to Updati  [ Vineet Kumar <debian-user@virtual.d ]
>   Re: X doesn't seem to load app-defau  [ Wim De Smet <fragmeat@yucom.be> ]
>   Re: X doesn't seem to load app-defau  [ Wim De Smet <fragmeat@yucom.be> ]
>   Mozilla and TrueType                  [ Ismael Valladolid Torres <ismaeval@ ]
>   Re: Dumb question: How do you reboot  [ Wim De Smet <fragmeat@yucom.be> ]
>   formail help                          [ Attila Csosz <csosz77@axelero.hu> ]
>   Re: The Very Verbose Guide to Updati  [ Travis Crump <pretzalz@techhouse.or ]
>   Re: Patched sendmail? testing?        [ Colin Watson <cjwatson@debian.org> ]
>   Re: Help with wireless                [ Sebastian Henschel <shensche@kodeaf ]
>   Re: OT: EchoLink equivalent for Linu  [ Kent West <westk@acu.edu> ]
>   kernel-source-2.4.18-bf2.4?           [ Kris Kerwin <snoopy248th@ameritech. ]
>   Re: Setting Default Framebuffer Mode  [ Ian Melnick <dazed@vonsteuben.cps.k ]
>
>   ------------------------------------------------------------------------
>
> Subject: Re: ssh and X---where do I switch the remote to X-listen
> Date: Wed, 5 Mar 2003 16:13:45 -0500
> From: "David Gaudine" <david@annette.concordia.ca>
> To: <debian-user@lists.debian.org>
> References: <35kc6vsfmrcjhj4v5t2j7g4voc23mip16g@4ax.com>
>
> Here is a link to a pdf file that contains everything I know about
> running remote X clients with and without ssh, and with and without xdm.
> Since it contains everything I know, it's a very short download.
> http://annette.concordia.ca/~david/X.pdf
>
>   ------------------------------------------------------------------------
>
> Subject: RE: Network config help needed
> Date: Wed, 5 Mar 2003 13:31:50 -0800
> From: "deFreese, Barry" <Barry.deFreese@nike.com>
> To: "'chris1622@telia.com'" <chris1622@telia.com>,
>      debian-user@lists.debian.org
>
> Barry deFreese
> NTS Technology Services Manager
> Nike Team Sports
> > -----Original Message-----
> > From: chris1622@telia.com [mailto:chris1622@telia.com]
> > Sent: Wednesday, March 05, 2003 1:16 PM
> > To: debian-user@lists.debian.org
> > Subject: Re: Network config help needed
> >
> >
> >
> > Yep, read Net-HOWTO, but still I can't get it to work. ...
> >
> > Setting up the loopback and pingin it works fine, pinging into the
> > machine also works fine (tried from an old win95 machine). But
> > pinging out of the machine dosn't work, I'm getting the error message
> > "Unable to connect to remote host: No route to host" when telnetting.
> >
> > Is "ifconfig eth0 192.168.0.1 netmask 255.255.255.0 up" enough to
> > set up the network, I don't have to edit /etc/hosts or something
> > else?
> >
>
> Chris,
>
> Your /etc/network/interfaces should look like so:
>
> iface eth0 inet static
>         address         192.168.0.1
>         netmask         255.255.255.0
>         network         192.168.0.0
>         broadcast       192.168.0.255
>         gateway 192.168.0.?? --> Whatever your default router/gateway
> address is.
>
> Actually the gateway shouldn't matter since the other host is on the same
> subnet.  Again, you need to verify that the subnet mask for both hosts are
> the same.
>
> Barry deFreese
> NTS Technology Services Manager
> Nike Team Sports
> (949)-616-4005
> Barry.deFreese@nike.com
>
> "Technology doesn't make you less stupid; it just makes you stupid faster."
> Jerry Gregoire - Former CIO at Dell
>
>   ------------------------------------------------------------------------
>
> Subject: Re: lost X... non valid arg: tcp ....
> Date: Wed, 5 Mar 2003 22:38:17 +0100
> From: bboett@bboett.dyndns.org (Bruno Boettcher)
> Reply-To: bboett@adlp.org
> To: debian-user@lists.debian.org
> References: <20030305162905.GK27209@adlp.org> <20030305170726.GA19262@jeeves.mine.nu>
>
> On Wed, Mar 05, 2003 at 06:07:26PM +0100, Mark Schouten wrote:
> > Perhaps you could be more specific?
> uhm indeed.... the image shown me on the start of xdm is a pixelized
> chaos, i thus disabled xdm....
> in fact a strange mix of old images somehow still stored in the grafic
> card buffer....
>
> started with startx....
>
> >       * Does your displaymanager start?
> starts, reports no errors, but i only get an empy frame on the display
> where normally the chooser would be...
> typing blindly the login doesn't yield any result...
>
> >       * Does your windowmanager start?
> i can't start another one.. so somehow sawfish seems started....
>
> > What do /var/log/XFree86.0.log ~/.xsession-errors say?
> general one ends with:
> (EE) Generic Mouse: cannot open input device
> (EE) PreInit failed for input device "Generic Mouse"
> (II) UnloadModule: "mouse"
> (II) XINPUT: Adding extended input device "Configured Mouse" (type:
>                                                               MOUSE)
> Could not init font path element unix/:7100, removing from list!
>
> which seems quite normal....
>
> xsession-errors gives:
> SESSION_MANAGER=local/laptop:/tmp/.ICE-unix/1357
> Gnome-Message: gnome_execute_async_with_env_fds: returning -1
> Gnome-Message: gnome_execute_async_with_env_fds: returning -1
> Gnome-Message: gnome_execute_async_with_env_fds: returning -1
>
> no idea what that means....
>
> i started X with : startx 2>&1 |tee log
> and that gives a lot more stuff, but still:
> ** (gnome-panel:8513): WARNING **: Unable to load panel stock icon 'go'
>
> No panel_id set for panel object with ID 00000001
> Unable to open desktop file
> file:///home/bboett/.gnome2/panel2.d/default/launcher
> s/hammer-0051ace0aa.desktop for panel launcher: Error reading file
> 'file:///home/
> bboett/.gnome2/panel2.d/default/launchers/hammer-0051ace0aa.desktop':
> File not found
>
> last 2 things repeated several times....
>
> i tryed exporting the display from a console and start there an xterm to
> see what's happening....
>
> the strange thing is, the xterm launches, gives no error messages
> anyway, and on the display appears a rectangle with some old grafic
> buffer displayed inside, no windowmanager borders, no shell inside....
>
> its really strange...
>
> --
> ciao bboett
> ==============================================================
> bboett@adlp.org
> http://inforezo.u-strasbg.fr/~bboett
> ===============================================================
>
>   ------------------------------------------------------------------------
>
> Subject: RE: Working with WAV files
> Date: Wed, 5 Mar 2003 16:41:53 -0500
> From: "David Turetsky" <davidturetsky@earthlink.net>
> To: "'Debian Users'" <debian-user@lists.debian.org>
>
> >>> On Tue, Mar 04, 2003 at 04:07:07PM -0500, David Turetsky wrote:
>
>    What packages are out there which facilitate editing?
>
> >>> sean finney [mailto:seanius@seanius.net]
> >>> Sent: Wednesday, March 05, 2003 11:14 AM
>
>    a good one that you can run from the command line is sox.  it has a
> bunch
>    of basic effects and filters you can pass the sound through, i've
> used
>    it in the past and been happy with it
>
>
> >>> David Turetsky:
>
>    I checked it out and was impressed. Not seeing how to listen to the
>    WAV file, I tried 'play' which makes use of sox and discovered that
>    my sound card uses a chip set provided by a bankrupted manufacturer,
>    Aureal
>
>    I check 'modconf' and before attempting to install any driver,
>    visited http://aureal.sourceforge.net/ and
>    http://www.vortexofsound.com/techhelp/th-v2a43.htm and
>    related sites. Windows identifies my sound card as 'Aureal Vortex
>    8830 Audio (WDM)'. 'lspci' gives Multimedia audio controller: Aureal
>    Semiconductor Vortex 2 (rev fe)
>
>    When I purchased the card with my Dell system, it was described as
>    Montego Bay (which shows up on 'modconf's list)
>
>    Before I go off experimenting with modconf, I wonder if anyone has
>    been over this ground. If I add a driver using modconf and get no
>    result, how do I remove it?
>
>
>    --
>    David
>
>   ------------------------------------------------------------------------
>
> Subject: Re: Patched sendmail? testing?
> Date: Wed, 5 Mar 2003 17:05:05 -0500
> From: Joey Hess <joeyh@debian.org>
> To: Debian User List <debian-user@lists.debian.org>
> References: <20030304133702.GA7861@teddy.fas.com> <20030304141502.GB1543@moonkingdom.net> <20030304163234.GA12357@teddy.fas.com> <20030304170210.GA5930@riva.ucam.org> <20030304190448.GA16100@teddy.fas.com> <20030304193005.GA7219@riva.ucam.org> <20030304211102.GC19652@teddy.fas.com> <20030304215318.GB5959@riva.ucam.org> <20030304230821.GA6862@riva.ucam.org>
>
> Colin Watson wrote:
> > the new safe signals implementation has caused some problems which mean
> > that the next upstream release will allow them to be turned off.
>
> Argh.
> Do you know if that is a compile-time switch or a run-time switch? I've
> had some very fun debugging sessions based on perl's signal handling
> changes and the only thing worse than having to deal with the current
> safe signals would be making my programs have to deal with both sorts.
>
> --
> see shy jo
>
>   ------------------------------------------------------------------------
>    Part 1.6.1.2Type: application/pgp-signature
>
>   ------------------------------------------------------------------------
>
> Subject: Re: Network config help needed
> Date: Wed, 5 Mar 2003 17:02:05 -0500 (EST)
> From: Patrick Wiseman <pwiseman@mindspring.com>
> To: debian-user@lists.debian.org
>
> On Wed, 5 Mar 2003 at 9:00pm, chris1622@telia.com wrote:
>
> :Setting up the loopback and pingin it works fine, pinging into the
> :machine also works fine (tried from an old win95 machine). But
> :pinging out of the machine dosn't work, I'm getting the error message
> :"Unable to connect to remote host: No route to host" when telnetting.
>
> Does "route -n" show a gateway?  It should show something like:
>
> Kernel IP routing table
> Destination  Gateway      Genmask      Flags Metric Ref    Use Iface
> 192.168.1.0  0.0.0.0      255.255.255.0   U     0    0      0  eth1
> 0.0.0.0      192.168.1.1  0.0.0.0         UG    0    0      0  eth1
>
> If it shows something like
>
> Destination  Gateway      Genmask      Flags Metric Ref    Use Iface
> 192.168.1.0     *         255.255.255.0   U     0    0      0  eth1
>
> then you don't have a default gateway set up.  Do "route add default gw
> 192.168.1.1" substituting the correct IP address for your gateway of
> course.  Edit /etc/interfaces (as directed at "man interfaces") to have it
> work on boot.
>
> Patrick
>
> --
> Patrick Wiseman                               pwiseman@mindspring.com
> Linux user #17943                             *Google First, Ask Later*
>
>   ------------------------------------------------------------------------
>
> Subject: Re: The Very Verbose Guide to Updating and Compiling Your Debian Kernel
> Date: Wed, 5 Mar 2003 14:13:24 -0800
> From: Vineet Kumar <debian-user@virtual.doorstop.net>
> To: Debian User List <debian-user@lists.debian.org>
> References: <3E648B25.9070304@ihug.co.nz> <20030305195635.GA26597@brillig>
>
> * Daniel Farnsworth Teichert <danielt@ee.byu.edu> [20030305 12:23 PST]:
> > (Note that the above requires that root has access to your X
> > display, because it uses 'xconfig'. Now, this is probably going
> > to show you how clue-less I am, but one simple way I do this on
> > occasion is by 'ssh -X root@localhost' to become root for the
> > above; go ahead, tell me it's silly--I know : ).
>
> Actually, you get a big round of applause.  ssh -X root@localhost is a
> fine way to go.  When you started to say clueless I was preparing myself
> for another "why nobody should ever use xhost, ever" rant coming on, but
> you've done things the^H^H^H^H a good way =)
>
> > Anyway, like I have already implied, I'm no expert here--but I
> > thought this was more along the Debian lines.
>
> I haven't taken a look at the referenced document yet, so I can't say
> how it compares, but your procedure looks good, at least by my cursory
> glance.  (Although, I generally use menuconfig, which makes the whole X
> discussion moot.  That's just a matter of personal preference, though.)
>
> good times,
> Vineet
> --
> http://www.doorstop.net/
> --
> http://www.digitalconsumer.org/
>
>   ------------------------------------------------------------------------
>                        Name: signature.asc
>    signature.asc       Type: application/pgp-signature
>                 Description: Digital signature
>
>   ------------------------------------------------------------------------
>
> Subject: Re: X doesn't seem to load app-defaults using gdm
> Date: Wed, 5 Mar 2003 23:12:11 +0100
> From: Wim De Smet <fragmeat@yucom.be>
> To: debian-user@lists.debian.org
> References: <20030304224511.49427e6a.fragmeat@yucom.be>
>      <20030305031741.GC1543@moonkingdom.net>
>
> On Tue, 4 Mar 2003 19:17:41 -0800
> Marc Wilson <msw@cox.net> wrote:
> > On Tue, Mar 04, 2003 at 10:45:11PM +0100, Wim De Smet wrote:
> > > /etc/X11/app-defaults/Rxvt contains the following two lines:
> > > background:black
> > > foreground:white
> > > Yet rxvt is allways loaded with background white and foreground
> > > black.
> >
> > If that's all the line actually says, of course rxvt isn't going to
> > pay the slightest attention.  You haven't created a resource that it
> > SHOULD pay attention to.
>
> I haven't created any resource. This is a standard app-default that gets
> installed with the package. Maybe a bug?
>
> >
> > X resources are hierarchial.  The name of the file they're defined in
> > is entirely irrelevant.
> >
> > So, try this:
> >
> > rxvt*background:        black
> > rxvt*foreground:        white
> >
> > I don't know for sure what class name rxvt actually uses, but a
> > preusal of the documentation will tell you.
> >
> > --
>
> I'll try it. But this still doesn't solve the entire problem. When using
> .xsession, none of the app-defaults get loaded (eg. Xterm has a white
> background and other stuff like that). Any thoughts on that would still
> be welcome.
>
> thx,
> Wim
>
> --
> Only two things are infinite: human stupidity and the universe, and I'm
> not sure about the latter. -- Albert Einstein
>
>   ------------------------------------------------------------------------
>
> Subject: Re: X doesn't seem to load app-defaults using gdm
> Date: Wed, 5 Mar 2003 23:19:42 +0100
> From: Wim De Smet <fragmeat@yucom.be>
> To: debian-user@lists.debian.org
> References: <20030304224511.49427e6a.fragmeat@yucom.be>
>      <20030305031741.GC1543@moonkingdom.net>
>      <20030305064233.GA14734@amutor.kolej.mff.cuni.cz>
>
> On Wed, 5 Mar 2003 07:42:33 +0100
> Martin Kacerovsky <wizard@matfyz.cz> wrote:
> > Hi,
> >
> > On Tue, Mar 04, 2003 at 07:17:41PM -0800, Marc Wilson wrote:
> > > So, try this:
> > >
> > > rxvt*background:        black
> > > rxvt*foreground:        white
> > >
> > > I don't know for sure what class name rxvt actually uses,
> > > but a preusal of the documentation will tell you.
> > >
> >
> > Most terminal emulators accept class name XTerm, I guess,
> > (yeah, I know, Eterm does not, it has it's own conf. file)
> > so I have in my /etc/X11/Xresources/xterm file:
> >
> > ! /etc/X11/Xresources/xterm
> >
> > XTerm*font:     -misc-fixed-medium-r-normal--20-*iso8859-2
> > XTerm*scrollBar:        false
> > XTerm*foreground:       grey
> > XTerm*background:       black
> >
> > And rxvt accepts it so, and aterm too.
> >
>
> My bad. Apparently there was no line like this present. So basically the
> settings for xterm background color get loaded from somewhere else when
> not using the Xsession session under gdm. Only question is where. I'll
> look to /etc/X11/Session.d/ but I didn't find it in there earlier. Maybe
> I overlooked it...
>
> --
> Only two things are infinite: human stupidity and the universe, and I'm
> not sure about the latter. -- Albert Einstein
>
>   ------------------------------------------------------------------------
>
> Subject: Mozilla and TrueType
> Date: Wed, 5 Mar 2003 23:16:31 +0100
> From: Ismael Valladolid Torres <ismaeval@terra.es>
> To: debian-user@lists.debian.org
>
> Hi,
>
> To enable TrueType support for Mozilla at work I configure my
> /etc/mozilla/prefs.js as follows:
>
> // TrueType
> pref("font.FreeType2.enable", true);
> pref("font.freetype2.shared-library", "libfreetype.so.6");
> pref("font.FreeType2.autohinted", true);
> pref("font.FreeType2.unhinted", false);
> pref("font.antialias.min",        10);
> pref("font.directory.truetype.1", "/usr/share/fonts/truetype");
>
> I have copied some .ttf files inside this directory. But Mozilla only
> allows me to select these fonts if the directory, owned by root, is
> world writable, as I have detected that a .mozilla_font_summary.ndb
> file needs first to be created and later to be open for writing.
>
> I'd like to know the usage for this file. I also wonder if there is some
> kind of workaround that allows me to avoid having that
> /usr/share/fonts/truetype directory world writable, as if I install
> the msttcorefonts package, those fonts show up in Mozilla without the
> need of changing /usr/lib/X11/fonts/TrueType permissions. Any info
> will be very useful. Thanks.
>
> Regards, Ismael
>
>   ------------------------------------------------------------------------
>
> Subject: Re: Dumb question: How do you reboot?
> Date: Wed, 5 Mar 2003 23:23:07 +0100
> From: Wim De Smet <fragmeat@yucom.be>
> To: "Eric G. Miller" <egm2@jps.net>
> CC: debian-user@lists.debian.org
> References: <3E65631F.2030502@msstate.edu>
>      <3E656C53.2050400@acu.edu>
>      <20030305050147.GB14238@calico.local>
>
> On Tue, 4 Mar 2003 21:01:47 -0800
> "Eric G. Miller" <egm2@jps.net> wrote:
> > On Tue, Mar 04, 2003 at 09:17:39PM -0600, Kent West wrote:
> > > I believe the next version of Gnome's login screen (gdm) implements
> > > a menu allowing you to shutdown/reboot.
> >
> > Hmm, doesn't the version in Woody have that cabability?  GDM has been
> > able to do that for quite some time (I think SystemMenu is set "false"
> > by default).
> >
> > /etc/gdm/gdm.conf
> >
> > [daemon]
> > ...
> > HaltCommand=/sbin/shutdown -h now "Halted from gdm menu."
> > ...
> > RebootCommand=/sbin/shutdown -r now "Rebooted from gdm menu."
> > ...
> >
> > [greeter]
> > ...
> > SystemMenu=true
> > ...
> >
>
> You can also launch the gdm configurator from the gdm menus. It is one
> of the "basic" menu options in the configurator I think. It is indeed
> present in that version of gdm (I'm sure of it)
>
> grtz,
> Wim
>
> --
> Only two things are infinite: human stupidity and the universe, and I'm
> not sure about the latter. -- Albert Einstein
>
>   ------------------------------------------------------------------------
>
> Subject: formail help
> Date: Wed, 05 Mar 2003 23:23:36 +0100
> From: Attila Csosz <csosz77@axelero.hu>
> To: debian-user <debian-user@lists.debian.org>
>
> Hi,
>
> Which fields should I place at least to this list to get correct
> mailbox? I use the followings but I've got an error message in mutt
> "this is not a correct mailbox" (or similar)
>
> in my .procmailrc
>
> :0
> *
> | formail -k X From: -X Subject: >> inbox
>
> Thanks
>  Attila
>
>   ------------------------------------------------------------------------
>
> Subject: Re: The Very Verbose Guide to Updating and Compiling Your Debian
>      Kernel
> Date: Wed, 05 Mar 2003 17:52:46 -0500
> From: Travis Crump <pretzalz@techhouse.org>
> To: Debian User List <debian-user@lists.debian.org>
> References: <3E648B25.9070304@ihug.co.nz> <20030305195635.GA26597@brillig>
>
> Daniel Farnsworth Teichert wrote:
> > # make sure you've got the bzip2 package; the comment in the
> > # article confusing 'tar' and 'gzip' also confused me, BTW...
> > apt-get install bzip2
> >
> not necessary since kernel-source depends on bzip2 it will be brought it
> automatically when you install the kernel source
> > # Get the make-kpkg program and friends...
> > apt-get install kernel-package
> > # get the kernel source...
> > apt-get install kernel-source-2.4.20
> >
>
>  From this point on you shouldn't be root, add yourself to the group
> 'src' instead.['adduser <yourself> src' as root, you'll have to restart
> your shell for this to take effect, the easiest way is to just start a
> new subshell with 'bash' or similar.]
> > # go to the source...
> > cd /usr/src
> >
> > # unpack it; note that the 'j' flag un-bzips it...
> > tar -xjvf kernel-source-2.4.20.tar.bz2
> >
> > # into the unzip'ed, un-tar'ed  source...
> > cd kernel-source-2.4.20
> >
> > make-kpkg kernel_image
> >
>
> You need to use fakeroot for this step since you shouldn't be doing this
> as root.  I typically use 'fakeroot make-kpkg --append-to-version blah
> --initrd kernel_image kernel_headers modules_image'.  The
> append-to-version option makes it possible to install two kernels from
> the same tree simultaneously.
>
> > (Note that the above requires that root has access to your X
> > display, because it uses 'xconfig'. Now, this is probably going
> > to show you how clue-less I am, but one simple way I do this on
> > occasion is by 'ssh -X root@localhost' to become root for the
> > above; go ahead, tell me it's silly--I know : ).
> >
>
> It is not a silly way to become root, it is just silly to become root. :)
>
>   ------------------------------------------------------------------------
>
> Subject: Re: Patched sendmail? testing?
> Date: Wed, 5 Mar 2003 23:04:55 +0000
> From: Colin Watson <cjwatson@debian.org>
> To: Debian User List <debian-user@lists.debian.org>
> References: <20030304133702.GA7861@teddy.fas.com> <20030304141502.GB1543@moonkingdom.net> <20030304163234.GA12357@teddy.fas.com> <20030304170210.GA5930@riva.ucam.org> <20030304190448.GA16100@teddy.fas.com> <20030304193005.GA7219@riva.ucam.org> <20030304211102.GC19652@teddy.fas.com> <20030304215318.GB5959@riva.ucam.org> <20030304230821.GA6862@riva.ucam.org> <20030305220505.GB19354@dragon.kitenet.net>
>
> On Wed, Mar 05, 2003 at 05:05:05PM -0500, Joey Hess wrote:
> > Colin Watson wrote:
> > > the new safe signals implementation has caused some problems which mean
> > > that the next upstream release will allow them to be turned off.
> >
> > Argh.
> > Do you know if that is a compile-time switch or a run-time switch? I've
> > had some very fun debugging sessions based on perl's signal handling
> > changes and the only thing worse than having to deal with the current
> > safe signals would be making my programs have to deal with both sorts.
>
> Fear not; I believe that it'll be controlled by $ENV{PERL_SIGNALS} being
> 'unsafe' or 'safe'. All the other syntactic tricks that were proposed
> seemed to blow up on older versions of perl, which would have defeated
> the point.
>
> (The signature was the implementor's frustrated summary on trying to get
> anyone to agree on what the switch should be ...)
>
> --
> Colin Watson                                  [cjwatson@flatline.org.uk]
> "My suggestion is that we create a new programming language for the
> purpose, written completely in Akkadian cuneiform, Nepalese, and
> backwards." -- Jarkko Hietaniemi, perl5-porters
>
>   ------------------------------------------------------------------------
>
> Subject: Re: Help with wireless
> Date: Thu, 6 Mar 2003 00:05:08 +0100
> From: Sebastian Henschel <shensche@kodeaffe.de>
> To: Jord Swart <jords@gmx.net>
> CC: Rus Foster <rghf@fsck.me.uk>, Emilio Murcia <emmurcia@terra.es>,
>      debian-laptop@lists.debian.org,
>      debian-user <debian-user@lists.debian.org>
> References: <3E66502A.7080704@terra.es> <20030305115450.S48343@thor.65535.net> <200303052127.23332.jords@gmx.net>
>
> hi there..
>
> Received at 2003-03-05 / 23:51 by Jord Swart:
> >
> > Which pretty much comes down to doing an:
> >
> > apt-get install wireless-tools
>
> especially take a look into "iwconfig".
>
> > But the reading on Jeans site is also very important. First thing you really
> > need to find out is what chipset is on your card. tuxmobile.org might help as
> > well here.
>
> now for the real reason for this mail: it is http://tuxmobil.org. :)
>
> cheers,
>  sebastian
> --
> ::: sebastian henschel
> ::: kodeaffe
> ::: lynx -source http://www.kodeaffe.de/shensche.pub | gpg --import
>
>   ------------------------------------------------------------------------
>    Part 1.16.1.2Type: application/pgp-signature
>
>   ------------------------------------------------------------------------
>
> Subject: Re: OT: EchoLink equivalent for Linux
> Date: Wed, 05 Mar 2003 17:06:44 -0600
> From: Kent West <westk@acu.edu>
> To: debian-user@lists.debian.org
> References: <3E57F046.9030802@acu.edu>
>
> Kent West wrote:
>
> > As an amateur radio operator (ham), I've just been introduced to a
> > very neat little program called EchoLink, which is an interesting
> > marriage between the internet and radio. The only problem is that it
> > appears to be Windows only. Does anyone know of a similar program for
> > Linux?
>
> I've been able to get EchoLink to _almost_ work in Linux via WINE. I can
> see who's online/on-air, I can connect to them, I can type and recieve
> messages, I can hear their audio, but I can't send audio. As I've
> tinkered with it, I've about decided the problem is not in
> EchoLink/WINE, but rather in my sound setup. I've never used a
> microphone on Linux before, and no matter what I try I can't seem to get
> any indication of audio from my mic. I can hear audio if I get right up
> close to the mic, but I think it's just feeding straight through the
> sound card without getting digitized and processed through the computer
> itself. I've tried playing with the settings in aumix and gmix and kmix
> and krec and etc, but haven't had much luck. Well, that's not entirely
> true; from the command prompt I can type "rec hello.wav" and record some
> voice audio that way, and then play it back via "play hello.wav". If any
> of you hams out there have a few minutes and have working microphone
> audio, you might try downloading EchoLink
> (http://www.synergenics.com/el/) and giving it a try and letting me know
> if it works or not.
>
> Thanks!
>
> Kent
>
>   ------------------------------------------------------------------------
>
> Subject: kernel-source-2.4.18-bf2.4?
> Date: Wed, 5 Mar 2003 17:30:47 -0600
> From: Kris Kerwin <snoopy248th@ameritech.net>
> To: debian-user@lists.debian.org
>
> Hi all,
>
> Something tells me this is a question that has already been asked, and that
> I'll probably be flamed for it, so, flame away!  :-)  Anyways - could anyone
> tell me where I could find the source for kernel 2.4.18-bf2.4?  I've checked
> in Debian's archives, as well as kernel.org and on Google.  Scary thing -
> Google either says it doesn't exist, or (more likely) I don't know where to
> begin to look.
>
> I'm looking to install ALSA and a (pirated) copy of VMWare, so if you can
> think of a better kernel for those (that has a source and image available), I
> could do with any help I can get. Thanks.
>
> Kris Kerwin
>
>   ------------------------------------------------------------------------
>
> Subject: Re: Setting Default Framebuffer Mode
> Date: Wed, 5 Mar 2003 17:46:08 -0600
> From: Ian Melnick <dazed@vonsteuben.cps.k12.il.us>
> Reply-To: debian-user@lists.debian.org
> To: debian-user@lists.debian.org
> References: <20030304213153.GA21444@vonsteuben.cps.k12.il.us> <20030305004608.GE73784@doorstop.net>
>
> > I think it depends on your specific framebuffer driver.
>
> It does. I use the rivafb driver on this computer, and it doesn't
> support kernel arguments at stat-up, so 'vga=whatever' doesn't work with
> this driver. Instead, you need to edit the fbdev.c file in
> linux/drivers/video/riva, and change the default settings within "struct
> fb_var_screeninfo rivafb_default_var", to match the settings that you
> want from /etc/fb.modes. Since I was satisfied with 640x480 but wanted a
> better refresh rate (from 60 to 100Hz), I had to change pixclock to
> 22272, left_margin to 48, right_margin to 32, upper_margin to 17,
> lower_margin to 22, hsync_len to 128, vsync_len to 12. Hopefully this is
> useful to someone else. Thanks for cluing me on referring to
> 'documentation' (what's that?!).



Reply to: