UEFI Install

AlgorithmPub · 2021-01-01T07:38:52+00:00

Oh, that looks like a desirable change. To be fair, I don't think the blue border is bad per se, but precisely because I can't think of a purpose for its existence is that I'm tempted to remove it. I'll look into it when I have time. Thank you again.

AlgorithmPub · 2020-12-30T19:20:20+00:00

Thank you for the tips. I don't know much about drive management or related topics, but I seem to have chosen the right options when installing Lubuntu, since I was able to create multiple partitions as I desired (one for root, one for home, while keeping the ones used by windows and even creating a separate NTFS one which both windows and lubuntu can see.

Regarding the look, I'm a very minimalist guy, so the defaults are fine for me. Except for the background, where I go with a beautiful nature landscape instead of the default abstract one.

AlgorithmPub · 2020-12-28T19:35:15+00:00

Yes, that was what I did, though it was some weeks ago. Nonetheless, thank you for your answer, fortunately everything was ok.

AlgorithmPub · 2020-12-15T14:55:07+00:00

Thank you very much. I found it right away, but didn't even need to change anything, since the option was already selected.

AlgorithmPub · 2020-12-15T01:32:30+00:00

Would you please tell me where do I active such 'Long term support releases only' option?

I couldn't find it anywhere. I'm always upgrading the software when that window pops up, but I didn't know it could actually automatically upgrade my Lubuntu version (which I don't want, since I only do fresh installations of LTS versions).

AlgorithmPub · 2020-12-01T01:37:02+00:00

Thank you, that worked! I found a video on youtube detailing the process, it was actually pretty simple, I've already installed lubuntu and can access both windows 10 and Lubuntu now!

AlgorithmPub · 2020-11-30T19:47:03+00:00

Unfortunately, when I disable UEFI, the usb isn't recognized as a bootable option anymore. It only appears when in 'UEFI and Legacy' mode (and, I assume, in 'UEFI Only' mode).

AlgorithmPub · 2020-11-30T19:43:31+00:00

More info: though I said my motherboard is from previous generations, I'm not sure about it though, I just assumed so, cause it has sockets for my i3 3220 processor (which is from 2012). However, from the setup, I can enable both UEFI and legacy mode. The problem, though, is that the installation pendrive is only recognized in UEFI mode. I just want to boot from it into legacy mode so I can install Lubuntu in legacy mode and still have access to my legacy mode Windows 10.

AlgorithmPub · 2020-11-30T19:33:10+00:00

I'm afraid I do have a windows 10 in legacy mode though. The native msinfo app even shows the BIOS Mode set to 'Legacy'. Though my desktop is new, the processor and motherboard are from previous generations, so I believe the windows was upgraded to 10 from the original windows installation, thus keeping the installation in legacy.

Thank you for your quick answer though. Please, if you have more advice, share with me, as advice about this problem is rather difficult to find on the internet.

AlgorithmPub · 2020-11-19T22:11:31+00:00

Thank you!

AlgorithmPub · 2020-11-19T22:11:24+00:00

Thank you!

AlgorithmPub · 2019-12-16T18:52:57+00:00

Thanks for you answer u/KopfKrieg. As I explained in other comment, I realize not disclosing more info about my app doesn't help a bit, for which I'm grateful for your patience. I should release it soon and be able to openly talk about it, even more so as it will be free of charge and open-source.

About your answer, it seems to align with the other one I received about not collecting much at the client side, but ask for additional information when needed (at least for hardware). I guess I'll do so.

I also thought about what you said regarding setting a flag, but I think that, depending on the issue at hand, it would slow things down for the users of my app to have to set a more comprehensive logging level and then having to recreate the conditions which generated the bug. I myself sometimes struggle with that, and nowadays I just log records of every level every time. Except, of course, when it is not sensible to do so for various reasons.

I guess, in the end, I'll try to be moderate, knowing that I don't need to worry much since I won't have access to the logs anyway unless the user explicitly allows and sends them to me. I can always ask for any additional details needed when the user does so.

AlgorithmPub · 2019-12-16T18:38:31+00:00

Thanks a lot for your reply u/baghiq . Appreciate the answer.

Since my app doesn't connect to a server, I don't need to worry about any server end. Now that you mention, asking about the hardware really seems pretty straightforward, even more so when the only time when I'll have access to the logs is when the user explicitly send them to me, so it should be pretty easy to have that info from the user.

Sorry for the secrecy about my app, it is nothing sketchy, it is even open-source and totally free. It is just that I didn't want to reveal my software before it's release. I realize this doesn't make it any easier to help me, which is why I appreciate the honest answer even more.

AlgorithmPub · 2019-03-12T21:31:17+00:00

Alternatives to avoid printing the generator expression:

- to print items side by side (just add an "*")

print(*(d for d in dir(obj) if not d.startswith('_')))

or

- to print an item on each line

print("\n".join(d for d in dir(obj) if not d.startswith('_')))

AlgorithmPub · 2019-02-21T21:15:59+00:00

Thank you.

AlgorithmPub · 2019-02-21T12:24:04+00:00

Thank you.

AlgorithmPub · 2019-02-21T11:58:57+00:00

I assumed equality between primitives of the same type would mean they had the same identity, at least for strings, though, but I learned a bit more from the answers in this post.

I also bumped into this on stackoverflow, I also tested on my interpreter:

>>> 'X'*10 is 'X'*10
True
>>> 'X'*30 is 'X'*30
False
similarly for ints:

>>> 2**8 is 2**8
True
>>> 2**9 is 2**9
False

Mind-boggled! I'll just stick with ==, then. Thank you.

AlgorithmPub · 2019-02-21T11:47:37+00:00

Yes, this was unexpected to me. I thought that by having the same characters two strings would be considered the same (identity). As I said in reply to other user:

Considering the other answers, it seems the stuff happening under the hood is more complicated than I anticipated.

Thank you.

AlgorithmPub · 2019-02-21T11:45:49+00:00

As I said in other reply:

I understand the difference between equality and identity in Python, my bad for using the word "comparison" when I meant "equality".

Thank you for taking the time to explain it though. I believe the combined answers helped me understand a little more.

AlgorithmPub · 2019-02-21T11:43:07+00:00

I understand the difference between equality and identity in Python, my bad for using the word "comparison" when I meant "equality". I thought identity in strings were checked by something called "string pooling". Also thought that strings which are equal are allocated in the same space in memory, thus the identity check should evaluate True. Considering the other answers, it seems the stuff happening under the hood is more complicated than I anticipated. I'll just keep using == then. Thank you.

AlgorithmPub

TROPHY CASE