|
Message Closed
modified 15-May-23 19:07pm.
|
|
|
|
|
Member 14968771 wrote: Here is HERS new advise
" turn the power off, UNPLUG the modem coax, wait 30 seconds etc etc "
I have long suffered the Internet Service Provider's helpdesk saying,
"Unplug the coax and plug it back in..."
A recent call (when the final fault was the ISP themselves) the 2nd level tech told me to unplug and plug coax back in.
Me: Hey, man, they tell me to do this all the time. What would that really do?
2nd level tech: Umm...well...ermmm...I'm not actually sure. I think they are just checking to see if you have it attached properly at all.
Me: Yeah, that's what I thought....Ok, I did that then. (as far as you know).
|
|
|
|
|
I would say, "OK, I've done that at my end, now you do your end!"
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
My last contact with my phone / ISP provider went like this:
Cable was out; I dialed their service number to see what was what. Their recording went: "If you're calling about a problem, we've sent a reset to your cable box" ... and that was that. Didn't even have to identify myself. Was impressed. (It's also why I think stealing cable services with non-service provider boxes isn't that easy as some providers may claim).
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it.
― Confucian Analects: Rules of Confucius about his food
|
|
|
|
|
Is Hepatitis C a dangerous place to swim?
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Tough to say whether you'll liver die. Now if one gets stung by a Hepatitis B, you're definitely doomed.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
modified 19-May-21 10:59am.
|
|
|
|
|
You are sharp as a needle, Griff!
"If we don't change direction, we'll end up where we're going"
|
|
|
|
|
That's hollow praise.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
That, infect, is still an open question. I don't know virus is the case but it's not a sneezy a question to answer as you'd imagine.
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
In this thread[^] from yesterday, Linux development on Windows was discussed. I want to do this eventually and would appreciate any pointers so I don't bang my head against the wall, let alone get it nailed to the floor.
I currently build C++ console applications on Windows, and that's all I need on Linux for now. So...
- Which Linux do you run? Debian? Ubuntu? RedHat?
- How do you run it on your Windows machine? In a VM? If so, which one? Or using WSL?
- How do you edit? VS2017? VS2019? VS Code? vi?
 - How do you build? Within Linux? From within VS?[^]
- Which compiler do you use? g++? clang?
- How do you debug? Within Linux? If so, which debugger? Or remotely, from within VS?
- How do you interface to GitHub? Within Linux? Using the VS plug-in?
- What should be avoided?
Thanks.
|
|
|
|
|
I wonder, like I did yesterday, why you dont turn your back on Windows.
But, aside from that, my suggestion is that you CAN run vs code on Windows with the plugins Remote Containers (locally towards a Docker container) or Remote SSH (towards a Linux server). This solution works fine for server applications, not sure about GUI apps. That might need more steps. In this case you build and debug inside code.
If you are new to Docker: Basically it allows you to run a Linux server inside your box. The first time (only) it takes quite a while to start the container, it has to compose an entire Linux. No worries, next time it starts much faster than any laptop boots.
Developing inside a Container using Visual Studio Code Remote Development[^]
Good luck.
"If we don't change direction, we'll end up where we're going"
|
|
|
|
|
I had briefly been using VS 2017's Linux development tools. You can set it up to build over TCP on a different computer, although it looks like now you can do it on WSL. You needed to install openssh, and after you configured everything it would build and debug on the linux machine, while letting you edit and step through the code in VS on Windows. I used g++ but clang was supported too.
|
|
|
|
|
Which Linux do you run? Debian? Ubuntu? RedHat?
LMDE (Linux Mint based on Debian) and ESXi
I run Windows in VM's. One exception is a Windows system running BlueIris for cameras.
Stick your toe in the water: Get a Raspberry Pi and use VS Code/VS Studio to develop remotely. You can even run Blazor stuff for web.
If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.
|
|
|
|
|
I did write a program in VS that was compiled on a remote Ubuntu server with g++ via SSH. I tried to do some MPI programming with MPICH[^] for some numerical simulations on a rather large grid.
Seem to remember that I had to set it up using mpicc compiler instead of g++ with remote debugging and all went rather well. Was a University run server though.
|
|
|
|
|
|
1. I run Ubuntu in a VM. A lot of people don't like it - heck I don't like it (but then I don't like any distro except ArchLinux which isn't usable as a primary desktop OS), but it has the largest userbase of any distro so when there are inevitably problems there's a lot more solutions to search for Ubuntu than say Debian. These days I prefer using MiniGW and using GCC that way without running it on Linux at all when I'm on a windows OS.
2. See 1
3. VS Code. It is simply better than anything else I've used, including for the most part, Visual Studio
4. See 1
5. Both. My code compiles with both or I change it until it does - and i always use the -std=C++XX options. Always.
6. I debug using GDB by way of VS Code's integrated debugger UI
7. VS Code
8. Hmmmm. Don't use VirtualBox - its USB device mapping has been dodgy for me. It can be hard to find a download link from the main site but google "VMWare Player" and download that.
Real programmers use butterflies
|
|
|
|
|
I've never done anything crazy in it but I use VirtualBox with Debian for some linux stuff. Aside from some of the convenience options sometimes bugging out (like cut/paste between VM and host) it's been pretty solid. You HAVE to install the Guest Additions though - lots of QoL improvements. Ubuntu didn't run the best on it for me but that also might be my setup because I know it has for others.
I'll have to check out VMWare Player though. Maybe I just don't know what I'm missing 
|
|
|
|
|
I just know I had issues with it capturing USB devices. The devices would capture but then they would come back with some kind of failure whenever I tried to access them - except once in a blue moon they would magically work.
Real programmers use butterflies
|
|
|
|
|
The only useful thing I found when I searched was this but I've really only ever used basic keyboard and mouse so never had to worry about those things. Does seem like a recurring issue though.
|
|
|
|
|
It's been five years, but I found VirtualBox better for running Linux and VMWare better for running Windows.
(And I found both problematic with USB so never bothered.)
|
|
|
|
|
1. Ubuntu
2. WSL
3. VSCode
4. g++ in Linux
5. see 4.
6. Current apps are not big enough to need debugging. But I have used with gdb quite extensively in the past.
7. Never used github.
8. Children and animals.
|
|
|
|
|
I can see the irony of this question.The desk would be a better place to bang your head when you start..
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
|
|
|
|
|
1. Ubuntu
2. WSL
3. Alternate between Notepad++/VSCode/VS2019.
4. Most of the time I build/debug in VS2019. Than makefiles/g++/gdb for platform specific issues.
5. g++
6. See 4 above. I find VS2019 a class above other environments and I go to gdb only for specific issues.
7. TortoiseGit is my friend. Occasionally using VS plugin.
8. Spending too much time in front of your screen. They say it's bad for your eyes.
Mircea
|
|
|
|
|
I have Ubuntu as main OS of my notebook and use Windows inside a Virtualbox VM.
1) Ubuntu
2) Linux as main OS, Windows in a VM
3) QtCreator
4) build within QtCreator (cmake / qmake)
5) both gcc and clang (MinGW and occasionally VS on windows)
6) Inside QtCreator using gdb
7) within QtCreator or with git cli (remotes on gitlab)
8) my personal feeling.... Windows 
Main thing here is that in my personal opinion QtCreator is *much* better than VSCode for C++ development (unfortunately I have to use VSCode for other non C++ projects and I find it quite messy and chaotic).
modified 20-May-21 3:32am.
|
|
|
|
|
i vote for qtcreator, too. qt is super frickin great imho.
i'm just like you except my flavor is kubuntu. just ubuntu w kde instead o gnome.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
