Re: kde / gnome / blackbox

2004-09-03 Thread John Hedges
On Thu, Sep 02, 2004 at 06:11:54PM -0700, SML wrote:
> I have a new installation of Sarge on a Gateway M305 and the default
> desktop is KDE. I'm a Gnome girl :) I've looked all over the startx
> script, xsession, and xinit -- but I couldn't find where the call is to
> start KDE. 
> 
> My initial run level is 3 so I startx at a command prompt and I would
> like to start Gnome, and occassionally Blackbox, instead of KDE. 
> 
> Where can I change that?

I like gnome too :) You might try something like 

dpkg -r kdm
apt-get install gdm

which will replace the kde init script with the gnome one (I think!)

Cheers

John


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: testing ppp w/ debian

2004-09-23 Thread John Hedges
Hi James

I did this last week so while it's fresh in my mind ...
I was new to dial-in so it's unlikely to be the perfect solution, but it
seems to work.

Make sure you have ppp and mgetty installed. Both have good docs -
info mgetty (install mgetty-docs) and man pppd.

The last line of /etc/inittab (at least on my woody install) was a
commented out mgetty line.  Uncomment it and change to reflect your own
serial port. eg:

T0:23:respawn:/sbin/mgetty -x0 -s 57600 ttyS0

Run 'telinit q' to get init to start mgetty listening on your serial
port.

For PAP you need to alter /etc/ppp/pap-secrets. For a user brian wanting
to login to machine zinc, add a line:

brian   zinc""

Finally - ignoring the steps I've completely forgotten about :) set up
/etc/ppp/options (or /etc/ppp/options.ttyS0 (0/1/2...)) to set the IPs
for either end of the ppp link eg:

192.168.1.1:192.168.1.2

Leaving first field blank will defualt to an IP address from the server.
Leaving the second field blank allows the client to set its own IP.
Other handy settings were 'defaultroute' and 'ipcp-accept-remote'.
/var/log/messages is useful for seeing how far you are getting with ppp.

The first time I dialled in my modem got into a strange state and it
wouldn't answer incoming calls. Dialling out with wvdial reinitialised
it prefectly.

Cheers

John

On Thu, Sep 23, 2004 at 11:25:56AM -0400, wireless wrote:
> Hello,
> 
> I'm trying to get ppp working on friend's debian portable. wvdial is 
> what I have used in the past, but, any other ppp package 
> recommedations are welcome. What I'm need to do is put a serialport 
> (rs232) modem on another debian system and set it for the dialin 
> (inbound) part of the ppp connection connect. Once I get that to work, 
> I need to be able to require various things, such as pap, chap, etc, 
> on the inbound side so at to emulate what the ISP requires. That way 
> we can test the various settings on my friends' portable. Having cable 
> modem access at home, it's been a long time since I've messed around 
> with dialin ppp. One other question, instead of going to the trouble 
> to setup a radius server (would not even know which radius package is 
> good), can I just make up a shell account for the user and auth the 
> passwd on the same server that the serialport modem is connected to?
> 
> 
> Any ideas on packages for the ppp dialin on single serial port?
> 
> TIA,
> James
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact 
> [EMAIL PROTECTED]
> 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: testing ppp w/ debian

2004-09-23 Thread John Hedges
> > On Thu, Sep 23, 2004 at 11:25:56AM -0400, wireless wrote:
> > >Hello,
> > >
> > >I'm trying to get ppp working on friend's debian portable. wvdial is 
> > >what I have used in the past, but, any other ppp package 
> > >recommedations are welcome. What I'm need to do is put a serialport 
> > >(rs232) modem on another debian system and set it for the dialin 
> > >(inbound) part of the ppp connection connect. Once I get that to work, 
> > >I need to be able to require various things, such as pap, chap, etc, 
> > >on the inbound side so at to emulate what the ISP requires. That way 
> > >we can test the various settings on my friends' portable. Having cable 
> > >modem access at home, it's been a long time since I've messed around 
> > >with dialin ppp. One other question, instead of going to the trouble 
> > >to setup a radius server (would not even know which radius package is 
> > >good), can I just make up a shell account for the user and auth the 
> > >passwd on the same server that the serialport modem is connected to?
> > >
> > > 
> > >Any ideas on packages for the ppp dialin on single serial port?

