- WLUG - wlug.mailman3.com

Possible linux or hardware bug?

by Kevin Stratton

I have been chasing my tail trying to download a very large to my desktop. The bug is strange enough that it might be specific to hardware. The issue is that I can not copy very large files accurately. The threshold value size of the file seems to be about 8589934592. Any file this size or larger seems to be uncopyable on my desktop. I had downloaded a corrupted file of 71.9GB with Ubuntu 20.04, Ubuntu 22.04, Windows 10 virtua machine running under Ubuntu 20.04, Manjaro. All of theses OS;s were running on the same hardware. I had no issues downloading the file from a raspberry pi with and external hard drive. I have included the C file I used to create the files which also has some notes opn the results of the tests. Any advice or help would be appreciated.

April 28, 2022

Re: Uptime!

by Richard Klein

Is that really a useful data point? I'm thinking that past reboot performance is not indicative of future returns. On Thu, Apr 21, 2022, 10:06 AM Michael Voorhis via WLUG <wlug(a)lists.wlug.org> wrote: > Additionally if you never reboot, how do you know the machine WILL > reboot? How do you know what the system will do after a power failure, > etc? Fate will intervene at some point and force you to reboot whether > you want to or not, so you should be prepared with the knowledge of how > the system will respond to that. > > On 4/21/22 09:54, David Glaser via WLUG wrote: > > It you kept it up all of the time, how would you apply updates that > > require a re-boot? > > _______________________________________________ > 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/2CNXU… >

April 26, 2022

Re: Uptime!

by John Stoffel

Tim> I just shutdown a linux machine with 3169 days of uptime! Aww... why?!?! Tim> It had userland processes that have been actively running since 2013! I'm quite impressed. Can you give more details on the OS, hardware, etc?

April 26, 2022

Re: Snaps and the future of Ubuntu

by Dennis Payne

I think history has shown that the fragmentation will decrease. It would increase if Ubuntu continued to focus on its walled garden and succeeded but Ubuntu is not good at that. They pushed upstart but the community went with systemd. They pushed Mir but the community went with Wayland. They pushed Unity but dropped it for Gnome. Maybe they do better with smaller contributions to existing projects but their attempts to drive the linux community has largely failed. On Mon, 2022-04-25 at 13:42 -0400, Joshua Stone via WLUG wrote: > Last week marked the release of Ubuntu 22.04 LTS, and so far it looks > like some noteworthy improvements over the last LTS, notably Wayland > being enabled for Intel/AMD users by default! > > There is no Wayland enablement for Nvidia users in 22.04 LTS though, > and Pulseaudio is still the default audio server instead of the more > modern pipewire+wireplumber that's been appearing in other > distributions. It also appears that Firefox in 22.04 LTS is now > installed as a snap at the request of Mozilla, and it drops the deb > package from the official repo. > > Also interesting is that Ubuntu will continue to avoid supporting > flatpak in favor of snap, as explained by Mark Shuttleworth: > > https://www.omgubuntu.co.uk/2022/04/ubuntu-wont-support-flatpak-anytime-soon > > >I can say right now Flatpak’s wouldn’t work for us. I don’t think > they have the security story and I also don’t think they have the > ability to deliver the same integrity of execution over time that > Snaps have ‘cos we built those things into Snaps > > >I like the fact that people have a diversity of opinions on ways to > solve the problem […] but I also think we’re going to deliver a far > better experience to developers and to users if we concentrate our > efforts around something we really can move forward. > > I respectfully disagree with Shuttlesworth's appraisal, because it > seems to contradict the overall experience I've seen from open source > projects that have a tendency to package flatpaks and appimages which > in turn tend to be well-supported across many distributions. > > While I understand that it's very easy to set up flatpak in Ubuntu > these days, I'm still disappointed that this is the stance Ubuntu is > taking because I feel that this doesn't quite align with the > interests of the Linux community at large who're trying to improve > the desktop experience. > > I worry that the distribution that got me into Linux years ago will > increase fragmentation as time goes on if it continues to focus on > its walled garden approach. What do you think? > > - Josh > _______________________________________________ > 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/GZEMS…

April 25, 2022

Snaps and the future of Ubuntu

by Joshua Stone

