TinyCore/RaspberryPi Photo Scanning Project

[Shadow_8472]

The point for me would be because I have three Pi units: 3B+, 4, and 400. The 4 is mainly serving as my family's entertainment system running LibreELEC, and my 400 is tied up running a minimal Raspian installation I've configured as a wireless to wired router.

Right now, my main concern is figuring out why adding a boot code to change my username to "shadow8472" also prompted me to enter a password I know nothing about.

[Juanito]

At least gimp is present in the aarch64 repo 

[Rich]

Hi Shadow_8472
The /etc/init.d/tc-config script has an  addUser  function that looks like this:

Code: [Select]

addUser(){
echo "${GREEN}Adding user ${YELLOW}$USER ${NORMAL}"
/usr/sbin/adduser -s /bin/sh -G staff -D "$USER"
echo "$USER":tcuser | /usr/sbin/chpasswd -m
echo -e "$USER\tALL=NOPASSWD: ALL" >> /etc/sudoers
}If you use the  user=  boot code it will create that user with the password  tcuser.

[Shadow_8472]

Thanks, though the ease at which I was able to drop into root concerned me. I'm going to test it. Hopefully I haven't found a glaring security flaw.

At least gimp is present in the aarch64 repo 

Does Aarch64 have supported NFS? The three deal breakers for me are GIMP, NFS support, and the ability to scan.

[Rich]

Hi Shadow_8472
I don't see NFS currently listed.

You can see which extensions are currently available here:
http://tinycorelinux.net/12.x/aarch64/tcz/

[Shadow_8472]

...I don't see NFS currently listed.

Oof. Maybe an old version has something like what I'm working with now. The real kicker is that I have in-fact locked myself out of root by changing it to the Kali default for testing, and "tcuser" won't let me in either. I'm going to try removing the boot code from another system.

[Shadow_8472]

Maybe an old version has something like what I'm working with now.

I looked this one up myself. Sounds like I may want to stop by for a package request.

The real kicker is that I have in-fact locked myself out of root by changing it to the Kali default for testing, and "tcuser" won't let me in either. I'm going to try removing the boot code from another system.

Operation successful. I'm back to my tc user desktop and sudo whoami returned root. Good to know


Edit: Reality check: I need to work on what I have now, or I'll be tweaking it til Kingdom come. I've recovered it to a workable state. I need to refocus on mission critical stuff unless it would really be that much better in the long run during production.

[Shadow_8472]

OK, I'm coming back to this project to get a workspace I can tolerate. FLWM's sideways windows just aren't doing it for me. Where can I find a list of all available window managers in the repository? If I'm only running GIMP and a terminal, do I even need a window manager?

Requirements as I understand them:

• It needs to run GIMP in full screen on a standard HD monitor.
• I prefer to use something that's not been abandoned by its developers.
• A small CPU/RAM footprint is a priority here.
• I'm missing the ability to open a terminal with CTRL+ALT+T.

Edit: I've looked in the keyword function in tce. Looks like it's flwm (Fast Light Window Manager), jwm (Joe's Window Manager), and one called screen (I don't know anything more about this one). Are there any more, or am I talking compiling my own?

Edit2: Looks like "screen" is aimed primarily at terminal usage. Doesn't sound like what I need.

[Rich]

Hi Shadow_8472

... FLWM's sideways windows just aren't doing it for me. ...

Yeah, I never understood why someone would want that. I use  flwm_topside.  It's the same window manager, except the
title bar is at the top where it belongs, not on the left side of the window. Download the following to your  tce/optional
directory:

Code: [Select]

flwm_topside.tcz
flwm_topside.tcz.dep
flwm_topside.tcz.md5.txt
Open your  tce/onboot.lst  file and change this:

Code: [Select]

flwm.tczto this:

Code: [Select]

flwm_topside.tcz
Reboot.

[Shadow_8472]

I'm playing with Joe's Window Manager right now. I'm also not a fan of wbar, and JWM fills that niche all the same. So far, I think I can work with what I see. I read that it's configured by some kind of text file.

[Shadow_8472]

Well, now. I've started poking about in GIMP, but I don't like the colorless icons. Switching to colored icons, though is proving difficult without crashing JWM. I can't get to filetool.sh to save changes before restarting. I used

Code: [Select]

sleep 15s && jwm to kick it back alive. Saving!

...

Now GIMP won't start at all. It never did find its way into the path.

Edit: I've noticed that the version of GIMP in tce is a development build. Is there a way to get tce to install a stable build?

[Juanito]

The stable version of gimp is still gtk2 - the "development" gtk3 version has been years in the making and it seems to work fine..

What did you mean by "It never did find its way into the path"?

[Shadow_8472]

File Path. "which gimp" returns nothing and yet the program ran.

Edit: Oh, the things a reboot fixes. GIMP restartability among them.

[Juanito]

Code: [Select]

$ ls /usr/local/bin/gimp*
gimp-2.99

[Shadow_8472]

Code: [Select]

$ ls /usr/local/bin/gimp*
gimp-2.99

OK, so I'll want to make an alias.

At this point, I think I just need to figure out plugins to run SANE in GIMP or something and to make my nfs drive load on boot. Turns out /etc/fstab is one of those things that gets flushed.

Complete:

• PiCore Installation
• Xorg/JWM/aterm Installed
• GIMP Installed
• nfs-utils Installed
• Underscan Adjusted
• Hostname

To Do:

• GIMP alias
• GIMP scanning plugin(s)
• Persistent NFS drive mounting
• Test workflow: Scan into GIMP, save directly to NFS
• Benchmark on Pi 4 and 400 (Units in use elsewhere)

Wishlist:

• Username (without locking myself out)
• Make Ctrl+Alt+T bring up a Terminal
• Compare JWM to FLWM_Topside, each configured to my liking
• Rebuild everything in 64-bit