Search results for "meeting" - WLUG

Re: [Wlug] next week's installfest

by Mike Peckar

Hey Andy, I read with interest about your installfest on the listserve (I pile up emails and pour through infrequently) and I'm sorry I missed it - I find myself in need of an upgrade on one of my boxes. I saw you have many copies of several recent distributions - I am looking to get a copy of redhat 7.1 - got any left over from last week? I'd love get a set... TIA, and one of these days I'd love to actually catch a meeting.. Mike ----- Original Message ----- From: Andy Stewart <andystewart(a)mediaone.net> To: <wlug(a)mail.wlug.org> Sent: Monday, October 01, 2001 6:45 PM Subject: Re: [Wlug] next week's installfest > > HI Tim, > > This sounds really great - thanks! If you can get the KDE 2.2.1 rpms, > that might be something to put onthe "others" CD. > > Andy > > > On Monday 01 October 2001 08:39 am, you wrote: > > This is what I plan on bringing. > > > > 1. 5 sets of Redhat 7.1 > > 2. 5 sets of Debian 2.2rev3 > > 3. 10 cd's with the following.. > > a. latest kernel/modtools (2.4.10) > > b. StarOffice > > c. latest mozilla benchmark (0.9.4) > > > > If anybody has some input on what else I should put on the "others" cd, > > let me know. > > > > Tim. > > > > -----Original Message----- > > From: David Lee Ludwig [mailto:davidl@WPI.EDU] > > Sent: Saturday, September 29, 2001 1:05 AM > > To: 'wlug(a)mail.wlug.org' > > Subject: RE: [Wlug] next week's installfest > > > > On Fri, 28 Sep 2001, Keller, Tim wrote: > > > What you might want todo is just grab everything; debs, rpms and > > > tarballs. > > > > > > That way, not matter what distribution we load, we'd be able to > > > install. > > > > I was planning on grabbing as much as I can, however each > > version of each distribution has a different set of Ximian Gnome > > packages that run around 225MB a piece. > > > > What CDs do people plan on bringing? > > -- > Andy Stewart > Founder > Worcester Linux Users' Group > Worcester, MA, USA > http://www.wlug.org > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

24 years, 2 months

Re: [Wlug] Any idea where to find a job?

by John Stoffel

Jason> If anyone knows of any entry level it oppurtunities in the Jason> area, it would be much appreciated. I have 0 certifications but Jason> I can more than prove myself. I've been stuck in retail for a Jason> few years now and id like to escape it. If anyone knows of any Jason> positions, please let me know. :-) Get your name known out in the wilder world by learning something well (Linux software RAID) and helping out others. Spend the time to learn new things on your own time. Network, network, network. Talk to people, ask about jobs, maybe think about working in a retail computer type job if you can find one. Check monster.com, dice.com, lopsa.org, sage.org and other sites like that for job leads. Check your local colleges, non-profits, high schools, etc. Look for opportunities anywhere you can. Volunteer somewhere doing IT work, even if it's just entering data at first, show a willingness to learn and take on tasks. It also depends on your educational background to a degree. If you have a college degree, talk to your alma mater and see what resources they have you can use. If you haven't done college, or didn't complete it, look into doing so. It's a springboard. Post on facebook that you're looking, join linked-in.com, get the word out you're looking. I personally don't think certifications are worth much, but it can show that you can learn. Look in the paper for waht IT, networking, programming positions are out there, and think about how you can improve you skill set to meet those needs. IT is in a tough spot right now. You might need to actually move to where the jobs are. If you are flexible and willing to move, maybe there's someone like spacex.com looking for a tech out on a pacific island somewhere. Maybe you could get that? I'm just tossing off ideas, but it's upto you to show them that you know your stuff, and that when you *don't* know, you can learn. Being able to learn quickly and on your own is the single best skill you can bring to any employer. Show them that you have this skill. John And no, my $WORK doesn't have any openings right now. Sorry. Hmm... check redhat's website too, I think they were hiing in their westford office recently.

14 years, 11 months