> John Hedges wrote:
> >I did this last week so while it's fresh in my mind ...
> >I was new to dial-in so it's unlikely to be the perfect solution, but it
> >seems to work.
> >
> >Make sure you have ppp and mgetty installed. Both have good docs -
> >info mgetty (install mgetty-docs) and man pppd.
> >
> >The last line of /etc/inittab (at least on my woody install) was a
> >commented out mgetty line.  Uncomment it and change to reflect your own
> >serial port. eg:
> >
> >T0:23:respawn:/sbin/mgetty -x0 -s 57600 ttyS0
> >
> >Run 'telinit q' to get init to start mgetty listening on your serial
> >port.
> >
> >For PAP you need to alter /etc/ppp/pap-secrets. For a user brian wanting
> >to login to machine zinc, add a line:
> >
> >brian   zinc""
> >
> >Finally - ignoring the steps I've completely forgotten about :) set up
> >/etc/ppp/options (or /etc/ppp/options.ttyS0 (0/1/2...)) to set the IPs
> >for either end of the ppp link eg:
> >
> >192.168.1.1:192.168.1.2
> >
> >Leaving first field blank will defualt to an IP address from the server.
> >Leaving the second field blank allows the client to set its own IP.
> >Other handy settings were 'defaultroute' and 'ipcp-accept-remote'.
> >/var/log/messages is useful for seeing how far you are getting with ppp.
> >
> >The first time I dialled in my modem got into a strange state and it
> >wouldn't answer incoming calls. Dialling out with wvdial reinitialised
> >it prefectly.
> 
On Thu, Sep 23, 2004 at 05:14:31PM -0400, James wrote:
> OK, This if for setting up the dialin(host) serial port and modem I 
> presume?
> 
> What, if anyting do I need to apt-get for the host?
> 
> And you used wvdial on the other system to effect the dialout(user pc) 
> part of the ppp with just a standard /etc/wvdial.conf file?
> 
> apt-get wvdial (on the user's pc) and edit wvdial.conf, is all that is 
> needed?
> 
> If I understand your missing parts?
> 
> James
> 
Correct. This setup was for the dial-in host.

Unfortunately the dial-in clients are windows. This shouldn't make much
difference though.

On the host:

apt-get install ppp (this is almost certainly already installed)
apt-get install mgetty mgetty-docs

On the client:

apt-get install wvdial

If you need to adjust wvdial.conf I expect it to be minimally as the
installation prompts you for most things. 

John


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: mini/micro ATX w/ PCI

2003-08-11 Thread John Hedges
On Sun, Aug 10, 2003 at 11:56:01PM -0400, James wrote:
> Hello,
> 
> Does anyone have any experience or recommendations on very small ATX 
> form factor
> Linux based machines?  I'm looking to put debian on an x86 compatible 
> architecture.
> I'd like (2) PCI slots arranged so that the PCI cards are parallel with 
> the main (small) motherboard.
> 
> I intend to build a few custom routers (10-30), so any  serial(T1) cards 
> or experience getting T1
> cards to work  in a mini/micro ATX package is most welcome. I have used 
> Sangoma, Imagestream
> and several other T1 cards, but,it's always a pain finding small form 
> factor hardware.. I'd like
> something small,  portable, and with a 12VDC power supply (am I 
> dreaming or what?). I see
> "VIA" everywhere, but, I do not have any experience with this chipset, 
> to build a router.
> 
> Maybe someone knows of an OEM router that runs linux, where you actually 
> get access to
> the kernel, sources, etc,  so you can build/customize from scratch, a 
> router that is actually
> pleasurable to install and manage. Obviously, Cisco and I have 
> parted ways
> 
> What I hope to find is a small, highly portable, router, that runs linux 
> and make the sources
> available.
> 
> All ideas are welcome.
> 
> 
> James

Have a look at http://www.meshbook.com for a wireless router. These are
linux on mini itx.

There is also IPCop which is (I believe) a linux router/firewall.

Both are available pre-installed in PCs or on CF from
http://www.linitx.com . Sources for both are also freely available.

Good luck

John



Re: mini/micro ATX w/ PCI

2003-08-14 Thread John Hedges
On Sun, Aug 10, 2003 at 11:56:01PM -0400, James wrote:
> Hello,
> 
> Does anyone have any experience or recommendations on very small ATX 
> form factor
> Linux based machines?  I'm looking to put debian on an x86 compatible 
> architecture.
> I'd like (2) PCI slots arranged so that the PCI cards are parallel with 
> the main (small) motherboard.
> 
> I intend to build a few custom routers (10-30), so any  serial(T1) cards 
> or experience getting T1
> cards to work  in a mini/micro ATX package is most welcome. I have used 
> Sangoma, Imagestream
> and several other T1 cards, but,it's always a pain finding small form 
> factor hardware.. I'd like
> something small,  portable, and with a 12VDC power supply (am I 
> dreaming or what?). I see
> "VIA" everywhere, but, I do not have any experience with this chipset, 
> to build a router.
> 
> Maybe someone knows of an OEM router that runs linux, where you actually 
> get access to
> the kernel, sources, etc,  so you can build/customize from scratch, a 
> router that is actually
> pleasurable to install and manage. Obviously, Cisco and I have 
> parted ways
> 
> What I hope to find is a small, highly portable, router, that runs linux 
> and make the sources
> available.
> 
> All ideas are welcome.
> 
> 
> James

Have a look at http://www.meshbook.com for a wireless router. These are
linux on mini itx.

There is also IPCop which is (I believe) a linux router/firewall.

Both are available pre-installed in PCs or on CF from
http://www.linitx.com . Sources for both are also freely available.

Good luck

John


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: kde / gnome / blackbox

2004-09-03 Thread John Hedges
On Thu, Sep 02, 2004 at 06:11:54PM -0700, SML wrote:
> I have a new installation of Sarge on a Gateway M305 and the default
> desktop is KDE. I'm a Gnome girl :) I've looked all over the startx
> script, xsession, and xinit -- but I couldn't find where the call is to
> start KDE. 
> 
> My initial run level is 3 so I startx at a command prompt and I would
> like to start Gnome, and occassionally Blackbox, instead of KDE. 
> 
> Where can I change that?

I like gnome too :) You might try something like 

