On Thu, 25 Aug 2022 07:59:00 - (UTC)
Stuart Henderson wrote:
> /var, maybe exclude /var/cache. (maybe also /var/log, but it can be
> useful to have).
>
Is there a way to exclude directories within a selected volume for a
full backup? It looks as though nodump only works for levels above 0.
for
backups. Do you understand what it does and how it works?
A backup done to the same machine is not really a backup.
> i already have /home /etc and /root set for backup,
> are there any other partitions i should bear in mind ?
/var, maybe exclude /var/cache. (maybe also /var/log, but it can be
useful to have).
--
Please keep replies on the mailing list.
Remember that some that some things need to be explicitly dumped -
eg databases and repositories
because when you do restore, you might want to restore to an upgraded OS
version.
Rather than use dump, I use gtar - I have restored stuff after 30 years
with gtar,
to completely different OSes - eg
partitions i should bear in mind ?
shadrock
I agree with "know exactly what you need" or "save everything"
If backups are cheap in time and money just save everything
as often as you can - daily if you do a lot online.
Rebuilding from incremental dumps can be painful.
Even i
partitions i should bear in mind ?
shadrock
/root and /etc should be on the root partition ( / , sd0a, typically).
There is *generally* not much data of substance in the directory /root,
but that depends on your environment.
Also depending on your environment, there's often a lot of really important
Hello Shadrock
24.08.2022 20:28 tarihinde Shadrock Uhuru yazdı:
1 i want to do a fresh reinstall e.g. to move to a larger hard drive.
2 for a disaster recovery like what i experienced above.
These arguments will require a "full backup". It means backup all
partitions, so you c
On 2022-08-24 12:51:16-0500, Allan Streib wrote:
> On Wed, Aug 24, 2022, at 12:28, Shadrock Uhuru wrote:
> > i already have /home /etc and /root set for backup,
> > are there any other partitions i should bear in mind ?
>
> I always backup /var
The above make sense to me a
On Wed, Aug 24, 2022, at 12:28, Shadrock Uhuru wrote:
> i already have /home /etc and /root set for backup,
> are there any other partitions i should bear in mind ?
I always backup /var
Allan
for a disaster recovery like what i experienced above.
i will be using ville walveranta's autodump 1.5a script
which does a full dump on sundays and incremental dumps during the week,
i already have /home /etc and /root set for backup,
are there any other partitions i should bear in mind ?
shadrock
; details). I was wondering if there is a way to compact the partitions, i.e.
>> move the partitions following the deleted one up to fill the hole,
>> potentially leaving corresponding free space at the end.
>>
>> I’d prefer to not have to use dd(1) on the raw device to move the da
On 2022-06-13, Mike Fischer wrote:
> After solving a recent problem on a VM where the /usr/local was full I was
> left with a disklabel that had a hole of unused space in it (see below for
> details). I was wondering if there is a way to compact the partitions, i.e.
> move th
Hi!
After solving a recent problem on a VM where the /usr/local was full I was left
with a disklabel that had a hole of unused space in it (see below for details).
I was wondering if there is a way to compact the partitions, i.e. move the
partitions following the deleted one up to fill
For people who really want to tinker with the ports system,
perhaps non intuitively, bulk(8) is the manpage that contains
the most exhaustive set of information about how you might
want to configure your system and the choices involved.
"James Mintram" writes:
> For context, I need erlang 24 + elixir 13 and the current packages
> are older than that. Which is why I have found myself working
> with ports almost immediately (pro level yak shaving..)
There were a post in ports mailing list with a patch for erlang port
update:
As a long time OpenBSD user I install from packages but also build from ports.
There is a usage case for both, but realize building packages is not a
"standard" system.
Twenty years ago building packages from ports was the norm, but not today.
73
diana
On April 18, 2022 9:35:27 AM MDT,
On Mon, Apr 18, 2022 at 04:15:46PM +, James Mintram wrote:
> Thanks for all of the very useful replies, I have managed to get
> everything working.
>
> For context, I need erlang 24 + elixir 13 and the current packages
> are older than that. Which is why I have found myself working
> with
On Mon, Apr 18, 2022 at 01:36:18PM -, Stuart Henderson wrote:
[...]
> > 2) Should there be a /usr/local/pobj partition created with correct mount
> > options? (I appreciate building ports is an "advanced" thing to do - but it
> > feels weird having to mess with partition layout after a
. There are downsides with the policy of creating seperate
partitions like we do, so that we can vary mountpoint flat options.
We kind of shrug and cope with it.
James Mintram wrote:
> Hi. I am new to OpenBSD, so these questions come from my first
> experience with the system.
>
>
it elsewhere.
On a typical system I don't think it's helpful to have this much larger
(though it is now starting to get a little tight for a checkout so maybe it
could go up a few hundred MB). /usr/src isn't needed on a typical machine
and raising the size will impact on sizes of other partitions,
ed behaviour. Since your disk has a 'real' disklabel on it, any
other fdisk partitions that you create will not be parsed and added
automatically.
> I need a way to generate it without having to reinstall OpenBSD.
You need to add the details of the new, non-OpenBSD partition to the disk
On Mon, Apr 12, 2021 at 08:08:12PM -0700, Paul Pace wrote:
> Hello!
>
> I generally try and run things as a project recommends, but I am wondering
> about running different additional partitions (e.g., add /var/www) or
> changing partition letter (e.g., move /var to the end for
Hello!
I generally try and run things as a project recommends, but I am
wondering about running different additional partitions (e.g., add
/var/www) or changing partition letter (e.g., move /var to the end for
convenient VPS expansion).
I know it isn't the biggest thing in the world
On Sun, Feb 28, 2021 at 08:30:14PM +0100, Janne Johansson wrote:
Is /var a filesystem of its own? Otherwise it could be /var/tmp or
some other place under /var which is used for unpacking packages.
Yes, /var is on its own filesystem, with 10.4G available.
On Sun, Feb 28, 2021 at 05:17:15PM +, James Cook wrote:
> This makes little sense to me. Why should deleting a 20MB file on a
> filesystem with >700MB free space be sufficient for the install to go
> through? Especially when the install obviously doesn't need that much space
> on the
Den sön 28 feb. 2021 kl 14:51 skrev :
> I deleted the file and `pkg_add libreoffice` worked as expected.
> Post-install I still have 746MB free in /, according to `df -h`.
>
> This makes little sense to me. Why should deleting a 20MB file on a
> filesystem with >700MB free space be sufficient for
On Sat, Feb 27, 2021 at 11:52:39PM +, James Cook wrote:
Sorry, you're right, pkg_add can add files to /. But generally those
will be quite small (/etc/make2fs.conf sounds like a configuration
file).
How big is your root partition, and how much space is used? For example
mine is like this
On Sat, Feb 27, 2021 at 11:52:39PM +, James Cook wrote:
If you have a lot more space used, you could try to figure out what's
using it. My go-to command is "du -xah /|sort -h|less"
That's a neat command, and amazingly enough it did the trick: there was
a 20MB file, INS@yjf(...) located in
On Sat, Feb 27, 2021 at 03:27:41PM -0600, Edgar Pettijohn wrote:
Its more likely that you accidentaly used dd to write to a usb stick
and instead
wrote to a file in /dev. Thats the only way I've ever had this
problem.
You're right -- I had written a file to /dev. After deleting it, the
On Sat, Feb 27, 2021 at 08:27:07PM +, James Cook wrote:
Something's strange about your setup. The installer normally creates a
separate partition for /usr and maybe /usr/local. If you're using
pkg_add, then packages go in /usr/local, so they shouldn't end up on
your root partition.
If your
On Sat, Feb 27, 2021 at 11:21:45PM +, tetrahe...@danwin1210.me wrote:
> On Sat, Feb 27, 2021 at 08:27:07PM +, James Cook wrote:
> > Something's strange about your setup. The installer normally creates a
> > separate partition for /usr and maybe /usr/local. If you're using
> > pkg_add, then
When installing OpenBSD, the default partition layout only allocates 1GB
to / ... most of the disk space is allocated to /home.
Once you start installing packages, / quickly grows beyond 1GB, and it
looks like even some large packages exceed the available space on their
own:
Error:
On Sat, Feb 27, 2021 at 11:21:45PM +, tetrahe...@danwin1210.me wrote:
> On Sat, Feb 27, 2021 at 08:27:07PM +, James Cook wrote:
> > Something's strange about your setup. The installer normally creates a
> > separate partition for /usr and maybe /usr/local. If you're using
> > pkg_add, then
On Sat, Feb 27, 2021 at 03:32:44PM +, tetrahe...@danwin1210.me wrote:
> When installing OpenBSD, the default partition layout only allocates 1GB to
> / ... most of the disk space is allocated to /home.
>
> Once you start installing packages, / quickly grows beyond 1GB, and it looks
> like
On Sat, Feb 27, 2021 at 03:32:44PM +, tetrahe...@danwin1210.me wrote:
> When installing OpenBSD, the default partition layout only allocates 1GB to
> / ... most of the disk space is allocated to /home.
>
> Once you start installing packages, / quickly grows beyond 1GB, and it looks
> like
are obnoxiously harsh.'
>
> I read the 16 partitions thread and think, "I marvel at their patience
> with interlocutors who have not read the relevant source code and give
> no indication that they would understand it if they did."
>
> --
>
> Edward Ahlsen-Girard
&g
On Thu, Apr 30, 2020 at 11:13 AM Consus wrote:
> On Thu, Apr 30, 2020 at 07:22:35AM -0500, Ed Ahlsen-Girard wrote:
> > I read the 16 partitions thread and think, "I marvel at their patience
> > with interlocutors who have not read the relevant source code and gi
On Thu, Apr 30, 2020 at 07:22:35AM -0500, Ed Ahlsen-Girard wrote:
> Some people read replies in misc and say, "wow, Theo and the OBSD devs
> are obnoxiously harsh.'
>
> I read the 16 partitions thread and think, "I marvel at their patience
> with interlocutors who h
Some people read replies in misc and say, "wow, Theo and the OBSD devs
are obnoxiously harsh.'
I read the 16 partitions thread and think, "I marvel at their patience
with interlocutors who have not read the relevant source code and give
no indication that they would understand it i
- 1 root operator4, 28 Apr 17 11:50 sd1m
> brw-r- 1 root operator4, 29 Apr 17 11:50 sd1n
> brw-r- 1 root operator4, 30 Apr 17 11:50 sd1o
> brw-r- 1 root operator4, 31 Apr 17 11:50 sd1p
>
> Look very carefully at this column ^^
>
Are th
> Medoesn't a care a flying fsck about what is "trendy".
Is this the most ironic sentence ever posted on here? Dubiously censoring an
expletive with a common 'Unix' utility isn't motivated by some sort of desire
to feel like a part of the righteous ones? Come on.
by on this forum
without scrutiny.
--
Patrick Harper
paia...@fastmail.com
On Thu, 23 Apr 2020, at 18:06, zeurk...@volny.cz wrote:
> "Groot" wrote:
> > I've tried and failed to create more than 16
> > partitions on OpenBSD. First of all I don't
> > understand the di
Amelia A Lewis wrote:
> So, and I recognize that the answer might reasonably be "go read more
> code and figure it out yourself," a question for Theo and others if you
> have a moment: why couldn't an arch expand past sixteen? It seems, both
> from the math calculating struct size (which may
/* the magic number (again) */
u_int16_t d_checksum; /* xor of data incl. partitions
*/
/* filesystem and partition information: */
u_int16_t d_npartitions; /* number of partitions in
following */
u_int32_t d_bbsize;
Theo de Raadt writes:
> Reality hasn't changed. A sector is still 512 bytes, and
> disklabel has to fit in it.
OK.
Allan
e complaining about the 16 partition limit, and I'm not
> >> asking for anything to change. I've only said I think it's something
> >> that is the way it is because of the design decisions made on the
> >basis
> >> of "reality" at the time, and which pr
ve only said I think it's something
>> that is the way it is because of the design decisions made on the
>basis
>> of "reality" at the time, and which probably didn't contemplate the
>day
>> when everyone would have multi-terabyte hard drives and that people
>
"reality" at the time, and which probably didn't contemplate the day
> when everyone would have multi-terabyte hard drives and that people
> might want more than 16 partitions. I stand corrected on that
> speculation if I'm wrong.
Reality hasn't changed. A sector is still 512 bytes, and
disklabel has to fit in it.
You are not LISTENING.
when everyone would have multi-terabyte hard drives and that people
might want more than 16 partitions. I stand corrected on that
speculation if I'm wrong.
Allan
Ingo Schwarze wrote:
The limitation to 16 partitions definitely feels painful to me.
There is softraid(4). The only discipline that supports a single
chunk is crypto. Make a couple of OpenBSD RAID partitions,
set them up as crypto, partition those new crypto pseudo-devices,
up to 16
A little bit of fun, slightly related to some of the discussion:
[1] is something that comes into my mind each time i read some of the emails
[2] is coming next
[1] https://www.youtube.com/watch?v=nlt5Wa13fFU
[2] https://www.youtube.com/watch?v=zIV4poUZAQo
Allan Streib wrote:
> Theo de Raadt writes:
>
> > Allan Streib wrote:
> >
> >> Seems like one of those numbers that was chosen long ago, when disks
> >> had orders of magnitude less storage capacity they have now, and 16
> >> parti
Theo de Raadt writes:
> Allan Streib wrote:
>
>> Seems like one of those numbers that was chosen long ago, when disks
>> had orders of magnitude less storage capacity they have now, and 16
>> partitions really would have been more than enough.
>
> the wo
Allan Streib wrote:
> Seems like one of those numbers that was chosen long ago, when disks
> had orders of magnitude less storage capacity they have now, and 16
> partitions really would have been more than enough.
the word "chosen" makes it seem like such an arbitrary deci
Ingo Schwarze writes:
> The limitation to 16 partitions definitely feels painful to me.
Well, one pragmatic solution is to add another disk -- 16 more
partitions. Not always possible, granted.
Seems like one of those numbers that was chosen long ago, when disks
had orders of magnitude l
Lars,
Your email didn't contain a diff.
Is there a reason for that?
I'm wondering whether it is because it is too difficult for you,
or maybe it is too difficult for everyone, or maybe you are simply
talking out of your ass by trying to assign work to other people
because that is your nature?
HAMMER2 could be ported. There is much collaboration between OpenBSD
and DragonflyBSD already (drivers for example).
https://www.dragonflybsd.org/docs/handbook/environmentquickstart/#index3h2
On Thu, 2020-04-23 at 16:48 -0400, Eric Furman wrote:
> ZFS cannot be ported to OBSD. It has an
Hi Strahil,
Strahil Nikolov wrote on Thu, Apr 23, 2020 at 11:16:41PM +0300:
> And who the hell needs more than 16 partitions ?
Me, and i'm quite sure many do. It's certainly not a good idea to
combine any partitions that are separate in a default install because
there are good reasons for
On 2020-04-23, Ian Darwin wrote:
> So: I was able to newfs, mount, and use an OpenBSD partition which
> disklabel called 'a' and which had no trace of an fdisk partition around it.
>
> As Allan pointed out, this is not for booting from - none of those
> fdisk partitions loo
On 2020-04-24 04:45, zeurk...@volny.cz wrote:
> Your point is well-taken (though this is just the way mespeaks); yet,
> Theo is a native speaker
No-one is a native speaker of this made up crap, mecraps
On Thu, Apr 23, 2020 at 10:29:01PM +0200, Francois Pussault wrote:
> I agree ; Using more than 10 partitions is rare but in case of NFS or other
> network shares of course.
> 16 is really enough in my point of view.
>
I've got to disgree with this one. I'm doing porting work.
I
On 2020-04-23 11:45, zeurk...@volny.cz wrote:
"Jan Betlach" wrote:
For a non-native English speaker like myself, it is very difficult to
read your mestuff...
Your point is well-taken (though this is just the way mespeaks); yet,
Theo is a native speaker, and he seems to have completely
re n Go Drive
duid:
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 478
total sectors: 768
boundstart: 0
boundend: 768
drivedata: 0
16 partitions:
#size offset fstype [fsize bsize cpg]
c: 768000
>
> From: Strahil Nikolov
> Sent: Thu Apr 23 22:16:41 CEST 2020
> To: , Theo de Raadt ,
>
> Cc: Martin Schröder
> Subject: Re: More than 16 partitions
>
>
> On April 23, 2020 10:46:44 PM GMT+03:00, Theo de Raadt
On Thu, Apr 23, 2020 at 08:14:25PM +0200, Jan Betlach wrote:
> For a non-native English speaker like myself, it is very difficult to read
> your mestuff…
One may practice by reading Gollum/Smeagol-passages..
For a non-native English speaker like myself, it is very difficult to
read your mestuff…
Jan
On 23 Apr 2020, at 19:47, zeurk...@volny.cz wrote:
theo wrote:
That is a rewriting of history.
It's history the way meknows it. Mecertainly predates some of it.
The disklabel format
On Thu, Apr 23, 2020, at 4:16 PM, Strahil Nikolov wrote:
> So, can I setup openBSD labels on x86_64 without legacy/GPT partition
> first ?
> And who the hell needs more than 16 partitions ? Why not we just port
> ZFS from FreeBSD, or LVM from Linux and get over it ?
>
>
> So, can I setup openBSD labels on x86_64 without legacy/GPT partition first ?
IIRC yes you can, as long as you don't need to boot from that disk.
Allan
gt;>
Some of these e-mails were useful others not...
So, can I setup openBSD labels on x86_64 without legacy/GPT partition first ?
And who the hell needs more than 16 partitions ? Why not we just port ZFS from
FreeBSD, or LVM from Linux and get over it ?
P.S.: The last one was not a real question, but I would like to hear if
anyone has attempted to port any of these 2 .
Best Regards,
Strahil Nikolov
You need to stop making this mailing list just about you.
STFU.
wrote:
> "Martin Schröder" wrote:
> > Am Do., 23. Apr. 2020 um 21:31 Uhr schrieb :
> >> No problem. Would it be too crude a suggestion that we go back to the
> >> content now...?
> >
> > You didn't provide any patch.
>
> That
"Martin Schröder" wrote:
> Am Do., 23. Apr. 2020 um 21:31 Uhr schrieb :
>> No problem. Would it be too crude a suggestion that we go back to the
>> content now...?
>
> You didn't provide any patch.
That is entirely correct.
--zeurkous.
--
Friggin' Machines!
Am Do., 23. Apr. 2020 um 21:31 Uhr schrieb :
> No problem. Would it be too crude a suggestion that we go back to the
> content now...?
You didn't provide any patch.
"Christian Groessler" wrote:
> On 4/23/20 7:57 PM, zeurk...@volny.cz wrote:
>
>> theo wrote:
>>> You made it all up.
>> That's an easy accusation, with an easy response: No, medid not make any
>> of it up
>
>
> Could you refrain from using your idiotic "me.."-words?
Fine, me'll try and keep the
On 4/23/20 7:57 PM, zeurk...@volny.cz wrote:
theo wrote:
You made it all up.
That's an easy accusation, with an easy response: No, medid not make any
of it up
Could you refrain from using your idiotic "me.."-words? Thanks
"Jan Betlach" wrote:
> For a non-native English speaker like myself, it is very difficult to
> read your mestuff...
Your point is well-taken (though this is just the way mespeaks); yet,
Theo is a native speaker, and he seems to have completely missed the
content of merecent responses.
Weird,
theo wrote:
> You made it all up.
That's an easy accusation, with an easy response: No, medid not make any
of it up.
--zeurkous.
--
Friggin' Machines!
You made it all up.
wrote:
> theo wrote:
> > That is a rewriting of history.
>
> It's history the way meknows it. Mecertainly predates some of it.
>
> > The disklabel format predates the PC.
>
> Indeed. Mewasn't sure where and when exactly it appeared, so meleft that
> bit out. But medid
theo wrote:
> That is a rewriting of history.
It's history the way meknows it. Mecertainly predates some of it.
> The disklabel format predates the PC.
Indeed. Mewasn't sure where and when exactly it appeared, so meleft that
bit out. But medid know it was older, and metried to communicate that
ve tried and failed to create more than 16
> > partitions on OpenBSD. First of all I don't
> > understand the difference between the operations
> > performed by fdisk and disklabel. Is it that
> > OpenBSD sees partitions differently? First we
> > create an OpenBSD par
"Groot" wrote:
> I've tried and failed to create more than 16
> partitions on OpenBSD. First of all I don't
> understand the difference between the operations
> performed by fdisk and disklabel. Is it that
> OpenBSD sees partitions differently? First we
> create an
Haai,
theo wrote:
> Groot wrote:
>
>> I've tried and failed to create more than 16
>> partitions on OpenBSD. First of all I don't
>> understand the difference between the operations
>> performed by fdisk and disklabel. Is it that
>> OpenBSD sees partit
Groot wrote:
> I've tried and failed to create more than 16
> partitions on OpenBSD. First of all I don't
> understand the difference between the operations
> performed by fdisk and disklabel. Is it that
> OpenBSD sees partitions differently? First we
> create an OpenBSD pa
On 25/12/19 10:30 pm, Sriram Narayanan wrote:
> On Wed, 25 Dec 2019 at 7:41 PM, Stuart Longland
> wrote:
>
>> Both VMs should probably be re-built from scratch as a matter of sanity,
>> but I can do that at leisure now, what I have, works.
>
>
> What hypervisor are you using? Does it support
ter VM I had to do a very
> brutal equivalent of it when it ran out of disk space mid-update in the
> installer… I basically blew away /usr/* (minus directories that are on
> different partitions like 'local') figuring it'd re-instate the files
> when it unpacked the newer file sets.
ew away /usr/* (minus directories that are on
different partitions like 'local') figuring it'd re-instate the files
when it unpacked the newer file sets.
This lead to some missing files in /usr/share/relink but I was able to
re-instate those from another 6.6 VM that did update cleanly
(ironi
On Mon, Dec 23, 2019 at 10:42:47PM +, rgci...@disroot.org wrote:
December 24, 2019 4:42 AM, "Dumitru Moldovan" wrote:
On Sun, Dec 22, 2019 at 10:56:20AM +1000, Stuart Longland wrote:
So, a few years ago now, I deployed a router VM with OpenBSD 6.1 AMD64.
Later that got updated to 6.2,
On 24/12/19 12:51 pm, Edgar Pettijohn wrote:
>
> On Dec 23, 2019 4:42 PM, rgci...@disroot.org wrote:
>>
>> December 24, 2019 4:42 AM, "Dumitru Moldovan" wrote:
>> one thing that is useful is sysclean(8)
>>
>> my process now after a doas sysupgrade is
>> 1) doas sysclean; and review the output
>>
On Dec 23, 2019 4:42 PM, rgci...@disroot.org wrote:
>
> December 24, 2019 4:42 AM, "Dumitru Moldovan" wrote:
>
> > On Sun, Dec 22, 2019 at 10:56:20AM +1000, Stuart Longland wrote:
> >
> >> So, a few years ago now, I deployed a router VM with OpenBSD 6.1 AMD64.
> >> Later that got updated to
On Mon, Dec 23, 2019 at 3:10 PM Stuart Longland
wrote:
...
> Where do you get `sysclean` from? I don't seem to have it:
> > sjl-router# man sysclean
>
> > man: No entry for sysclean in the manual.
> > sjl-router# which sysclean
> > which: sysclean: Command not found.
>
$ pkg_info sysclean
On 24/12/19 8:42 am, rgci...@disroot.org wrote:
>> My understanding is that this is by design. In an update, some libs are
>> overwritten (if they keep the same file name), but others are left on
>> disk (theoretically unused) when lib versions are incremented. I can
>> see a few ways in which
December 24, 2019 4:42 AM, "Dumitru Moldovan" wrote:
> On Sun, Dec 22, 2019 at 10:56:20AM +1000, Stuart Longland wrote:
>
>> So, a few years ago now, I deployed a router VM with OpenBSD 6.1 AMD64.
>> Later that got updated to 6.2, then 6.3, 6.4…
>>
>> Yesterday I updated it to 6.5, then 6.6…
On Sun, Dec 22, 2019 at 10:56:20AM +1000, Stuart Longland wrote:
So, a few years ago now, I deployed a router VM with OpenBSD 6.1 AMD64.
Later that got updated to 6.2, then 6.3, 6.4…
Yesterday I updated it to 6.5, then 6.6… now I'm trying to run syspatch:
I have a similar issue with my
Stuart Longland writes:
> > 16 partitions:
> > #size offset fstype [fsize bsize cpg]
> > a: 268416 64 4.2BSD 2048 16384 2097 # /
> > b: 373010 268480swap# none
&
.6 GENERIC#353 amd64
8GB seemed like a reasonable amount for something that would just be
routing. And looking at that `df` output, it would appear that there's
about 2.5GB locked away, in partitions that the original automatic
layout dictated I should have, but then didn't utilise.
I'm thankful I had t
On 2019-11-19, Steve Litt wrote:
> In OpenBSD is there such a thing as a bind mount like they have in
> Linux?
No. The closest is probably "mount from 127.0.0.1 over NFS".
On Tue, 19 Nov 2019 12:52:52 +0200
Dumitru Moldovan wrote:
>
> 1. Install the same OS on new hardware, in your case with a better
> partitioned drive.
>
> 2. rsync everything relevant to the new machine (but make sure it
> still boots afterwards and functions as expected, so amend
On Mon, 18 Nov 2019 18:28:55 - (UTC)
Stuart Henderson wrote:
> On 2019-11-17, Lev Lazinskiy wrote:
> > Hi folks,
> >
> > I am new to openBSD, so forgive me if I am missing something
> > obvious.
> >
> > I recently installed openBSD on a server using the auto-partition
> > layout during
On Tue, Nov 19, 2019 at 12:31:25PM +0200, Dumitru Moldovan wrote:
On Sun, Nov 17, 2019 at 03:12:06PM -0800, Lev Lazinskiy wrote:
This makes sense, but I was curious what the recommended approach is for
a server that you cannot simply reinstall.
A humble piece of advice from a fellow system
On Sun, Nov 17, 2019 at 03:12:06PM -0800, Lev Lazinskiy wrote:
This makes sense, but I was curious what the recommended approach is for
a server that you cannot simply reinstall.
A humble piece of advice from a fellow system admin... Never ever build
a system that "you cannot simply
Stuart Henderson wrote:
> On 2019-11-17, Lev Lazinskiy wrote:
> > Hi folks,
> >
> > I am new to openBSD, so forgive me if I am missing something obvious.
> >
> > I recently installed openBSD on a server using the auto-partition layout
> > during installation and am quickly starting to run out
On 2019-11-17, Lev Lazinskiy wrote:
> Hi folks,
>
> I am new to openBSD, so forgive me if I am missing something obvious.
>
> I recently installed openBSD on a server using the auto-partition layout
> during installation and am quickly starting to run out of disk space.
>
> I have read the
1 - 100 of 314 matches
Mail list logo
