Re: [e-smith-devinfo] procmail ofr dummies
On Fri, 12 Oct 2001, Graeme Robinson wrote: > On Thu, 11 Oct 2001, Charlie Brady wrote: > > Indeed, this seems quite reasonable behaviour. As Stephen said, "uses the > > user-panel add-on". Hence, you should first install e-smith-userpanel. > > well yes, but what is it and where do I install it? There's no instruction > in readme-procmail.html and no evidence of an rpm in Stephens' contrib > area. If only grep worked over ftp :-) Daniel's I believe. It's our fault really, we should keep the contrib index up to date, but we don't (yet). Just not enough hours in the day (yet) :-) Charlie Brady [EMAIL PROTECTED] Lead Product Developer Network Server Solutions Grouphttp://www.e-smith.com/ Mitel Networks Corporationhttp://www.mitel.com/ Phone: +1 (613) 368 4376 or 564 8000 Fax: +1 (613) 564 7739 -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
Re: [e-smith-devinfo] procmail ofr dummies
On Thu, 11 Oct 2001, Charlie Brady wrote: > Indeed, this seems quite reasonable behaviour. As Stephen said, "uses the > user-panel add-on". Hence, you should first install e-smith-userpanel. well yes, but what is it and where do I install it? There's no instruction in readme-procmail.html and no evidence of an rpm in Stephens' contrib area. If only grep worked over ftp :-) -=-=-==-=-=--=-=-=-=-=-=-=-=-=-=-=-= Graeme Robinson - Graenet consulting www.graenet.com - internet solutions -=-=-=-=-=-=-=-=-=-=-==---=-=--=-=-= -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
Re: [e-smith-devinfo] procmail ofr dummies
On Fri, 12 Oct 2001, Graeme Robinson wrote: > On Fri, 12 Oct 2001, stephen noble wrote: > > > ftp://ftp.e-smith.org/pub/e-smith/contrib/StephenNoble/RPMS/noarch/ > > readme-procmail.html > > > > > > uses the user-panel addon to help ordinary users to configure > > procmail and make rules via a web form > > Stephen - I get a dependency error: > bash-2.04$ sudo rpm -Uvh \ > /home/e-smith/files/ibays/applications/files/\ > installs/contribs/procmail/e-smith-procmail-0.1-5.noarch.rpm > error: failed dependencies: e-smith-userpanel is needed by e-smith-procmail-0.1-5 Indeed, this seems quite reasonable behaviour. As Stephen said, "uses the user-panel add-on". Hence, you should first install e-smith-userpanel. Charlie Brady [EMAIL PROTECTED] Lead Product Developer Network Server Solutions Grouphttp://www.e-smith.com/ Mitel Networks Corporationhttp://www.mitel.com/ Phone: +1 (613) 368 4376 or 564 8000 Fax: +1 (613) 564 7739 -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
Re: [e-smith-devinfo] procmail ofr dummies
On Fri, 12 Oct 2001, stephen noble wrote: > ftp://ftp.e-smith.org/pub/e-smith/contrib/StephenNoble/RPMS/noarch/ > readme-procmail.html > > > uses the user-panel addon to help ordinary users to configure > procmail and make rules via a web form Stephen - I get a dependency error: bash-2.04$ sudo rpm -Uvh /home/e-smith/files/ibays/applications/files/installs/contribs/procmail/e-smith-procmail-0.1-5.noarch.rpm error: failed dependencies: e-smith-userpanel is needed by e-smith-procmail-0.1-5 -=-=-==-=-=--=-=-=-=-=-=-=-=-=-=-=-= Graeme Robinson - Graenet consulting www.graenet.com - internet solutions -=-=-=-=-=-=-=-=-=-=-==---=-=--=-=-= -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
[e-smith-devinfo] procmail ofr dummies
ftp://ftp.e-smith.org/pub/e-smith/contrib/StephenNoble/RPMS/noarch/ readme-procmail.html uses the user-panel addon to help ordinary users to configure procmail and make rules via a web form suggestions for more rules in can include are welcome such as auto-responder / vacation as per d.may howto thanks charlie / greg for the perl lesson regards stephen -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
[e-smith-devinfo] custom iso/cdrom [was Re: [e-smith-devinfo] blades and SMEServer updates]
Lionel <[EMAIL PROTECTED]> said: > Would you care to pass on any tips on how to build SME 5.0 + updates > onto a CDROM? Having a definitive CDROM would be very useful to me. Thanks for the interest however for various reasons I will not be releasing this information or releasing updated iso images public. This is a service I offer. If you are interested in having a custom iso/cd built, please e-mail your requirements to me directly. I've yet to receive a request for SME 5.0 + updates only. Requests I do receive typically start with SME 5.0 + updates and then a much larger additional wish list follows. I'm happy to build a custom iso/cd to meet your exact needs. Regards, -- Darrell May DMC NETSOURCED.COM http://netsourced.com http://myEZserver.com -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
Re: [e-smith-devinfo] blades and SMEServer updates
On Thu, 11 Oct 2001 16:04:38 -, Darrell May <[EMAIL PROTECTED]> wrote: >10) The above blades may be added and a custom iso built (difficult but >I've done this) that installs an up to date, ready to go SME Server >at install. I've been too busy to follow any list traffic for a little while, so I'm not up to date on the SME version of the E-Smith server. So I apologise in advance if I'm asking any dumb questions. Would you care to pass on any tips on how to build SME 5.0 + updates onto a CDROM? Having a definitive CDROM would be very useful to me. -- W . | ,. w , "Some people are alive only because \|/ \|/ it is illegal to kill them."Perna condita delenda est ---^^--- -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
RE: [e-smith-devinfo] Re: Comments in generated config
On Thu, 11 Oct 2001, Smith, Jeffery S (Scott) wrote: > Perhaps another "feature" needed is a template editor. Rather than having to > create the path in templates-custom, copy over the template, etc, it would > be a relatively simple matter to create a perl script to automate this. I'm guessing you envisage this editor as a 'create a custom template/fragment' web-manager plugin as there are lots of unix editors capable of being programmed with macros in the ways you suggest already I believe - emacs, vi ... My instinct is that anyone capable of understanding clearly what needs to be done in template customisation would find it easier and faster to direct edit. And there is the potential to create a mess if such an editor is accessable by someone who doesn't know what they're doing. But that's not really an excuse not to develop it - the real test is how useful it would be and it seems to me your idea at least has the potential to make life easier for the e-smith developer/integrator, making the templating system a little more transparent to function. -=-=-==-=-=--=-=-=-=-=-=-=-=-=-=-=-= Graeme Robinson - Graenet consulting www.graenet.com - internet solutions -=-=-=-=-=-=-=-=-=-=-==---=-=--=-=-= -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
RE: [e-smith-devinfo] Re: Comments in generated config
> -Original Message- > From: Darrell May [mailto:[EMAIL PROTECTED]] > Sent: Thursday, October 11, 2001 1:29 PM > Subject: RE: [e-smith-devinfo] Re: Comments in generated config > > /sbin/e-smith/modify-template templatepath > > Just so I understand, templatepath would be the actual file > name right? Yes, as in your example: ./modify-template /etc/smb.conf So the path is the final location of the configuration file, or relative to /etc/e-smith/templates if you prefer to think of it that way. The fragmentname would be just that. For example: ./modify-template -f 10globals /etc/smb.conf Or, and I somewhat prefer this syntax: ./modify-template /etc/smb.conf:10globals Or to make the perlites fall in love: ./modify-template /etc/smb.conf::10globals :-) > I think this is a great idea Scott. thanks > The perl script could even start with a menu. > > Modify Template Options: > > V - View template output > D - Display with comments and fragment names visable > E - Edit fragment > A - Add fragment > S - Search template > L - Load changes I think if you want to make a fully menu driven mode, the first task should be to select a template (configuration file), and then provide the options above which are relative to a specific template. Also, the selection of templates might include the search option as well, in order to present a list of templates containing specified string in any fragment. Since we're dreaming here, another useful option might be tacked onto the "Load changes" option you suggest. I'm assuming load changes would perform an expand-template. Sometimes that is enough, but often what is really needed is a signal-event. If there were a database that listed templates and the events (or actions?) that should be executed whenever the template is updated, then load changes would be truly effective. Otherwise, I think expand-template is not enough. > So who's the perl wizard that will create this? Not my forte yet, unfortunately. I'm groping my way through perl, but am nowhere near being able to do such a thing in any kind of reasonable timeframe. Though it would be a good learning project ;-) I'm sure the good folks at Mitel are quite capable, but I think they have their hands full with other tasks at the moment. Volunteers? Scott -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
RE: [e-smith-devinfo] Re: Comments in generated config
"Smith, Jeffery S (Scott)" <[EMAIL PROTECTED]> said: > /sbin/e-smith/modify-template templatepath Just so I understand, templatepath would be the actual file name right? /sbin/e-smith/modify-template /etc/smb.conf I think this is a great idea Scott. The perl script could even start with a menu. Modify Template Options: V - View template output D - Display with comments and fragment names visable E - Edit fragment A - Add fragment S - Search template L - Load changes So who's the perl wizard that will create this? -- Darrell May DMC NETSOURCED.COM http://netsourced.com http://myEZserver.com -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
Re: [e-smith-devinfo] blades and SMEServer updates
Darrell, > Also, is a 'How To Build a Blade' document coming? Yep... we're working on it. Soon... Dan -- Dan York, Director of Training, Network Server Solutions Group Mitel Networks Corporation [EMAIL PROTECTED] Ph: +1-613-751-4401 Cell: +1-613-263-4312 Fax: +1-613-564-7739 150 Metcalfe Street, Suite 1500, Ottawa,ON K2P 1P1 Canada http://www.e-smith.com/ http://www.mitel.com/sme/ -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
RE: [e-smith-devinfo] Re: Comments in generated config
Perhaps another "feature" needed is a template editor. Rather than having to create the path in templates-custom, copy over the template, etc, it would be a relatively simple matter to create a perl script to automate this. /sbin/e-smith/modify-template templatepath This script could present a list of the available template fragments, from which the user would select one, and then load the fragment into vi or pico. After editing, if the saved file is different than the original, the fragment would automatically be placed into templates-custom. Exit logic could either return to the prompt, or return to the fragment list. The editor would of course need to check for existing custom templates -- basically the same logic that goes into selecting files for template expansion. Edit the custom template if it exists, else load the default and save to custom. Also display any new fragments from custom. For editing a specific fragment, a special syntax for templatepath: templatepath:fragmentname Or an alternate syntax: /modify-template -f fragmentname templatepath Another option would be to provide a grep filter in the editor: ./modify-template -s "searchstring" templatepath This would present a list of only those fragments containing the specified searchstring. Note that the -f option would not apply here. Lastly, some options to check what type a template (or fragment) is, and to restore a template (or fragment) to the default state. Display all fragments (or the specified fragment) and indicate if it is the default or custom: ./modify-template -t [-f fragmentname] templatepath Delete the specified template or fragment: ./modify-template -d [-f fragmentname] templatepath Some more search options. A -a to search all fragments in a directory, and a -r to search recusively: ./modify-template -a -r -s "searchstring" pathname Note that pathname in this case would be interpreted relative to /etc/e-smith/templates. Oh, and I suppose an option to create a new template: ./modify-template -n fragmentname templatepath And one to "copy" one from an existing fragment: ./modify-template -c sourcepath:fragment targetpath:fragment This modify-template editor interface would eliminate the primary need for comments in the output (ie, finding the fragment that generates the output) and would simplify the process of editing fragments (not really necessary to understand the templates / templates-custom structure.) Comments? Scott -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
Re: [e-smith-devinfo] Re: Comments in generated config
Dan Brown <[EMAIL PROTECTED]> said: > You might be right on this, Darrell, but I don't think a user who > doesn't grok grep is very likely to go tinkering with templates > either. Point taken. I agree templates are best left for the experts. But in my example, if comments are not found in the templated files the user is more likely to change smb.conf directly following the 'expert' advice of their database software support tech. We all know where that will lead. Cheers, -- Darrell May DMC NETSOURCED.COM http://netsourced.com http://myEZserver.com -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
[e-smith-devinfo] blades and SMEServer updates
I'd like to relate my experience with blades and see if I am missing anything. Ok, here goes: 1) blades get downloaded into /var/cache/e-smith/blades/packages 2) blades are rpms that checks for depencies 3) blades are installed like any other rpm 4) blades are identified as being installed just like rpms 5) blades do not have to be downloaded via the server-manager Blades panel. You can get them via ftp to e-smith.org directly. 6) blades may be copied and installed to servers just like you are installing a standard rpm. 7) blades once installed do not have to be saved or placed in /var/cache/e-smith/blades/packages 8) blades installed manually correctly show up in the server-manager Blades panel as being installed. 9) blades do not have to be installed release 1 then release 2. For instance, here are the current update blades: SMEServer-5.0_Update1-04.noarch.rpm SMEServer-5.0_Update2-07.noarch.rpm e-smith-base-4.6.1-09.noarch.rpm e-smith-base-4.6.1-17.noarch.rpm e-smith-blades-1.0.0-19.noarch.rpm e-smith-email-4.6.1-05.noarch.rpm e-smith-lib-1.6.0-11.noarch.rpm e-smith-mod_ssl-1.8.0-05.noarch.rpm e-smith-release-5.0-03.noarch.rpm e-smith-release-5.0-04.noarch.rpm imap-4.7-1mdir8es.i386.rpm obtuse-smtpd-2.0-29.i386.rpm Yet you do not have to install all of these. Just like standard rpms you only need to install the most current releases to bring yourself up to date: e-smith-base-4.6.1-17.noarch.rpm e-smith-blades-1.0.0-19.noarch.rpm e-smith-email-4.6.1-05.noarch.rpm e-smith-lib-1.6.0-11.noarch.rpm e-smith-mod_ssl-1.8.0-05.noarch.rpm e-smith-release-5.0-04.noarch.rpm imap-4.7-1mdir8es.i386.rpm obtuse-smtpd-2.0-29.i386.rpm SMEServer-5.0_Update2-07.noarch.rpm 10) The above blades may be added and a custom iso built (difficult but I've done this) that installs an up to date, ready to go SME Server at install. This is from my own testing and experience. Did I get anything incorrect or am I missing any crucial blade issue? Also, is a 'How To Build a Blade' document coming? -- Darrell May DMC NETSOURCED.COM http://netsourced.com http://myEZserver.com -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
Re: [e-smith-devinfo] Re: Comments in generated config
Quoting Darrell May <[EMAIL PROTECTED]>: > The key thing to remember is your customers knowledge. The average > Mitel user will not know the grep command exists. You might be right on this, Darrell, but I don't think a user who doesn't grok grep is very likely to go tinkering with templates either. I don't have a problem with including the names of the template fragments in the fragments themselves, and agree it could save a little bit of time, but I don't think it'd make much of a positive impact. -- Dan Brown, KE6MKS, [EMAIL PROTECTED] "Since all the world is but a story, it were well for thee to choose the more enduring story rather than the story that is less enduring." -- The Judgment of St. Colum Cille -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
Re: [e-smith-devinfo] Re: Comments in generated config
Charlie Brady <[EMAIL PROTECTED]> said: > No. You didn't have to be nasty. You could have dealt with the issues we > raised. My apologizes Charlie and Gordon. Let's deal with the issues raised... > As Daniel pointed out, there will be some files for which '#' > prefixed lines are not treated as comments. So we could then simply 'identify' which files this is an issue with and not comment these files or comment in the files acceptable syntax. > I don't know whether the "proposed standard" was intended to be > automated, or to be a de facto standard applied by the author of each > template fragment. Again, if we identify what files have an issue it could be either way. Automated would take some work on Mitel's end. Maybe you are moving in this direction. Authored would leave the work to the author of course. An identified and posted list of files and their appropriate comments syntax would solve this issue. File | Comment Syntax smb.conf | # ; httpd.conf | # file_to_be_named | no comments permitted The key thing to remember is your customers knowledge. The average Mitel user will not know the grep command exists. An example issue for your clients is they call a software vendor for support. Their database isn't working right. The software vendors determines they have an incorrect setting in smb.conf. The support tells them to set 'strict locking = no'. The client looks at smb.conf and sees the VERY important comment at the top that this is a templated file. (You are not planning on removing this comment are you?) They read through the file and find strict locking set to yes. They see immediately, from the commented fragment title that this is set in the [11strictLocking] fragment. They now know what to change, where it is set and with a little more digging on e- smith.org will figure out how to change a template fragment correctly. One less support call for us. One happy customer feeling good that he/she has solved their database problem and now has an understanding of template fragments. Regards, -- Darrell May DMC NETSOURCED.COM http://netsourced.com http://myEZserver.com -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
Re: [e-smith-devinfo] When does console content get regenerated?
Brad Hards <[EMAIL PROTECTED]> said: > G'day all, > > I recently got a Winbond 840 based card working with e-smith 4.1.2, I have a 'somewhat' similar HowTo: http://myezserver.com/docs/mitel/nic-drivers-howto.html In addition, I think your steps would be to run the console config and manually choose any nic card you want to perform the initial IP setup. Then copy the winbond-840.o into /lib/modules/x.x.x-x/net/ via floppy or CD. /sbin/e-smith/config set EthernetDriver1 winbond-840 /sbin/e-smith/signal-event console-save /sbin/ifconfig eth0 up If you wanted to go really fancy you could build an rpm that installs the driver and issues the above commands. I'd be interested to know if this works for you. Regards, -- Darrell May DMC NETSOURCED.COM http://netsourced.com http://myEZserver.com -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
Re: [e-smith-devinfo] Re: Comments in generated config
On Thu, 11 Oct 2001, Darrell May wrote: > Sorry for being nasty but I just had to ;-> No. You didn't have to be nasty. You could have dealt with the issues we raised. As Daniel pointed out, there will be some files for which '#' prefixed lines are not treated as comments. In fact, there are some templated configuration files for which there is no valid comment syntax. Any automated addition of fragment name would need to be aware of these issues. I don't know whether the "proposed standard" was intended to be automated, or to be a de facto standard applied by the author of each template fragment. If the latter, I'd advise against it. In my experience, incorrect comments are usually worse than no comments at all. And I've seen very few projects where comments are always updated when they should be. Charlie Brady [EMAIL PROTECTED] Lead Product Developer Network Server Solutions Grouphttp://www.e-smith.com/ Mitel Networks Corporationhttp://www.mitel.com/ Phone: +1 (613) 368 4376 or 564 8000 Fax: +1 (613) 564 7739 -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
Re: [e-smith-devinfo] root / shell access
Hi Joost_De_Raeymaeker! On Thu, 11 Oct 2001, [EMAIL PROTECTED] wrote: PuTTY even has tunneling in the latest development snapshot > The only reason I use something else besides PUTTY is if I want to do > tunneling. Putty is great and doesn't have all the quircks with keys not > working the way they usually do. > > Joost > > > > > Rob Hillis <[EMAIL PROTECTED]> > 11-10-2001 14:18 > > > To: <[EMAIL PROTECTED]> > cc: > Subject:Re: [e-smith-devinfo] root / shell access > > > On Thu, 11 Oct 2001 03:09, John Powell wrote: > > > Personally, I can't see much reason to go past PuTTY... it's a small, > single > file (unusual for a Windows program) which does a better terminal > emulation > job than any other SSH client that I've tried... > > -- > Please report bugs to [EMAIL PROTECTED] > Please mail [EMAIL PROTECTED] (only) to discuss security issues > Support for registered customers and partners to [EMAIL PROTECTED] > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org > > > > > > -- > Please report bugs to [EMAIL PROTECTED] > Please mail [EMAIL PROTECTED] (only) to discuss security issues > Support for registered customers and partners to [EMAIL PROTECTED] > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
Re: [e-smith-devinfo] root / shell access
The only reason I use something else besides PUTTY is if I want to do tunneling. Putty is great and doesn't have all the quircks with keys not working the way they usually do. Joost Rob Hillis <[EMAIL PROTECTED]> 11-10-2001 14:18 To: <[EMAIL PROTECTED]> cc: Subject:Re: [e-smith-devinfo] root / shell access On Thu, 11 Oct 2001 03:09, John Powell wrote: Personally, I can't see much reason to go past PuTTY... it's a small, single file (unusual for a Windows program) which does a better terminal emulation job than any other SSH client that I've tried... -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
Re: [e-smith-devinfo] root / shell access
On Thu, 11 Oct 2001 03:09, John Powell wrote: > As far as SSH clients. I use SecureCRT when coming in from a Windows box. > I love it. Others have high praise for Putty, haven't used it personally > though. I am not sure what super-advanced Telnet clients you are referring > to, but I find it hard to grasp what they have over SecureCRT and other > solid SSH clients. Personally, I can't see much reason to go past PuTTY... it's a small, single file (unusual for a Windows program) which does a better terminal emulation job than any other SSH client that I've tried... -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
[e-smith-devinfo] When does console content get regenerated?
G'day all, I recently got a Winbond 840 based card working with e-smith 4.1.2, and have made some notes that I would like to turn into a HOWTO eventually. Basically I added the driver to the modules directory and edited the pcitable file. I didn't expect to have to reboot twice though. Can someone explain when the list of ethernet drivers in the console gets regenerated, and if there is an easier way to get it updated than rebooting? Brad --- Introduction I recently bought a TRENDnet TW100-S4PCI four port switch card. For those not familiar with the hardware, it is a PCI card with a five port switch built into it. One of the switch ports is connected to a Winbond W89C840 10/100Mbps ethernet chip, and the other four ports are available on the outside of the PCI card. Probably a pretty useful card for a small office setup. The outside of the box says "Compatible with Major Network Operating Systems", so I knew it'd be supported by Linux :-) Problem Statement The switch functionality worked fine. Unfortunately the Winbond W89C840 PCI ethernet adapter wasn't recognised by e-smith 4.1.2 (nor with 5.0, but I wanted to stick with 4.1.2 in any case). Fix 1. Download the drivers from Trendnet's web site (http://www.trendware.com/downloads/_downloads.htm, and work through the dialogs). Extract the zip file. 2. The file you need is called winbond-840.o. Copy it into /lib/modules/2.2.16-22/net/ on the e-smith server. 3. Open /usr/share/kudzu/pcitable, and scroll down until you find the line with vendor ID 0x1050 and product ID 0x0840 (they are the first two columns). You should see a description of the card on the right hand side. Change the "unknown" to "winbond-840". 4. Reboot 5. Run through the console configuration, and you should be given the option of selecting this card. Obviously you need to select it at this point. 6. You will need to reboot again. 7. You now have network connectivity on that card :) Caveats and Limitations A. This probably only works with uP. B. You would probably need to find another source of the driver to make it work on e-smith 5.0, although a simple recompile of the source code (winbond-840.c) provided in the TRENDnet download would be enough. Questions or Feedback Contact Brad Hards ([EMAIL PROTECTED]) with any questions or suggestions on this HOWTO. -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
