I am awaiting a HP ProLiant MicroServer Gen8 which I plan to use as a home media server and to create iso files from DVDs with Brasero.
I am pretty well 100% Windows user although I am using Brasero on one of the original micro servers to prepare iso files at the moment, the Gen8 has a Xeon processor so I expect it to be a bit more responsive.
I will be using Linux Mint Mate as it's cleanish and reasonably lightweight. My understanding is it will split the OS drive by using mount points rather than partitions (on Windows I use separate drives C:(OS) and D:(Data)). The Microserver was made before the days of UEFI, I hope Linux can live with that.
I will use 2 x additional drives, first one for shared media, second to back it up (in turn this will be backed up to my home server).
If I understand it a add the second drive after the install, set it up as GPT then mount it so it can be seen on the network.
Does it matter where I mount it i.e. in /root or /home or /mnt?
If I put it in /mnt and call it "Mediashare" with sub directories "Music", "Pictures" and "Videos" is the network path /Mediashare/Music or /mnt/Mediashare/Music?
I want to try and follow any conventions that exist as if I need to shout for help it's easier for people if the base is a conventional layout.
Many thanks :-)
I am awaiting a HP ProLiant MicroServer Gen8 which I plan to use as a
home media server and to create iso files from DVDs with Brasero.
I am pretty well 100% Windows user although I am using Brasero on one of
the original micro servers to prepare iso files at the moment, the Gen8
has a Xeon processor so I expect it to be a bit more responsive.
I will be using Linux Mint Mate as it's cleanish and reasonably lightweight. My understanding is it will split the OS drive by using
mount points rather than partitions (on Windows I use separate drives C: (OS) and D:(Data)). The Microserver was made before the days of UEFI, I
hope Linux can live with that.
If I understand it a add the second drive after the install, set it up
as GPT then mount it so it can be seen on the network.
Does it matter where I mount it i.e. in /root or /home or /mnt?
If I put it in /mnt and call it "Mediashare" with sub directories
"Music", "Pictures" and "Videos" is the network path /Mediashare/Music
or /mnt/Mediashare/Music?
I want to try and follow any conventions that exist as if I need to
shout for help it's easier for people if the base is a conventional layout.
I am awaiting a HP ProLiant MicroServer Gen8 which I plan to use as a home media server and to create iso files from DVDs with Brasero.
I am pretty well 100% Windows user although I am using Brasero on one of
the original micro servers to prepare iso files at the moment, the Gen8
has a Xeon processor so I expect it to be a bit more responsive.
I will be using Linux Mint Mate as it's cleanish and reasonably lightweight. My understanding is it will split the OS drive by using mount points rather than partitions (on Windows I use separate drives C:(OS) and D:(Data)). The Microserver was made before the days of UEFI, I hope Linux can live with that.
I will use 2 x additional drives, first one for shared media, second to
back it up (in turn this will be backed up to my home server).
If I understand it a add the second drive after the install, set it up as GPT then mount it so it can be seen on the network.
Does it matter where I mount it i.e. in /root or /home or /mnt?
If I put it in /mnt and call it "Mediashare" with sub directories "Music", "Pictures" and "Videos" is the network path /Mediashare/Music or /mnt/Mediashare/Music?
I want to try and follow any conventions that exist as if I need to shout for help it's easier for people if the base is a conventional layout.
Many thanks :-)
On Mon, 3/9/2026 11:57 AM, Jeff Gaines wrote:
OK, so our first step, is to "initialize" the disk. Look for something that
offers MBR or GPT as options in gparted. I like gparted, because it is
graphical. sudo fdisk is for legacy command line. sudo gdisk is for GPT command line.
sudo gdisk /dev/sdb # Later on, after project is finished. Use P for Print, Q for Quit.
2) Once we have the partition scheme selected, the entire disk is "unallocated".
We create a partition, set the size of it, set the partition type
(the GPT identifier does not say exactly what the file system is, it
might say a partition is a "Linux disk" versus the "Windows disk" type
which covers NTFS/ExFat and so on).
If at that point, you are defining the partition type (it is not RAW),
like EXT4, then the partition will be formatted, superblocks written out and so on.
For a high capacity drive, this might take a minute. On an NTFS, it would
be writing a $MFT instead.
There is a place to assign a label. Whatever fields will accept a name,
I generally put a name in there like "MediaServer" for the label. When
I use the "df" command to list my partitions mounted, now they can have
the nicer label-name and so on. df stands for "disk-free".
You can do (recommended)
/mnt/MediaServer
/mnt/OtherDisk
I will be using Linux Mint Mate as it's cleanish and reasonably
lightweight. My understanding is it will split the OS drive by using
mount points rather than partitions (on Windows I use separate
drives C:(OS) and D:(Data)).
Does it matter where I mount it i.e. in /root or /home or /mnt?
b) /usr/local/share ...
c) /var ...
d) /opt ...
e) under the root directory
I do recommend not not have a mount point inside another mount
point, as it can give you issues.
Modern fdisk can do gpt.
If I put it in /mnt and call it "Mediashare" with sub directories "Music", >> "Pictures" and "Videos" is the network path /Mediashare/Music or
/mnt/Mediashare/Music?
Probably not.
If you are sharing with Windows systems, you will either need to run a
Samba (SMB) server in Linux on your Microserver, in which case, the
network path is whatever you configure Samba to externalize it as, or
you run a Linux NFS server on the Microserver, (and a Windows NFS client
on the Windows boxes), and externalize as
<microserver_host_name>:/mnt/Mediashare/Music
At the time, this was an example of a mediaserver.
http://en.wikipedia.org/wiki/Serviio
Windows Media Player Legacy, has a mediaserver on it.
On Mon, 9 Mar 2026 23:47:01 -0400, Paul wrote:
At the time, this was an example of a mediaserver.
http://en.wikipedia.org/wiki/Serviio
No need to use anything proprietary, or even dedicate a machine to it.
<https://packages.debian.org/trixie/gerbera> <https://packages.debian.org/trixie/minidlna>
Windows Media Player Legacy, has a mediaserver on it.
Whatever happened to Windows Home Server?
Couldn’t compete with Linux.
I want to try and follow any conventions that exist as if I need to shout >for help it's easier for people if the base is a conventional layout.
On Mon, 9 Mar 2026 23:47:01 -0400, Paul wrote:
At the time, this was an example of a mediaserver.
http://en.wikipedia.org/wiki/Serviio
No need to use anything proprietary, or even dedicate a machine to it.
<https://packages.debian.org/trixie/gerbera> ><https://packages.debian.org/trixie/minidlna>
Windows Media Player Legacy, has a mediaserver on it.
Whatever happened to Windows Home Server?
Couldn’t compete with Linux.
On Mon, 9 Mar 2026 21:07:07 +0100, Carlos E.R. wrote:
Modern fdisk can do gpt.
That was fixed ages ago, so long ago I can barely remember. When did
2TB drives become commonplace?
On Mon, 9 Mar 2026 18:32:48 -0000 (UTC), Lew Pitcher wrote:
d) /opt ...
/opt and /usr/local are explicitly set aside as areas where the
standard distro packages will never put anything. So yes, you can use
these how you like. I think the convention is, /opt is available for third-party applications that don’t install through the package system (e.g. proprietary apps), while /usr/local is available for whatever
the local sysadmin wants to install there.
On Mon, 9 Mar 2026 18:16:51 +0100, J.O. Aho wrote:
I do recommend not not have a mount point inside another mount
point, as it can give you issues.
You don’t have a choice. The only mount point not inside another mount point is the root filesystem, “/”.
On Mon, 3/9/2026 2:32 PM, Lew Pitcher wrote:
<snip>If I put it in /mnt and call it "Mediashare" with sub directories "Music", >>> "Pictures" and "Videos" is the network path /Mediashare/Music or
/mnt/Mediashare/Music?
Probably not.
If you are sharing with Windows systems, you will either need to run a
Samba (SMB) server in Linux on your Microserver, in which case, the
network path is whatever you configure Samba to externalize it as, or
you run a Linux NFS server on the Microserver, (and a Windows NFS client
on the Windows boxes), and externalize as
<microserver_host_name>:/mnt/Mediashare/Music
You can get mediaserver software, which uses its own protocol.
Something like VLC (available for Windows and Linux), should be
able to connect to a media server.
There is one utility, that "lists" what the media server
has stored on it, for your selections. Then, when you use
a "client" software such as VLC, you expect the client to
also reproduce the list of entries for a ten foot interface
(selecting a movie with your TV remote in your movie room).
it is when the mediaserver fouls up, that the diagnostic
does not show anything, and then you know when the
client or viewer-software is also not showing the list,
it is not the fault of the client, and is the fault of the server.
"AI Overview
A DLNA (Digital Living Network Alliance) media server allows you
to stream videos, music, and photos from a storage device (PC, NAS, phone)
to compatible devices (Smart TVs, consoles) over a local network.
It uses UPnP for easy, automatic discovery of content. Popular software
solutions include Plex, Universal Media Server, and Windows Media Streaming.
"
I couldn't see the drive from Windows so installed Samba but have hit the >snag that smb.conf is read only. Is there a Linux file manager that has >options such as change permissions or open as root or whatever is needed?
"AI Overview
A DLNA (Digital Living Network Alliance) media server allows you
to stream videos, music, and photos from a storage device (PC, NAS, phone)
to compatible devices (Smart TVs, consoles) over a local network. >> It uses UPnP for easy, automatic discovery of content. Popular software
solutions include Plex, Universal Media Server, and Windows Media Streaming.
"
Not Kodi?
On 10/03/2026 in message <[email protected]> Jeff Gaines wrote:
I couldn't see the drive from Windows so installed Samba but have hit the snag that smb.conf is read only. Is there a Linux file manager that has options such as change permissions or open as root or whatever is needed?
OK, a cup of tea later...
I did chmod 777 smb.conf which I think removes permissions then edited the file and I can now see the Mediashare directory from Windows.
However, I think that was overkill but all the help I have found for chmod produces reams of stuff when I just want something simple.
What about the following:
chmod +w smb.conf
Do the editing and save
chmod -w smb.conf
Would that do it? If not can somebody tell me what I need please?
Whatever happened to Windows Home Server?
Couldn’t compete with Linux.
The NVidia TV Show can just share a network without DLNA, Kodi (the
app on the NVidia) treats iso files as DVDs, a rare accomplishment
but enormously useful!
On Mon, 3/9/2026 2:32 PM, Lew Pitcher wrote:
<snip>If I put it in /mnt and call it "Mediashare" with sub directories "Music", >>> "Pictures" and "Videos" is the network path /Mediashare/Music or
/mnt/Mediashare/Music?
Probably not.
If you are sharing with Windows systems, you will either need to run a
Samba (SMB) server in Linux on your Microserver, in which case, the
network path is whatever you configure Samba to externalize it as, or
you run a Linux NFS server on the Microserver, (and a Windows NFS client
on the Windows boxes), and externalize as
<microserver_host_name>:/mnt/Mediashare/Music
You can get mediaserver software, which uses its own protocol.
Something like VLC (available for Windows and Linux), should be
able to connect to a media server.
On Tue, 3/10/2026 10:19 AM, Jeff Gaines wrote:
On 10/03/2026 in message <[email protected]> Jeff Gaines wrote:
I couldn't see the drive from Windows so installed Samba but have hit the snag that smb.conf is read only. Is there a Linux file manager that has options such as change permissions or open as root or whatever is needed?
OK, a cup of tea later...
I did chmod 777 smb.conf which I think removes permissions then edited the file and I can now see the Mediashare directory from Windows.
However, I think that was overkill but all the help I have found for chmod produces reams of stuff when I just want something simple.
What about the following:
chmod +w smb.conf
Do the editing and save
chmod -w smb.conf
Would that do it? If not can somebody tell me what I need please?
On a Linux machine, you wear two hats.
When unelevated, you slap things around without a care in the world.
When a job calls for "changes" to a secured thing, you think about
all the implications while wearing your "root hat". You are, after all,
the *provider* of security for the user community time-sharing the
Linux box. As the administrator/root , you don't take chances.
*******
sudo nano smb.conf # We leave the permissions alone. Security.
# Yes, Jeff, you can make Windows 98 out of it by chmod 777 the-whole-world
# but then when the box tips over, do remember to tell us
# it is a "Windows 98 setup" :-)
Some things inadvertently have the wrong permissions when unpacked
from a ZIP or something. Those are the ones we chmod to correct the situation. But lots of stuff in /etc needs security and root ownership,
and we can't be smashing the permissions in /etc . Everything in
there was prepared for us, and should already have correct permissions.
On a Linux machine, you wear two hats.
When unelevated, you slap things around without a care in the world.
When a job calls for "changes" to a secured thing, you think about
all the implications while wearing your "root hat". You are, after all,
the provider of security for the user community time-sharing the
Linux box. As the administrator/root , you don't take chances.
*******
sudo nano smb.conf # We leave the permissions alone. Security.
# Yes, Jeff, you can make Windows 98 out of it by chmod 777 the-whole-world
# but then when the box tips over, do remember to tell us
# it is a "Windows 98 setup" :-)
Some things inadvertently have the wrong permissions when unpacked
from a ZIP or something. Those are the ones we chmod to correct the >>situation. But lots of stuff in /etc needs security and root ownership,
and we can't be smashing the permissions in /etc . Everything in
there was prepared for us, and should already have correct permissions.
Ok, I don't need to get in and do the lecture again :-)
I'll just mention that there are several editors which you can choose the >one you like. You can use joe, which comes in 5 names: joe, jstar, jmacs, >rjoe, jpico. Choose the one you prefer. Another one you can use is
"mcedit", which is actually the editor of "Midnight Commander" or "mc".
The two traditional Linux editors are "vi" and "emacs". There are
flamewars about the two. Both very powerful, but neither is easy to use, >specially coming from Windows. But "vi" is present in every Linux or Unix >machine.
I recommend you edit root.bashrc and create this line:
export EDITOR=/usr/bin/jstar
Put there the editor you prefer. This way, when you call a command like >"visudo" or "crontab -e", the edit will happen using your preferred editor >instead of the default "vi".
To get back on track what about the following:
chmod +w smb.conf
Do the editing and save
chmod -w smb.conf
Would that do it?
If not can somebody tell me what I need please?
On 10/03/2026 in message <[email protected]r> Carlos E.R. wrote:
On a Linux machine, you wear two hats.
When unelevated, you slap things around without a care in the world.
When a job calls for "changes" to a secured thing, you think about
all the implications while wearing your "root hat". You are, after all,
the provider of security for the user community time-sharing the
Linux box. As the administrator/root , you don't take chances.
*******
sudo nano smb.conf # We leave the permissions alone. Security.
# Yes, Jeff, you can make Windows 98 out of it by chmod 777 the-whole-world
# but then when the box tips over, do remember to tell us
# it is a "Windows 98 setup" :-) >>>
Some things inadvertently have the wrong permissions when unpacked
from a ZIP or something. Those are the ones we chmod to correct the
situation. But lots of stuff in /etc needs security and root ownership,
and we can't be smashing the permissions in /etc . Everything in
there was prepared for us, and should already have correct permissions.
Ok, I don't need to get in and do the lecture again :-)
I'll just mention that there are several editors which you can choose the one you like. You can use joe, which comes in 5 names: joe, jstar, jmacs, rjoe, jpico. Choose the one you prefer. Another one you can use is "mcedit", which is actually the editor of "Midnight Commander" or "mc".
The two traditional Linux editors are "vi" and "emacs". There are flamewars about the two. Both very powerful, but neither is easy to use, specially coming from Windows. But "vi" is present in every Linux or Unix machine.
I recommend you edit root.bashrc and create this line:
export EDITOR=/usr/bin/jstar
Put there the editor you prefer. This way, when you call a command like "visudo" or "crontab -e", the edit will happen using your preferred editor instead of the default "vi".
[snipped]
To get back on track what about the following:
chmod +w smb.conf
Do the editing and save
chmod -w smb.conf
Would that do it? If not can somebody tell me what I need please?
On 10 Mar 2026 11:33:35 GMT, Jeff Gaines wrote:
Whatever happened to Windows Home Server?
Couldn’t compete with Linux.
The NVidia TV Show can just share a network without DLNA, Kodi (the
app on the NVidia) treats iso files as DVDs, a rare accomplishment
but enormously useful!
Not actually that rare -- Kodi is Linux-based, after all. And Kodi
boxes are what killed Windows Media Center.
Windows Home Server was left in the dust by versatile NAS boxes
running Linux.
On Tue, 3/10/2026 2:43 PM, Lawrence D’Oliveiro wrote:
Windows Home Server was left in the dust by versatile NAS boxes
running Linux.
Windows Media Center was killed by the cost of providing certain
things.
[snipped]
To get back on track what about the following:
chmod +w smb.conf
Do the editing and save
chmod -w smb.conf
Would that do it? If not can somebody tell me what I need please?
It doesn't happen too often, but there are web pages which
actually display "best practices", the same "best practices"
that get you hired as an IT person.
It's a pain in the ass to do
sudo nano /etc/samba/smb.conf # and type in that password
The sudo means "do it as if I was root right now". It
has the elevation needed for the job of editing
things in the /etc area.
In the Windows world, one individual was demonstrating
how an IT person handles Windows permissions. Most of
us, while editing Windows, we smash a permission and don't
put it back. This leaves a gap-toothed mess on a disk
with regard to permissions.
The IT class person, demonstrated how you can use ICACLS
utility, and record all the permissions on a tree section.
Then, reach in and smash to your hearts content. Finally,
after all necessary permissions have been restored by an
ICACLS playback command, now it is as if the IT class person
had never been there and mucking about.
These are the kinds of lessons we're suppose to learn
while repairing/preparing computers.
The one and only time I've had malware on a computer,
the truth of the matter is, I left the barn door open
and that's how the malware got in. I did not explicitly
"pull a Windows 98", but I was fascinated by an obscure
way of installing the OS. And I had not even considered
what a mess that made. And that's the foothold the
malware needed. It was easy malware to remove, but
it spoils my "track record".
I can share that experience with you by telling you
to "not leave any barn doors open" :-) If you start
fiddling write bits, sooner or later, you leave
them open.
At work, I used to do very minor admin tasks with "local root"
(a permission that isn't worth shit). But, as part of the
local IT allowing me to do that, I have to keep my house
in order and keep my nose clean with regard to "making a mess".
That's how you lose your privileges at work. (This
was on Sun Sparc machines and Unix.) Did I make grievous errors
while running as local root ? You betcha :-)
On 10/03/2026 in message <[email protected]r> Carlos E.R. wrote:
On a Linux machine, you wear two hats.
When unelevated, you slap things around without a care in the world.
When a job calls for "changes" to a secured thing, you think about
all the implications while wearing your "root hat". You are, after all,
the provider of security for the user community time-sharing the
Linux box. As the administrator/root , you don't take chances.
*******
sudo nano smb.conf # We leave the permissions alone. Security.
# Yes, Jeff, you can make Windows 98 out of it
by chmod 777 the-whole-world
# but then when the box tips over, do remember
to tell us
# it is a "Windows 98 setup" :-) >>>
Some things inadvertently have the wrong permissions when unpacked
from a ZIP or something. Those are the ones we chmod to correct the
situation. But lots of stuff in /etc needs security and root ownership,
and we can't be smashing the permissions in /etc . Everything in
there was prepared for us, and should already have correct permissions.
Ok, I don't need to get in and do the lecture again :-)
I'll just mention that there are several editors which you can choose
the one you like. You can use joe, which comes in 5 names: joe, jstar,
jmacs, rjoe, jpico. Choose the one you prefer. Another one you can use
is "mcedit", which is actually the editor of "Midnight Commander" or
"mc".
The two traditional Linux editors are "vi" and "emacs". There are
flamewars about the two. Both very powerful, but neither is easy to
use, specially coming from Windows. But "vi" is present in every Linux
or Unix machine.
I recommend you edit root.bashrc and create this line:
export EDITOR=/usr/bin/jstar
Put there the editor you prefer. This way, when you call a command
like "visudo" or "crontab -e", the edit will happen using your
preferred editor instead of the default "vi".
[snipped]
To get back on track what about the following:
chmod +w smb.conf
Do the editing and save
chmod -w smb.conf
Would that do it? If not can somebody tell me what I need please?
On Tue, 3/10/2026 2:43 PM, Lawrence D’Oliveiro wrote:
On 10 Mar 2026 11:33:35 GMT, Jeff Gaines wrote:
On a lot of TV tuner packages, the TV Guide Data cost money,
and no central authority can pay those forever, and they stop
providing them after a while. And any small companies
that sell the listings, also go out of business because they
don't sell enough subscriptions to pay a TV network $50,000 for
a year of listings.
On Mon, 09 Mar 2026 15:57:00 +0000, Jeff Gaines wrote:
I am awaiting a HP ProLiant MicroServer Gen8 which I plan to use as
a home media server and to create iso files from DVDs with Brasero.
I am pretty well 100% Windows user although I am using Brasero on
one of the original micro servers to prepare iso files at the
moment, the Gen8 has a Xeon processor so I expect it to be a bit
more responsive.
I will be using Linux Mint Mate as it's cleanish and reasonably lightweight. My understanding is it will split the OS drive by
using mount points rather than partitions (on Windows I use
separate drives C:(OS) and D:(Data)). The Microserver was made
before the days of UEFI, I hope Linux can live with that.
I will use 2 x additional drives, first one for shared media,
second to back it up (in turn this will be backed up to my home
server).
If I understand it a add the second drive after the install, set it
up as GPT then mount it so it can be seen on the network.
Does it matter where I mount it i.e. in /root or /home or /mnt?
Yes, sort of.
Linux standards reserve the use of a number of directories, including
/root and /mnt. Your "shared media" doesn't fit within the use of
/root and (if you squint with one eye closed) might fit within the
use of /mnt or /media. If you really want to keep out of trouble, you
can either create a media sharing data directory under a) /home (like
the quintessential /home/ftp directory), or b) /usr/local/share, or
c) /var, or d) /opt, or e) under the root directory and mount your
"shared media" drive there.
If I put it in /mnt and call it "Mediashare" with sub directories
"Music", "Pictures" and "Videos" is the network path
/Mediashare/Music or /mnt/Mediashare/Music?
Probably not.
If you are sharing with Windows systems, you will either need to run
a Samba (SMB) server in Linux on your Microserver, in which case, the
network path is whatever you configure Samba to externalize it as, or
you run a Linux NFS server on the Microserver, (and a Windows NFS
client on the Windows boxes), and externalize as
<microserver_host_name>:/mnt/Mediashare/Music
I want to try and follow any conventions that exist as if I need to
shout for help it's easier for people if the base is a conventional
layout.
Placement is the easy part; mountpoints are just directories (they
don't need to be empty) that you want to overlay with the device to
be mounted. Just pick a mountpoint that won't interfere with the
system (something empty that isn't required by the OS or it's
utilities) and go with it.
Setting up the networking will be the hard point.
Many thanks :-)
Luck be with you
Some amount of SAMBA was neutered for security reasons.
This is a constant annoyance. You are unlikely to ever
see a "Network Neighbourhood".
| Sysop: | DaiTengu |
|---|---|
| Location: | Appleton, WI |
| Users: | 1,099 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 492373:54:55 |
| Calls: | 14,106 |
| Calls today: | 2 |
| Files: | 187,124 |
| D/L today: |
1,512 files (693M bytes) |
| Messages: | 2,496,031 |