dpkg -r kdm
apt-get install gdm

which will replace the kde init script with the gnome one (I think!)

Cheers

John



Re: testing ppp w/ debian

2004-09-23 Thread John Hedges
Hi James

I did this last week so while it's fresh in my mind ...
I was new to dial-in so it's unlikely to be the perfect solution, but it
seems to work.

Make sure you have ppp and mgetty installed. Both have good docs -
info mgetty (install mgetty-docs) and man pppd.

The last line of /etc/inittab (at least on my woody install) was a
commented out mgetty line.  Uncomment it and change to reflect your own
serial port. eg:

T0:23:respawn:/sbin/mgetty -x0 -s 57600 ttyS0

Run 'telinit q' to get init to start mgetty listening on your serial
port.

For PAP you need to alter /etc/ppp/pap-secrets. For a user brian wanting
to login to machine zinc, add a line:

brian   zinc""

Finally - ignoring the steps I've completely forgotten about :) set up
/etc/ppp/options (or /etc/ppp/options.ttyS0 (0/1/2...)) to set the IPs
for either end of the ppp link eg:

192.168.1.1:192.168.1.2

Leaving first field blank will defualt to an IP address from the server.
Leaving the second field blank allows the client to set its own IP.
Other handy settings were 'defaultroute' and 'ipcp-accept-remote'.
/var/log/messages is useful for seeing how far you are getting with ppp.

The first time I dialled in my modem got into a strange state and it
wouldn't answer incoming calls. Dialling out with wvdial reinitialised
it prefectly.

Cheers

John

