On Wed May 1, 2024 at 5:16 PM CEST, Jeff Pohlmeyer wrote:
> On Wed, May 1, 2024 at 9:51 AM Sertonix wrote:
>
> > +https://elinux.org/Linux_Tiny/;>trimming
>
> The new link[1] takes me to a page that says "There is currently no
> text in this page."
> Removing the trailing slash[2] fixes the
---
Remove trailing slash causing 'page not found'.
FAQ.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/FAQ.html b/FAQ.html
index 11f8602..f34c54d 100644
--- a/FAQ.html
+++ b/FAQ.html
@@ -1234,7 +1234,7 @@ This has a
build/deployment environment we still put any effort
On Wed, May 1, 2024 at 9:51 AM Sertonix wrote:
> +https://elinux.org/Linux_Tiny/;>trimming
The new link[1] takes me to a page that says "There is currently no
text in this page."
Removing the trailing slash[2] fixes the problem.
[1] https://elinux.org/Linux_Tiny/
[2]
---
FAQ.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/FAQ.html b/FAQ.html
index 11f8602..dfff0e2 100644
--- a/FAQ.html
+++ b/FAQ.html
@@ -1234,7 +1234,7 @@ This has a
build/deployment environment we still put any effort into maintaining. (If
anyone takes an interest
Sam James wrote:
>David Leonard writes:
>> I worry that the fprintf() may destroy the errno which perror() uses,
>> so you could get a random error message.
>> Perhaps remove the fprintf(s) completely? Because the context should be
>> clear enough from the filename alone that perror displays.
>