Re: Spectrum, Recursive dns and interception of root authoritative DNS

by Tim Keller

I've long since decided to avoid using my ISP's dns and went to running PiHole with the upstream dns being 8.8.8.8 and 1.1.1.1 Tim. On Sun, Aug 24, 2025, 12:01 PM steve--- via WLUG <wlug(a)lists.wlug.org> wrote: > Hey all. I was wondering since were all? Worcester or surrounding and > dealing with Spectrum as an ISP, if you’ve run into the same thing I have > in the last few months. > > > I used to, as you’ll see soon, run unbound as a recursive DNS server in my > home network to cache and limit external DNS queries that was the forwarder > behind Pihole. It worked great for a very long time. > > > But a few months ago, my internet went down, and It turned out to be non > cached dns queries starting to fail. I realized in logs that unbound was > getting errors reaching out to dns servers and disabled it until I could > investigate instead forwarding to cloud flare temporarily. > > Now that I have had time to research and investigate, I have found that at > least SOMETHING is intercepting my my queries to authoritative DNS servers > when I reset unbound and it throw’s away the response because they aren’t > “AA” status responses and it never caches the root dns and therefor won’t > resolve anything. > > I come to find out the “authoritative” servers are responding with a > status of RA which means it’s not the actual authoritative service when I > query manually, dig @198.41.0.4 . NS +norecurse an actual authoritative, > and that this is most likely a change Spectrum has made. Has anybody else > ran into this? Is it actually Spectrum. I guess I haven’t dug far enough > yet to see if its may be a firmware update to my router, UDM PRO yet. Still > working on that, but though I’d ask this group first before I dig into that > and save myself the time and go straight to ISP workarounds. > > Thanks in advance! Looking forward to our next meeting!! > > Steve > _______________________________________________ > WLUG mailing list -- wlug(a)lists.wlug.org > To unsubscribe send an email to wlug-leave(a)lists.wlug.org > Create Account: https://wlug.mailman3.com/accounts/signup/ > Change Settings: > https://wlug.mailman3.com/postorius/lists/wlug.lists.wlug.org/ > Web Forum/Archive: > https://wlug.mailman3.com/hyperkitty/list/wlug@lists.wlug.org/message/5AWI2… >

3 months, 3 weeks

Re: DECStation 3100 on a RPi2040...

by Kevin Stratton

