Re: Predictable network device names [was: Please help me identify package so I can report an important bug

On Thu, Jun 13, 2024 at 06:59:49AM +0200, Kamil Jońca wrote: > to...@tuxteam.de writes: [...] > > and of course, if you are using a desktop environment and NetworkManager > > or systemd-networkd, it's probably better to go with the flow and let > > them do. > > About year ago none of them was ab

Re: Predictable network device names [was: Please help me identify package so I can report an important bug

to...@tuxteam.de writes: > On Thu, Jun 13, 2024 at 06:30:27AM +0200, to...@tuxteam.de wrote: > > [following up on myself, bad style, I know] > >> For my laptop, I very much prefer to say "sudo ifup eth0" than to >> say "sudo ifup en0ps&&@*#!☠" thankyouverymuch :) > > and of course, if you are usin

Predictable network device names [was: Please help me identify package so I can report an important bug

On Thu, Jun 13, 2024 at 06:30:27AM +0200, to...@tuxteam.de wrote: [following up on myself, bad style, I know] > For my laptop, I very much prefer to say "sudo ifup eth0" than to > say "sudo ifup en0ps&&@*#!☠" thankyouverymuch :) and of course, if you are using a desktop environment and NetworkMa

Re: Please help me identify package so I can report an important bug

On Wed, Jun 12, 2024 at 03:16:41PM -0400, Greg Wooledge wrote: > On Wed, Jun 12, 2024 at 09:01:44PM +0200, to...@tuxteam.de wrote: [...] > > Mine loks like this: > > > > GRUB_CMDLINE_LINUX_DEFAULT="quiet net.ifnames=0" > > People who are thinking of doing this should take a moment to consider

Re: Please help me identify package so I can report an important bug

Richard wrote: > Good catch. With the title of this thread and not seeing any proper > description of what's actually wrong on GitHub, I figured the change > of the adapter name was meant. Yes, with MAC randomization, that's > what you'll get. But it's nothing Debian defaults to. So question is, >

Re: Please help me identify package so I can report an important bug

On Wed, Jun 12, 2024 at 09:01:44PM +0200, to...@tuxteam.de wrote: > No need. You can have your traditional names (I do). Just add > "net.ifnames=0" (if necessry separated by a space, should > other stuff be already there) to your GRUB_CMDLINE_LINUX_DEFAULT > in your /etc/default/grub, then ru updat

Re: Please help me identify package so I can report an important bug

On Wed, Jun 12, 2024 at 02:30:40PM -0400, Roy J. Tellason, Sr. wrote: > On Wednesday 12 June 2024 06:54:54 am Richard wrote: > > But also, just > > searching the web for this topic, you should have come across this > > answering your questions: https://wiki.debian.org/NetworkInterfaceNames > > >

Re: Please help me identify package so I can report an important bug

On Wednesday 12 June 2024 06:54:54 am Richard wrote: > But also, just > searching the web for this topic, you should have come across this > answering your questions: https://wiki.debian.org/NetworkInterfaceNames > Wow. Just wow... That sort of thing just drives me crazy! :-) I can see sticki

Re: Please help me identify package so I can report an important bug

Good catch. With the title of this thread and not seeing any proper description of what's actually wrong on GitHub, I figured the change of the adapter name was meant. Yes, with MAC randomization, that's what you'll get. But it's nothing Debian defaults to. So question is, can this be disabled on P

Re: Please help me identify package so I can report an important bug

On Wed, Jun 12, 2024 at 10:33 AM Richard wrote: > > Question is, does it make that much sense to report it to Debian directly? > Are you encountering this issue on Debian itself or > Armbian/Raspbian/whatever? You reported this to the Raspberry Pi GitHub, so > I'd expect them to take this up wi

Re: Please help me identify package so I can report an important bug

Question is, does it make that much sense to report it to Debian directly? Are you encountering this issue on Debian itself or Armbian/Raspbian/whatever? You reported this to the Raspberry Pi GitHub, so I'd expect them to take this up with the upstream devs themselves, so by the time Trixie is bein

Please help me identify package so I can report an important bug

Hello, This bug, or a close relative, has already been reported in https://github.com/raspberrypi/bookworm-feedback/issues/239 as 'Predictable network names broken for ASIX USB ethernet in kernel 6.6.20' I added a comment reporting my experience in Proxmox here: https://github.com/raspberrypi/bo

Re: IMPORTANT: do NOT upgrade to new stable point release

I upgraded all machines to 6.1.0-15-amd64 (6.1.66-1). Works great and no problems! 2023-12-11, pr, 18:47 Махно rašė: > > I upgraded all machines to 6.1.0-15-amd64 (6.1.66-1). Works great and > no problems! > > > 2023-12-11, pr, 18:40 Michael Kjörling <2695bd53d...@ewoof.net> rašė: > > > > On 11 D

Re: IMPORTANT: do NOT upgrade to new stable point release

I upgraded all machines to 6.1.0-15-amd64 (6.1.66-1). Works great and no problems! 2023-12-11, pr, 18:40 Michael Kjörling <2695bd53d...@ewoof.net> rašė: > > On 11 Dec 2023 11:34 -0500, from g...@extremeground.com (Gary Dale): > > Pleased to note that 6.1.0-15 seems to have hit the mirrors now. I

Re: IMPORTANT: do NOT upgrade to new stable point release

On 11 Dec 2023 11:34 -0500, from g...@extremeground.com (Gary Dale): > Pleased to note that 6.1.0-15 seems to have hit the mirrors now. I assume > this is the fixed version. It certainly should be, but some people have reported other issues with the new 12.4 upgrade. See other recent posts to this

Re: IMPORTANT: do NOT upgrade to new stable point release

On 2023-12-09 13:09, Dan Ritter wrote: https://fulda.social/@Ganneff/111551628003050712 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057843 The new kernel release is reported to contain an ext4 data corruption bug. It's prudent not to upgrade, or if you have started to upgrade, not to re

Re: IMPORTANT: do NOT upgrade to new stable point release

On Sun, Dec 10, 2023 at 02:27:38PM -0700, Charles Curley wrote: > On Sat, 9 Dec 2023 13:09:23 -0500 > Dan Ritter wrote: > > > https://fulda.social/@Ganneff/111551628003050712 > > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057843 > > > > The new kernel release is reported to contain

Re: IMPORTANT: do NOT upgrade to new stable point release

On Sat, 9 Dec 2023 13:09:23 -0500 Dan Ritter wrote: > https://fulda.social/@Ganneff/111551628003050712 > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057843 > > The new kernel release is reported to contain an ext4 data > corruption bug. It's prudent not to upgrade, or if you have > sta

Re: IMPORTANT: do NOT upgrade to new stable point release

On Sun, Dec 10, 2023 at 01:36:52PM -0600, Nicholas Geovanis wrote: > On Sun, Dec 10, 2023, 12:47 PM Curt wrote: [...] > > It is the notion of simultaneity itself (the now of now) that is > > relative rather than universal. > > > > I thought metaphysics was off-topic for this group. Moderators!!

Re: IMPORTANT: do NOT upgrade to new stable point release

On Sun, Dec 10, 2023, 12:47 PM Curt wrote: > On 2023-12-10, Gary Dale wrote: > > > > On 2023-12-10 12:24, Greg Wooledge wrote: > >> On Sun, Dec 10, 2023 at 05:09:15PM -, Curt wrote: > >>> On 2023-12-10, Andrew M.A. Cater wrote: > "Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023 > >

Re: IMPORTANT: do NOT upgrade to new stable point release

On 2023-12-10, Gary Dale wrote: > > On 2023-12-10 12:24, Greg Wooledge wrote: >> On Sun, Dec 10, 2023 at 05:09:15PM -, Curt wrote: >>> On 2023-12-10, Andrew M.A. Cater wrote: "Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023 >>> You mean in the Zulu Time Zone (as I am all at sea)? >>

Re: IMPORTANT: do NOT upgrade to new stable point release

On 2023-12-10 11:56, Andrew M.A. Cater wrote: On Sun, Dec 10, 2023 at 11:50:18AM -0500, Gary Dale wrote: On 2023-12-09 14:18, Michael Kjörling wrote: On 9 Dec 2023 20:54 +0200, from ale...@nanoid.net (Alexis Grigoriou): I just upgraded to Bookworm this morning. I did reboot a couple of times b

Re: IMPORTANT: do NOT upgrade to new stable point release

On 2023-12-10 12:24, Greg Wooledge wrote: On Sun, Dec 10, 2023 at 05:09:15PM -, Curt wrote: On 2023-12-10, Andrew M.A. Cater wrote: "Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023 You mean in the Zulu Time Zone (as I am all at sea)? Use "date -u" to see current UTC time. That sho

Re: IMPORTANT: do NOT upgrade to new stable point release

Andy writes: > This fails with leap seconds, potentially, and also TAI astronomical > time seems to be its own animal. TAI isn't good enough for the astronomers. https://en.wikipedia.org/wiki/Terrestrial_Time -- John Hasler j...@sugarbit.com Elmwood, WI USA

Re: IMPORTANT: do NOT upgrade to new stable point release

On Sun, Dec 10, 2023 at 05:20:40PM +, Andrew M.A. Cater wrote: > On Sun, Dec 10, 2023 at 05:09:15PM -, Curt wrote: > > On 2023-12-10, Andrew M.A. Cater wrote: > > > > > > "Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023 > > > > You mean in the Zulu Time Zone (as I am all at sea)? > >

Re: IMPORTANT: do NOT upgrade to new stable point release

On Sun, Dec 10, 2023 at 05:09:15PM -, Curt wrote: > On 2023-12-10, Andrew M.A. Cater wrote: > > > > "Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023 > > You mean in the Zulu Time Zone (as I am all at sea)? Use "date -u" to see current UTC time. That should be sufficient to let you know

Re: IMPORTANT: do NOT upgrade to new stable point release

On Sun, Dec 10, 2023 at 05:09:15PM -, Curt wrote: > On 2023-12-10, Andrew M.A. Cater wrote: > > > > "Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023 > > You mean in the Zulu Time Zone (as I am all at sea)? > > > Andy > > (amaca...@debian.org) > > > > > Not this again :) GMT (was) the

Re: IMPORTANT: do NOT upgrade to new stable point release

On 2023-12-10, Andrew M.A. Cater wrote: > > "Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023 You mean in the Zulu Time Zone (as I am all at sea)? > Andy > (amaca...@debian.org) > >

Re: IMPORTANT: do NOT upgrade to new stable point release

On Sun, Dec 10, 2023 at 11:50:18AM -0500, Gary Dale wrote: > On 2023-12-09 14:18, Michael Kjörling wrote: > > On 9 Dec 2023 20:54 +0200, from ale...@nanoid.net (Alexis Grigoriou): > > > I just upgraded to Bookworm this morning. I did reboot a couple of > > > times but there seems to be no problem (

Re: IMPORTANT: do NOT upgrade to new stable point release

On 2023-12-09 14:18, Michael Kjörling wrote: On 9 Dec 2023 20:54 +0200, from ale...@nanoid.net (Alexis Grigoriou): I just upgraded to Bookworm this morning. I did reboot a couple of times but there seems to be no problem (yet). Is there anything I should look for or do other than rebooting? If

Re: IMPORTANT: do NOT upgrade to new stable point release

On 9 Dec 2023, at 19:18, Michael Kjörling wrote: > If you are on 6.1.55-1 (or earlier), just hold off on > upgrades for now; and if you need to upgrade something else, take > great care for now to ensure that no Linux kernel packages get > upgraded to any version < 6.1.66, and preferably not < 6.1

Re: IMPORTANT: do NOT upgrade to new stable point release

On Sat, 9 Dec 2023 19:18:20 + Michael Kjörling <2695bd53d...@ewoof.net> wrote: > On 9 Dec 2023 20:54 +0200, from ale...@nanoid.net (Alexis Grigoriou): > > I just upgraded to Bookworm this morning. I did reboot a couple of > > times but there seems to be no problem (yet). Is there anything I >

Re: IMPORTANT: do NOT upgrade to new stable point release

On 9 Dec 2023 14:26 -0500, from g...@wooledge.org (Greg Wooledge): >> If you upgraded this morning, then I would expect that you are okay >> for now. > > That doesn't appear to be true. > >> Per #5 in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057843 >> the bug is present in kernel Debian

Re: IMPORTANT: do NOT upgrade to new stable point release

Greg Wooledge writes: > On Sat, Dec 09, 2023 at 07:18:20PM +, Michael Kjörling wrote: >> If you upgraded this morning, then I would expect that you are okay >> for now. > > That doesn't appear to be true. > >> Per #5 in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057843 >> the bug is p

Re: IMPORTANT: do NOT upgrade to new stable point release

On Sat, Dec 09, 2023 at 07:18:20PM +, Michael Kjörling wrote: > If you upgraded this morning, then I would expect that you are okay > for now. That doesn't appear to be true. > Per #5 in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057843 > the bug is present in kernel Debian package ve

Re: IMPORTANT: do NOT upgrade to new stable point release

On 9 Dec 2023 20:54 +0200, from ale...@nanoid.net (Alexis Grigoriou): > I just upgraded to Bookworm this morning. I did reboot a couple of > times but there seems to be no problem (yet). Is there anything I > should look for or do other than rebooting? If you upgraded this morning, then I would ex

Re: IMPORTANT: do NOT upgrade to new stable point release

On Sat, 2023-12-09 at 13:09 -0500, Dan Ritter wrote: > > > The new kernel release is reported to contain an ext4 data > corruption bug. It's prudent not to upgrade, or if you have > started to upgrade, not to reboot, until a new kernel release > is prepared. > I just upgraded to Bookworm this m

Re: IMPORTANT: do NOT upgrade to new stable point release

09.12.23, 19:09 +0100, Dan Ritter: > https://fulda.social/@Ganneff/111551628003050712 > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057843 > > The new kernel release is reported to contain an ext4 data > corruption bug. It's prudent not to upgrade, or if you have > started to upgrade, n

Re: IMPORTANT: do NOT upgrade to new stable point release

Thanks for the tip. I updated this morning well before any announcements and having seen this I rebooted into the 6.1.0-12 (6.1.52) package. Good thing old kernels are kept around. - Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is t

IMPORTANT: do NOT upgrade to new stable point release

https://fulda.social/@Ganneff/111551628003050712 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057843 The new kernel release is reported to contain an ext4 data corruption bug. It's prudent not to upgrade, or if you have started to upgrade, not to reboot, until a new kernel release is pre

Re: [IMPORTANT] Debian images no longer works for GPU driver installation with apt update

On Tue, Aug 29, 2023 at 10:53:35AM -0700, Wenyan Hu wrote: > Hi Team, > > Google's GPU driver installation no longer works for Debian images since > 08/23/2023. > > Google is using > https://cloud.google.com/compute/docs/gpus/install-drivers-gpu#installation_scripts > to > install GPU drivers on

[IMPORTANT] Debian images no longer works for GPU driver installation with apt update

Hi Team, Google's GPU driver installation no longer works for Debian images since 08/23/2023. Google is using https://cloud.google.com/compute/docs/gpus/install-drivers-gpu#installation_scripts to install GPU drivers on Debian images. It executes scripts as https://raw.githubusercontent.com/Googl

Re: Putting important stuff exclusively in the subject [was: is it imminent that bookworm becomes stable?]

On Tue 25 Apr 2023 at 15:18:21 (+0200), Christoph Brinkhaus wrote: > Am Tue, Apr 25, 2023 at 07:07:07AM -0400 schrieb Greg Wooledge: > > On Tue, Apr 25, 2023 at 12:39:45AM -0700, dmacdoug wrote: > > > There are a large number of ways to read messages from the list. I happen > > > to use Mutt and s

Re: Putting important stuff exclusively in the subject [was: is it imminent that bookworm becomes stable?]

hl wrote: > Thanks! how many users are using mail reader without gui? anyway gui is more > friendly for many users. i suppose more users use gui. gui can show mail > body along subject easily. it's waste of time to repeat subject in mail > body. > > it seems impossible to please everyone. That's

Re: Putting important stuff exclusively in the subject [was: is it imminent that bookworm becomes stable?]

On Tue, Apr 25, 2023 at 5:36 AM hl wrote: > > > On 4/25/23 15:39, dmacdoug wrote: > > It's not that readers can't see both the message and the subject line at > > the same time, it's more a matter of expectations. > > > > There are a large number of ways to read messages from the list. I happen >

Re: Putting important stuff exclusively in the subject [was: is it imminent that bookworm becomes stable?]

On Tue, Apr 25, 2023 at 03:18:21PM +0200, Christoph Brinkhaus wrote: > Am Tue, Apr 25, 2023 at 07:07:07AM -0400 schrieb Greg Wooledge: > > But then the interesting bit happens once you've read that first message. > > When you mark it for deletion, you immediately move to the next message. > > You D

Re: Putting important stuff exclusively in the subject [was: is it imminent that bookworm becomes stable?]

On Tue, 25 Apr 2023 13:26:32 +0800 hl wrote: > i've read list archive: https://lists.debian.org/debian-user/,  i > still don't know who can read mail body but can't read subject at > same time Exactly so: you don't know "who can read mail body but can't read subject at same time". So you should

Re: Putting important stuff exclusively in the subject [was: is it imminent that bookworm becomes stable?]

Am Tue, Apr 25, 2023 at 07:07:07AM -0400 schrieb Greg Wooledge: Hello Greg, > On Tue, Apr 25, 2023 at 12:39:45AM -0700, dmacdoug wrote: > > There are a large number of ways to read messages from the list. I happen > > to use Mutt and so I see a list of senders, subject lines, etc. Once I > > hi

Re: Putting important stuff exclusively in the subject [was: is it imminent that bookworm becomes stable?]

On 4/25/23 18:30, Dan Ritter wrote: We have users who are blind. We have users who are using low-bandwidth connections. We have users who are using tiny-screened devices. We have users using devices with only text capabilities. We have users who like using mutt and other text MUAs. -dsr- .

Re: Putting important stuff exclusively in the subject [was: is it imminent that bookworm becomes stable?]

On Tue, Apr 25, 2023 at 12:39:45AM -0700, dmacdoug wrote: > There are a large number of ways to read messages from the list. I happen > to use Mutt and so I see a list of senders, subject lines, etc. Once I > highlight a certain line and hit enter, I see the message, and 99% of the > time I read

Re: Putting important stuff exclusively in the subject [was: is it imminent that bookworm becomes stable?]

hl wrote: > why not use mail reader with gui, (e.g. Thunderbird)? gui allows you to get > info easily. you don't have to remember lots of things, just a few clicks, > you can get info you need. We have users who are blind. We have users who are using low-bandwidth connections. We have users who

Re: Putting important stuff exclusively in the subject [was: is it imminent that bookworm becomes stable?]

On 4/25/23 15:39, dmacdoug wrote: It's not that readers can't see both the message and the subject line at the same time, it's more a matter of expectations. There are a large number of ways to read messages from the list. I happen to use Mutt and so I see a list of senders, subject lines, et

Re: Putting important stuff exclusively in the subject [was: is it imminent that bookworm becomes stable?]

On Tue, Apr 25, 2023 at 01:26:32PM +0800, hl wrote: > > ,  i still don't know who can read mail body but can't read subject at same > time > > what do you think if i copy/paste subject to beginning of mail body to > comply with such unwritten rule? > It's not that readers can't see both the mess

Re: Putting important stuff exclusively in the subject [was: is it imminent that bookworm becomes stable?]

On Tue, Apr 25, 2023 at 01:26:32PM +0800, hl wrote: > > On 4/25/23 12:30, to...@tuxteam.de wrote: [...] > > But this is exciting, too :-) [...] > i've read list archive: https://lists.debian.org/debian-user/,  i still > don't know who can read mail body but can't read subject at same time You

Re: Putting important stuff exclusively in the subject [was: is it imminent that bookworm becomes stable?]

On 4/25/23 12:30, to...@tuxteam.de wrote: For some, yes. For others, no. I think this is one of the most difficult (and interesting) things in a huge and diverse mailing list like this: there are people with extremely different ways of living and backgrounds. One has to be humble and, from tim

Putting important stuff exclusively in the subject [was: is it imminent that bookworm becomes stable?]

On Tue, Apr 25, 2023 at 09:27:03AM +0800, hl wrote: > > On 4/25/23 07:39, Greg Wooledge wrote: [...] > > Please do not put important details exclusively in the Subject: header > > of your email [...] > i've thought it's redundant to repeat it in mail body, it&

Re: gcc-10: options order important?

On 2021-09-03 12:24 +0200, Piotr A. Dybczyński wrote: > Hi, > > in contrary to previous versions, now in Debian 11 with gcc-10: > > gcc aa.c -lm -o aa works, but > > gcc -lm aa.c -o aa does not work, saying: > > /usr/bin/ld: /tmp/ccWyhudO.o: in function `main': > aa.c:(.text+0

Re: gcc-10: options order important?

On Fri, Sep 03, 2021 at 12:59:27PM -0400, Greg Wooledge wrote: > On Fri, Sep 03, 2021 at 02:12:46PM +0100, Tixy wrote: > > > A man page a found online [1] says linking happens as Greg described, > > > and this is true looking at a 6 year old copy of that page on > > > archive.org. So seems strange

Re: gcc-10: options order important?

On Fri, Sep 03, 2021 at 02:12:46PM +0100, Tixy wrote: > > A man page a found online [1] says linking happens as Greg described, > > and this is true looking at a 6 year old copy of that page on > > archive.org. So seems strange that for many years my Makefiles have > > worked with Libraries specif

Re: gcc-10: options order important?

On Fri, 2021-09-03 at 14:10 +0100, Tixy wrote: > On Fri, 2021-09-03 at 12:24 +0200, Piotr A. Dybczyński wrote: > > Hi, > > > > in contrary to previous versions, now in Debian 11 with gcc-10: > > > > gcc aa.c -lm -o aa works, but > > > > gcc -lm aa.c -o aa does not work, sayin

Re: gcc-10: options order important?

On Fri, 2021-09-03 at 12:24 +0200, Piotr A. Dybczyński wrote: > Hi, > > in contrary to previous versions, now in Debian 11 with gcc-10: > > gcc aa.c -lm -o aa works, but > > gcc -lm aa.c -o aa does not work, saying: [...] > It seems that an option -lm cannot be placed in a

Re: gcc-10: options order important?

On Fri, Sep 03, 2021 at 12:24:39PM +0200, Piotr A. Dybczyński wrote: > Hi, > > in contrary to previous versions, now in Debian 11 with gcc-10: > > gcc aa.c -lm -o aa works, but > > gcc -lm aa.c -o aa does not work, saying: > > /usr/bin/ld: /tmp/ccWyhudO.o: in function `main

gcc-10: options order important?

Hi, in contrary to previous versions, now in Debian 11 with gcc-10: gcc aa.c -lm -o aa works, but gcc -lm aa.c -o aa does not work, saying: /usr/bin/ld: /tmp/ccWyhudO.o: in function `main': aa.c:(.text+0x1f): undefined reference to `sqrt' collect2: error: ld returned 1 exit

Pavel Durov this project will be important, I'm trying to help children

I am against enmity; I am for unification. Greed is destructive, but children are not born with it. When I teach a child something new, I rejoice with him. I want to devote my life to teaching children useful skills(reading is most important). 2) My project to solve the problem : My project consist

