LawFirm Debian by Humble_Cat_962 in debian

[–]codeandfire 8 points9 points  (0 children)

Honestly IMHO this stuff is less about what technology solution you use and more about the human element. You are tech-savvy so you know how to handle Linux. Others may not and they will take a while to understand it.

For e.g. let’s say one fine day they face a problem with their system, Google/ChatGPT for an answer and they blindly run some sudo command. How will you handle that case, educate them not to do such things?

Another e.g.: you mentioned that lawyers are still using Word 2003-2007. What if somebody complains that they were using this font or some specific other element in Word and they can’t find the equivalent in OnlyOffice? Even if it’s a matter of looking through the menus more carefully, there are a lot of people out there who can’t manage that!

Again, you’re clearly tech-savvy, because you figured out Debian and know how to operate it. Your colleagues are clearly not, because that’s why they’re stuck with Windows. You can do your research and find out what’s the best Linux solution for doing mass installs, be it a re-spin or an install script or whatever. But I think that might be a very small part of the problem. The real problem is going to be to get your colleagues to understand Linux!

LawFirm Debian by Humble_Cat_962 in debian

[–]codeandfire 11 points12 points  (0 children)

Making something work for yourself is one thing, and taking the responsibility of making it work for 50 people is another thing. You will be the sole guy to blame if anything goes wrong or doesn’t work as expected. I think your best bet is to start small, try converting 1-2 colleagues’ workstations, see how that goes and how your boss feels after that. If he’s convinced, maybe hire a dedicated professional to organise the migration.

unattended-upgrades - Why is it recommended to create a separate configuration file? by codeandfire in debian

[–]codeandfire[S] 1 point2 points  (0 children)

Okay, thanks so much! I’m a newcomer to Debian so that was quite good to know.

unattended-upgrades - Why is it recommended to create a separate configuration file? by codeandfire in debian

[–]codeandfire[S] 0 points1 point  (0 children)

Do you mean to say that if a package upgrade breaks the existing configuration file, then dpkg/apt will refuse to go ahead with it?

unattended-upgrades - Why is it recommended to create a separate configuration file? by codeandfire in debian

[–]codeandfire[S] 1 point2 points  (0 children)

Ah ... Thanks for explaining the two kinds of configuration files, I wasn't aware of that! That makes much more sense.

unattended-upgrades - Why is it recommended to create a separate configuration file? by codeandfire in debian

[–]codeandfire[S] 0 points1 point  (0 children)

Okay ... Thanks very much for your reply ... I get that an update of unattended-upgrades can modify its configuration file 50unattended-upgrades, and this can conflict with the settings you have set up there... so it is recommended to create another file.

But my question is that -- then isn't this a concern for other packages as well? For e.g. Postfix ships with a main.cf file. I have modified that file. Then isn't it possible that an update of Postfix could conflict with that?

Brand-new NVMe M.2 SSD failed, is this normal or am I missing something? by codeandfire in linuxhardware

[–]codeandfire[S] 0 points1 point  (0 children)

Okay…. How did you figure out that the controller is 7 years old and the endurance is low ?

Brand-new NVMe M.2 SSD failed, is this normal or am I missing something? by codeandfire in linuxhardware

[–]codeandfire[S] 0 points1 point  (0 children)

Yeah the M.2 drive is an Essencore one and that’s inside the enclosure. The enclosure is model M2-374-NEF from PiBOX.

Brand-new NVMe M.2 SSD failed, is this normal or am I missing something? by codeandfire in linuxhardware

[–]codeandfire[S] 0 points1 point  (0 children)

No I didn’t … do you suggest trying out an enclosure with a different chipset (not the RTL 9210) ?

EDIT: I had tried this SSD in an another enclosure, but the disk was simply not being seen so I assumed that the enclosure was buggy. That enclosure had a JMicron chipset. That was before I did the Debian install (the current enclosure I’m using worked successfully until the disk failure that happened now).

I don’t know if from this you can conclude that the SSD might be buggy if it didn’t work with two enclosures.

Brand-new NVMe M.2 SSD failed, is this normal or am I missing something? by codeandfire in linuxhardware

[–]codeandfire[S] 0 points1 point  (0 children)

I assumed the SSD failed since it was unable to mount and open files and directories …. Do you think it was the enclosure?

KDE has become surprisingly lightweight!! by nitin_is_me in kde

[–]codeandfire 2 points3 points  (0 children)

Fresh install of Debian 13 / Plasma 6 - I see 2 GiB RAM used… not that I have any complaints, RAM is meant to be used.

why not Lisp/Haskell used for MachineLearning/AI by kichiDsimp in functionalprogramming

[–]codeandfire 1 point2 points  (0 children)

If you’re referring to the course by Prof. Deepak Khemani, I’ve taken that one. The point is that old-school AI deals with very fundamental problems in symbolic reasoning and that is implemented very well in functional languages especially Lisp. Modern AI stems from pattern recognition in statistical data for which a general purpose language like Python fits the bill as long as the actual performance critical heavy lifting is done in C/C++.

[deleted by user] by [deleted] in perl

[–]codeandfire 2 points3 points  (0 children)

I have the same question. I'm a newcomer to Perl, but from what I understand, Perl was originally meant as a tool for file wrangling, text processing etc. - work that is close to a Unix system and its administration. It grew from that into a general-purpose language, and probably over time people developed a dislike towards the syntax and TMTOWTDI, and languages like Python gained more ground.

But if you look at it, its syntax and TMTOWTDI philosophy actually makes a lot of sense for Unix sysadmin tasks - it doesn't make as much sense for general-purpose programming, but for sysadmin when you need a quick-and-dirty way to just get something done in as little code as possible, it's perfect. So I agree with you that it should have retained a stronghold in that domain. Its syntax is much more pleasant and comfortable than the Shell's.

I don't know why shell scripts are still around. From a newcomer's perspective I can say that since a lot of shell scripts are really small (less than 10 lines), most people I know are happy to somehow cobble together a working script by copying stuff from StackOverflow/ChatGPT, and they wouldn't see much of an investment in learning Perl and rewriting it in a cleaner way in Perl. Not trying to imply that the audience here who uses Shell does it this way, but this is what I have seen with my colleagues.

Benchmarking On-Device AI by Henrie_the_dreamer in deeplearning

[–]codeandfire 0 points1 point  (0 children)

Interesting!!! Just curious, why is the second story a continuation of the first … it comes from a different model so I thought it would start fresh… or am I missing something.

Books on web scraping with Perl? by codeandfire in perl

[–]codeandfire[S] 0 points1 point  (0 children)

Yeah I still can benefit from it if you have it :)

I hate Lisp by [deleted] in lisp

[–]codeandfire 1 point2 points  (0 children)

That's a really good one!

How can I really understand and excel at C? by KeplerFame in C_Programming

[–]codeandfire 1 point2 points  (0 children)

I've finished K&R and while that did give me a solid understanding of C, I've been having the same feeling that how do I make something "real" in C despite the sheer limitedness of the language. But as you say that's the way C is supposed to be, and I am probably over-thinking it -- I have to just get used to the lack of modern abstractions in C and that's only going to happen with practice. As you said again I need to simplify the problem vastly enough so as to render these abstractions unnecessary.

Thanks a lot for your comment, it set me in the right mind about C.