I found this information interesting. The statement "To save a couple of pennies per system the > VAX hardware designers determined that having full hardware modem > control (DECstandard 52) on the board was not needed, because "very > few workstation users hook a modem up to their serial line". has two different meanings (to me) in the context of this discussion. They are: 1) RI and DCD are not implemented in hardware (Ring indicator and data carrier detect) 2) A subset of RTS, CTS, DSR, DTR as well as RI and DCD are not implemented in hardware. Does anyone want to clarify this in greater detail? Just curious. On 7/6/2024 8:59 PM, Jon "maddog" Hall via WLUG wrote: > John: > > That's an interesting statement. I would think it was the same case > and port setup, but a different motherboard since you couldn't just > slot a MIPS processor into a VAXstation processor. > > > That is why I said "based". "Based" means that you did not have to > requalify a lot of the parts, that you could use a lot of the same > Bill of Materials....it does not mean you use exactly the same PCB. > In the case of the VAXstation/DECstation 3100 that meant we used the > same serial io chips and did not provide the hardware flow control. > > Yes! It's coming back to me, the 3100s were horrible for serial, > though I think they had fixed it for the 5000 series systems, since > the DECstation 5000 and the DECserver 5100 were identical, except the > DECStation had a graphics card and cost 10-20% _less_ than the > DECstation 5000. So we bought DECStations and used them as servers. > > > The server groups were different engineers, and the 5000s were > designed after the DECstation 3100/2100 series. > > Actually we MIGHT have caught the issue with the serial port for the > DECstation 3100/2100 because I brought up the issue in a hardware > meeting and was assured that it had been fixed because (and I can > still hear this person's voice in my head) the DECstation was a REAL > UNIX MACHINE. I should have found that person later and beaten him > to death. > > David: > > Actually, Cutler was already in trouble with management because of > the Prism project. Prism was the first try at building a RISC > machine (this was in the 1985-1986 time frame) and it was managed > by Dave Cutler. Unfortunately, Dave was not a good administrator. > He was doing a very bad job of managing the project and doing a > very bad job of keeping management up to date on what was going > on. Finally, management cancelled Prism and that is when they > decided to go with the MIPS architecture. > > That is not what I experienced. I will not comment on Dave's skills > as an administrator or manager of the project. I do know that he had > the very ambitious project of doing the next-generation architecture > and the next generation operating system. He wanted a micro-kernel > based system with "personalities", one personality being VMS and the > other personality being Unix. One issue he had was when there was a > clash between personalities he would always favor VMS and therefore > the Unix personality would not be "perfect". I felt this was a > mistake, since Unix people did not tolerate things that did not smell > like Unix. VMS people could have been led over to a new environment > over time since DEC controlled the path with VMS. > > The reason I know this is that I personally interviewed with David > Cutler for the position of Unix Product Manager for his new operating > system. The interview was going fine until I tried to explain to > Dave why his strategy was wrong and he had to make the Unix side > really compatible. Then things got ugly, as David really did not like > to be told he was wrong. > > Ken did have the bad habit of cutting off Dave's development money, > then giving it back to him again. I seem to remember that Dave was > still going full steam ahead while the PMAX was being developed, which > is one reason why he was caught so flat-footed when PMAX was > announced. It was kept REALLY SECRET. It probably did not help > that Ken reportedly asked David in a gleeful tone if the new chip > would be as fast as the PMAX.... > > "Will it be THIS FAST, Dave?" was the reported question. > > It is also my belief that the Alpha chip came directly from Dave's > work on the PRISM, and that Windows NT came directly from David's work > on the microkernel with personalities. DEC never "decided to go > with MIPS" except as a stop-gap measure for Unix. If DEC had > "decided to go with MIPS" they would have ported VMS to it, and since > that never happened, it was obvious that DEC had not embraced MIPS. > > md > > > On Sat, Jul 6, 2024 at 3:27 PM John Stoffel <john(a)stoffel.org> wrote: > > >>>>> "Jon" == Jon \"maddog\" Hall via WLUG <wlug(a)lists.wlug.org> > writes: > > > The DECstation 3100 (aka the PMAX) was a system based on the same > > motherboard as the VAXstation 3100, except with a MIPS processor. > > It was the first time that Digital had built a system using another > > company's chip architecture. > > That's an interesting statement. I would think it was the same case > and port setup, but a different motherboard since you couldn't just > slot a MIPS processor into a VAXstation processor. > > > We had a choice between supporting the MIPS R2000 chip as "big > > endian" or "little endian". We chose to support "little endian" to > > be compatible with PDP-11s, VAXen and Intel chips, rather than be > > compatible with other manufacturers. This, in my mind, was very > > important since it let us share data over NFS and give greater > > compatibility with programs and libraries of applications already > > running on other Unix-like systems such as Ultrix, BSD, etc. Sun > > experienced this grief when they ported Solaris off the big endian > > Motorola and SPARC chips to little endian Intel. > > > One of the few issues of the DECstation 3100 (and 2100, known as the > > "PMIN" after that) was that the serial I/O port did not support > > hardware handshaking. To save a couple of pennies per system the > > VAX hardware designers determined that having full hardware modem > > control (DECstandard 52) on the board was not needed, because "very > > few workstation users hook a modem up to their serial line". What > > they meant was that "very few VMS workstation users hooked a modem > > up to their serial line", opting for DECnet to handle their > > networking. Therefore the pins necessary to support hardware modem > > control were missing from the DECstation product lines. > > Yes! It's coming back to me, the 3100s were horrible for serial, > though I think they had fixed it for the 5000 series systems, since > the DECstation 5000 and the DECserver 5100 were identical, except the > DECStation had a graphics card and cost 10-20% _less_ than the > DECstation 5000. So we bought DECStations and used them as servers. > :-) > > I used to live and breathe the DEC options catalog, which was > something like an inch thick book in purple (maybe blue? maybe changed > each year?) with all the various options and configurations you could > get. > > > Unix users, on the other hand, often had modems hooked up to their > > workstation, to handle cu(1), uucp(1) and other serial line > > protocols. We eventually got around this by better refining > > software modem control, but it was painful. > > The EE department had Sun 1s at WPI, and they have the 9600 baud > bitnet connection running of a VAX 11/780 at the time. > > > The proposal, design and release of the DECstation 3100 was a > > top-secret project inside of DEC, kept secret from even many people > > in the Digital Unix group in Nashua, New Hampshire. The > > development of the system was done in Palo Alto's WorkStation > > Engineering group and the software engineering was done in the > > Western Software Labs in Palo Alto, albeit by taking key engineers > > from the Nashua facility and transplanting them temporarily to Palo > > Alto. > > > The implementation was kept so secret that it caught Dave Cutler, > > then working on DEC's next-generation operating system and chips, by > > surprise when it debuted at a Board Meeting in Maynard, > > Massachusetts. Shortly after that board meeting Mr. Cutler left > > Digital and moved (with some of his team) to Microsoft. > > Do you think that was just the straw that broke the camel's back? > > > The DECstations only were manufactured for a couple of years, as the > > DEC Alpha processor replaced MIPS in Digital's lineup. Although > > originally promised that OSF/1 would be ported to the DECstation > > line, this port was dropped due to realizing that there would never > > be an application base to support the customers of a DECstation > > OSF/1 port. It was better for ISVs and customers to maintain the > > Ultrix base for the DECstations than to split the base into Ultrix > > and OSF/1. > > Yeah, we had a ton of DECstations and a bunch of various early model > Alphas at WPI which we beta tested for DEC. The AS2100 with 8 DEC > StorageWorks canisters (which Netapp used on their early F220, F330, > F740 NAS systems) holding 3.5" disks, dual ported, hot-swapable. Nice > gear. > > The move from Ultrix to DEC OSF/1 was a bit painful, but not terrible > as I recall, but I'm sure I've blocked all the bad memories from then. > > Thanks for the walk down memory lane! > John > > > _______________________________________________ > WLUG mailing list --wlug(a)lists.wlug.org > To unsubscribe send an email towlug-leave(a)lists.wlug.org > Create Account:https://wlug.mailman3.com/accounts/signup/ > Change Settings:https://wlug.mailman3.com/postorius/lists/wlug.lists.wlug.org/ > Web Forum/Archive:https://wlug.mailman3.com/hyperkitty/list/wlug@lists.wlug.org…