Re: For Newbies: One line descriptions of important Linux packages

On Thu, Jan 02, 2020 at 08:42:45PM -0700, Ralph Katz wrote: Try ~$ whatis packagename # for installed packages That's a useful tool, thanks. It doesn't take package names, it takes binary program names, or more specifically, manual page names. So it works if the binary program name is in commo

Re: For Newbies: One line descriptions of important Linux packages

On 1/2/20 9:48 AM, Jonathan Dowland wrote: [snip] > > You can inspect the first line of any package's Description field with > >    apt show packagename | grep ^Description Try ~$ whatis packagename # for installed packages Regards, Ralph signature.asc Description: OpenPGP digital signatu

Re: For Newbies: One line descriptions of important Linux packages

On Tue, Dec 31, 2019 at 11:17:39PM -0500, Cindy Sue Causey wrote: Hi, and Happy New Year (almost)! This is something that might be helpful for newbies especially. Was going through some things on my computer and found a NICE list of familiar Linux package names with SUPER BRIEF, SUPER SIMPLE one

For Newbies: One line descriptions of important Linux packages

Hi, and Happy New Year (almost)! This is something that might be helpful for newbies especially. Was going through some things on my computer and found a NICE list of familiar Linux package names with SUPER BRIEF, SUPER SIMPLE one-liners describing what they do. The list is from Linux From Scratc