Last week marked the release of Ubuntu 22.04 LTS <https://ubuntu.com/blog/ubuntu-22-04-lts-released>, and so far it looks like some noteworthy improvements over the last LTS, notably Wayland being enabled for Intel/AMD users by default! There is no Wayland enablement for Nvidia users in 22.04 LTS though, and Pulseaudio is still the default audio server instead of the more modern pipewire+wireplumber that's been appearing in other distributions. It also appears that Firefox in 22.04 LTS is now installed as a snap at the request of Mozilla, and it drops the deb package from the official repo. Also interesting is that Ubuntu will continue to avoid supporting flatpak in favor of snap, as explained by Mark Shuttleworth: https://www.omgubuntu.co.uk/2022/04/ubuntu-wont-support-flatpak-anytime-soon *>I can say right now Flatpak’s wouldn’t work for us. I don’t think they have the security story and I also don’t think they have the ability to deliver the same integrity of execution over time that Snaps have ‘cos we built those things into Snaps* >*I like the fact that people have a diversity of opinions on ways to solve the problem […] but I also think we’re going to deliver a far better experience to developers and to users if we concentrate our efforts around something we really can move forward.* I respectfully disagree with Shuttlesworth's appraisal, because it seems to contradict the overall experience I've seen from open source projects that have a tendency to package flatpaks and appimages which in turn tend to be well-supported across many distributions. While I understand that it's very easy to set up flatpak in Ubuntu <https://flatpak.org/setup/Ubuntu> these days, I'm still disappointed that this is the stance Ubuntu is taking because I feel that this doesn't quite align with the interests of the Linux community at large who're trying to improve the desktop experience. I worry that the distribution that got me into Linux years ago will increase fragmentation as time goes on if it continues to focus on its walled garden approach. What do you think? - Josh

April 25, 2022

Re: Uptime!

by Jon "maddog" Hall

Thanks for the info. I went from FORTRAN to FORTRAN II to FORTRAN IV to FORTRAN 66, then FORTRAN 77 with a brief dabbling in WATFOR. md On Thu, Apr 21, 2022 at 8:08 PM Michael Voorhis <mvoorhis(a)mcvau.net> wrote: > Wikipedia's "Fortran" page has descriptions for both Fortran-5 (Data > General) and Fortran-V (Control Data). > > from https://en.wikipedia.org/wiki/Fortran : > > Fortran 5 was marketed by Data General Corp in the late 1970s and > > early 1980s, for the Nova, Eclipse, and MV line of computers. It had > > an optimizing compiler that was quite good for minicomputers of its > > time. The language most closely resembles FORTRAN 66. > > > > FORTRAN V was distributed by Control Data Corporation in 1968 for the > > CDC 6600 series. The language was based upon FORTRAN IV.[64] >

April 22, 2022

Re: Uptime!

by Michael Voorhis

Wikipedia's "Fortran" page has descriptions for both Fortran-5 (Data General) and Fortran-V (Control Data). from https://en.wikipedia.org/wiki/Fortran : > Fortran 5 was marketed by Data General Corp in the late 1970s and > early 1980s, for the Nova, Eclipse, and MV line of computers. It had > an optimizing compiler that was quite good for minicomputers of its > time. The language most closely resembles FORTRAN 66. > > FORTRAN V was distributed by Control Data Corporation in 1968 for the > CDC 6600 series. The language was based upon FORTRAN IV.[64]

April 22, 2022

Re: Uptime!

by Mike Peckar