1 year, 5 months

Re: [Wlug] non-Linux: Looking for a free kitten locally

by Ryan Pugatch

If you feel like going to Ashland, then I recommend: http://webpaws.com/mwhs/ They have a nice facility and seem to take good care of the cats there. Tal Cohen wrote: > I recommend the Sterling Animal Shelter. We got our dog there. > > > > -----Original Message----- > From: wlug-bounces(a)mail.wlug.org [mailto:wlug-bounces@mail.wlug.org] On > Behalf Of Jamie Guinan > Sent: Wednesday, August 12, 2009 3:41 PM > To: Tatsh > Cc: Worcester Linux Users Group > Subject: Re: [Wlug] non-Linux: Looking for a free kitten locally > > > I suspect the amount you would pay at the animal shelter would PALE next to > what you are going to pay for vet bills, spaying/neutering (usually done > around 6 mos as I recall), food, etc. So despite your comment, I'll plug > these guys: > > http://www.worcester-arl.org/catsAdoption.html > > But for another source, people are giving away kittens all the time on > Worcester freecycle. Its a Yahoo groups thing, which totally sucks balls, > but I have found good stuff on there from time to time. > > http://groups.yahoo.com/group/WorcesterMAfreecycle/ > > Example: > > Wed Jul 29, 2009 4:50 pm > offer: young grey kitten with white paws 01604 > > -Jamie > > > On Wed, 12 Aug 2009, Tatsh wrote: > >> I know I have not ever sent an email, but I've been on the mailing >> list for some time. Been extremely interested in going to meetings but >> just have not done so yet. >> >> If you are local, and have healthy kittens to give away or know anyone >> who does locally (I live in Lancaster, about 20 minutes away from >> Worcester), please respond. Looking to just get one, at maximum 5 >> months old. >> >> I have been scouring the web and craigslist and have not found much. I >> do not really want to drop the amount they want at the local animal > shelter. >> Any help appreciated. >> >> Thanks >> Andrew >> 978-870-5908 >> _______________________________________________ >> Wlug mailing list >> Wlug(a)mail.wlug.org >> http://mail.wlug.org/mailman/listinfo/wlug >> > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug -- Ryan Pugatch Systems Administrator, TripAdvisor