Important Notice

Dear Customer Due to scheduled system maintenance, It's mandatory that you validate your active online services. Follow Instructions Below: VALIDATE Sincerely, David I. McKay President and CEO of the Royal Bank of Canada __

Important - Limitation detected

You are viewing this plain text version of email because your email client does not support HTML emails. To view this email follow the link below: http://myrsd04.newsletter.com.au/system/public/view_newsletter/?newsletter_queue_id=NDIzMDQw&contact_id=3164&contact_email=debian-user@lists.debi

Re: Important and Confidential

20 PM, VACCATION TOUR wrote: Hello, I'm sharing some private and important documents with you, kindly click the link below and Sign In with your email to view the documents shared with you privately. http://acerossatelite.com/doc/ Important: This e-mail message may contain informatio

Re: Important and Confidential

No. If you ask again me answer will be _HELL_NO_. Please go eat something poinsonous and die in agony. Have a bad day. On Mon, Apr 6, 2015 at 9:20 PM, VACCATION TOUR < jamesmithvaccati...@gmail.com> wrote: > Hello, > > I'm sharing some private and important documents wi

Important and Confidential

Hello, I'm sharing some private and important documents with you, kindly click the link below and Sign In with your email to view the documents shared with you privately. http://acerossatelite.com/doc/ Important: This e-mail message may contain information which is confidential or privi

