Message Area
Casually read the BBS message area using an easy to use interface. Messages are categorized exactly like they are on the BBS. You may post new messages or reply to existing messages!

You are not logged in. Login here for full access privileges.

Previous Message | Next Message | Back to The Linux/FreeBSD MBSE BBS Suppo...  <--  <--- Return to Home Page
   Networked Database  The Linux/FreeBSD MBSE BBS Suppo...   [506 / 554] RSS
 From   To   Subject   Date/Time 
Message   Vince Coen    Niels Haedecke   Installing on a Pi 3 B+   December 5, 2018
 6:30 PM *  

Hello Niels!

Wednesday December 05 2018 16:18, you wrote to me:

 > Vince Coen wrote to All:
 VC>> Hello All!
 VC>>
 VC>> I have managed to build mbse on a brand new Pi (using a SD card as
 VC>> total storage).
 VC>>
 VC>> I must work out how to use a USB hard drive with its own power
 VC>> supply (the Pi power is not high enough at 2.5A).
 VC>>
 VC>> How ever when trying to install mbse I have hit a snag and cannot
 VC>> work out how to get around it.
 VC>>
 VC>> Namely I cannot so a 'su' to install it via make install that is
 VC>> because (I suspect) that the su feature is not available only
 VC>> sudo.
 VC>>
 VC>> The standard user needless to say is user  pi when starting the
 VC>> system.
 VC>>
 VC>> If I do a sudo -s
 VC>>
 VC>> then run make it complains about $MBSE_ROOT not availble.
 VC>>
 VC>> Can I do a sudo -s the set $MBSE_ROOT by just running export
 VC>> $MBSE_ROOT=/home/mbse
 VC>>
 VC>> Then make install ?
 VC>>
 VC>> Will that work correctly?

 > become root user (sudo su) and then set a password for root (passwd).
 > The classic su will work afterwards. This is how I worked around that
 > issue.

Thanks sorted but did do an export $MBSE_ROOT to cover it as well.


 VC>> One issue I do know is that the O/S Raspbian is only 32 bit while
 VC>> the Pi is 64 so creating a reduced system. The Pi 3B is possibly
 VC>> the first that is 64 bit.

 > Nope, the Pi 2 already was / is 64 bit but at that time no 64 bit
 > distros (aarch64) were avaialbe for it. (Open) SuSE were the first to
 > come up with that.

 > Hop this helps,
 > Niels


Wonder why they have not created dual platforms 32 and 64 bit like every other 
distro?

Now to try and work out why their instruction for migtating a SD card to a HDD 
does not result in a
working system.  Did take a look at the network boot but not convinced it is a 
real working solution as
its wired link does not look that it is running at full speed.

I wish they come out with an upgraded mobo with improved bus speed (to match 
the CPU etc) and 2 Sata
connectors (or even just esata). Would get around the speed problems although 
increasing RAm to 4GB would
also help and I would expect the cost to double.

Vince

--- Mageia Linux v6 X64/Mbse v1.0.7.11/GoldED+/LNX 1.1.501-b20150715
 * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)
  Show ANSI Codes | Hide BBCodes | Show Color Codes | Hide Encoding | Hide HTML Tags | Show Routing
Previous Message | Next Message | Back to The Linux/FreeBSD MBSE BBS Suppo...  <--  <--- Return to Home Page

VADV-PHP
Execution Time: 0.104 seconds

If you experience any problems with this website or need help, contact the webmaster.
VADV-PHP Copyright © 2002-2024 Steve Winn, Aspect Technologies. All Rights Reserved.
Virtual Advanced Copyright © 1995-1997 Roland De Graaf.
v2.0.140505

Warning: Unknown: open(c:\Sessions\sess_6c6l7iibo2kd8ulrtoub6e93t7, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0 PHP Warning: session_start(): open(c:\Sessions\sess_6c6l7iibo2kd8ulrtoub6e93t7, O_RDWR) failed: No such file or directory (2) in D:\wc5\http\public\VADV\include\common.inc.php on line 45 PHP Warning: Unknown: open(c:\Sessions\sess_6c6l7iibo2kd8ulrtoub6e93t7, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 PHP Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0