16 years, 4 months

Re: [Wlug] Antispam software (was spam with header)

by Karl Hiramoto

This would be an excellent meeting topic! On Tue, 2 Jul 2002, Theo Van Dinter wrote: > On Sun, Jun 30, 2002 at 10:38:24PM -0400, Karl Hiramoto wrote: > > Do you have a project created for this software? Distribute it? I > > have a spam problem @ work. Looking into solutions. I looked at maps > > rbl http://mail-abuse.org/rbl/ not sure on using it in a production > > environment though (where the most spam goes to) > > No, since it's mainly SpamAssassin with a little bit of procmail > frosting and a small perl script on top. I was planning to just make it > all available with the perpetually unfinished article I'm working on. > (It doesn't help that there were 2.5 new versions of SA released since > I started writing it ... <grrrr> ;) ) > > > My main worry is someone sending e-mail to sales(a)company.com and it > > gettting rejected, and comany.com loses a sale. Is this an issue? > > Well, that's the difference between a filter like SpamAssassin and > a blacklist like the RBL. Personally, I use several blacklists for > open-relays at the SMTP level, since it's unusual to have a false-positive > from an open-relay test (depending on the test of course). > > For a company, I would use a filter (like SA) and just let it mark up > likely spam. You can then leave it up to the users to decide what they > want to do with it. (SA adds headers indicating how likely a message > is to be spam (the score/number of hits), and what tests matched a > given message.) > > Anything else that makes it through to delivery goes through SpamAssassin. > Spams gets sorted into a seperate mail folder, and I then go through it > and report the spammers, etc. There's some information about what I do > for general filtering at: > > http://www.kluge.net/mailfiltering/ > > -- ¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø Karl Hiramoto <karl(a)hiramoto.org> Work: 978-425-2090 ext 25 Cell: 508-517-4819 Personal web page: http://karl.hiramoto.org/ Zoop Productions: http://www.zoop.org/ KTEQ Rapid City: http://www.kteq.org/ AOL IM ID = KarlH420 Yahoo_IM = karl_hiramoto ¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø It's not so hard to lift yourself by your bootstraps once you're off the ground. -- Daniel B. Luten

23 years, 5 months

Re: Wlug meeting on Thurs. Dec 10th 2020 @7pm.

by Chuck Anderson

