21
News / Re: RazWall Alpha 1.2 ISO
« Last post by razwall on March 31, 2025, 08:07:28 AM »I will rebuild the ISO today with a fix for the console bug.
News:
RazWall Status: Active development - New UI
Recent Posts
22
News / RazWall Alpha 1.2 ISO
« Last post by razwall on March 28, 2025, 03:47:38 PM »This will be online shortly. Download on our SF!
RazWall Aplha 1.2 ISO Release 3/28/2025
This ISO release includes the first RazWall Package. This is FAR from stable or usable but its a great test bed for anyone anxious to start working with this project since it contains everything I have worked on so far.
Default Console UI Login:
User: admin
Password: razwall
*A quick note: I have found a hug bug right after install.. The console does not not start.
To fix this:
CTL+ALT+F2 to get console 2
Login as root with the password you set during install.
run command: chmod +x /razwall/razi3
run command: reboot
After reboot, you should reach the UI Login on console 1
RazWall Aplha 1.2 ISO Release 3/28/2025
This ISO release includes the first RazWall Package. This is FAR from stable or usable but its a great test bed for anyone anxious to start working with this project since it contains everything I have worked on so far.
Default Console UI Login:
User: admin
Password: razwall
*A quick note: I have found a hug bug right after install.. The console does not not start.
To fix this:
CTL+ALT+F2 to get console 2
Login as root with the password you set during install.
run command: chmod +x /razwall/razi3
run command: reboot
After reboot, you should reach the UI Login on console 1
23
News / Re: RazWall 1.0 Console Demo Screenshot
« Last post by razwall on March 28, 2025, 02:41:10 PM »more..
24
News / Re: RazWall 1.0 Console Demo Screenshot
« Last post by razwall on March 28, 2025, 02:37:02 PM »A few more screenshots..
25
News / Changes coming down the pipe
« Last post by razwall on March 27, 2025, 04:56:22 PM »I just committed over 5000 changes to github. I have built a new ISO and running a test install. If this "works" I will upload to SF, even if still its broken, but accessible. fingers crossed..
26
News / Re: Broken modules
« Last post by razwall on March 27, 2025, 02:02:59 PM »i am going to take a difference approach and try stripping way only the interface modules in the ISO. Previously, I started with no modules and built up only the minimum but I suspect i broke something when i did this. So.. maybe a backwards (or forwards?) approach might be easier than trying to troubleshoot exactly what is missing, leaving me with a very generic error. I already spent most of yesterday trying to capture the the error in the code but I seem to get nothing. Even with manually adding output headers and building a custom simplified version of the modules I am getting the same error. It's definitely a mystery... So rather than fight the uphill battle, I will start with everything, less the X interface stuff, and test the ISO. If this works out, I can begin removing things until i find the culprit. I know some of you are patiently waiting for me to release something that works enough to begin testing and developing, so i apologize for my slowness.. I am only one man, but through this project I hope to create an army!
27
News / Broken modules
« Last post by razwall on March 26, 2025, 02:03:33 PM »Hello and sorry for the delay. After rebuilding with modules included I am stuck on a dreaded "End of script output before headers" error. The error tells me only that its not out putting data before it completes execution. Without a line number, i am forced to step through the code and create a stop error at every junction point until I locate the issue. This means hundreds of lines of code to soft through... Again sorry for the delay. i promise I am still working on this, it's just been a real show stopper trying get an install working "out of the box".
28
News / Re: SourceForge
« Last post by razwall on March 17, 2025, 02:24:35 PM »Nice try! Get off my account! lol
I am aware of the module problem. 3ndian was self-hosting modules for their own needs.
I might have to include a built module in the slackware/razwall package. I will have to find a source and build it on slackware, then just add it to the razwall the package.
I am aware of the module problem. 3ndian was self-hosting modules for their own needs.
I might have to include a built module in the slackware/razwall package. I will have to find a source and build it on slackware, then just add it to the razwall the package.
29
News / Re: SourceForge
« Last post by p3rlphr33k on March 17, 2025, 02:17:58 PM »Downloaded the ISO ran git clone of the current repo and copied the build package to the root. Some of the Perl modules were not loaded on install. tried CPAN to install modules but ran into issues with missing make and gc. used slackpkg to install both of these and viola! Things started to work I was able to install a few of the missing Perl modules noted the Apache error log using CPAN but still had issues installing a few of the older modules that do not seem to be supported such as Net::WebSocket::Server. Where can I get this and probably other missing modules?
30
General Discussion / Re: RazWall will be an Endian Community Fork
« Last post by razwall on March 17, 2025, 09:49:05 AM »Welcome! Thanks for posting. Perl is similar to C in syntax and take a little bit to get used to. yes, the CGI modules is no longer supported but there are ways around this. For example, I use a small script that emulates some of the basic functions of CGI.pm with the same function calls:
Here is the simple CGI.pm file I use as a replacement. Just put it in the cgi-bin folder and include the local path.
Example:
...
#!/usr/bin/perl
use lib './';
use CGI;
...
Here is the CGI.pm:
...
package CGI;
use strict;
use warnings;
use Carp;
use URI::Escape;
our $VERSION = '1.0';
our @EXPORT_OK = qw(header cookie param);
# Constructor: creates a new CGI object and parses the input.
sub new {
my ($class, %args) = @_;
my $self = bless {}, $class;
$self->_parse_input();
return $self;
}
# Internal: parse input parameters from QUERY_STRING or STDIN (for POST)
sub _parse_input {
my ($self) = @_;
my %params;
my $data = '';
# Determine request method
if (exists $ENV{REQUEST_METHOD} && uc($ENV{REQUEST_METHOD}) eq 'POST') {
if (defined $ENV{CONTENT_LENGTH} && $ENV{CONTENT_LENGTH} > 0) {
read(STDIN, $data, $ENV{CONTENT_LENGTH});
}
}
else {
$data = $ENV{QUERY_STRING} || '';
}
# Parse the query string (or POST data)
foreach my $pair (split /&/, $data) {
my ($name, $value) = split /=/, $pair, 2;
$name = uri_unescape($name);
$value = defined $value ? uri_unescape($value) : '';
push @{ $params{$name} }, $value;
}
$self->{params} = \%params;
}
# Returns a list of parameter names if called without arguments.
# With a parameter name, returns its value (or list of values in list context).
sub param {
my ($self, @args) = @_;
# Allow non-object calls by creating a new object
unless (ref $self) {
$self = CGI->new();
}
if (@args) {
my $name = $args[0];
my $values = $self->{params}{$name} || [];
return wantarray ? @$values : $values->[0];
}
else {
return keys %{ $self->{params} };
}
}
# Generates and returns an HTTP header string.
# Accepts named parameters similar to the original CGI header function.
# For example:
# print CGI::header(-type=>'text/html', -charset=>'utf-8', -cookie=>$cookie);
sub header {
my %params = @_;
my $status = $params{-status};
my $type = $params{-type} || 'text/html';
my $charset = $params{-charset} ? "; charset=" . $params{-charset} : '';
my $cookie = '';
# Process cookies if provided
if ($params{-cookie}) {
my @cookies;
if (ref $params{-cookie} eq 'ARRAY') {
@cookies = @{$params{-cookie}};
}
else {
@cookies = ($params{-cookie});
}
$cookie = join("\n", map { "Set-Cookie: $_" } @cookies) . "\n";
}
my $header = '';
$header .= "Status: $status\n" if $status;
$header .= "Content-Type: $type$charset\n";
$header .= $cookie;
$header .= "\n";
return $header;
}
# Creates a cookie string when parameters are provided.
# When called without arguments, returns a hash of cookies from HTTP_COOKIE.
# Example usage:
# my $cookie = CGI::cookie(-name=>'session', -value=>'ABC123', -path=>'/');
sub cookie {
my %params = @_;
if (%params) {
my $name = $params{-name} or croak "Cookie name (-name) is required";
my $value = defined $params{-value} ? $params{-value} : '';
my $cookie = "$name=" . uri_escape($value);
$cookie .= "; expires=" . $params{-expires} if $params{-expires};
$cookie .= "; path=" . $params{-path} if $params{-path};
$cookie .= "; domain=" . $params{-domain} if $params{-domain};
$cookie .= "; secure" if $params{-secure};
return $cookie;
}
else {
# No parameters provided: return current cookies as a hash
my %cookies;
if ($ENV{HTTP_COOKIE}) {
foreach my $pair (split /; ?/, $ENV{HTTP_COOKIE}) {
my ($k, $v) = split /=/, $pair, 2;
$cookies{$k} = $v;
}
}
return %cookies;
}
}
1;
...
Here is the simple CGI.pm file I use as a replacement. Just put it in the cgi-bin folder and include the local path.
Example:
...
#!/usr/bin/perl
use lib './';
use CGI;
...
Here is the CGI.pm:
...
package CGI;
use strict;
use warnings;
use Carp;
use URI::Escape;
our $VERSION = '1.0';
our @EXPORT_OK = qw(header cookie param);
# Constructor: creates a new CGI object and parses the input.
sub new {
my ($class, %args) = @_;
my $self = bless {}, $class;
$self->_parse_input();
return $self;
}
# Internal: parse input parameters from QUERY_STRING or STDIN (for POST)
sub _parse_input {
my ($self) = @_;
my %params;
my $data = '';
# Determine request method
if (exists $ENV{REQUEST_METHOD} && uc($ENV{REQUEST_METHOD}) eq 'POST') {
if (defined $ENV{CONTENT_LENGTH} && $ENV{CONTENT_LENGTH} > 0) {
read(STDIN, $data, $ENV{CONTENT_LENGTH});
}
}
else {
$data = $ENV{QUERY_STRING} || '';
}
# Parse the query string (or POST data)
foreach my $pair (split /&/, $data) {
my ($name, $value) = split /=/, $pair, 2;
$name = uri_unescape($name);
$value = defined $value ? uri_unescape($value) : '';
push @{ $params{$name} }, $value;
}
$self->{params} = \%params;
}
# Returns a list of parameter names if called without arguments.
# With a parameter name, returns its value (or list of values in list context).
sub param {
my ($self, @args) = @_;
# Allow non-object calls by creating a new object
unless (ref $self) {
$self = CGI->new();
}
if (@args) {
my $name = $args[0];
my $values = $self->{params}{$name} || [];
return wantarray ? @$values : $values->[0];
}
else {
return keys %{ $self->{params} };
}
}
# Generates and returns an HTTP header string.
# Accepts named parameters similar to the original CGI header function.
# For example:
# print CGI::header(-type=>'text/html', -charset=>'utf-8', -cookie=>$cookie);
sub header {
my %params = @_;
my $status = $params{-status};
my $type = $params{-type} || 'text/html';
my $charset = $params{-charset} ? "; charset=" . $params{-charset} : '';
my $cookie = '';
# Process cookies if provided
if ($params{-cookie}) {
my @cookies;
if (ref $params{-cookie} eq 'ARRAY') {
@cookies = @{$params{-cookie}};
}
else {
@cookies = ($params{-cookie});
}
$cookie = join("\n", map { "Set-Cookie: $_" } @cookies) . "\n";
}
my $header = '';
$header .= "Status: $status\n" if $status;
$header .= "Content-Type: $type$charset\n";
$header .= $cookie;
$header .= "\n";
return $header;
}
# Creates a cookie string when parameters are provided.
# When called without arguments, returns a hash of cookies from HTTP_COOKIE.
# Example usage:
# my $cookie = CGI::cookie(-name=>'session', -value=>'ABC123', -path=>'/');
sub cookie {
my %params = @_;
if (%params) {
my $name = $params{-name} or croak "Cookie name (-name) is required";
my $value = defined $params{-value} ? $params{-value} : '';
my $cookie = "$name=" . uri_escape($value);
$cookie .= "; expires=" . $params{-expires} if $params{-expires};
$cookie .= "; path=" . $params{-path} if $params{-path};
$cookie .= "; domain=" . $params{-domain} if $params{-domain};
$cookie .= "; secure" if $params{-secure};
return $cookie;
}
else {
# No parameters provided: return current cookies as a hash
my %cookies;
if ($ENV{HTTP_COOKIE}) {
foreach my $pair (split /; ?/, $ENV{HTTP_COOKIE}) {
my ($k, $v) = split /=/, $pair, 2;
$cookies{$k} = $v;
}
}
return %cookies;
}
}
1;
...