eft: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left:=
1ex;">
I'm relativly new to Debian Linux. Last month I found a package to inst=
all
the necessary modules to compile C and C++ source code. Because of a=
HD
problem, I had to do a rebuild of my system, losing everything I had=
. I<br>
can't recall the call-out of that package. I'm almost certain it wa=
s a<br>Debian package, but I could be wrong. It installed without problems =
using<br>aptitude.<br><br>Does anyone know what I'm talking about?<br>
--
John Salmon
salmonjj@=
comcast.netB
---- Posted via Pronews.com - Premium Corporate Usenet =
News Provider ----<br>
http://www.pronews.com" target=3D"_blank">
http://www.pronews.com=
offers corporate packages that have access to 100,000+ newsgroups
<=
font color=3D"#888888">
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian=
.org</a><br>
with a subject of "unsubscribe". Trouble? Contact <a href=3D"mail=
to:listmaster@lists.debian.org">listmaster@lists.debian.org</a><br><br></fo=
nt></blockquote></div><br>
------=_Part_15813_11783243.1202492835720--
Date: Fri, 8 Feb 2008 17:47:46 +0000
From: Tzafrir Cohen <tzafrir@cohens.org.il>
To: debian-user@lists.debian.org
Subject: Re: Basic C and C++ Package
Message-ID: <20080208174745.GY8028@pear.tzafrir.org.il>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Fri, Feb 08, 2008 at 11:09:06AM -0600, John Salmon wrote:
> I'm relativly new to Debian Linux. Last month I found a package to install
> the necessary modules to compile C and C++ source code. Because of a HD
> problem, I had to do a rebuild of my system, losing everything I had. I
> can't recall the call-out of that package. I'm almost certain it was a
> Debian package, but I could be wrong. It installed without problems using
> aptitude.
>
> Does anyone know what I'm talking about?
build-essential
--
Tzafrir Cohen | tzafrir@jabber.org | VIM is
http://tzafrir.org.il | | a Mutt's
tzafrir@cohens.org.il | | best
ICQ# 16849754 | | friend
Date: Fri, 08 Feb 2008 11:48:37 -0600
From: Ron Johnson <ron.l.johnson@cox.net>
To: debian-user@lists.debian.org
Subject: Re: Basic C and C++ Package
Message-ID: <47AC95F5.7080708@cox.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02/08/08 11:09, John Salmon wrote:
> I'm relativly new to Debian Linux. Last month I found a package to install
> the necessary modules to compile C and C++ source code. Because of a HD
> problem, I had to do a rebuild of my system, losing everything I had. I
> can't recall the call-out of that package. I'm almost certain it was a
> Debian package, but I could be wrong. It installed without problems using
> aptitude.
>
> Does anyone know what I'm talking about?
The C compiler is gcc, the C++ compiler is g++.
- --
Ron Johnson, Jr.
Jefferson LA USA
PETA - People Eating Tasty Animals
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHrJX1S9HxQb37XmcRAvi9AJ43ZzQWiD8FABABooU1D0IaMMjeEQCfWzwq
D8o/XqvuwGryKS3kFIZgDvU=
=jOpB
-----END PGP SIGNATURE-----
Date: Fri, 8 Feb 2008 15:53:43 -0200
From: Klaus Imgrund <klaus@jactex.biz>
To: debian-user@lists.debian.org
Subject: xserver crashing
Message-Id: <200802081553.43997.klaus@jactex.biz>
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Hello,
I've been over the archives for the last two month but couldn't find any info
about my specific problem.
I updated xorg a couple of days ago from an older version (running sid).
Please don't ask what older version - it's been a while.
After that the xserver started crashing after a couple of hours.
That wasn't a big surprise since I run nvidia binary drivers.
Figured I reinstall the nvidia driver and throw in a new kernel for good
measure.
xserver is 1:7.3+10
Kernel: 2.6.24-1-686
nvidia : version: 171.05
Unfortunately the xserver is still crashing.Well I figured since the nvidia
installer gave me a warning about the kernel being compiled with a different
version of gcc I just walk away and use the nv driver since I don't care
about 3d anyway.
Unfortunately the nv driver also crashes :-)
This is with a 7600GS and a nforce 650i motherboard.
Does anybody have any suggestions what might be the problem here?
The only thing I could think about doing right now is downgrading xorg but
that might open a whole new can of worms...
Klaus
Date: Fri, 08 Feb 2008 20:10:09 +0100
From: Christopher Bianchi <ienabellamy@gmail.com>
To: debian-user@lists.debian.org
Subject: Re: Cannot authenticate with DSA-pubkey in Etch
Message-Id: <1202497809.2912.12.camel@sharpy.localdomain>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Emh, sorry, but i didn't past the config and the errors because I
thought that attach to the mail was better.
Anyway, the default sshd_config is NOT right for the authentication with
pubkey, because the Password Authentication is set to 'yes' in default
config.
I changed only:
PubkeyAuthentication yes
ChallengeResponseAuthentication no
PasswordAuthentication no
The permissions are ok.
And i've copied the id_dsa.pub in this way:
# scp ~/.ssh/id_dsa.pub \
leopard@server.example.com:~/.ssh/authorized_keys
Jonathan Wilson, you're to nervous. Calm. Life is good. Open a txt
file ? == 2 seconds. To read 10-11 lines ? 20 seconds.
Kisses.
Any help would be appreciate.
Il giorno ven, 08/02/2008 alle 11.41 -0600, Jonathan Wilson ha scritto:
> On Friday 08 February 2008 04:43:15 Christopher Bianchi wrote:
> > i wish to connect my laptop to my server with a ssh pubkey and no
> > password. The procedure that i use to create the key pair and setting
> > permission on the directories (.ssh/) on laptop and server, are correct.
> >
> > I think that it's a possible error in sshd_config.
>
> Why, did you change anything? There is nothing wrong with the default config
> in Debian, it works very well.
>
> If you have made any changes to the sshd config, you should tell us what they
> are. I know I don't have time to read through your file and look for changes.
>
> > I attached to mail 2 text file, with the sshd_config and the exact
> > error.
>
> Embedding them in the email would have been better, no one wants to read
> attachments.
>
> > Here there's the uname of machine:
> >
> > ienabellamy@sunny:~$ uname -a
> > Linux sunny 2.4.27-3-sparc64 #1 Tue Dec 5 22:18:03 UTC 2006 sparc64
> > GNU/Linux
>
>
> debug1: Authentications that can continue: publickey
> debug1: Next authentication method: publickey
> debug1: Offering public key: .ssh/id_dsa
> debug1: Authentications that can continue: publickey
> debug1: Trying private key: /home/ienabellamy/.ssh/identity
> debug1: Trying private key: /home/ienabellamy/.ssh/id_rsa
> debug1: Trying private key: /home/ienabellamy/.ssh/id_dsa
> debug1: PEM_read_PrivateKey failed
>
> Did you check the file permissions on /home/ienabellamy/.ssh/id_rsa
> and /home/ienabellamy/.ssh/ and /home/ienabellamy/.ssh/authorized_keys
> (or /home/ienabellamy/.ssh/authorized_keys2 if that's what you're using) on
> both machines?
>
> Also check perms on your home directory. As security feature, ssh won't let
> you log in if the permissions are too wide open.
>
>
> ls -l /home/me/.ssh/
> -rw------- 1 me users 392 2008-02-04 16:03 authorized_keys
>
> ls -ld /home/me/.ssh/
> drwx------ 2 me users 80 2008-02-04 16:03 /home/me/.ssh/
>
> ls -ld /home/jw/
> drwxr-xr-x 7 me users 472 2008-02-07 19:45 /home/me/
>
>
> Please explain HOW you copied your public key up to the server.
>
> JW
>
>
> --
>
> ----------------------
> System Administrator - Cedar Creek Software
> http://www.cedarcreeksoftware.com
>
>
Date: Fri, 8 Feb 2008 14:17:16 -0500
From: Celejar <celejar@gmail.com>
To: debian-user@lists.debian.org
Subject: Re: Iceweasel problems - 3 of 3
Message-Id: <20080208141716.0d1f619a.celejar@gmail.com>
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
On Thu, 07 Feb 2008 08:25:47 -0600
Ron Johnson <ron.l.johnson@cox.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 02/07/08 08:00, Dennis G. Wicks wrote:
[snip]
> > But it is only Iceweasel,on this machine, that has
> > these problems. Not Opera or Konq on this system or any
> > browser on any other system on my localnet.
> >
> > Of course everything else on the my net that does any
> > browsing is Win 2k. The other two Debian systems are a
> > web server and and a backup/archive system.
> >
> > Any other browsers I can try on Debian?
>
> link2, lynx, w3c, chimera2, epiphany, galeon, iceape, midori,
> netsurf & konqueror.
>
> And I'm sure I missed some.
s/w3c/w3m/
links, amaya, dillo, edbrowse, kazehakase
> Ron Johnson, Jr.
Celejar
--
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator
Date: Fri, 08 Feb 2008 13:58:27 -0600
From: Ron Johnson <ron.l.johnson@cox.net>
To: debian-user@lists.debian.org
Subject: Re: Iceweasel problems - 3 of 3
Message-ID: <47ACB463.6090102@cox.net>
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02/08/08 13:17, Celejar wrote:
> On Thu, 07 Feb 2008 08:25:47 -0600
> Ron Johnson <ron.l.johnson@cox.net> wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 02/07/08 08:00, Dennis G. Wicks wrote:
>
> [snip]
>
>>> But it is only Iceweasel,on this machine, that has
>>> these problems. Not Opera or Konq on this system or any
>>> browser on any other system on my localnet.
>>>
>>> Of course everything else on the my net that does any
>>> browsing is Win 2k. The other two Debian systems are a
>>> web server and and a backup/archive system.
>>>
>>> Any other browsers I can try on Debian?
>> link2, lynx, w3c, chimera2, epiphany, galeon, iceape, midori,
>> netsurf & konqueror.
>>
>> And I'm sure I missed some.
>
> s/w3c/w3m/
Oops...
> links, amaya, dillo, edbrowse, kazehakase
/links/ is obsoleted by /links2/. Thanks for the other ones. I
didn't realize, though, that amaya & dillo were still maintained.
- --
Ron Johnson, Jr.
Jefferson LA USA
PETA - People Eating Tasty Animals
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHrLRiS9HxQb37XmcRAosjAKDKUkFs2m3ujfUbhXb/RrZLlM85WACeLmc0
RzIYLY6x6Tly6uG+aJH7pPw=
=Pj1r
-----END PGP SIGNATURE-----
Date: Fri, 8 Feb 2008 20:03:19 -0000
From: marc <gmane@auxbuss.com>
To: debian-user@lists.debian.org
Subject: Re: vim + LaTeX (Was: What am I missing without mutt?)
Message-ID: <MPG.2216c59ba1a3881c989b2e@news.gmane.org>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Micha said...
> On Wed, 6 Feb 2008 19:11:32 -0000
> > The reason I asked is that I write books yet haven't found anything to
> > match WinEdt, which is a Windows editor, for handling chapters and LaTeX
> > on Linux. In all other cases, I use vim.
>
> Personally I work with either lyx or emacs + auctex, but you may want to have
> a look at texmaker which is much more similar to winedt (and it has both linux
> and windows versions so if you like it and have to work on both linux and
> windows you can use the same software)
Thanks for the texmaker pointer. I had a look at it, but unfortunately -
as did/does kile - it doesn't do realtime spell checking, and you can't
add words to the dictionary; as a writing tool, those are serious
omissions.
I'm not wedded to winedt, btw, in fact, I think it's rather nasty in
many ways, but it does do the basics very well.
--
Cheers,
Marc
Date: Fri, 08 Feb 2008 12:08:10 -0800
From: Jeff D <fixedored@gmail.com>
To: debian-user@lists.debian.org
Subject: Re: Cannot authenticate with DSA-pubkey in Etch
Message-ID: <47ACB6AA.8080804@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Christopher Bianchi wrote:
> Emh, sorry, but i didn't past the config and the errors because I
> thought that attach to the mail was better.
>
> Anyway, the default sshd_config is NOT right for the authentication with
> pubkey, because the Password Authentication is set to 'yes' in default
> config.
>
> I changed only:
>
> PubkeyAuthentication yes
> ChallengeResponseAuthentication no
> PasswordAuthentication no
>
> The permissions are ok.
> And i've copied the id_dsa.pub in this way:
> # scp ~/.ssh/id_dsa.pub \
> leopard@server.example.com:~/.ssh/authorized_keys
>
> Jonathan Wilson, you're to nervous. Calm. Life is good. Open a txt
> file ? == 2 seconds. To read 10-11 lines ? 20 seconds.
>
> Kisses.
>
> Any help would be appreciate.
>
You can still have password athentication and key authentication at the
same time. In the future, an easier way to copy keys is to use
ssh-copy-id, that will copy over your key file to the remote server and
make sure that proper permissions are set. Permissions on your
~/.ssh/authorized_keys file should be 600. If you look at the error log
on the *server* you will see what error is, not the client.
Date: Fri, 8 Feb 2008 20:54:02 +0000 (UTC)
From: Felix Karpfen <felixk@webone.com.au>
To: debian-user@lists.debian.org
Subject: Re: Non-understood advice - was Re: dist-upgrade from sarge to etch -
package
Message-ID: <foifh9$om6$1@ger.gmane.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
On Wed, 06 Feb 2008 20:34:14 +0000, Felix Karpfen wrote:
>=20
> On Tue, 05 Feb 2008 18:54:08 +0100, Florian Kulzer wrote:
>> Check for non-Debian packages on your system by running:
>>=20
>> aptitude search '~i!~Odebian'
>>
>=20
> As an aptitude-novice, I tried the above command on my
> fully-operational upgrade from Sarge to Etch. It gave **a long list of
> installed packages - almost all of which were part of the Debian
> install***.
>=20
> What have I <missed|misunderstood>?
Firstly, I would like to thank Florian Kulzer and Daniel Burrows for
their replies.
They failed to address my misunderstanding and the fault was mine.
My concern arose not from the absence of "vuescan" (which - as pointed
out - is a monolithic binary package) but the presence of many dozens
of packages that were *not* non-Debian packages.
The concern arose from the fact that - following the upgrade
instructions to the letter - I recollect running a command that
identified non-Debian packages as part of the upgrade to Etch and *the
command gave the expected output*. But, alas, I can no longer find
what that command was.=20
Felix Karpfen
--=20
Felix Karpfen
Public Key 72FDF9DF (DH/DSA)
Daniel Burrows
Date: Fri, 8 Feb 2008 14:02:30 -0700
From: ChadDavis <chadmichaeldavis@gmail.com>
To: debian <debian-user@lists.debian.org>
Subject: wrapper script issue
Message-ID: <4fe4c4f50802081302i9ebf08cs78ccde533ef1d663@mail.gmail.com>
Content-Type: multipart/alternative;
boundary="----=_Part_13970_2824750.1202504550610"
------=_Part_13970_2824750.1202504550610
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
I've started using wrapper scripts to set environment variables that are
required by individual applications, as per the debian policy manual. I've
encountered a problem that seems to arise out of some difference between
using the wrapper script and hitting the binary directly. It involves a
ruby script, but I don't think that matters at all. Its probably just a
common sense scripting thing. Here's the story.
First of all, I have wrapped my ruby binary in wrapper script as just
indicated. the wrapper script is called "ruby1.8" and here's the contents:
#!/bin/sh
export RUBYOPT=rubygems
exec /etc/alternatives/ruby1.8 "$@"
I'm trying to execute the following ruby script, matz.rb
#!/usr/bin/ruby1.8
puts "Hello, Matz!"
If I execute this script with explicit command line use of the ruby wrapper
script, such as:
me@myhost:~/temp/rubyTest$ ruby1.8 matz.rb
everything works fine!
The problem arises when I try to take advantage of the shebang notation to
invoke the ruby script with out explicit command line invocation of the ruby
binary, ala:
me@myhost:~/temp/rubyTest$ matz.rb
results in:
./matz.rb: line 2: puts: command not found
What am I missing here?
BTW, I originally posted this to the forums.debian.net but did not receive
any response. Does this count as cross posting? If so, I apologize.
------=_Part_13970_2824750.1202504550610
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
I've started using wrapper scripts to set environment variables that are required by individual applications, as per the debian policy manual. I've encountered a problem that seems to arise out of some difference between using the wrapper script and hitting the binary directly. It involves a ruby script, but I don't think that matters at all. Its probably just a common sense scripting thing. Here's the story. <br>
<br>First of all, I have wrapped my ruby binary in wrapper script as just indicated. the wrapper script is called "ruby1.8" and here's the contents:<br><br>#!/bin/sh<br>export RUBYOPT=rubygems<br>
exec /etc/alternatives/ruby1.8 "$@"<br><br>I'm trying to execute the following ruby script, matz.rb<br><br>#!/usr/bin/ruby1.8<br>puts "Hello, Matz!"<br><br>If I execute this script with explicit command line use of the ruby wrapper script, such as:<br>
<br>me@myhost:~/temp/rubyTest$ ruby1.8 matz.rb<br><br>everything works fine!<br><br>The problem arises when I try to take advantage of the shebang notation to invoke the ruby script with out explicit command line invocation of the ruby binary, ala:<br>
<br>me@myhost:~/temp/rubyTest$ matz.rb<br><br>results in:<br><br>./matz.rb: line 2: puts: command not found<br><br><br>What am I missing here?<br><br>BTW, I originally posted this to the forums.debian.net but did not receive any response. Does this count as cross posting? If so, I apologize.<br>
------=_Part_13970_2824750.1202504550610--
Date: Fri, 8 Feb 2008 14:58:29 -0500
From: "Douglas A. Tutty" <dtutty@porchlight.ca>
To: debian-user@lists.debian.org
Subject: Re: Cannot authenticate with DSA-pubkey in Etch
Message-ID: <20080208195829.GA6480@titan.hooton>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Fri, Feb 08, 2008 at 11:43:15AM +0100, Christopher Bianchi wrote:
> i wish to connect my laptop to my server with a ssh pubkey and no
> password. The procedure that i use to create the key pair and setting
> permission on the directories (.ssh/) on laptop and server, are correct.
I've put some comments within your file. Then I've included my
sshd_config file. I use this, then follow the instructions in the
Debian-Reference under ssh without passwords. It works.
I hope this helps.
Doug.
---
>
> I think that it's a possible error in sshd_config.
> **** sshd_config *****************************************************
> # What ports, IPs and protocols we listen for
> Port 10022
Are both machies using the same port?
> # Authentication:
> LoginGraceTime 1m
> PermitRootLogin no
> StrictModes yes
As long as its not root that is the trouble.
>
> # Max number of login attempts for a single connection
> MaxAuthTries 3
>
> RSAAuthentication no
Shouldn't this be yes?
> PubkeyAuthentication yes
> AllowGroups sshusers
Is the user trying to ssh in sshusers on both boxes?
> X11Forwarding no
> X11DisplayOffset 10
> PrintMotd no
> PrintLastLog yes
> KeepAlive yes
> #UseLogin no
>
> #MaxStartups 10:30:60
>
> Banner /etc/issue.net
>
> Subsystem sftp /usr/lib/openssh/sftp-server
>
> UsePAM no
I have UsePAM yes
>
> MaxStartups 2
[snip debug: I've never needed it so I've never read one before]
-----
For comparison, here's my sshd_config:
# Package generated configuration file
# See the sshd(8) manpage for details
# What ports, IPs and protocols we listen for
Port 22
# Use these options to restrict which interfaces/protocols sshd will bind to
#ListenAddress ::
#ListenAddress 0.0.0.0
ListenAddress 192.168.1.1
Protocol 2
# HostKeys for protocol version 2
HostKey /etc/ssh/ssh_host_rsa_key
HostKey /etc/ssh/ssh_host_dsa_key
#Privilege Separation is turned on for security
UsePrivilegeSeparation yes
# Lifetime and size of ephemeral version 1 server key
KeyRegenerationInterval 3600
ServerKeyBits 768
# Logging
SyslogFacility AUTH
LogLevel INFO
# Authentication:
LoginGraceTime 120
PermitRootLogin yes
StrictModes yes
RSAAuthentication yes
PubkeyAuthentication yes
#AuthorizedKeysFile %h/.ssh/authorized_keys
# Don't read the user's ~/.rhosts and ~/.shosts files
IgnoreRhosts yes
# For this to work you will also need host keys in /etc/ssh_known_hosts
RhostsRSAAuthentication no
# similar for protocol version 2
HostbasedAuthentication no
# Uncomment if you don't trust ~/.ssh/known_hosts for RhostsRSAAuthentication
#IgnoreUserKnownHosts yes
# To enable empty passwords, change to yes (NOT RECOMMENDED)
PermitEmptyPasswords no
# Change to yes to enable challenge-response passwords (beware issues with
# some PAM modules and threads)
ChallengeResponseAuthentication no
# Change to no to disable tunnelled clear text passwords
#PasswordAuthentication yes
####### added by dtutty after ~/.ssh/authorized_keys updated
PasswordAuthentication no
# Kerberos options
#KerberosAuthentication no
#KerberosGetAFSToken no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes
# GSSAPI options
#GSSAPIAuthentication no
#GSSAPICleanupCredentials yes
X11Forwarding yes
X11DisplayOffset 10
PrintMotd no
PrintLastLog yes
TCPKeepAlive yes
#UseLogin no
#MaxStartups 10:30:60
#Banner /etc/issue.net
# Allow client to pass locale environment variables
AcceptEnv LANG LC_*
Subsystem sftp /usr/lib/openssh/sftp-server
### added by dtutty (ref lskb on ssh, man sshd_config)
AllowGroups ssh
ClientAliveInterval 15
UsePAM yes
End of debian-user-digest Digest V2008 Issue #301
*************************************************
Received on Fri Feb 8 16:18:33 2008