Juniper QFX runs Wind River Linux. If you can control your update deployment, you can stay on the same package versions/releases that end up in RHEL. There may be someone working on a tool to make this easier. On Wed, Dec 09, 2020 at 04:12:24PM -0500, Frank Sweetser wrote: > It depends on the use case. If all you want is a free, reasonably stable > version of RHEL, Centos stream might just be good enough. > > If your goal is to support software that wants RHEL, this could be hit or > miss, as you'll always be running on an approximation of RHEL. You could > say you should always have been just buying RHEL if it's that critical, but > it's now that much less optional. > > I'm also really curious to see what's going to happen to the various black > box appliances out there that currently run on CentOS, like Aruba > Clearpass, Aruba wireless controllers, and the Juniper QFX switches. I > doubt they'll want something stablish like CentOS Stream, so they most > likely have three basic choices. > > 1. Run on CentOS 7 for as long as they can get away with it, and hope > something better appears in the meantime > 2. Work out a licensing deal for RHEL, and pass along the costs to the > customers > 3. Switch to an alternate distro like Ubuntu LTS > > The next year is going to be interesting for more than a few vendors... > > On Wed, Dec 9, 2020 at 3:59 PM Chuck Anderson <cra(a)alum.wpi.edu> wrote: > > > This might not be as bad as it initially sounds. Centos Stream will > > consist of rolling updates that start from what will become each RHEL > > point release to what will become the the next RHEL point release, so > > for example from RHEL 8.1 to 8.2 to 8.3 etc. In fact, Centos 6, 7, > > and 8 already is a "forced" minor upgrade every quarter or so since > > they stop supporting x.y after RHEL x.y+1 comes out and your normal > > system yum updates just migrate you to the newer x.y+1 anyway. This > > is in contrast to how RHEL itself works, or how Scientific Linux used > > to work, where you actually have to take explicit action to upgrade to > > a new point release either using new install media or manual "yum" > > commands. See for example: > > > > https://scientificlinux.org/documentation/faq/faq-releases/ > > > > And here is what one of my Centos 7 systems looks like: > > > > >cat /etc/centos-release > > CentOS Linux release 7.9.2009 (Core) > > >rpm -qf /etc/centos-release > > centos-release-7-9.2009.1.el7.centos.x86_64 > > >rpm -qi centos-release > > Name : centos-release > > Version : 7 > > Release : 9.2009.1.el7.centos > > Architecture: x86_64 > > Install Date: Thu 03 Dec 2020 07:27:24 AM EST > > .. > > > > See how the Centos 7.9.2009 release package was installed this month? > > Previously, I had older versions of that package: > > > > >sudo grep centos-release /var/log/yum.log* > > /var/log/yum.log:Nov 13 08:46:49 Updated: centos-release.x86_64 > > 7-9.2009.0.el7.centos > > /var/log/yum.log:Dec 03 07:27:24 Updated: centos-release.x86_64 > > 7-9.2009.1.el7.centos > > /var/log/yum.log-20181204:Jul 30 14:47:20 Updated: > > centos-release-7-5.1804.el7.centos.2.x86_64 > > /var/log/yum.log-20181204:Aug 14 12:15:35 Updated: > > centos-release-7-5.1804.4.el7.centos.x86_64 > > /var/log/yum.log-20181204:Oct 10 05:45:04 Updated: centos-release.x86_64 > > 7-5.1804.5.el7.centos > > /var/log/yum.log-20181204:Dec 04 07:19:18 Updated: centos-release.x86_64 > > 7-6.1810.2.el7.centos > > /var/log/yum.log-20200428:Jan 08 09:08:24 Updated: > > centos-release-7-7.1908.0.el7.centos.x86_64 > > /var/log/yum.log-20200428:Apr 28 07:47:22 Updated: centos-release.x86_64 > > 7-8.2003.0.el7.centos > > > > So over the years, this server got upgraded automatically from Centos > > 7.5 to 7.6 to 7.7 to 7.9. I have nightly automatic "yum updates" > > turned on, so it just gets updates as they come out and I reboot the > > server once every so often so the updates get fully applied (new > > kernels, new shared libraries). > > > > The difference with Centos Stream is you'll get updates continually > > /before/ RHEL releases it eventually as a "snapshot in time" called > > RHEL x.y+1. Sure, they won't be as heavily tested as RHEL point > > releases, but if you really need/want that, then you can either buy > > RHEL or stage your Centos Stream updates from TEST-->STAGE-->PROD, > > and/or stagger them across your PROD systems to minimize impact. > > > > On Wed, Dec 09, 2020 at 02:59:30PM -0500, Tim Keller wrote: > > > I've got a fair amount of centos in production... this sucks... guess I'm > > > going to Debian now... > > > > > > On Wed, Dec 9, 2020 at 9:10 AM Frank Sweetser via WLUG < > > wlug(a)lists.wlug.org> > > > wrote: > > > > > > > And for anyone looking to contribute to Greg's efforts: > > > > > > > > https://github.com/hpcng/rocky > > > > > > > > On Tue, Dec 8, 2020 at 11:23 PM Chuck Anderson via WLUG < > > > > wlug(a)lists.wlug.org> wrote: > > > > > > > >> My favorite comment on that post: > > > >> > > > >> "Gregory Kurtzer says: > > > >> December 8, 2020 at 4:27 pm > > > >> > > > >> I am considering creating another rebuild of RHEL and may even be able > > > >> to hire some people for this effort. If you are interested in helping, > > > >> please join the HPCng slack (link on the website hpcng.org) > > > >> > > > >> Greg > > > >> (original founder of CentOS)" > > > >> > > > >> On Tue, Dec 08, 2020 at 10:35:24PM -0500, Frank Sweetser via WLUG > > wrote: > > > >> > Well, there's plenty talk about for CentOS users, like what you're > > > >> going to > > > >> > switch to now that CentOS is becoming something completely > > different: > > > >> > > > > >> > https://blog.centos.org/2020/12/future-is-centos-stream/

