Re: Why (not?) Mozilla [was: Refugee from [x]ubuntu, a few initial questions]

On Fri, Oct 11, 2024 at 03:00:06AM -0400, Jeffrey Walton wrote: [...] > You might like this one, too. Mozilla just bought an ad company and > cut-in code in Firefox for targeted advertising: "Privacy-Preserving" > Attribution: Mozilla Disappoints Us Yet Again, >

Re: Why (not?) Mozilla [was: Refugee from [x]ubuntu, a few initial questions]

On Fri, Oct 11, 2024 at 2:07 AM wrote: > > On Thu, Oct 10, 2024 at 04:55:28PM -0400, Jeffrey Walton wrote: > > [...] > > > Lol... That's been the course for years now. Mozilla almost lost their > > non-profit status because they were making so much money from their > > Google partnership: > >

Why (not?) Mozilla [was: Refugee from [x]ubuntu, a few initial questions]

On Thu, Oct 10, 2024 at 04:55:28PM -0400, Jeffrey Walton wrote: [...] > Lol... That's been the course for years now. Mozilla almost lost their > non-profit status because they were making so much money from their > Google partnership: >

Why (not?) Mozilla [was: Refugee from [x]ubuntu, a few initial questions]

On Thu, Oct 10, 2024 at 08:52:13PM +, Michael Kjörling wrote: > On 10 Oct 2024 20:47 +0200, from to...@tuxteam.de: > >>> ...however, Flatpak works fine on Debian and is a pretty neat way of > >>> getting very fresh versions of certain selected pieces of software, like > >>> Firefox (official Mo

Re: can you parse and "tail" at once? (and if you can't why not?)

Thank you very much, Greg! Since ".description" is constant (an extension used by youtube) I chose to go: ydx=".description" ydxL=${#ydx} ... yut=${yl:-${ydxL}} ... where yl is the line read in in the way you suggested. lbrtchx

Re: can you parse and "tail" at once? (and if you can't why not?)

Hello, On Mon, Oct 23, 2023 at 01:32:08AM +, Albretch Mueller wrote: > On 10/22/23, Andy Smith wrote: > > So you might consider telling us what you will do next with the > > suffix of each line. > > Now you have gone into mind reading mode. I've gone into "avoid the need for mind reading"

Re: Shell-script variable name case [WAS: Re: can you parse and "tail" at once? (and if you can't why not?)]

On 23/10/2023 10:56, David wrote: Hi, for your info, this convention is specified by POSIX: https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap08.html Which says: Environment variable names used by the utilities in the Shell and Utilities volume of POSIX.1-2017 consist sol

Shell-script variable name case [WAS: Re: can you parse and "tail" at once? (and if you can't why not?)]

On Mon, 23 Oct 2023 at 13:25, Eduardo M KALINOWSKI wrote: > On 22/10/2023 23:13, Greg Wooledge wrote: > > 2) All-caps variable name IFL. All-caps variable names are reserved, > >by convention, for environment variables (e.g. PATH) and special > >shell variables (e.g. IFS). > While I don

Re: can you parse and "tail" at once? (and if you can't why not?)

On 22/10/2023 23:13, Greg Wooledge wrote: 2) All-caps variable name IFL. All-caps variable names are reserved, by convention, for environment variables (e.g. PATH) and special shell variables (e.g. IFS). While I don't disagree with the suggestion of using lower case for variables (and

Re: can you parse and "tail" at once? (and if you can't why not?)

On Mon, Oct 23, 2023 at 01:21:43PM +0530, Pankaj Jangid wrote: > Another way to do it is, > > cat "${IFL}"| cut -d "/" -f7-|sed 's/.description//' > > because you already know the prefix, you can count the fields. So "-f7-" > i.e. 7 onwards. Then use sed to remove the extension. Whoops! I compl

Re: can you parse and "tail" at once? (and if you can't why not?)

Albretch Mueller writes: > After generating a file with lines of text, I have to: > 1) parse some of those lines based on a pattern I know (no regex > necessary, just a FS path) > 2) once parsed from those lines I need the last n characters only > I am trying to use a one liner like: > cat "

Re: can you parse and "tail" at once? (and if you can't why not?)

On Sun, Oct 22, 2023 at 10:13:26PM -0400, Greg Wooledge wrote: [...] Good points all over -- I envy your clarity. To drive home Greg's point about naming conventions a bit more: bash (in general, shells) have very little protection for mis-naming variables (you don' have to declare them, they ha

Re: can you parse and "tail" at once? (and if you can't why not?)

On Sun, Oct 22, 2023, 10:39 PM Albretch Mueller wrote: > OK, Greg's suggestion once again "made my day". > I know at some point I will have to code everything in some > programming language, but for now I will just get things done as > quickly as possible. > Also, Greg, please, I would like fo

Re: can you parse and "tail" at once? (and if you can't why not?)

On Mon, Oct 23, 2023 at 01:32:08AM +, Albretch Mueller wrote: > On 10/22/23, Andy Smith wrote: > > Most of the points Greg makes to you are matters of correctness, not > > matters of taste. > > that you called "matters of correctness" may be "visual things" to > other people. this is somethi

Re: can you parse and "tail" at once? (and if you can't why not?)

On 10/22/23, Andy Smith wrote: > So you might consider telling us what you will do next with the > suffix of each line. Now you have gone into mind reading mode. On 10/22/23, Andy Smith wrote: > Most of the points Greg makes to you are matters of correctness, not > matters of taste. that you

Re: can you parse and "tail" at once? (and if you can't why not?)

On 10/22/23 17:11, Andy Smith wrote: Hello, On Sun, Oct 22, 2023 at 08:50:55PM +, Albretch Mueller wrote: Greg, please, I would like for you to understand that it is not my intention to upset you about what you find visually upsetting. We have talked about that before. Most of the points

Re: can you parse and "tail" at once? (and if you can't why not?)

Hello, On Sun, Oct 22, 2023 at 08:50:55PM +, Albretch Mueller wrote: > Greg, please, I would like for you to understand that it is not my > intention to upset you about what you find visually upsetting. We > have talked about that before. Most of the points Greg makes to you are matters of co

Re: can you parse and "tail" at once? (and if you can't why not?)

OK, Greg's suggestion once again "made my day". I know at some point I will have to code everything in some programming language, but for now I will just get things done as quickly as possible. Also, Greg, please, I would like for you to understand that it is not my intention to upset you about

Re: can you parse and "tail" at once? (and if you can't why not?)

Hello, On Sun, Oct 22, 2023 at 04:33:12PM +, Albretch Mueller wrote: > After generating a file with lines of text, I have to: > 1) parse some of those lines based on a pattern I know (no regex > necessary, just a FS path) > 2) once parsed from those lines I need the last n characters only

Re: can you parse and "tail" at once? (and if you can't why not?)

On Sun, Oct 22, 2023 at 04:33:12PM +, Albretch Mueller wrote: > After generating a file with lines of text, I have to: > 1) parse some of those lines based on a pattern I know (no regex > necessary, just a FS path) > 2) once parsed from those lines I need the last n characters only > I am t

Re: can you parse and "tail" at once? (and if you can't why not?)

On Sun, Oct 22, 2023 at 04:33:12PM +, Albretch Mueller wrote: > I am trying to use a one liner like: > cat "${IFL}" | grep "${DESC_DIR}" | tail -c+$_DESC_DIR > but this one liner repeats the output and the tail Brevity is not the measure of goodness. When you write a shell script, it's *OK

Re: can you parse and "tail" at once? (and if you can't why not?)

On Sun, 22 Oct 2023 16:33:12 + Albretch Mueller wrote: > After generating a file with lines of text, I have to: > 1) parse some of those lines based on a pattern I know (no regex > necessary, just a FS path) > 2) once parsed from those lines I need the last n characters only > I am trying

can you parse and "tail" at once? (and if you can't why not?)

After generating a file with lines of text, I have to: 1) parse some of those lines based on a pattern I know (no regex necessary, just a FS path) 2) once parsed from those lines I need the last n characters only I am trying to use a one liner like: cat "${IFL}" | grep "${DESC_DIR}" | tail -c+

Re: Why or why not back up "/lost+found"

On Fri, 2023-08-11 at 14:45 +0200, to...@tuxteam.de wrote: > On Fri, Aug 11, 2023 at 01:30:13PM +0100, > debian-u...@howorth.org.uk wrote: > > [...] > > > One other consideration that I haven't seen mentioned elsewhere in > > this > > thread is what happens if you back up filesystems to filesyste

Re: Why or why not back up "/lost+found"

On Fri, Aug 11, 2023 at 01:30:13PM +0100, debian-u...@howorth.org.uk wrote: [...] > One other consideration that I haven't seen mentioned elsewhere in this > thread is what happens if you back up filesystems to filesystems? I never use the backup's medium top-level dir as a target. In my current

Re: Why or why not back up "/lost+found"

wrote: > On Thu, Aug 10, 2023 at 03:42:01PM -0400, Default User wrote: > > Hi! > > > > When backing up my system I have been using this exclusions list: > > > > /dev/* > > /proc/* > > /sys/* > > /tmp/* > > /run/* > > /mnt/* > > /media/* > > /lost+found > > > > There are many sources online tha

Re: Why or why not back up "/lost+found"

On Thu, Aug 10, 2023 at 03:42:01PM -0400, Default User wrote: > Hi! > > When backing up my system I have been using this exclusions list: > > /dev/* > /proc/* > /sys/* > /tmp/* > /run/* > /mnt/* > /media/* > /lost+found > > There are many sources online that suggest that "/lost+found" should be

Re: Why or why not back up "/lost+found"

On Thu, Aug 10, 2023 at 09:15:31PM -0400, Default User wrote: > Fortunately, since my lost+found directories are all empty, I have no > "raw material" to practice extraction on. There's no "extraction". If a file is there, it will be a file. It will have a meaningful owner, group and permission

Re: Why or why not back up "/lost+found"

/lost+found should be excluded, then shouldn't > > > > "lost+found" > > > > in > > > > any other directories be excluded from backups as well? Why/why > > > > not? > > > > > > > > > > Before anybody answ

Re: Why or why not back up "/lost+found"

On Thu 10 Aug 2023 at 15:52:02 (-0700), Bob McGowan wrote: > On 8/10/23 03:03 PM, Nicolas George wrote: > > Default User (12023-08-10): > > > > > And, if /lost+found should be excluded, then shouldn't "lost+found" > > > > > in any other

Re: Why or why not back up "/lost+found"

On 8/10/23 03:03 PM, Nicolas George wrote: Default User (12023-08-10): And, if /lost+found should be excluded, then shouldn't "lost+found" in any other directories be excluded from backups as well? Why/why not? Unfortunately, I regret to say that I did not find that the answer

Re: Why or why not back up "/lost+found"

On Fri, Aug 11, 2023 at 12:03:26AM +0200, Nicolas George wrote: > Default User (12023-08-10): > > > > And, if /lost+found should be excluded, then shouldn't "lost+found" > > > > in any other directories be excluded from backups as well? Why/why > >

Re: Why or why not back up "/lost+found"

Default User (12023-08-10): > > > And, if /lost+found should be excluded, then shouldn't "lost+found" > > > in any other directories be excluded from backups as well? Why/why > > > not? > Unfortunately, I regret to say that I did not find that the an

Re: Why or why not back up "/lost+found"

On Thu, 2023-08-10 at 21:45 +0200, Nicolas George wrote: > Default User (12023-08-10): > > And, if /lost+found should be excluded, then shouldn't "lost+found" > > in > > any other directories be excluded from backups as well? Why/why > > not? > >

Re: Why or why not back up "/lost+found"

Default User (12023-08-10): > And, if /lost+found should be excluded, then shouldn't "lost+found" in > any other directories be excluded from backups as well? Why/why not? Before anybody answers all your question, there is something that needs checking: Do you know what l

Why or why not back up "/lost+found"

why. I do not know if restoring /lost+found would mess up the file system, or is it simply "not necessary" to back up/restore /lost+found.  If backup/restore of /lost+found would not hurt anything, then why not always back it up for the sake of thoroughness, "just in case". Af

Re: Why start the first partition at 2 MIB, why not at any multiple of 4096 bytes ...

On 2020-09-11 07:21, David Wright wrote: On Thu 10 Sep 2020 at 16:15:05 (-0700), David Christensen wrote: On 2020-09-09 23:02, David wrote: On Thu, 10 Sep 2020 at 11:26, David Christensen wrote: On 2020-09-09 08:03, David Wright wrote: ... having been bitten by https://bugs.debian.org/cgi-b

Re: Why start the first partition at 2 MIB, why not at any multiple of 4096 bytes ...

On Fri 11 Sep 2020 at 13:03:44 (+1000), David wrote: > On Fri, 11 Sep 2020 at 08:30, David Christensen > wrote: > > On 2020-09-10 09:44, David Wright wrote: > > > > I don't like parted particularly, and don't know what "free" does. > > > Can you elucidate? > > > > $ man parted | grep -i free >

Re: Why start the first partition at 2 MIB, why not at any multiple of 4096 bytes ...

On Thu 10 Sep 2020 at 16:15:05 (-0700), David Christensen wrote: > On 2020-09-09 23:02, David wrote: > > On Thu, 10 Sep 2020 at 11:26, David Christensen > > wrote: > > > On 2020-09-09 08:03, David Wright wrote: > > > > > > ... having been bitten by > > > > https://bugs.debian.org/cgi-bin/bugrepo

Re: Why start the first partition at 2 MIB, why not at any multiple of 4096 bytes ...

On 2020-09-10 20:03, David wrote: On Fri, 11 Sep 2020 at 08:30, David Christensen... wrote: On 2020-09-10 09:44, David Wright wrote: I don't like parted particularly, and don't know what "free" does. Can you elucidate? $ man parted | grep -i free $ info --output=/dev/stdout --subnodes par

Re: Why start the first partition at 2 MIB, why not at any multiple of 4096 bytes ...

On Fri, 11 Sep 2020 at 09:15, David Christensen wrote: > On 2020-09-09 23:02, David wrote: > > parted /dev/disk/by-id/ata-ST3300622AS_ 'unit compact print > > free unit s print free unit b print free' > That parted(8) incantation has issues It works for me, but then again my disks are n

Re: Why start the first partition at 2 MIB, why not at any multiple of 4096 bytes ...

On Fri, 11 Sep 2020 at 08:30, David Christensen wrote: > On 2020-09-10 09:44, David Wright wrote: > > I don't like parted particularly, and don't know what "free" does. > > Can you elucidate? > > $ man parted | grep -i free > > $ info --output=/dev/stdout --subnodes parted | grep -i free > I al

Re: Why start the first partition at 2 MIB, why not at any multiple of 4096 bytes ...

On 2020-09-09 23:02, David wrote: On Thu, 10 Sep 2020 at 11:26, David Christensen wrote: On 2020-09-09 08:03, David Wright wrote: ... having been bitten by https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923561 I have a 300 GB drive that has been causing me some confusion. Did I elicit

Re: Why start the first partition at 2 MIB, why not at any multiple of 4096 bytes ...

On 2020-09-10 09:44, David Wright wrote: On Thu 10 Sep 2020 at 16:02:59 (+1000), David wrote: On Thu, 10 Sep 2020 at 11:26, David Christensen wrote: ,,, I'm not sure what to ask for in terms of the encryption: See cryptsetup(8) with the 'isLuks' action and/or the '-v' option. For exampl

Re: Why start the first partition at 2 MIB, why not at any multiple of 4096 bytes ...

On Thu 10 Sep 2020 at 16:02:59 (+1000), David wrote: > On Thu, 10 Sep 2020 at 11:26, David Christensen > wrote: > > On 2020-09-09 08:03, David Wright wrote: > > > > ... having been bitten by > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923561 > > > I have a 300 GB drive that has been

Re: Why start the first partition at 2 MIB, why not at any multiple of 4096 bytes ...

On Thu, 10 Sep 2020 at 11:26, David Christensen wrote: > On 2020-09-09 08:03, David Wright wrote: > > ... having been bitten by > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923561 > I have a 300 GB drive that has been causing me some confusion. Did I > elicity the bug when I partitione

Re: Why start the first partition at 2 MIB, why not at any multiple of 4096 bytes ...

On 2020-09-09 08:03, David Wright wrote: ... having been bitten by https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923561 I have a 300 GB drive that has been causing me some confusion. Did I elicity the bug when I partitioned the disk as follows? 2020-03-03 08:39:57 root@po ~ # pa

Re: Why start the first partition at 2 MIB, why not at any multiple of 4096 bytes ...

David Wright writes: > On Wed 09 Sep 2020 at 08:53:20 (-0600), Joe Pfeiffer wrote: >> rhkra...@gmail.com writes: >> > On Tuesday, September 08, 2020 04:39:05 PM David Christensen wrote: >> >> Neither the string "2 MiB" nor the string "2 M" appear on page you have >> >> cited. >> > >> > That is co

Re: Why start the first partition at 2 MIB, why not at any multiple of 4096 bytes ...

On Wed 09 Sep 2020 at 08:53:20 (-0600), Joe Pfeiffer wrote: > rhkra...@gmail.com writes: > > On Tuesday, September 08, 2020 04:39:05 PM David Christensen wrote: > >> Neither the string "2 MiB" nor the string "2 M" appear on page you have > >> cited. > > > > That is correct, that's is what I have no

Re: Why start the first partition at 2 MIB, why not at any multiple of 4096 bytes ...

rhkra...@gmail.com writes: > On Tuesday, September 08, 2020 04:39:05 PM David Christensen wrote: >> Neither the string "2 MiB" nor the string "2 M" appear on page you have >> cited. > > That is correct, that's is what I have not found on that page. > >> Please provide a URL that advocates "start

Re: Why start the first partition at 2 MIB, why not at any multiple of 4096 bytes ...

On Tue 08 Sep 2020 at 17:43:21 (-0400), rhkra...@gmail.com wrote: > On Tuesday, September 08, 2020 04:39:05 PM David Christensen wrote: > > Neither the string "2 MiB" nor the string "2 M" appear on page you have > > cited. > > That is correct, that's is what I have not found on that page. > > >

Re: Why start the first partition at 2 MIB, why not at any multiple of 4096 bytes ...

On 2020-09-08 14:43, rhkra...@gmail.com wrote: On Tuesday, September 08, 2020 04:39:05 PM David Christensen wrote: Neither the string "2 MiB" nor the string "2 M" appear on page you have cited. That is correct, that's is what I have not found on that page. Please provide a URL that advocat

Re: Why start the first partition at 2 MIB, why not at any multiple of 4096 bytes ...

On Tuesday, September 08, 2020 04:39:05 PM David Christensen wrote: > Neither the string "2 MiB" nor the string "2 M" appear on page you have > cited. That is correct, that's is what I have not found on that page. > Please provide a URL that advocates "start the first partition at 2 MIB" Maybe

Re: Why start the first partition at 2 MIB, why not at any multiple of 4096 bytes ...

On Tue, Sep 08, 2020 at 12:53:00PM -0400, rhkra...@gmail.com wrote: Why start the first partition at 2 MIB, why not at any multiple of 4096 bytes that leaves room for whatever may need to be at the beginning of the disk (like maybe the MBR, or LILO, or ???)? The current basic default is 1MByte

Re: Why start the first partition at 2 MIB, why not at any multiple of 4096 bytes ...

On Tuesday, September 08, 2020 12:53:00 PM rhkra...@gmail.com wrote: Why start the first partition at 2 MIB, why not at any multiple of 4096 bytes that leaves room for whatever may need to be at the beginning of the disk (like maybe the MBR, or LILO, or ???)? I've seen the advice to

Re: Why start the first partition at 2 MIB, why not at any multiple of 4096 bytes ...

On Tue, 2020-09-08 at 12:53 -0400, rhkra...@gmail.com wrote: > Why start the first partition at 2 MIB, why not at any multiple of 4096 bytes > that leaves room for whatever may need to be at the beginning of the disk > (like maybe the MBR, or LILO, or ???)? I believe it's for &#

Re: Why start the first partition at 2 MIB, why not at any multiple of 4096 bytes ...

Sorry, the Wikipedia article is Advanced Format: http://en.wikipedia.org/wiki/Advanced_Format On Tuesday, September 08, 2020 12:53:00 PM rhkra...@gmail.com wrote: > Why start the first partition at 2 MIB, why not at any multiple of 4096 > bytes that leaves room for whatever may need to be

Why start the first partition at 2 MIB, why not at any multiple of 4096 bytes ...

Why start the first partition at 2 MIB, why not at any multiple of 4096 bytes that leaves room for whatever may need to be at the beginning of the disk (like maybe the MBR, or LILO, or ???)? I've seen the advice to align partitions properly by starting them at a multiple of 4096 bytes,

Re: Why not include an update notifier in Xfce by default?

I gave it a spin in my head. Can PackageKit not be available on all architectures and is it a prerequisite? Regards.

Why not include an update notifier in Xfce by default?

Hi friends, Is there any reason not to include pk-update-icon in task-xfce-desktop? Being a desktop environment, it seems essential to have a notifier of security updates and patches, when not? I would like to have a default installation unattended in the hands of the user. My congratulations t

Re: Would you? Really? Why not? Dana

hellooo On Thursday, 17 August 2017, 0:54, Dana Alsaffdi wrote: Come to my embrace – we’ll talk http://bitly.com/2uOZdGs

Re: [OT] Why not gnome3 (with gnome-shell)?

Alan Chandler writes: > Now I've been running it for about a week I am really starting to like > it EXCEPT FOR ONE THING > > I really wish the hot spot for shrinking the desktop could be moved to > the bottom left. I keep accidentally using it when moving to the > browser back button. (DOES ANYO

Re: [OT] Why not gnome3 (with gnome-shell)?

* On 2011 05 Nov 11:56 -0500, Selim T. Erdogan wrote: > You probably don't mean this when you say "slow...locked up", I meant exactly that because that's exactly the experience I had with GNOME3 shell. I never got to the point of typing *anything* since I couldn't get it to open an application.

Re: [OT] Why not gnome3 (with gnome-shell)?

On 05/11/11 09:06, Javier Barroso wrote: On Fri, Nov 4, 2011 at 10:19 PM, Hugo Vanwoerkom wrote: Walter Hurry wrote: On Fri, 04 Nov 2011 13:27:01 -0600, Hugo Vanwoerkom wrote: GNOME Shell is the defining technology of the GNOME 3 user experience. That's exactly the problem, and precisely

Re: [OT] Why not gnome3 (with gnome-shell)?

Nate Bargmann, 5.11.2011: > > On a whim I installed GNOME 3 (shell and fallback) recently and gave it > a spin. Until I moved my xorg.conf out of the way both modes would fail > upon startup. When I did get them running the only possible > configuration for the second monitor is as an extended

Re: [OT] Why not gnome3 (with gnome-shell)?

* On 2011 05 Nov 07:18 -0500, Camaleón wrote: > On Sat, 05 Nov 2011 10:06:31 +0100, Javier Barroso wrote: > > So, why people is hungry with it ? > > (...) > > I think you wanted to say "angry", like the famous birds ;-) > > And yes, I feel more than angry when someone (or something) do not all

Re: [OT] Why not gnome3 (with gnome-shell)?

On Sat, 05 Nov 2011 10:06:31 +0100, Javier Barroso wrote: (good "Subject" election :-P) > Currently I'm using (as second main desktop, first is awesome ;) ) > gnome3. I can read a lot of criticism about it > > What don't you like ing GNOME 3 - GNOME - Shell? > > I only see two things, but peopl

Re: [OT] Why not gnome3 (with gnome-shell)?

On Sat, 05 Nov 2011 10:55:30 +0100, Javier Barroso wrote: (...) >> PD: I think it run fine in relatively old computers (but maybe that is >> another issue, I don't know) > PD2: Ok, I see you need 3d accel [1], not sense to me. > > [1] > http://live.gnome.org/GnomeShell/FAQ#What_led_to_the_decisi

Re: [OT] Why not gnome3 (with gnome-shell)?

On Sat, Nov 5, 2011 at 10:06 AM, Javier Barroso wrote: > On Fri, Nov 4, 2011 at 10:19 PM, Hugo Vanwoerkom wrote: >> Walter Hurry wrote: >>> >>> On Fri, 04 Nov 2011 13:27:01 -0600, Hugo Vanwoerkom wrote: >>> GNOME Shell is the defining technology of the GNOME 3 user experience. >>> >>> That's

[OT] Why not gnome3 (with gnome-shell)?

On Fri, Nov 4, 2011 at 10:19 PM, Hugo Vanwoerkom wrote: > Walter Hurry wrote: >> >> On Fri, 04 Nov 2011 13:27:01 -0600, Hugo Vanwoerkom wrote: >> >>> GNOME Shell is the defining technology of the GNOME 3 user experience. >> >> That's exactly the problem, and precisely why I have moved on to LXDE.

Re: Hash salt (was Re: BCRYPT - Why not using it?)

On Thu, Apr 07, 2011 at 01:31:27AM -0500, Ron Johnson wrote: > Having the first 3 characters all be "$6$" makes sense based upon > the explanation in your other email. I thought that was the salt. > Each user's salt is definitely different. Ah, those first 3 characters. Yeah, that tells you that

Re: Hash salt (was Re: BCRYPT - Why not using it?)

On 04/07/2011 01:20 AM, Aaron Toponce wrote: On Wed, Apr 06, 2011 at 11:52:04PM -0500, Ron Johnson wrote: Is the salt just bits that are either pre- or suffixed to your password before being run through the hashing function? The salt is generally appended to the password. For the specific case

Re: Hash salt (was Re: BCRYPT - Why not using it?)

On Wed, Apr 06, 2011 at 11:52:04PM -0500, Ron Johnson wrote: > Is the salt just bits that are either pre- or suffixed to your > password before being run through the hashing function? The salt is generally appended to the password. For the specific case of passwd(1), I'm not entirely sure, without

Re: Hash salt (was Re: BCRYPT - Why not using it?)

On Wed, Apr 06, 2011 at 06:37:38PM -1000, Joel Roth wrote: > So is the salt a fixed number of characters? From system to system, it varies. On my Fedora 14 virtual machine, it's 16 characters. On Debian 6.0 stable, it's 8. > Otherwise, how would a process know which portion of the > string is the

Re: Hash salt (was Re: BCRYPT - Why not using it?)

On Thu, Apr 07, 2011 at 06:52:42AM +0200, Martin Ågren wrote: > In this particular scheme, it appears ('foo','salt') has the same hash > as ('foosalt',''). In a serious application, hopefully the wheel > wouldn't be reinvented in this way, but some well-studied, thoroughly > scrutinized approach wo

Re: Hash salt (was Re: BCRYPT - Why not using it?)

Boyd Stephen Smith Jr.: > The salt is randomly generated each > time the password is set, and it (usually) different for each entry in > /etc/shadow. > > This increases the size of a rainbow table by a factor of 2^(bits in salt), > effectively stopping the attack for all but the most high-profile t

Re: Hash salt (was Re: BCRYPT - Why not using it?)

Aaron Toponce: > For example, say you have the hash 633427ee13ba83a92778c91a795d444564b9214c > (which actually isn't the encoded format as shown in /etc/shadow, but it > will illustrate the point). You don't know what salt was used to create > that hash. It's 160 bits, so it could be SHA1. Assuming

Re: Hash salt (was Re: BCRYPT - Why not using it?)

On 04/06/2011 10:40 PM, Boyd Stephen Smith Jr. wrote: In<4d9d1b22.2010...@cox.net>, Ron Johnson wrote: On 04/06/2011 08:19 PM, Aaron Toponce wrote: First, if you don't have the salt, but you do have the hash, then a rainbow table attack is completely pointless. The OS must store the salt some

Re: Hash salt (was Re: BCRYPT - Why not using it?)

On Wed, Apr 06, 2011 at 10:40:58PM -0500, Boyd Stephen Smith Jr. wrote: > In <4d9d1b22.2010...@cox.net>, Ron Johnson wrote: > >On 04/06/2011 08:19 PM, Aaron Toponce wrote: > >> First, if you don't have the salt, but you do have the hash, then a > >> rainbow table attack is completely pointless. > >

Re: Hash salt (was Re: BCRYPT - Why not using it?)

On Wed, Apr 06, 2011 at 09:02:10PM -0500, Ron Johnson wrote: > The OS must store the salt somewhere, in order to correctly > authenticate the user when he logs in. But I've never heard of > /etc/hashsalt so what am I misunderstanding? Yes, the salt and the password are both stored in the /etc/sha

Re: Hash salt (was Re: BCRYPT - Why not using it?)

In <4d9d1b22.2010...@cox.net>, Ron Johnson wrote: >On 04/06/2011 08:19 PM, Aaron Toponce wrote: >> First, if you don't have the salt, but you do have the hash, then a >> rainbow table attack is completely pointless. > >The OS must store the salt somewhere, in order to correctly authenticate >the us

Hash salt (was Re: BCRYPT - Why not using it?)

On 04/06/2011 08:19 PM, Aaron Toponce wrote: [snip] First, if you don't have the salt, but you do have the hash, then a rainbow table attack is completely pointless. Reason being is rainbow tables store hashes with a 1:1 ration to text. How the table is traversed is another story, but the fact r

Re: BCRYPT - Why not using it?

On Wed, Apr 06, 2011 at 06:18:45PM -0500, Ron Johnson wrote: > On 04/06/2011 01:42 PM, johhny_at_poland77 wrote: > >http://unix.stackexchange.com/questions/10326/does-openbsd-use-bcrypt-by-default > > > >Why doesn't every modern Linux Distribution use BCRYPT? > > > >http://codahale.com/how-to-safel

Re: BCRYPT - Why not using it?

On 04/06/2011 01:42 PM, johhny_at_poland77 wrote: http://unix.stackexchange.com/questions/10326/does-openbsd-use-bcrypt-by-default Why doesn't every modern Linux Distribution use BCRYPT? http://codahale.com/how-to-safely-store-a-password/ https://secure.wikimedia.org/wikipedia/en/wiki/Bcrypt

BCRYPT - Why not using it?

http://unix.stackexchange.com/questions/10326/does-openbsd-use-bcrypt-by-default Why doesn't every modern Linux Distribution use BCRYPT? http://codahale.com/how-to-safely-store-a-password/ https://secure.wikimedia.org/wikipedia/en/wiki/Bcrypt WHY -- To UNSUBSCRIBE, email to debian-user-r

Re: Empty password field for libuuid & Debian-exim - Why not a security risk?

On Thu, 2009-10-15 at 22:55 -0400, Dr. Mark A. Friedman wrote: > Upon installation, Debian includes users libuuid and Debian-exim in > /etc/shadow with an empty password field: > Which release do you use? I checked some of my systems, those accounts are locked (shadow have an exclamation mark in

Re: Empty password field for libuuid & Debian-exim - Why not a security risk?

On Thu, Oct 15, 2009 at 10:55:37PM -0400, Dr. Mark A. Friedman wrote: > Upon installation, Debian includes users libuuid and Debian-exim in > /etc/shadow with an empty password field: > > libuuid::14292:0:9:7::: > Debian-exim::14377:0:9:7::: > > Although Debian-exim specifies /bin/false a

Re: Empty password field for libuuid & Debian-exim - Why not a security risk?

Quoth Dr. Mark A. Friedman at 2009-10-16 13:25... > Upon installation, Debian includes users libuuid and Debian-exim in > /etc/shadow with an empty password field: > > libuuid::14292:0:9:7::: > Debian-exim::14377:0:9:7::: Interesting question. Can't answer it, but will recount a similar

Empty password field for libuuid & Debian-exim - Why not a security risk?

Upon installation, Debian includes users libuuid and Debian-exim in /etc/shadow with an empty password field: libuuid::14292:0:9:7::: Debian-exim::14377:0:9:7::: Although Debian-exim specifies /bin/false as a shell in /etc/passwd to eliminate login, libuuid does not: libuuid:x:100:101::/

Re: Why not thunderbird

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sam Leon wrote: > T o n g wrote: >> Hi, >> I know that thunderbird has been renamed to icedove in Debian. But for >> iceweasel, we can still type the command firefox, mozilla-firefox, or >> even mozilla and start it. >> So why icedove is not providing

Re: Why not thunderbird

T o n g wrote: Hi, I know that thunderbird has been renamed to icedove in Debian. But for iceweasel, we can still type the command firefox, mozilla-firefox, or even mozilla and start it. So why icedove is not providing the thunderbird command? thanks You can try making a link: ln -s /u

Why not thunderbird

Hi, I know that thunderbird has been renamed to icedove in Debian. But for iceweasel, we can still type the command firefox, mozilla-firefox, or even mozilla and start it. So why icedove is not providing the thunderbird command? thanks -- Tong (remove underscore(s) to reply) http://xpt.s

Re: why not compiled eagle adsl

On Fri, 19 Oct 2007 08:59:32 +0200 "abdelkader belahcene" <[EMAIL PROTECTED]> wrote: > Hi, > I want to install the eagle for usb adsl, but it requires the source of > kernel, > Why there is no compiled package as other softwares? Drivers (usually?) have to be compiled against particular kernels;

Re: why not compiled eagle adsl

abdelkader belahcene wrote: > Hi, > I want to install the eagle for usb adsl, but it requires the source of > kernel, > Why there is no compiled package as other softwares? > > With adsl thru ethernet there is no such problem. > > am I obligied to download (44 MB) and recompile the source kerne

Re: why not compiled eagle adsl

abdelkader belahcene: > > I want to install the eagle for usb adsl, but it requires the source of > kernel, > Why there is no compiled package as other softwares? I don't know the software, but my guess would be the reason is a problem with the license. Debian adheres to the DFSG (Debian Free Sof

why not compiled eagle adsl

Hi, I want to install the eagle for usb adsl, but it requires the source of kernel, Why there is no compiled package as other softwares? With adsl thru ethernet there is no such problem. am I obligied to download (44 MB) and recompile the source kernel to use my adsl ? thanks for help -- To

Re: xconsole 'can't open console' (etch) - why not?

Krzysztof Luban'ski wrote: On Tue, 2007-09-11 at 18:44 +0100, Martin Waller wrote: Am trying to run xconsole as normal user as I have done on other versions of debian. When I try to run it on an etch box it pops up as expected but with the message 'Can't open console' in it. Now, on my s

Re: xconsole 'can't open console' (etch) - why not?

On Tue, 2007-09-11 at 18:44 +0100, Martin Waller wrote: > Am trying to run xconsole as normal user as I have done on other > versions of debian. > > When I try to run it on an etch box it pops up as expected but with the > message 'Can't open console' in it. > > Now, on my sarge box, which is d

xconsole 'can't open console' (etch) - why not?

Hi, Am trying to run xconsole as normal user as I have done on other versions of debian. When I try to run it on an etch box it pops up as expected but with the message 'Can't open console' in it. Now, on my sarge box, which is due for an upgrade, it runs fine. I noticed on sarge /dev/con

Re: why not try lilypond

Bob McGowan wrote: > David Baron wrote: >> On Friday 16 February 2007, >> [EMAIL PROTECTED] wrote: >>> I have not seen anyone in this thread suggest lilypond ? >> >> There are several GUI notation programs around opensource. > > Generally, I prefer denemo, for reasons related to typing, but both do

  1   2   3   4   >