I've been trying to build my music player with the new bookworm 32
bit lite OS. I've been building these players for some years but it
seems bookworm has at the very least broken my notes and my players
no longer work.
I've noticed that:
Files cmdline.txt and config.txt have been moved from /boot to /boot/firmware. I found that and hopefully that's one issue I've
sorted myself.
The whole directory /bin and its contents have been removed.
My player used /bin/systemd so obviously that can't work anymore.
I've searched the pi for that file (systemd) but it's just not there.
I've looked through the release notes, no mention of missing /bin and
only 1 mention of systemd and that doesn't help me at all.
I've been googling for info on /bin missing and systemd changes but
it's just as though there is no issue, there's no helpful information anywhere on this, at least I cannot find it.
Any advice help appreciated.
Thanks.
Bob.
Looking at my Bookworm lite:
/bin is a link to /usr/bin
/bin/systemd is a link to /lib/systemd/systemd
/boot/config.txt is a link to /boot/firmware/config.txt
same with cmdline.txt
None of which should matter to you.
Just reference them as always.
In article <ugbku9$37rtn$1@dont-email.me>,
Knute Johnson <knute2023@585ranch.com> wrote:
I very much appreciate your help but I just don't understand. Sorry
I'm thick.
Looking at my Bookworm lite:
/bin is a link to /usr/bin
But /bin doesn't exist!
How can something that doesn't exist be a link to anything?
The directory /bin used to have a file in it called systemd. The
instructions to build a player tells me to add "init=/bin/systemd" to /boot/cmdline.txt.
I don't understand how that can work when neither /bin or the file
systemd exist. I looked inside /usr/bin and there is no file in there
called 'systemd' either. Very similar names yes but not just systemd
so I cannot point the instruction there either.
/bin/systemd is a link to /lib/systemd/systemd
/boot/config.txt is a link to /boot/firmware/config.txt
same with cmdline.txt
Again I don't understand your use of the work "link". It looks to me
as though the two files /boot/config.txt and /boot/cmdline.txt have
been moved to a new directory at /boot/firmware/. That's the only
thing I thought I understood. Am I wrong? Is there more to it?
None of which should matter to you.
I have no comprehension at all why that is so.
During player construction I had to issue a command:
sudo /home/pi/mediaplayer/run.sh
Under previous OS that kicked things off, now nothing happens.
The player no longer works at all.
Just reference them as always.
Sorry, but I don't know what that means either.
How can I reference something that doesn't exist?
Thanks for trying to help me.
Bob.
On 13/10/2023 17:41, Bob Latham wrote:
But /bin doesn't exist!
then something is awry in your installation.
If its even a cut downm linux thsi is what you should see
bin -> usr/bin
lib -> usr/lib
sbin -> usr/sbin
In article <5af2d290d0bob@sick-of-spam.invalid>,
Bob Latham <bob@sick-of-spam.invalid> wrote:
bin -> usr/bin
lib -> usr/lib
sbin -> usr/sbin
If I take one example and see if someone can give me another clue.
Please. Perhaps one example will give some scooby of some sorts.
The instructions for the music player say:
Edit /boot/cmdline.txt and add to the end of it " init=/bin/systemd".
Now under the previous OS this worked fine for years but there was a
file: /bin/systemd
So I've worked out (I think) that that file is now
/boot/firmware/cmdline.txt and I found the file and amended it as
instructed.
But now there is no such file and worse there is no file
/usr/bin/systemd either.
What do I do?
Bob.
In article <5af2d290d0bob@sick-of-spam.invalid>,
Bob Latham <bob@sick-of-spam.invalid> wrote:
bin -> usr/bin
lib -> usr/lib
sbin -> usr/sbin
If I take one example and see if someone can give me another clue.
Please. Perhaps one example will give some scooby of some sorts.
The instructions for the music player say:
Edit /boot/cmdline.txt and add to the end of it " init=/bin/systemd".
Now under the previous OS this worked fine for years but there was a
file: /bin/systemd
So I've worked out (I think) that that file is now
/boot/firmware/cmdline.txt and I found the file and amended it as
instructed.
But now there is no such file and worse there is no file
/usr/bin/systemd either.
What do I do?
Bob.
In article <ugbsjh$39gl1$5@dont-email.me>,
The Natural Philosopher <tnp@invalid.invalid> wrote:
On 13/10/2023 17:41, Bob Latham wrote:
But /bin doesn't exist!
then something is awry in your installation.
If its even a cut downm linux thsi is what you should see
Thank you for that, I so hope you're right and it gives me something
to work on. Thank you.
My bookworm does not have the following directories.
/bin
/lib
/sbin
<builds new card>
Its' the same!!
That's looking from samba.
However, copying what you did - ls -l, then I get these:
bin -> usr/bin
lib -> usr/lib
sbin -> usr/sbin
I would never, ever have found that without help.
It leaves fully baffled as how I adapt the build procedure to this complication and indeed my whole method of doing things looks broken
as I do almost everything via samba and that's been taken off me by
the looks of it.
I did fully carry out the build earlier today and of course it didn't
work at all. With such changes I cannot imagine where or how to start
working out what to do. Nothing makes any sense to me now.
Frankly, I'm stuffed.
Thanks.
Bob.
On 10/13/23 13:39, Bob Latham wrote:
In article <5af2d290d0bob@sick-of-spam.invalid>,
Bob Latham <bob@sick-of-spam.invalid> wrote:
bin -> usr/bin
lib -> usr/lib
sbin -> usr/sbin
If I take one example and see if someone can give me another clue.
Please. Perhaps one example will give some scooby of some sorts.
The instructions for the music player say:
Edit /boot/cmdline.txt and add to the end of it " init=/bin/systemd".
Now under the previous OS this worked fine for years but there was a
file: /bin/systemd
So I've worked out (I think) that that file is now
/boot/firmware/cmdline.txt and I found the file and amended it as
instructed.
But now there is no such file and worse there is no file
/usr/bin/systemd either.
What do I do?
Bob.
pi@projectroompi:~ $ ls -al /bin/systemd
lrwxrwxrwx 1 root root 20 Jul 29 04:53 /bin/systemd -> /lib/systemd/systemd
That's /lib/systemd/systemd
Bob said "That's looking from samba."
That would have been a nice tidbit for the first post Bob. Samba is
black magic. I never fool with it.
Ah. Finally I understand.
Samba by default does NOT FOLLOW OR REVEAL SYMLINKS
I have the same issues with NFS.
A 5 second google netted this, Try it
Edit smb.conf
[global]
unix extensions = no
[share]
follow symlinks = yes
wide links = yes
Bob said "That's looking from samba."
That would have been a nice tidbit for the first post Bob. Samba
is black magic. I never fool with it.
The directory /bin used to have a file in it called systemd. The
instructions to build a player tells me to add "init=/bin/systemd" to /boot/cmdline.txt.
Bob Latham <bob@sick-of-spam.invalid> writes:
The directory /bin used to have a file in it called systemd. The instructions to build a player tells me to add "init=/bin/systemd" to /boot/cmdline.txt.
Why do you think you need do to this?
Bookworm will start up with systemd anyway.
In article <ugc2ad$3b8jb$1@dont-email.me>,
The Natural Philosopher <tnp@invalid.invalid> wrote:
Ah. Finally I understand.
Samba by default does NOT FOLLOW OR REVEAL SYMLINKS
I have the same issues with NFS.
A 5 second google netted this, Try it
Yes, okay. I'm not very successful with google. You have to know the
right question to ask and I didn't know this was (at least in part) a
samba issue.
Edit smb.conf
[global]
unix extensions = no
[share]
follow symlinks = yes
wide links = yes
That worked !!! I now have virtual /bin /sbin and /lib.
I didn't even know such things as symlinks existed !1
Thank you for getting me to this point.
I probably need to have a look through again now with this new light
to see if I can spot the problem.
Cheers,
Bob.
In article <wwvh6mu1bp3.fsf@LkoBDZeT.terraraq.uk>,
Richard Kettlewell <invalid@invalid.invalid> wrote:
Bob Latham <bob@sick-of-spam.invalid> writes:
The directory /bin used to have a file in it called systemd. The
instructions to build a player tells me to add "init=/bin/systemd" to
/boot/cmdline.txt.
Why do you think you need do to this?
The short answer is that I follow the instructions and I don't know
enough to better them.
The players I build are based on this: https://github.com/PeteManchester/MediaPlayer
A few years ago the start up method started to fail (can't remember
its name) and couldn't be fixed. Pete changed over to using systemd
and that's been great until now but I follow his instructions.
Bookworm will start up with systemd anyway.
Interesting, is that for just bookworm?
If I go back to a player built on bullseye (april 2023) PiOS release
and remove that change? Will it still startup MediaPlayer?
Cheers,
Bob.
Richard Kettlewell <invalid@invalid.invalid> wrote:
Bob Latham <bob@sick-of-spam.invalid> writes:
The directory /bin used to have a file in it called systemd. The
instructions to build a player tells me to add "init=/bin/systemd"
to /boot/cmdline.txt.
Why do you think you need do to this?
The short answer is that I follow the instructions and I don't know
enough to better them.
The players I build are based on this: https://github.com/PeteManchester/MediaPlayer
A few years ago the start up method started to fail (can't remember
its name) and couldn't be fixed. Pete changed over to using systemd
and that's been great until now but I follow his instructions.
Bookworm will start up with systemd anyway.
Interesting, is that for just bookworm?
With respect Bob, you are well off the newbie reservation with what
you are trying to do. I don't say don't do it, just that you have a
pretty big learning curve here, and much of the documentation you
would like is going to be recondite to the extreme.
On 14/10/2023 10:06, Bob Latham wrote:
The players I build are based on this: https://github.com/PeteManchester/MediaPlayer
I just looked at this: https://github.com/PeteManchester/MediaPlayer/wiki/Install-Raspberry-Pi
and can find no reference to editing /boot/cmdline.txt or systemd
What am I missing?
I guess you mean
https://github.com/PeteManchester/MediaPlayer/wiki/Using-'systemd'--for-the-MediaPlayer-service-controller
Thatæs about wheezy (i.e. Debian 7), which is before systemd was the
default. Itæs unfortunate the author didnæt update their guide.
Itæs been the default since jessie (Debian 8).
In article <wwvr0lxzbqj.fsf@LkoBDZeT.terraraq.uk>,
Richard Kettlewell <invalid@invalid.invalid> wrote:
I guess you mean
https://github.com/PeteManchester/MediaPlayer/wiki/Using-'systemd'--for-the-MediaPlayer-service-controller
Oh thanks for finding that but yes I would imagine that is the source
of my notes.
That‘s about wheezy (i.e. Debian 7), which is before systemd was the
default. It‘s unfortunate the author didn‘t update their guide.
Wow, thanks for that information.
It‘s been the default since jessie (Debian 8).
Thanks for getting to the bottom of it. I dread to think what else
should be changed in my instructions.
With respect Bob, you are well off the newbie reservation with what
you are trying to do. I don't say don't do it, just that you have
a pretty big learning curve here, and much of the documentation
you would like is going to be recondite to the extreme.
| Sysop: | Xerxes |
|---|---|
| Location: | Azle, Texas |
| Users: | 119 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 143:04:21 |
| Calls: | 3,030 |
| Calls today: | 6 |
| Files: | 156 |
| U/L today: |
0 files (0K bytes) |
| D/L today: |
0 files (0K bytes) |
| Messages: | 294,210 |
| Posted today: | 0 |