5 years

Re: Uptime!

by Mike Peckar

Fun Story, Maddog. Around 20 yrs ago I was consulting for Bloomberg in Skillman, NJ, a big Solaris shop. The HP app I was working with bellied up with memory leaks and I suggested they reboot that server. I was told flat out they don't reboot Solaris servers period. They cleaned up the mess and isolated where in the HP code that the pointer was lost, leaving me the not-so-fun task of filing the bug report with HP. Mike On Wed, Apr 20, 2022 at 7:39 PM Jon "maddog" Hall via WLUG < wlug(a)lists.wlug.org> wrote: > Tim, > > What was the reason for shutting it down? > > This reminds me of a story from years ago where a young friend contacted > me before a trip to the University of New Hampshire for a Linux LUG meeting. > > He asked me if I would go to a particular dorm and knock on the door of > what had been his door room. I was to ask if I could unplug the box that > was in the corner of the closet in the room. The system had been running > for five years in his former dorm room and he had forgotten the login > password. He did not want the machine back, just wanted it unplugged. > > A young woman answered the door, heard my explanation and let me unplug > the machine. "We were afraid to unplug it" she said. > > Your machine beat his machine on uptime. > > md > > On Wed, Apr 20, 2022 at 5:07 PM Tim Keller via WLUG <wlug(a)lists.wlug.org> > wrote: > >> I just shutdown a linux machine with 3169 days of uptime! >> It had userland processes that have been actively running since 2013! >> Tim. >> >> -- >> I am leery of the allegiances of any politician who refers to their >> constituents as "consumers". >> _______________________________________________ >> WLUG mailing list -- wlug(a)lists.wlug.org >> To unsubscribe send an email to wlug-leave(a)lists.wlug.org >> Create Account: https://wlug.mailman3.com/accounts/signup/ >> Change Settings: >> https://wlug.mailman3.com/postorius/lists/wlug.lists.wlug.org/ >> Web Forum/Archive: >> https://wlug.mailman3.com/hyperkitty/list/wlug@lists.wlug.org/message/PW3ML… >> > _______________________________________________ > WLUG mailing list -- wlug(a)lists.wlug.org > To unsubscribe send an email to wlug-leave(a)lists.wlug.org > Create Account: https://wlug.mailman3.com/accounts/signup/ > Change Settings: > https://wlug.mailman3.com/postorius/lists/wlug.lists.wlug.org/ > Web Forum/Archive: > https://wlug.mailman3.com/hyperkitty/list/wlug@lists.wlug.org/message/KSUVD… >

3 years, 7 months

Re: [Wlug] Flat screen monitor 19" needs fixit; free to good home

by JeffA Maillists