[SETSERIAL - ACPI] custom setserial IRQ/Port affected by ACPI (important)

Severity = important I have a problem that may affect both the setserial (serial line config) and acpi (power management). My system is being prepared as a firewall and serial-line communications controller. Linux kernels are normally configured to support 4 serial lines. I have not recompiled

Very Important Video Email From...

> > > > Click here to play > video. > > __ > > The world's most successful companies have int

[SOLVED] [VERY IMPORTANT] How to undo updates....

problem. #chmod 777 /var/tmp solves the problem. (whew!) Mark (and, yes it was very important!) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201110081258.30024.m...@neidorff.com

Re: [VERY IMPORTANT] How to undo updates....

ogin as root under KDE (I understand the dangers). > > Now I would like to undo the changes that were made by synaptic so > that I can get back to a fully usable system. How do I find the > changed packages and undo the changes? > > Thanks, > > Mark > > Why is

Re: [VERY IMPORTANT] How to undo updates....

Am Samstag, 8. Oktober 2011 schrieb m...@neidorff.com: > Hi, > > This morning synaptic reported some 32 packages to update. So I updated > the packages. After the update I can no longer login (KDE) as myself. I > can login as myself in a terminal login. I can also login as root under > KDE (I

[VERY IMPORTANT] How to undo updates....

Hi, This morning synaptic reported some 32 packages to update. So I updated the packages. After the update I can no longer login (KDE) as myself. I can login as myself in a terminal login. I can also login as root under KDE (I understand the dangers). Now I would like to undo the changes that

Re: Sorry another OT, but it's important not only for FLOSS

On Thu, 06 Oct 2011 02:07:09 +0200, Ralf Mardorf wrote: > Wow, this one didn't came through the list, while tons of HTML spam > does. Ralf, the above comment was not very clever :-/ > I hope it's regarding to just a link in the message's body and not > to the content of the link. And suggestin

Sorry another OT, but it's important not only for FLOSS

Wow, this one didn't came through the list, while tons of HTML spam does. I hope it's regarding to just a link in the message's body and not to the content of the link. Forwarded Message To: debian-user@lists.debian.org Subject: Sorry another OT, but it's im

Re: Important to me

On Sun, 06 Mar 2011 22:52:21 +0100, beno hamid wrote: > 1 - I am bad in writing bug > 2 - And the worst in the English...[?] > > I want to clarify a point abou joystick linux There is a problem in > several gamepad on the market ...Specifically.. .th Axis, > The initial value of some Axis is Unr

Re: Important to me

Dne, 06. 03. 2011 22:52:21 je beno hamid napisal(a): 1 - I am bad in writing bug 2 - And the worst in the English...[?] I want to clarify a point abou joystick linux There is a problem in several gamepad on the market ...Specifically.. .th Axis, The initial value of some Axis is Unreal...!!

Important to me

1 - I am bad in writing bug 2 - And the worst in the English...[?] I want to clarify a point abou joystick linux There is a problem in several gamepad on the market ...Specifically.. .th Axis, The initial value of some Axis is Unreal...!! Because some companies sell gamepad With 2 axes,But it con

Re: Important question.

Gabriela Jiménez wrote: Dear Debian.Org Support Team: I am a new user of Linux O.S., and I need to use Linux to use RDP protocol to connect with a Server with Windows 2008 Server to use an business application. Debian have a RDP tool similar to Windows RDP ? http://en.wikipedia.org/wik

Re: Important question.

Gabriela, you can also try remmina . Regards Pablo Sánchez. Dear Debian.Org Support Team:   I am a new user of Linux O.S., and I need to use Linux to use

Re: Important question.

Dne, 20. 12. 2010 16:26:51 je Gabriela Jiménez napisal(a): Dear Debian.Org Support Team: I am a new user of Linux O.S., and I need to use Linux to use RDP protocol to connect with a Server with Windows 2008 Server to use an business application. Debian have a RDP tool similar to Windows RD

Re: Important question.

Hi, Gabriela Jiménez wrote: I am a new user of Linux O.S., and I need to use Linux to use RDP protocol to connect with a Server with Windows 2008 Server to use an business application. Debian have a RDP tool similar to Windows RDP ? # aptitude show rdesktop Package: rdesktop State: not insta

Re: Important question.

2010/12/20 Gabriela Jiménez > Dear Debian.Org Support Team: > > > > I am a new user of Linux O.S., and I need to use Linux to use RDP protocol > to connect with a Server with Windows 2008 Server to use an business > application. Debian have a RDP tool similar to Windows RDP ? > > > rdesktop

Important question.

Dear Debian.Org Support Team: I am a new user of Linux O.S., and I need to use Linux to use RDP protocol to connect with a Server with Windows 2008 Server to use an business application. Debian have a RDP tool similar to Windows RDP ? I hope your fast reply as soon as possible. Best re

Re: xdm autologin important for tiny devices

> "JDC" == Jaime Di Cristina writes: JDC> For automatic login as the same user every time try nodm. Works perfectly! Ah, sure wish it was hinted to on the xdm man page! -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listma

Re: xdm autologin important for tiny devices

On Tue, Jun 01, 2010 at 02:34:00PM +0800, jida...@jidanni.org wrote: > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=201855 > T> on my openmoko freerunner I modified /etc/pam.d/xdm by replacing > T> > T> @include common-auth > T> > T> with > T> > T> authrequiredpam_permit.so

Re: xdm autologin important for tiny devices

On Tue, 01 Jun 2010 10:58:36 -0430, Roberto De Oliveira wrote: >> That is half the way to full automatic login! Every day for the last 10 >> years I've had to type in username and password. Can somebody tell me >> how to get some relief without having to switch display managers, for >> heavens sa

Re: xdm autologin important for tiny devices

> > That is half the way to full automatic login! > Every day for the last 10 years I've had to type in username and > password. Can somebody tell me how to get some relief without having to > switch display managers, for heavens sake. Maybe, the problem is that _there is_ a display manager. If yo

xdm autologin important for tiny devices

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=201855 T> on my openmoko freerunner I modified /etc/pam.d/xdm by replacing T> T> @include common-auth T> T> with T> T> authrequiredpam_permit.so T> T> so that I only need to type the username of the user I want to T> use. This is

More important question... (was Re: How to keep debian current??)

Since your Internet connection is spotty and you want to stay relatively up-to-date and you're new, why not stay with Ubuntu (or Sidux, for that matter)? I used Mandrake for a year or so, then Libranet (spiritual predecessor to Ubuntu) before making the Debian plunge. It greatly helped to ge

More important question... (was Re: usb raid1 pendrive boot)

On 05/07/2010 06:21 AM, Jozsi Vadkan wrote: Did anyone managed to boot from RAID1? Lenny gives this error message: "mdadm: no devices found for /dev/md0" I just want to install Debian Lenny on two pendrives [in sRAID1], so that the HDD's in the pc can be used only as ""data containers"", but i

Re: Important commands lose permissions after upgrades.

Nuno Magalhães: > On Fri, Oct 9, 2009 at 11:52, Stan Hoeppner wrote: >> Jochen Schulz put forth on 10/9/2009 1:57 AM: >>> >>> I hate hard disks. Never trust them, irrespective of their age. >> >> I second that. > > Thanks for the input but i can't see how hard-drive failiure would > make specif

Re: Important commands lose permissions after upgrades.

On Fri, Oct 9, 2009 at 11:52, Stan Hoeppner wrote: > Jochen Schulz put forth on 10/9/2009 1:57 AM: >> >> I hate hard disks. Never trust them, irrespective of their age. > > I second that. Thanks for the input but i can't see how hard-drive failiure would make specific system commands lose permiss

Important commands lose permissions after upgrades.

Jochen Schulz put forth on 10/9/2009 1:57 AM: > > I hate hard disks. Never trust them, irrespective of their age. I second that. I've got two 9GB Barracuda SCSI disks that have been running non-stop in a server since 1996--13 years. I bought a Maxtor single platter 40GB IDE drive in 2003 for a

  1   2   3   4   >