[marathon.duran...@gmail.com: Re: Unsolicited GNU bc patch]

2022-10-14 Thread SDA
- Forwarded message from SDA  -

Date: Thu, 4 Aug 2022 20:37:47 -0400
From: SDA 
Subject: Re: Unsolicited GNU bc patch
To: debian-user@lists.debian.org

On Sat, Jul 30, 2022 at 07:29:23AM +, Thomas DiModica wrote:

Hi, Thomas. I'd send this to the debian-developer email list rather than 
this user list. Not sure if any developers are lurking here ...

> Greetings,
> 
> I don't remember how or why I initially stumbled across this bug report 
> (https://bugs.launchpad.net/ubuntu/+source/bc/+bug/1775776), but, given that 
> I have some familiarity with GNU bc, I decided to fix some of the issues. 
> Turns out, this also seems to fix the crashes reported here 
> (https://www.openwall.com/lists/oss-security/2018/11/28/1). I think it would 
> be a lot more useful to share this, as there isn't a lot to review. There are 
> three bug fixes and some self-defensive checks in the runtime for malformed 
> bytecode. Address Sanitizer tells me that these previously invalid memory 
> references now just leak memory. I don't appear to have broken anything in 
> the process, either.
> 
> Just trying to be somewhat helpful,
> Thomas DiModica

> From 3ecfe21c965956f3913e9bc340df729234e4453b Mon Sep 17 00:00:00 2001
> From: Thomas DiModica 
> Date: Tue, 19 Jul 2022 19:28:12 -0600
> Subject: [PATCH] Resolving the crashes found through fuzz testing by
>  HongxuChen.
> 
> ---
>  bc/execute.c | 54 +---
>  bc/storage.c | 38 ++--
>  bc/util.c|  2 +-
>  3 files changed, 71 insertions(+), 23 deletions(-)
> 
> diff --git a/bc/execute.c b/bc/execute.c
> index 256e4b7..d30c6f5 100644
> --- a/bc/execute.c
> +++ b/bc/execute.c
> @@ -130,7 +130,7 @@ execute (void)
> gp = functions[pc.pc_func].f_label;
> l_gp  = label_num >> BC_LABEL_LOG;
> l_off = label_num % BC_LABEL_GROUP;
> -   while (l_gp-- > 0) gp = gp->l_next;
> +   while ((l_gp-- > 0) && (gp != NULL)) gp = gp->l_next;
>if (gp)
>  pc.pc_addr = gp->l_adrs[l_off];
>else {
> @@ -146,6 +146,13 @@ execute (void)
>   if ((new_func & 0x80) != 0) 
> new_func = ((new_func & 0x7f) << 8) + byte(&pc);
>  
> + /* Check to make sure it is valid. */
> + if (new_func >= f_count)
> +   {
> + rt_error ("Internal error.");
> + break;
> +   }
> +
>   /* Check to make sure it is defined. */
>   if (!functions[new_func].f_defined)
> {
> @@ -204,25 +211,32 @@ execute (void)
>  
>case 'O' : /* Write a string to the output with processing. */
>   while ((ch = byte(&pc)) != '"')
> -   if (ch != '\\')
> - out_schar (ch);
> -   else
> - {
> -   ch = byte(&pc);
> -   if (ch == '"') break;
> -   switch (ch)
> - {
> - case 'a':  out_schar (007); break;
> - case 'b':  out_schar ('\b'); break;
> - case 'f':  out_schar ('\f'); break;
> - case 'n':  out_schar ('\n'); break;
> - case 'q':  out_schar ('"'); break;
> - case 'r':  out_schar ('\r'); break;
> - case 't':  out_schar ('\t'); break;
> - case '\\': out_schar ('\\'); break;
> - default:  break;
> - }
> - }
> +   {
> + if (pc.pc_addr == functions[pc.pc_func].f_code_size)
> +   {
> + rt_error ("Broken String.");
> + break;
> +   }
> + if (ch != '\\')
> +   out_schar (ch);
> + else
> +   {
> + ch = byte(&pc);
> + if (ch == '"') break;
> + switch (ch)
> +   {
> +   case 'a':  out_schar (007); break;
> +   case 'b':  out_schar ('\b'); break;
> +   case 'f':  out_schar ('\f'); break;
> +   case 'n':  out_schar ('\n'); break;
> +   case 'q':  out_schar ('"'); break;
> +   case 'r':  out_schar ('\r'); break;
> +   case 't':  out_schar ('\t'); break;
> +   case '\\': out_schar ('\\'); break;
> +   default:  break;
> +   }
> +  

Re: Unsolicited GNU bc patch

2022-08-04 Thread SDA
On Sat, Jul 30, 2022 at 07:29:23AM +, Thomas DiModica wrote:

Hi, Thomas. I'd send this to the debian-developer email list rather than 
this user list. Not sure if any developers are lurking here ...

> Greetings,
> 
> I don't remember how or why I initially stumbled across this bug report 
> (https://bugs.launchpad.net/ubuntu/+source/bc/+bug/1775776), but, given that 
> I have some familiarity with GNU bc, I decided to fix some of the issues. 
> Turns out, this also seems to fix the crashes reported here 
> (https://www.openwall.com/lists/oss-security/2018/11/28/1). I think it would 
> be a lot more useful to share this, as there isn't a lot to review. There are 
> three bug fixes and some self-defensive checks in the runtime for malformed 
> bytecode. Address Sanitizer tells me that these previously invalid memory 
> references now just leak memory. I don't appear to have broken anything in 
> the process, either.
> 
> Just trying to be somewhat helpful,
> Thomas DiModica

> From 3ecfe21c965956f3913e9bc340df729234e4453b Mon Sep 17 00:00:00 2001
> From: Thomas DiModica 
> Date: Tue, 19 Jul 2022 19:28:12 -0600
> Subject: [PATCH] Resolving the crashes found through fuzz testing by
>  HongxuChen.
> 
> ---
>  bc/execute.c | 54 +---
>  bc/storage.c | 38 ++--
>  bc/util.c|  2 +-
>  3 files changed, 71 insertions(+), 23 deletions(-)
> 
> diff --git a/bc/execute.c b/bc/execute.c
> index 256e4b7..d30c6f5 100644
> --- a/bc/execute.c
> +++ b/bc/execute.c
> @@ -130,7 +130,7 @@ execute (void)
> gp = functions[pc.pc_func].f_label;
> l_gp  = label_num >> BC_LABEL_LOG;
> l_off = label_num % BC_LABEL_GROUP;
> -   while (l_gp-- > 0) gp = gp->l_next;
> +   while ((l_gp-- > 0) && (gp != NULL)) gp = gp->l_next;
>if (gp)
>  pc.pc_addr = gp->l_adrs[l_off];
>else {
> @@ -146,6 +146,13 @@ execute (void)
>   if ((new_func & 0x80) != 0) 
> new_func = ((new_func & 0x7f) << 8) + byte(&pc);
>  
> + /* Check to make sure it is valid. */
> + if (new_func >= f_count)
> +   {
> + rt_error ("Internal error.");
> + break;
> +   }
> +
>   /* Check to make sure it is defined. */
>   if (!functions[new_func].f_defined)
> {
> @@ -204,25 +211,32 @@ execute (void)
>  
>case 'O' : /* Write a string to the output with processing. */
>   while ((ch = byte(&pc)) != '"')
> -   if (ch != '\\')
> - out_schar (ch);
> -   else
> - {
> -   ch = byte(&pc);
> -   if (ch == '"') break;
> -   switch (ch)
> - {
> - case 'a':  out_schar (007); break;
> - case 'b':  out_schar ('\b'); break;
> - case 'f':  out_schar ('\f'); break;
> - case 'n':  out_schar ('\n'); break;
> - case 'q':  out_schar ('"'); break;
> - case 'r':  out_schar ('\r'); break;
> - case 't':  out_schar ('\t'); break;
> - case '\\': out_schar ('\\'); break;
> - default:  break;
> - }
> - }
> +   {
> + if (pc.pc_addr == functions[pc.pc_func].f_code_size)
> +   {
> + rt_error ("Broken String.");
> + break;
> +   }
> + if (ch != '\\')
> +   out_schar (ch);
> + else
> +   {
> + ch = byte(&pc);
> + if (ch == '"') break;
> + switch (ch)
> +   {
> +   case 'a':  out_schar (007); break;
> +   case 'b':  out_schar ('\b'); break;
> +   case 'f':  out_schar ('\f'); break;
> +   case 'n':  out_schar ('\n'); break;
> +   case 'q':  out_schar ('"'); break;
> +   case 'r':  out_schar ('\r'); break;
> +   case 't':  out_schar ('\t'); break;
> +   case '\\': out_schar ('\\'); break;
> +   default:  break;
> +   }
> +   }
> +   }
>   fflush (stdout);
>   break;
>  
> diff --git a/bc/storage.c b/bc/storage.c
> index c79db82..28e933b 100644
> --- a/bc/storage.c
> +++ b/bc/storage.c
> @@ -349,6 +349,7 @@ get_var (int var_name)
>  {
>var_ptr = variables[var_name] = bc_malloc (sizeof (bc_var));
>bc_init_num (&var_ptr->v_value);
> +  var_ptr->v_next = NULL;
>  }
>return var_ptr;
>  }
> @@ -370,6 +371,12 @@ get_array_num (int var_index, unsigned long idx)
>unsigned int ix, ix1;
>int sub [NODE_DEPTH];
>  
> +  if (var_index >= a_count)
> +{
> +  rt_error ("Internal Error.");
> +  return NULL;
> +}
> +
>/* Get the array entry. */
>ary_ptr = arrays[var_index];
>if (ary_ptr == NULL)
> @@ -588,6 +595,12 @@ store_array (int var_name)
>bc_num *num_ptr;
>long idx;
>  
> +  if (var_name >= a_count)
> +{
> +  rt_error ("Internal Error.");
> +  return;
> +}
> +
>   

Appstream-cli warning

2022-03-20 Thread SDA
Hey gurus,
I'm getting the following message for some time and am wondering if it's 
safe to remove the icon? Only seems to happen when I update apt repos from 
the cli.
Thanks.

** (appstreamcli:42191): WARNING **: 17:05:19.451: Found icon of unknown type 
'unknown' in 'system/flatpak/flatpak/cc.nift.nsm/*', skipping it.

** (appstreamcli:42191): WARNING **: 17:05:19.451: Found icon of unknown type 
'unknown' in 'system/flatpak/flatpak/cc.nift.nsm/*', skipping it.




KODI won't start on SID

2022-03-04 Thread SDA
Hi,
Since Thursday I'm having this issue on SID
/usr/lib/x86_64-linux-gnu/kodi/kodi.bin: symbol lookup error: 
/usr/lib/x86_64-linux-gnu/kodi/kodi.bin: undefined symbol:
+_ZN7wayland9display_t12create_queueEv

Any ideas?



Re: Kodi (SID)

2022-01-23 Thread SDA
On Sun, Jan 23, 2022 at 09:47:31AM +0100, Andrei POPESCU wrote:
> On Sb, 22 ian 22, 15:41:37, SDA wrote:
> > Greetings!
> > 
> > The past week or so, up until today Kodi has been segfaulting on me - 
> > Anyone 
> > else?
> > Starting from a term:
> > 
> > failed to open zone.tab
> > libva info: VA-API version 1.13.0
> > libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so
> > libva info: Found init function __vaDriverInit_1_13
> > libva info: va_openDriver() returns 0
> > Segmentation fault
> > 
> > So, appears to be a video driver issue ...
> > file via reportbug. Haven't rec'd bug# yet. Will update when rec'd.
>  
> Do you have the firmware for your video card installed?
> 
> dmesg | grep -i firmware
> 
> (needs sudo or root)

Hi Andre, thanks for responding. I have attached a stack trace to my bug 
report.
But yes, I expect this is affirmative according to dmesg:

0.271260] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[0.277570] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain  [bus 
00-3f] only partially covers this bridge
[1.305909] radeon :03:00.0: firmware: direct-loading firmware 
radeon/pitcairn_pfp.bin
[1.305917] radeon :03:00.0: firmware: direct-loading firmware 
radeon/pitcairn_me.bin
[1.305925] radeon :03:00.0: firmware: direct-loading firmware 
radeon/pitcairn_ce.bin
[1.305933] radeon :03:00.0: firmware: direct-loading firmware 
radeon/pitcairn_rlc.bin
[1.305943] radeon :03:00.0: firmware: direct-loading firmware 
radeon/si58_mc.bin
[1.305956] radeon :03:00.0: firmware: direct-loading firmware 
radeon/pitcairn_k_smc.bin
[1.316035] radeon :03:00.0: firmware: direct-loading firmware 
radeon/TAHITI_uvd.bin
[1.316051] radeon :03:00.0: firmware: direct-loading firmware 
radeon/TAHITI_vce.bin
[1.316212] [drm] Found VCE firmware/feedback version 50.0.1 / 17!
[5.916462] platform regulatory.0: firmware: direct-loading firmware 
regulatory.db
[5.916761] platform regulatory.0: firmware: direct-loading firmware 
regulatory.db.p7s
[5.961527] iwlwifi :04:00.0: firmware: direct-loading firmware 
iwlwifi-9260-th-b0-jf-b0-46.ucode
[5.961787] iwlwifi :04:00.0: loaded firmware version 46.6b541b68.0 
9260-th-b0-jf-b0-46.ucode op_mode iwlmvm
[6.277082] bluetooth hci0: firmware: direct-loading firmware 
intel/ibt-18-16-1.sfi
[6.277085] Bluetooth: hci0: Found device firmware: intel/ibt-18-16-1.sfi
[6.277093] Bluetooth: hci0: Firmware Version: 6-12.21
[6.277094] Bluetooth: hci0: Firmware already loaded
[6.500794] cx25840 14-0044: firmware: direct-loading firmware 
v4l-cx23885-avcore-01.fw
[7.138158] cx25840 14-0044: loaded v4l-cx23885-avcore-01.fw firmware (16382 
bytes)
[7.449970] r8169 :05:00.0: firmware: direct-loading firmware 
rtl_nic/rtl8168h-2.fw



Re: Kodi (SID)

2022-01-22 Thread SDA
Here is the deets for my report: Bug#1004214. Please add any additional 
information to the report itself if you suffer from same issue. Thanks!



Kodi (SID)

2022-01-22 Thread SDA
Greetings!

The past week or so, up until today Kodi has been segfaulting on me - Anyone 
else?
Starting from a term:

failed to open zone.tab
libva info: VA-API version 1.13.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so
libva info: Found init function __vaDriverInit_1_13
libva info: va_openDriver() returns 0
Segmentation fault

So, appears to be a video driver issue ...
file via reportbug. Haven't rec'd bug# yet. Will update when rec'd.



[marathon.duran...@gmail.com: Libinput Error]

2021-08-23 Thread SDA
Resending, didn't make it to the list for some reason.

- Forwarded message from SDA  -

Date: Sat, 21 Aug 2021 13:38:12 -0400
From: SDA 
Subject: Libinput Error
To: debian-user@lists.debian.org

Hi,
I've been getting the following messages in the journal-log even before
I installed Debian 11. Could someone help decipher them for me? I have
each device plugged into USB v 3.x USB buses as that's all my
motherboard supports.
Is the message saying that the device's are too slow being that they're
probably USB v2? It doesn't make sense that an AMD Ryzen CPU with 32 Gb
of ram would be too slow for any USB socket.
===
Aug 21 13:23:13 home gnome-shell[2096]: libinput error: event2  - dakai 
PS/2+USB Keyboard: client bug: event processing lagging
+behind by 36ms, your system is too slow
Aug 21 13:23:13 home gnome-shell[2096]: libinput error: event2  - dakai 
PS/2+USB Keyboard: WARNING: log rate limit exceeded (5
+msgs per 60min). Discarding future messages.


- End forwarded message -



Libinput Error

2021-08-21 Thread SDA
Hi,
I've been getting the following messages in the journal-log even before
I installed Debian 11. Could someone help decipher them for me? I have
each device plugged into USB v 3.x USB buses as that's all my
motherboard supports.
Is the message saying that the device's are too slow being that they're
probably USB v2? It doesn't make sense that an AMD Ryzen CPU with 32 Gb
of ram would be too slow for any USB socket.
===
Aug 21 13:23:13 home gnome-shell[2096]: libinput error: event2  - dakai 
PS/2+USB Keyboard: client bug: event processing lagging
+behind by 36ms, your system is too slow
Aug 21 13:23:13 home gnome-shell[2096]: libinput error: event2  - dakai 
PS/2+USB Keyboard: WARNING: log rate limit exceeded (5
+msgs per 60min). Discarding future messages.



Re: On improving mailing list [was: How to Boot Linux ISO Images Directly From Your Hard Drive Debian]

2021-08-17 Thread SDA
On Mon, Aug 16, 2021 at 03:01:43PM +0100, Jonathan Dowland wrote:
> On Mon, Aug 16, 2021 at 08:26:34AM -0400, SDA wrote:
> > BTW there has been an off-topic list introduced by a community member,
> > but it seems has had little uptake.
> 
> I looked into this the other day, because I hadn't seen reference to it
> for a while. It was called d-community-offtopic; it was hosted on the
> Alioth server, and I think its eventual demise was when Alioth was
> turned off in around 2018.
> 
> The last non-spam message to it was, I think, in 2016. The archives are
> here:
> 
> https://alioth-lists-archive.debian.net/pipermail/d-community-offtopic.mbox/
>
Thanks for the update Jonathan.



Re: On improving mailing list [was: How to Boot Linux ISO Images Directly From Your Hard Drive Debian]

2021-08-16 Thread SDA
On Mon, Aug 09, 2021 at 06:05:58PM -0700, Weaver wrote:
> I'm afraid this conversation is a waste of time.
> The goal posts are moved around at convenience, rather in than any
> serious manner at resolving an issue that is minor, if even existent.
> Cheers!
> 
> Harry.

Oh it exists Harry! I've been on this list (usually lurking) for almost
20 years. The off topic posts often go on to enormous lengths often
withouit a subject change (which itself is problematic). Way too much
noise to signal ration lately, and it's often a handful of users who
think this is their debate club.
I'm for this being an on topic user support list and that posters/users
that want to talk off topic be sanctioned appropriately. This list
through the eyes of a beginner wanting help has been atrocius lately.
Can you imagine trying to search for a given subject through the
archives and having to wade through all the noise in these mega threads
in case something relevant is in them? Ridicoulous.

BTW there has been an off-topic list introduced by a community member,
but it seems has had little uptake.

So I agree completely with Andy Smith's (and others) statements and
support this list being actively monitored for such off topic breaches.
It would make the list what it's supposed to be, and make the archives
better quality when searching for terms.



Re: Scribus has stopped importing PDF files - repost - original thread was hijacked

2018-09-30 Thread SDA
On Wed, Sep 26, 2018 at 02:45:18PM -0400, Gary Dale wrote:
> For the last few days, some Scribus documents I work with have stopped
> accepting PDF files within image frames. Prior to this, they would display a
> preview. Now new image frames that I create show just the file name, but
> some older frames within the document still show the preview.
> 
> When I export the document as a PDF, the frames that just display the file
> name export as empty/blank. The older frame that shows a preview causes the
> export to stop with an error saying it was unable to load the image.
> 
> I'm not sure if this is related to something in the PDFs or not. However it
> is happening on two documents I am working on.

You got an answer - It was suggested to ask on the Scribus forums. Not many 
poeple here are going to be in desktop publishing.

You might have told the poster to stop hijacking threads in your orignal 
post too! He probably didn't no better and it would have helped him amend 
his ways ... Just saying. 



Re: update bios from debian

2018-03-14 Thread SDA
On Thu, Mar 08, 2018 at 03:38:58PM +0100, Sven Hoexter wrote:
> On Wed, Mar 07, 2018 at 09:22:06PM -0800, Don Armstrong wrote:
> 
> Hi,
> 
> > sudo apt install grub-imageboot;
> > sudo cp 7wuj43uc.iso /boot/images;
> > sudo update-grub2;
> > 
> > then reboot, and select the right cd image in your grub menu.
> 
> That's a nice approach.
> Added it to https://wiki.debian.org/Firmware/Updates which already collects a 
> few
> other ways on how you can handle BIOS/EFI/Firmware updates.
> 
> Sven
>
Great information, thanks Don & Sven! 



Re: Problem using "dpkg -i"

2018-01-17 Thread SDA
On Mon, Jan 15, 2018 at 01:23:30PM -0600, Richard Owlett wrote:
> On 01/15/2018 11:38 AM, Sven Joachim wrote:
> > On 2018-01-15 01:32 -0600, Richard Owlett wrote:
> > > [snip]
> > > 2. Is there a recommended HTML editor in the repository that"
> > > A. simple UI
> > > B. can render the code so I can tell if my changes display
> > >as intended?
> > 
> > There is bluefish, but it only supports previews via an external browser
> > (according to the package description, I have not used it myself).
> > 
> 
> Not for this project. But the manual hints it would useful for other things.
> Much reading ahead.
> 
> Thanks
 
Bluefish isn't WYSIWYG, whereas Blue Griffon is - It's a pretty fair WebPage 
Editor. If you're not comfortable with markup, best use BlueGriffon. I've 
been happy with the latest version.
 



Re: [OFFTOPIC] Re: "Meltdown" and "Spectre": Every modern processor has unfixable security flaws

2018-01-07 Thread SDA
Show who you're quoting with an attribution line, please!



Re: Android Debian - Lets start Debian for Android hw phones

2018-01-07 Thread SDA
On Wed, Jan 03, 2018 at 12:25:50AM +0100, Anders Andersson wrote:
> On Tue, Jan 2, 2018 at 5:50 PM, Samuel  wrote:
> > could you add a support for wiko
> > I have a wiko lenny 4 plus
> 
> Sure! Probably a small job. I'll submit a patch tomorrow to port
> debian to android.
>

Well, Debian does call itself the 'Universal Operating System'. Maybe that 
phrase should be rethought since it doesn't run on all devices. Worthy 
thought, but not reality. 



Facebook Engineer Comments After Using systemd 1 Year Later

2017-10-29 Thread SDA
Thought it might be worthwhile to understand how systemd helps the large 
enterprise. https://media.ccc.de/v/ASG2017-126-systemd_facebook_a_year_later



Re: Replace systemd

2017-07-05 Thread SDA
On Tue, Jul 04, 2017 at 07:33:25PM -0500, John Hasler wrote:
> Jimmy Johnson writes:
> > Funny, that sounds like something a Slack'er would say. Patrick, we
> > are not all keyboard wizards like you and that other Patrick who can
> > keyboard faster than I can read. That's a compliment on your abilities
> > by the way.
> 
> Gnome or the Slacker way are not the only alternatives.  I use FVWM with
> four desktops with 16 panels each.  Unlike Gnome, FVWM is infinitely
> customizeable and does not have thousands of baffling dependencies.

Be sweet to see a screen grab of that, John. :-)



Re: Problems with apt in a clean stretch install.

2017-07-04 Thread SDA
On Tue, Jul 04, 2017 at 08:17:53PM +0930, Wayne Hartell wrote:

Er ... sorry that last email should read " Phil Wyett's suggestion" in 
this thread. 



Re: Problems with apt in a clean stretch install.

2017-07-04 Thread SDA
On Tue, Jul 04, 2017 at 08:17:53PM +0930, Wayne Hartell wrote:
> Thanks. Yeah I have tried importing keys (even though they already exist 
> as confirmed with 'apt-key list' and it makes no difference. All the keys 
> complained about are already present.
> 
> I don't have enough experience nor understanding of Linux to know whether 
> it's a bug or dumb user and though I suspect the latter, I feel like there's 
> a chance it could be the former.

Did you try Phil Hartnell's suggestion? It sounds promising - In fact I had 
this exact issue on a relatives computer, and I'm going to try his 
suggestion later on. The sequence of events he describes sounds relevant to 
the situation I experienced, so worth a shot methinks. Please advise us how 
it goes. 



Re: quasi-SOLVED: Re: no network after jessie -> stretch

2017-06-23 Thread SDA
On Fri, Jun 23, 2017 at 05:37:29PM -0400, Fungi4All wrote:
>  From: doc.ev...@gmail.com
>  To: debian-user@lists.debian.org 
>  Fungi4All wrote on 06/22/2017 09:48 PM:
>  >> From: doc.ev...@gmail.com
>  >> To: debian-user@lists.debian.org
>  >>
>  >> D. R. Evans wrote on 06/21/2017 09:53 AM:
>  >> It adds about 30 useless seconds to the boot time while the system
>  waits for it
>  >> to time out, so it sure would be nice to know how to get rid of the
>  delay somehow.
>  >
>  > 30 useless seconds! What has humanity been reduced to? How many times
>  a day
>  > do you reboot?
>  Anyway, my question is technical, not philosophical, which seems
>  appropriate
>  for a technical reflector.
> 
>You are the calling yourself a doctor, as far as I know that is a doctor
>of philosophy.
>What would I know, I'm just a technician!  But for life's sake I hope you
>are not in
>the life sciences as you probably don't deserve your title.
>In other words, the answer to your question can not come in 30sec, it may
>take millenniums to answer.

This is uncalled for Fungi4All: please refrain from such childish behaviour 
on this list. And must you write HTML emails for gawds sake?



Re: switching flavors

2017-06-07 Thread SDA
On Wed, Jun 07, 2017 at 08:57:40AM +0900, Mark Fletcher wrote:
> On Tue, Jun 06, 2017 at 04:55:01PM -0400, SDA wrote:
> > On Sun, Jun 04, 2017 at 06:44:10PM +0100, Joe wrote:
> > > On Sun, 4 Jun 2017 12:20:51 -0400
> > > SDA  wrote:
> > > 
> > > > On Sun, Jun 04, 2017 at 04:20:02PM +1000, Davor Balder wrote:
> > > > > Yes - and based on some work I did earlier in the week if you keep
> > > > > the things simple I would say your upgrade should be uneventful.
> > > > > 
> > > > > I  changed the repo to unstable
> > > > > 
> > > > > Then I did:
> > > > > 
> > > > > apt-get update
> > > > > 
> > > > > apt-get upgrade
> > > > > 
> > > > > That was it.  
> > > > 
> > > > Nope, not done yet. You still need to do a full upgrade. In apt it's
> > > > 'apt full-upgrade' in aptitude it's 'aptitude dist-upgrade'. Not sure
> > > > what the eqivalent command is in apt-get.
> > > > 
> > > 
> > > Other way around, aptitude is safe-upgrade and full-upgrade, it's
> > > apt-get which has upgrade and dist-upgrade. apt mixes the two, with
> > > upgrade and full-upgrade.
> > 
> > Not unless it was changed in aptitude just recently, (I've used it for 
> > years 
> > prior). Aptitude has 'safe-upgrade' yes, but it also has 'upgrade' and 
> > 'dist-upgrade'. So 3 options.
> > 
> 
> >From the man page for aptitude, search for dist-upgrade, in the section 
> on full-upgrade -- "This command was originally named dist-upgrade for 
> historical reasons, and aptitude still recognises dist-upgrade as a 
> synonym for full-upgrade."
> 
> The man page does not acknowledge just upgrade as a command. According 
> to the man page, the two options are safe-upgrade and full-upgrade, but 
> I can testify that upgrade still works (and I _think_ does a 
> safe-upgrade).

Ah I see. Thanks Mark, it's been sometime since I've used Aptitude for 
managing my packages.



Re: (abort)Re: why can't I visit this web site

2017-06-06 Thread SDA
On Wed, Jun 07, 2017 at 05:30:05AM +0800, Long Wind wrote:
> Thank Thomas!
> I disable javascript, but it still display nothing.
> 
> the web site is in Chinese, use Unicode
> 
> my energy is limited,I give up
> Thank all those who reply!

I posted a link to what the page looks like as a webm movie. Not see it? 



Re: why can't I visit this web site

2017-06-06 Thread SDA
On Tue, Jun 06, 2017 at 09:31:26AM +0800, Long Wind wrote:
>i am not at home and can't use debian pc
>my problem is like Richard's description
>it loads sth., but display nothing
>thanks!

Here is a screen recording of what that abomination of a web page looks 
like.  
https://drive.google.com/file/d/0B84pZZOsDAK5UVNUTXcwZFRUOWs/view?usp=sharing



Re: switching flavors

2017-06-06 Thread SDA
On Sun, Jun 04, 2017 at 06:44:10PM +0100, Joe wrote:
> On Sun, 4 Jun 2017 12:20:51 -0400
> SDA  wrote:
> 
> > On Sun, Jun 04, 2017 at 04:20:02PM +1000, Davor Balder wrote:
> > > Yes - and based on some work I did earlier in the week if you keep
> > > the things simple I would say your upgrade should be uneventful.
> > > 
> > > I  changed the repo to unstable
> > > 
> > > Then I did:
> > > 
> > > apt-get update
> > > 
> > > apt-get upgrade
> > > 
> > > That was it.  
> > 
> > Nope, not done yet. You still need to do a full upgrade. In apt it's
> > 'apt full-upgrade' in aptitude it's 'aptitude dist-upgrade'. Not sure
> > what the eqivalent command is in apt-get.
> > 
> 
> Other way around, aptitude is safe-upgrade and full-upgrade, it's
> apt-get which has upgrade and dist-upgrade. apt mixes the two, with
> upgrade and full-upgrade.

Not unless it was changed in aptitude just recently, (I've used it for years 
prior). Aptitude has 'safe-upgrade' yes, but it also has 'upgrade' and 
'dist-upgrade'. So 3 options.



Re: switching flavors

2017-06-04 Thread SDA
On Sun, Jun 04, 2017 at 04:20:02PM +1000, Davor Balder wrote:
> Yes - and based on some work I did earlier in the week if you keep the
> things simple I would say your upgrade should be uneventful.
> 
> I  changed the repo to unstable
> 
> Then I did:
> 
> apt-get update
> 
> apt-get upgrade
> 
> That was it.

Nope, not done yet. You still need to do a full upgrade. In apt it's 'apt 
full-upgrade' in aptitude it's 'aptitude dist-upgrade'. Not sure what the 
eqivalent command is in apt-get.



Re: Update Notifier

2017-05-17 Thread SDA
On Fri, May 05, 2017 at 04:32:44PM +, sare...@att.net wrote:
> Why doesn't Debian 8 Cinnamon notify when updates are ready to install after 
> all these years Debian has existed? Don't tell me there is one, because after 
> installing Debian I waited a long time to see if a notification would pop up. 
> It never did. I know about doing apt-get update && apt-get upgrade,but why 
> should we have to use a command line? It makes me wonder about Debian 
> security. Would you please put an update notifier in all your versions of 
> Debian.
>
There is a gnome-shell extension that does this, it's configurable as well.  
Should work for Cinnamon too, right? https://extensions.gnome.org/ 



Re: How stable is the frozen stretch?

2017-05-16 Thread SDA
On Tue, May 16, 2017 at 08:50:45AM -0500, Richard Owlett wrote:
> 
> *ROFL!*  ;/
> I've been a computer _user_ for a half-century.
> About 5 years ago I started seriously plotting my escape from the gloppy GUI
> of an organization recently in the news.
> I investigated "Linux from Scratch", Slackware, and Ubuntu. Debian was
> chosen for having a good mixture of customizing possibilities and breath of
> easily installed tested software.

IMHO You should do LFS - Over the past 18 months or so, the amount of 
traffic attributed to you and your learning is incredible. A lot of time is 
spent on your issues, (which face it aren't really problems) while I feel 
that other users don't get the attention needed. What makes you think you 
should monopolize this list as your personal research tool? It's fucking 
ridiculous!
 
> My current mantra is "If retirement isn't for learning, what use is it?"

Maybe get out and enjoy life more? I'm retired too, but don't spend all my 
time at the keyboard! 



Re: FossaMail

2017-05-03 Thread SDA
On Wed, May 03, 2017 at 07:21:16PM -0400, Stephen P. Molnar wrote:
> Dose anyone have a installation copy of FossaMail that they would be willing
> to share?

Ugh, just noticed my previous post was for MSFT - The only download I was 
able to find for Linux, is this: 
ftp://ftp2.palemoon.org/Pale_Moon/12.x/Linux/

HTH. 



Re: FossaMail

2017-05-03 Thread SDA
On Wed, May 03, 2017 at 07:21:16PM -0400, Stephen P. Molnar wrote:
> Dose anyone have a installation copy of FossaMail that they would be willing
> to share?
> 
> Thanks in advance.

Stephen, appears to still be available here: 
http://www.softpedia.com/get/Internet/E-mail/E-mail-Clients/FossaMail.shtml 



Re: Apt trusted.gpg file problems

2017-03-26 Thread SDA
On Sun, Mar 26, 2017 at 09:03:31AM +, Miltiades Vasiliades wrote:
> I tried switching the mirrors through synaptic then synaptic as usual asked 
> to refresh however the refresh ended with the following errors
> 
> W: http://repo.steampowered.com/steam/dists/precise/InRelease: The key(s) in 
> the keyring /etc/apt/trusted.gpg are ignored as the file is not readable by 
> user '_apt' executing apt-key.
> W: 
> http://security.debian.org/…/dists/stretch/updates/InRelease:
>  The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is 
> not readable by user '_apt' executing apt-key.
> W: http://ftp.de.debian.org/debian/dists/stretch/InRelease: The key(s) in the 
> keyring /etc/apt/trusted.gpg are ignored as the file is not readable by user 
> '_apt' executing apt-key.
> 
> 
> Any ideas how to resolve that issue?

Have noticed the exact same problem on a clients desktop too, after installing 
via the Stretch RC2 installer & subsequent upgrade via synaptic.



Re: Sound Problem

2017-03-12 Thread SDA
On Sat, Mar 11, 2017 at 10:36:54PM +, Dominic Knight wrote:
 
> As you most likely have two sound cards, one on-board and one with the
> video card (HDMI) it may be worthwhile installing pasystray as this may
> give you better control over which card you want to use, lots of
> options to reset sink, add modules etc. It helped me solve sound issues
> in the past when switching between on-board headphones and HDMI to the
> TV so worth a try at least.

I 2nd Dominic's advice - My scenario as well, and when running SID at times 
having pasystray helped select the right card when needed. Of course now, with 
Stretch installed, haven't had to do this for some time. 



exim4 config help

2005-04-30 Thread SdA
Hello:
I'm attempting to configure 'exim4 daemon heavy' to deliver mail via a 
smarthost.

When setting up the configuration via 'dpkg-reconfigure exim4-config' I 
selected the 'monolithic' option. However I can't find a exim4-config 
file anywhere after doing so in order to edit it -- That's my first problem.

My second problem is that my smarthost is Yahoo.com smtp server, which 
requires me to use port#587 in order to get around my ISPs blocking of 
the regular port. So when I know which file to edit, I'm not sure of the 
syntax.

I realize these are rather Noob questions, but all the online help I'm 
finding, isn't very explicit or helpful to a newbie like myself.

I'd appreciate some guidance. I can receive mail fine via fetchmail and 
exim4 delivers it properly, I simply cannot send.

Thanks.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: upgrading kernel 2.2.20-idepci

2004-05-23 Thread sda
OK, did the upgrade and I am booted into a new 2.4.x kernel. The only problem is
that the new kernel, doesn't recognize my ethernet card eth0, so I don't have a
network on the Debian box.
Is there any way to fix this? I did modprobe for Realtek (which I believe is my
card) but there aren't any modules for it. All my services seem to be running,
 Apache, MySQL, samba, etc.
Help please.

--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: kernel panic

2004-03-04 Thread sda
[EMAIL PROTECTED] wrote:
Yes. Your simplest option (going from memory here) is to boot off the CD
again, choose the bf24 kernel, skip the majority of the configuration
options, opting instead for mount previous installation, install lilo, and
reboot - then you should be back in bussiness.
NOTE: I'm at uni at the moment, doing this from memory, if anything look
weird, cancel out and let me know, I'll be home in a couple of hours, atwhich point I 
can actually take a look myself at the menu and give you the
exact instructions.
Cheers
Edward
Thanks Edward and everyone else, appreciated the effort very much!

In the meantime, I re-installed. I couldn't do nothing for a day, so had to go 
and do the windoze thing, and re-install. I tried to use the exisiting 
configuration and fake an install, but unfortunately it didn't work.

--
Stephen


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: kernel panic

2004-03-04 Thread sda
Jonathan Schmitt wrote:



> You should always keep the old kernel in Your bootmenu to prevent such things,
> this is, what the construct with /vmlinuz and /vmlinuz.old is for.
Yes, however, I didn't delete anything... When I was working in Lilo previous to 
the 'accident', the old config was there. Beats me what happened to it. It was 
called 'Linux.old'

> Nevertheless, You could boot the woody installation disk, select "execute a
> shell" from the menu and then
> mount /dev/hda1 /mnt # assuming this is, where Your root partition is
> cd /mnt
> chroot /mnt
Yeah, I did something similar prior to posting on debian-user. I booted from the 
install cd, attempted to rescue/mount hda1, but the system kept saying 'invalid 
argument'.

> So You should get back to Your old system environment and be able to rerun
> lilo with Your old kernel in the boot menu.
> Best regards
>js
I'll try your commands above.

--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: kernel panic

2004-03-04 Thread sda
Jonathan Schmitt wrote:

Hallo


So, I took the plunge and installed '2.4.18.img' and ran lilo afterwards. 
Lilo 

gave an error on the stanza I added to lilo as per the debian installer 
instructions: I think it was the 'initrd=/initrd.img' line. I obviously added 
it 

to the wrong place.


You should always keep the old kernel in Your bootmenu to prevent such things, 
this is, what the construct with /vmlinuz and /vmlinuz.old is for.
Nevertheless, You could boot the woody installation disk, select "execute a 
shell" from the menu and then 
mount /dev/hda1 /mnt # assuming this is, where Your root partition is
cd /mnt
chroot /mnt
So You should get back to Your old system environment and be able to rerun 
lilo with Your old kernel in the boot menu.
Best regards
   js



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



kernel panic

2004-03-04 Thread sda
Hello Folks:

I'm desperate -- Previous to this morning I had the install bf24 kernel 
installed. I read on another list that basically it's intended for the install 
process only and should be replaced for adequate performance.

So, I took the plunge and installed '2.4.18.img' and ran lilo afterwards. Lilo 
gave an error on the stanza I added to lilo as per the debian installer 
instructions: I think it was the 'initrd=/initrd.img' line. I obviously added it 
to the wrong place.

Anyways, "Murphy's law' conveniently came to be, while I was doing this, I let 
the sink overflow in the kitchen, and the water was threating to splash over the 
electric equipment (power bars etc) that runs my 4 workstations. So, because we 
were tramping through water (electrocution possibility to) I had to throw the 
circuit breaker that was responsible for these components.

So, to make a long story short, I'm unable to boot into my Woody server, with 
the newly installed kernel. I tried the rescue disk, but it gives me a kernel 
panic. I tried the 'shift-tab' sequence at the lilo prompt, and it only gives me 
one kernel choice -- I can't see the old one.

The messages I'm getting at the kernel are thus;

-root filesytem not mounted
-VFS cannot open root device
-please append a correct root=boot option
-kernel panic
This is way over my head. Is there anything I can do, to mount this box?

I'd rather try to recover it if possible, as I'm not backed up... (I know, I know).

Thanks.
--
Stephen
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Exim (Woody) smarthost using authenicated ssmtp

2003-11-16 Thread sda
Hello:

I searched the archives but didn't find anything that solved or helped my 
situation and yes, I've RTFM, or parts of it. 

I'm using Rogers Cable HighSpeed, and they require all outbound smtp to be 
authenticated using SMTP AUTH LOGIN. I can't figure out the syntax to use. I do 
have fetchmail setup and receiving properly.

Thanks for reading. Suggestions?

--
Regards
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]