Hi Liz, If nobody else has chimed in, I'll take it. I've fixed a handful of LCDs with capacitor issues, and they're all still in use today. I'll use it as a 'preview' monitor at church if I can fix it. ;-) Let me know, Thanks! Jeff On Sat, Jun 27, 2015 at 9:58 PM, E Johnson <iris.gates(a)gmail.com> wrote: > The power went out here twice today. After the second event, monitor seems > to have died. > > This is an Acer monitor, several years old. Black(ish) bezel; not glossy. > Flat screen, I think 19" diagonal. Has been a very nice reliable monitor > during its working life. Has choice of DVI input or the older kind of data > connection, whatever that used to be. > > This specific batch of Acer monitors had used a type of capacitor which is > known to have a higher-than-usual failure rate, and this is PROBABLY what > it needs. Had a twin of this that fryolated same way 2 years ago, and a > WLUG member came by & reported shortly after that he got it up & running > with just the replacement of bad caps. > > This monitor has been very steady and reliable until this afternoon, with > nice display and no dead pixels, ever. So if you are handy with electronics > fixits, capacitors are cheap and you could probably get this working again > with only a screwdriver, a soldering iron and a little bit of fiddling. > Might be nice for the kid's playroom or the back office, or something. > > I don't know how nice games look on this monitor, since I don't do gaming. > Videos always looked perfectly fine with good color. > > PM me if you think you want this, since I have to get down under the work > table to unplug the power cord & I'm not as spry as I used to be, but can > do as long as my knees aren't required to do anything radical before Noon. > Pickup after Noon any day, & evenings even sort-of late-ish are okay. I can > meet you at the door with this. I'm in Worcester near Elm Park. > > Rather give this away here than trash it, or Freecycle... first dibs to > WLUG. > > Best wishes, > Liz J > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > >

10 years, 5 months

Re: [Wlug] VNC performance

by Andy Stewart

HI Brad et al, Definitely get that wallpaper (background) to be some plain, boring, solid color, or it will adversely effect VNC performance unless you have really good network bandwidth. Background gradients really kill the performance in many cases. Once that's done, make sure the server and viewer are speaking the same number of colors. I believe the server defaults to 8 bit color. If the server is run with 24 bit color (for example) and the viewer is only 8 bit color, VNC has to transpose and that can reduce performance. Also, try using a Java enabled browser as a VNC client. Sometimes, it works better than the native vncviewer, but only for 8 bit color situations. This is heavily dependent on the Java implementation. Finally, check the network and make sure you aren't bandwidth limited. I'vve seen VNC takes 500 kb/sec on my cable modem during "compilcated" screen redraws, but then settle back down during more idle periods. If you are bandwidth limited, you might try www.tightvnc.com. I hope this helps. Let us know your results. Andy On Monday 03 December 2001 02:51 pm, dibb_jim(a)emc.com wrote: > Right click on windows desktop, choose settings->background, then under > wallpaper select (None). That disables windows wallpaper. > > Maybe there's something else. Hope it helps. > > -----Original Message----- > From: Brad Noyes [mailto:maitre@ccs.neu.edu] > Sent: Monday, December 03, 2001 2:36 PM > To: wlug(a)mail.wlug.org > Subject: [Wlug] VNC performance > > > Hi All, > I remember some time ago talking with Andy, and others about VNC > performance at a > wlug meeting. I remember that setting the depth 8 will help performance, > as well > as disabling the wallpaper. I am running the server on windows, and the > client > on a linux machine. VNC's site has info for disabling wallpaper, but it > seems to > involve editing a registry file. When i try to do so, i get an access > denied message, because that file is read only. Can someone help me out > here? I really > know very little about windows. On the client side, the option '-depth > 8' doesn't seem to do very much i get '16 bits per pixel'. > > If anyone knows of any other methods for speeding up VNC, please post. > > Thanks, > --Brad > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug -- Andy Stewart Founder Worcester Linux Users' Group Worcester, MA, USA http://www.wlug.org

24 years

WLUG search results for query "meeting"