On Thu, Sep 23, 2004 at 11:25:56AM -0400, wireless wrote:
> Hello,
> 
> I'm trying to get ppp working on friend's debian portable. wvdial is 
> what I have used in the past, but, any other ppp package 
> recommedations are welcome. What I'm need to do is put a serialport 
> (rs232) modem on another debian system and set it for the dialin 
> (inbound) part of the ppp connection connect. Once I get that to work, 
> I need to be able to require various things, such as pap, chap, etc, 
> on the inbound side so at to emulate what the ISP requires. That way 
> we can test the various settings on my friends' portable. Having cable 
> modem access at home, it's been a long time since I've messed around 
> with dialin ppp. One other question, instead of going to the trouble 
> to setup a radius server (would not even know which radius package is 
> good), can I just make up a shell account for the user and auth the 
> passwd on the same server that the serialport modem is connected to?
> 
> 
> Any ideas on packages for the ppp dialin on single serial port?
> 
> TIA,
> James
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact 
> [EMAIL PROTECTED]
> 



Re: testing ppp w/ debian

2004-09-23 Thread John Hedges
> > On Thu, Sep 23, 2004 at 11:25:56AM -0400, wireless wrote:
> > >Hello,
> > >
> > >I'm trying to get ppp working on friend's debian portable. wvdial is 
> > >what I have used in the past, but, any other ppp package 
> > >recommedations are welcome. What I'm need to do is put a serialport 
> > >(rs232) modem on another debian system and set it for the dialin 
> > >(inbound) part of the ppp connection connect. Once I get that to work, 
> > >I need to be able to require various things, such as pap, chap, etc, 
> > >on the inbound side so at to emulate what the ISP requires. That way 
> > >we can test the various settings on my friends' portable. Having cable 
> > >modem access at home, it's been a long time since I've messed around 
> > >with dialin ppp. One other question, instead of going to the trouble 
> > >to setup a radius server (would not even know which radius package is 
> > >good), can I just make up a shell account for the user and auth the 
> > >passwd on the same server that the serialport modem is connected to?
> > >
> > > 
> > >Any ideas on packages for the ppp dialin on single serial port?

> John Hedges wrote:
> >I did this last week so while it's fresh in my mind ...
> >I was new to dial-in so it's unlikely to be the perfect solution, but it
> >seems to work.
> >
> >Make sure you have ppp and mgetty installed. Both have good docs -
> >info mgetty (install mgetty-docs) and man pppd.
> >
> >The last line of /etc/inittab (at least on my woody install) was a
> >commented out mgetty line.  Uncomment it and change to reflect your own
> >serial port. eg:
> >
> >T0:23:respawn:/sbin/mgetty -x0 -s 57600 ttyS0
> >
> >Run 'telinit q' to get init to start mgetty listening on your serial
> >port.
> >
> >For PAP you need to alter /etc/ppp/pap-secrets. For a user brian wanting
> >to login to machine zinc, add a line:
> >
> >brian   zinc""
> >
> >Finally - ignoring the steps I've completely forgotten about :) set up
> >/etc/ppp/options (or /etc/ppp/options.ttyS0 (0/1/2...)) to set the IPs
> >for either end of the ppp link eg:
> >
> >192.168.1.1:192.168.1.2
> >
> >Leaving first field blank will defualt to an IP address from the server.
> >Leaving the second field blank allows the client to set its own IP.
> >Other handy settings were 'defaultroute' and 'ipcp-accept-remote'.
> >/var/log/messages is useful for seeing how far you are getting with ppp.
> >
> >The first time I dialled in my modem got into a strange state and it
> >wouldn't answer incoming calls. Dialling out with wvdial reinitialised
> >it prefectly.
> 
On Thu, Sep 23, 2004 at 05:14:31PM -0400, James wrote:
> OK, This if for setting up the dialin(host) serial port and modem I 
> presume?
> 
> What, if anyting do I need to apt-get for the host?
> 
> And you used wvdial on the other system to effect the dialout(user pc) 
> part of the ppp with just a standard /etc/wvdial.conf file?
> 
> apt-get wvdial (on the user's pc) and edit wvdial.conf, is all that is 
> needed?
> 
> If I understand your missing parts?
> 
> James
> 
Correct. This setup was for the dial-in host.

Unfortunately the dial-in clients are windows. This shouldn't make much
difference though.

On the host:

apt-get install ppp (this is almost certainly already installed)
apt-get install mgetty mgetty-docs

On the client:

apt-get install wvdial

If you need to adjust wvdial.conf I expect it to be minimally as the
installation prompts you for most things. 

John