[rancid] Dell PowerConnect 5316M device archival in 2.3.3

[Eric Cables]

After a quick search through the archives, I came across this link (
http://www.rickyninja.net/rancid/), which quickly allowed me to archive a
couple Dell PowerConnect switches that I inherited. I am currently running
2.3.2, but after checking the latest 2.3.3 tarball it doesn't appear to have
native Dell integration. This also makes me wonder if the other changes
I've made over the years through community based patches (SAN-OS support,
for example) will be supported once moving to 2.3.3 (once it is officially
released).

Is it possible to add in the dlogin/drancid/fe-rancid updates found in the
above into the 2.3.3 release? Are other community based patches generally
incorporated into the next release, or is that not common practice?

Thanks,

-- Eric Cables

[john heasley]

Post by Eric Cables
After a quick search through the archives, I came across this link (
http://www.rickyninja.net/rancid/), which quickly allowed me to archive a
couple Dell PowerConnect switches that I inherited. I am currently running
2.3.2, but after checking the latest 2.3.3 tarball it doesn't appear to have
native Dell integration. This also makes me wonder if the other changes
I've made over the years through community based patches (SAN-OS support,
for example) will be supported once moving to 2.3.3 (once it is officially
released).
Is it possible to add in the dlogin/drancid/fe-rancid updates found in the
above into the 2.3.3 release? Are other community based patches generally
incorporated into the next release, or is that not common practice?

I won't import patches or new modules that I can't verify somehow because
they become support burdens for me - only occasionally is a contributed
module 95%+ functional and if i dont have that h/w myself, its really
difficult to help with problems. riverstone and netscreen for example.
nothing against their authors; consider my side of it.

someone else, you, verifying that the module works is great. I'd like to
see o/p and .raw files from a few folks, w/o stuff removed (change things
like password crypts to something similar but equal syntax), to help
ensure everything is covered. then try to make sure that error cases are
handled. please share your o/p.

i'm happy to make an unsupported section of the ftpsite for unproven
modules, if folks would like to send them to me.

[Eric Cables]

An unsupported, or "use at your own risk," modules section on the FTP site
would certainly make finding these easier, and allow for a central
repository that will remain up as long as RANCID is supported. As it stands
now they are hosted on various FTP/Web servers, which will probably be
broken links as time goes by.

-- Eric Cables

Post by Eric Cables

Post by Eric Cables
After a quick search through the archives, I came across this link (
http://www.rickyninja.net/rancid/), which quickly allowed me to archive

a

Post by Eric Cables
couple Dell PowerConnect switches that I inherited. I am currently

running

Post by Eric Cables
2.3.2, but after checking the latest 2.3.3 tarball it doesn't appear to

have

Post by Eric Cables
native Dell integration. This also makes me wonder if the other changes
I've made over the years through community based patches (SAN-OS support,
for example) will be supported once moving to 2.3.3 (once it is

officially

Post by Eric Cables
released).
Is it possible to add in the dlogin/drancid/fe-rancid updates found in

the

Post by Eric Cables
above into the 2.3.3 release? Are other community based patches

generally

Post by Eric Cables
incorporated into the next release, or is that not common practice?

I won't import patches or new modules that I can't verify somehow because
they become support burdens for me - only occasionally is a contributed
module 95%+ functional and if i dont have that h/w myself, its really
difficult to help with problems. riverstone and netscreen for example.
nothing against their authors; consider my side of it.
someone else, you, verifying that the module works is great. I'd like to
see o/p and .raw files from a few folks, w/o stuff removed (change things
like password crypts to something similar but equal syntax), to help
ensure everything is covered. then try to make sure that error cases are
handled. please share your o/p.
i'm happy to make an unsupported section of the ftpsite for unproven
modules, if folks would like to send them to me.