md, Here's where I saw the reference to Fortran V wrt Voyager's CSS... https://www.allaboutcircuits.com/news/voyager-mission-anniversary-computers… From http://www.quadibloc.com/comp/fort04.htm.... IBM never defined a language called FORTRAN V, or provided a compiler for it, but some of its competitors used the term for their extended versions of FORTRAN. Univac and Data General are two companies that sold compilers for a language which they called FORTRAN V. In general, FORTRAN V compilers included the CHARACTER data type as a standard feature of the language, and they added the ENCODE and DECODE statements as well. These statements allowed a character variable to be used instead of an input-output device as the source for a formatted read, or the target of a formatted write, and they looked like this: CHARACTER*80 BUFFER ... ENCODE(80,11,BUFFER),X,Y,Z ... DECODE(80,10,BUFFER),P,Q,R ... STOP 10 FORMAT (3F12.5) 11 FORMAT (3F12.5) END Mike On Thu, Apr 21, 2022 at 6:20 PM Jon "maddog" Hall <jon.maddog.hall(a)gmail.com> wrote: > I had not heard of Fortran 5 (or Fortran V) and a half-hearted search of > the Internet did not find anything. > > Do you have any pointers to it? > > Thanks, > > md > > On Thu, Apr 21, 2022, 18:09 Mike Peckar <mpeckar(a)gmail.com> wrote: > >> According to the Guiness Book of World records, The computer system that >> has been in continual operation for the longest period is the Computer >> Command System (CCS) onboard NASA's *Voyager 2* spacecraft. This system >> has been in continuous operation since the spacecraft's launch on 20 August >> 1977. Voyager 1's CCS uptime trails it by a couple of weeks and both are >> still going. >> >> Each Voyager has two CCSs, two Flight Data System (FDS) computers and two >> Attitude and Articulation Control System (AACS) computers, but the FDS & >> AACS do not operate continuously. The CCS's have two 18-bit word, interrupt >> type processors with 4096 words each of non-volatile plated wire memory >> amounting to 69.63 kilobytes. They execute about 81,000 instructions per >> second and transmit data back to Earth at 160 bits per second. They were >> originally programmed in Fortran 5. >> >> Mike >> >> On Thu, Apr 21, 2022 at 12:32 PM Jon "maddog" Hall < >> jon.maddog.hall(a)gmail.com> wrote: >> >>> Mike, >>> >>> Believe it or not, both VMS and Digital Unix systems were the same way. >>> They would go months and years without rebooting. >>> >>> The US Navy had two hospital ships, the "Mercy" and the "Hope". One >>> stationed on the East Coast and one in San Diego. The one on the East >>> Coast used WNT for the servers and the one in San Diego used GNU/Linux. >>> The ship using WNT had to have twice as many servers as the one in San >>> Diego because the Navy rules said that a WNT server HAD to be rebooted >>> every 30 days, whereas there was no such requirement for GNU/Linux. Since >>> a Naval deployment could last longer than 30 days, and since they needed >>> the server services to be up constantly that whole time, they needed twice >>> as many WNT servers. >>> >>> md >>> >>> On Thu, Apr 21, 2022 at 8:58 AM Mike Peckar via WLUG < >>> wlug(a)lists.wlug.org> wrote: >>> >>>> 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… >>>>> >>>> _______________________________________________ >>>> 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/ZZZSN… >>>> >>>

April 21, 2022

Re: Uptime!

by Dan Davis

A branch for my company has one remaining Solaris box that keeps up a service or two with a ridiculous uptime and they recently built a new facility. In a meeting we were discussing the move plan for their entire IT kit and they asked me about the feasibility of moving the Solaris box across town on an UPS so they wouldn't have to shut it down. I kindly asked them to reconsider because while they might keep power applied for the whole ride it'd be unlikely that the disks would survive the trip. On Thu, Apr 21, 2022 at 8:58 AM Mike Peckar via WLUG <wlug(a)lists.wlug.org> wrote: > 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… >> > _______________________________________________ > 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/ZZZSN… >

April 21, 2022

Re: Uptime!

by Jon "maddog" Hall

I had not heard of Fortran 5 (or Fortran V) and a half-hearted search of the Internet did not find anything. Do you have any pointers to it? Thanks, md On Thu, Apr 21, 2022, 18:09 Mike Peckar <mpeckar(a)gmail.com> wrote: > According to the Guiness Book of World records, The computer system that > has been in continual operation for the longest period is the Computer > Command System (CCS) onboard NASA's *Voyager 2* spacecraft. This system > has been in continuous operation since the spacecraft's launch on 20 August > 1977. Voyager 1's CCS uptime trails it by a couple of weeks and both are > still going. > > Each Voyager has two CCSs, two Flight Data System (FDS) computers and two > Attitude and Articulation Control System (AACS) computers, but the FDS & > AACS do not operate continuously. The CCS's have two 18-bit word, interrupt > type processors with 4096 words each of non-volatile plated wire memory > amounting to 69.63 kilobytes. They execute about 81,000 instructions per > second and transmit data back to Earth at 160 bits per second. They were > originally programmed in Fortran 5. > > Mike > > On Thu, Apr 21, 2022 at 12:32 PM Jon "maddog" Hall < > jon.maddog.hall(a)gmail.com> wrote: > >> Mike, >> >> Believe it or not, both VMS and Digital Unix systems were the same way. >> They would go months and years without rebooting. >> >> The US Navy had two hospital ships, the "Mercy" and the "Hope". One >> stationed on the East Coast and one in San Diego. The one on the East >> Coast used WNT for the servers and the one in San Diego used GNU/Linux. >> The ship using WNT had to have twice as many servers as the one in San >> Diego because the Navy rules said that a WNT server HAD to be rebooted >> every 30 days, whereas there was no such requirement for GNU/Linux. Since >> a Naval deployment could last longer than 30 days, and since they needed >> the server services to be up constantly that whole time, they needed twice >> as many WNT servers. >> >> md >> >> On Thu, Apr 21, 2022 at 8:58 AM Mike Peckar via WLUG <wlug(a)lists.wlug.org> >> wrote: >> >>> 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… >>>> >>> _______________________________________________ >>> 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/ZZZSN… >>> >>

April 21, 2022