Re: EFI zfs loader and beadm?

[krad]

Its also worth pointing that if you decouple the userland from the kernel
files you no longer have a boot environment, as all the basic stuff to boot
the os isn't contained within the bootfs. I'm still struggling to see why
/boot needs to be on a different dataset, its just a bit of a linuxism.

On 10 March 2016 at 19:23, Trond Endrestøl <
trond.endres...@fagskolen.gjovik.no> wrote:

> On Thu, 10 Mar 2016 18:38+0300, Andrey Fesenko wrote:
>
> > On Thu, Mar 10, 2016 at 6:11 PM, krad  wrote:
> > > As Eric said you cant have /boot on a separate dataset as the whole
> loader
> > > bootstrap isnt designed too look for it on the dataset defined by
> bootfs.
> > > Remember no other datasets are mounted at that stage of the bootstrap.
> > >
> > > You could maybe bodge something by manually playing around with the
> bootfs
> > > property, symlinks and rootfs variables in the loader.conf.  But why
> would
> > > you want to do this? It's more work and non standard, and will break a
> lot?
> > >
> > >
> > >
> > > On 10 March 2016 at 12:11, Andrey Fesenko  wrote:
> > >>
> > >> On Thu, Mar 10, 2016 at 2:55 PM, krad  wrote:
> > >> > presumably it boots now?
> > >> >
> > >> > On 10 March 2016 at 11:01, Andrey Fesenko 
> wrote:
> > >> >>
> > >> >> On Thu, Mar 10, 2016 at 1:49 PM, krad  wrote:
> > >> >> > Make sure you are running the latest snapshot of current or 10.3
> as
> > >> >> > well, as
> > >> >> > the MFC commits were in early February for 10-stable
> > >> >> >
> > >> >> >>
> > >> >> >> If remove efiwpool/ROOT/init/boot and copy his content on
> > >> >> >> efiwpool/ROOT/init my scheme work fine too.
> > >> >> >> /usr /var /home and other included in BE for consistent boot
> system
> > >> >> >> (CURRENT world may not boot with kernel other rev),  and old
> home
> > >> >> >> snapshot sometimes useful for backup/restore
> > >> >> >> ___
> > >> >>
> > >> >> % uname -a
> > >> >> FreeBSD x220.efi.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0
> r296548:
> > >> >> Wed Mar  9 01:16:17 MSK 2016
> > >> >> root@des.local:/usr/obj/usr/src/sys/X220  amd64
> > >> >
> > >> >
> > >>
> > >> My current working config
> > >> % mount
> > >> 
> > >>
> > >> This work fine, booted, beadm create new env, activate them, see boot
> > >> menu and select BE.
> > >>
> > >> % beadm list
> > >> BEActive Mountpoint  Space Created
> > >> init  -  -  420.7M 2016-03-09 02:57
> > >> init0 NR /   35.9G 2016-03-10 05:00
> > >>
> > >> If i'm add separate dataset for /boot (efiwpool/ROOT/init0/boot)
> > >> system not booted, efi loader (first stage) see only my pool, not
> > >> found /boot/loader.efi
> > >
> > >
> >
> > It probably does not matter, as bootfs have snapshots (BE), just
> > wanted to make it more clear (having taken significant mountpoint
> > /boot, /usr, /var... in zfs dataset) and was surprised why the system
> > does not boot
> >
> > It is clear that as long as the functionality is experimental and
> > under development, but would like to see where the full instructions
> > on its implementation / restrictions, at least as early as has been
> > described https://wiki.freebsd.org/RootOnZFS
>
> If you keep /boot as a separate dataset/filesystem, with
> efiwpool/ROOT/init0/boot as the given bootfs, then boot1.efi will not
> see a /boot directory inside that dataset. The files and directories
> from /boot will be presented as living in /, the local root directory
> of that dataset.
>
> You could create a /boot/boot symlink pointing to . (dot), but it's
> better to let /boot be part of the regular boot environment, pretty
> similar to what you would find on a UFS system using a separate root
> filesystem.
>
> --
> +---++
> | Vennlig hilsen,   | Best regards,  |
> | Trond Endrestøl,  | Trond Endrestøl,   |
> | IT-ansvarlig, | System administrator,  |
> | Fagskolen Innlandet,  | Gjøvik Technical College, Norway,  |
> | tlf. mob.   952 62 567,   | Cellular...: +47 952 62 567,   |
> | sentralbord 61 14 54 00.  | Switchboard: +47 61 14 54 00.  |
> +---++
> ___
> freebsd-hack...@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: EFI zfs loader and beadm?

[krad]

As Eric said you cant have /boot on a separate dataset as the whole loader
bootstrap isnt designed too look for it on the dataset defined by bootfs.
Remember no other datasets are mounted at that stage of the bootstrap.

You could maybe bodge something by manually playing around with the bootfs
property, symlinks and rootfs variables in the loader.conf.  But why would
you want to do this? It's more work and non standard, and will break a lot?



On 10 March 2016 at 12:11, Andrey Fesenko  wrote:

> On Thu, Mar 10, 2016 at 2:55 PM, krad  wrote:
> > presumably it boots now?
> >
> > On 10 March 2016 at 11:01, Andrey Fesenko  wrote:
> >>
> >> On Thu, Mar 10, 2016 at 1:49 PM, krad  wrote:
> >> > Make sure you are running the latest snapshot of current or 10.3 as
> >> > well, as
> >> > the MFC commits were in early February for 10-stable
> >> >
> >> >>
> >> >> If remove efiwpool/ROOT/init/boot and copy his content on
> >> >> efiwpool/ROOT/init my scheme work fine too.
> >> >> /usr /var /home and other included in BE for consistent boot system
> >> >> (CURRENT world may not boot with kernel other rev),  and old home
> >> >> snapshot sometimes useful for backup/restore
> >> >> ___
> >>
> >> % uname -a
> >> FreeBSD x220.efi.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r296548:
> >> Wed Mar  9 01:16:17 MSK 2016
> >> root@des.local:/usr/obj/usr/src/sys/X220  amd64
> >
> >
>
> My current working config
> % mount
> efiwpool/ROOT/init0 on / (zfs, local, noatime, nfsv4acls)
> devfs on /dev (devfs, local, multilabel)
> efiwpool/ROOT/init0/tmp on /tmp (zfs, local, noatime, nosuid, nfsv4acls)
> efiwpool/ROOT/init0/usr on /usr (zfs, local, noatime, nfsv4acls)
> efiwpool/ROOT/init0/usr/home on /usr/home (zfs, local, noatime, nfsv4acls)
> efiwpool/ROOT/init0/var on /var (zfs, local, noatime, nfsv4acls)
> efiwpool/ROOT/init0/var/crash on /var/crash (zfs, local, noatime,
> noexec, nosuid, nfsv4acls)
> efiwpool/ROOT/init0/var/db on /var/db (zfs, local, noatime, noexec,
> nosuid, nfsv4acls)
> efiwpool/ROOT/init0/var/db/pkg on /var/db/pkg (zfs, local, noatime,
> nosuid, nfsv4acls)
> efiwpool/ROOT/init0/var/db/tlpkg on /var/db/tlpkg (zfs, local,
> noatime, nosuid, nfsv4acls)
> efiwpool/ROOT/init0/var/empty on /var/empty (zfs, local, noatime,
> noexec, nosuid, read-only, nfsv4acls)
> efiwpool/ROOT/init0/var/log on /var/log (zfs, local, noatime, noexec,
> nosuid, nfsv4acls)
> efiwpool/ROOT/init0/var/mail on /var/mail (zfs, local, noatime,
> noexec, nosuid, nfsv4acls)
> efiwpool/ROOT/init0/var/run on /var/run (zfs, local, noatime, noexec,
> nosuid, nfsv4acls)
> efiwpool/ROOT/init0/var/tmp on /var/tmp (zfs, local, noatime, nosuid,
> nfsv4acls)
>
> =>   40  234441568  ada1  GPT  (112G)
>  40   1600 1  efi  (800K)
>1640  234439960 2  freebsd-zfs  (112G)
>   234441600  8- free -  (4.0K)
>
> % zfs get -r mountpoint efiwpool
> NAME  PROPERTY
> VALUE  SOURCE
> efiwpool  mountpoint  none
>   local
> efiwpool/ROOT mountpoint  none
>   inherited from efiwpool
> efiwpool/ROOT/initmountpoint
> legacy local
> efiwpool/ROOT/init/tmpmountpoint  /tmp
>   local
> 
>
> This work fine, booted, beadm create new env, activate them, see boot
> menu and select BE.
>
> % beadm list
> BEActive Mountpoint  Space Created
> init  -  -  420.7M 2016-03-09 02:57
> init0 NR /   35.9G 2016-03-10 05:00
>
> If i'm add separate dataset for /boot (efiwpool/ROOT/init0/boot)
> system not booted, efi loader (first stage) see only my pool, not
> found /boot/loader.efi
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: EFI zfs loader and beadm?

[krad]

presumably it boots now?

On 10 March 2016 at 11:01, Andrey Fesenko  wrote:

> On Thu, Mar 10, 2016 at 1:49 PM, krad  wrote:
> > Make sure you are running the latest snapshot of current or 10.3 as
> well, as
> > the MFC commits were in early February for 10-stable
> >
> >>
> >> If remove efiwpool/ROOT/init/boot and copy his content on
> >> efiwpool/ROOT/init my scheme work fine too.
> >> /usr /var /home and other included in BE for consistent boot system
> >> (CURRENT world may not boot with kernel other rev),  and old home
> >> snapshot sometimes useful for backup/restore
> >> ___
>
> % uname -a
> FreeBSD x220.efi.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r296548:
> Wed Mar  9 01:16:17 MSK 2016
> root@des.local:/usr/obj/usr/src/sys/X220  amd64
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: EFI zfs loader and beadm?

[krad]

Make sure you are running the latest snapshot of current or 10.3 as well,
as the MFC commits were in early February for 10-stable

On 9 March 2016 at 16:01, Andrey Fesenko  wrote:

> On Wed, Mar 9, 2016 at 6:48 PM, Eric van Gyzen  wrote:
> > On 03/09/2016 09:40, Andrey Fesenko wrote:
> >> Hello,
> >> I'm test EFI boot ZFSroot with BE, this not support now?
> >> svn 2965489
> >>
> >> If i build simplest system
> >>
> http://blog.multiplay.co.uk/2015/12/freebsd-10-2-release-efi-zfs-root-boot/
> >>
> >> # zfs get -r mountpoint efifpool
> >> NAME  PROPERTYVALUE  SOURCE
> >> efifpool  mountpoint  /mnt/efifpool  default
> >>
> >> =>  40  30712240  da0  GPT  (15G)
> >> 40  16001  efi  (800K)
> >>   1640  307106322  freebsd-zfs  (15G)
> >>   30712272 8   - free -  (4.0K)
> >>
> >> system boot nice
> >>
> >> If make BE env
> >>
> >> # zfs get -r mountpoint efiwpool
> >> NAME  PROPERTYVALUE  SOURCE
> >> efiwpool  mountpoint  none   local
> >> efiwpool/ROOT mountpoint  none
> >> inherited from efiwpool
> >> efiwpool/ROOT/initmountpoint  legacy local
> >> efiwpool/ROOT/init@init   mountpoint  -  -
> >> efiwpool/ROOT/init/boot   mountpoint  /media/bootlocal
> >> efiwpool/ROOT/init/tmpmountpoint  /media/tmp local
> >> efiwpool/ROOT/init/usrmountpoint  /media/usr local
> >> efiwpool/ROOT/init/usr@init   mountpoint  -  -
> >> efiwpool/ROOT/init/usr/home   mountpoint  /media/usr/home
> >> inherited from efiwpool/ROOT/init/usr
> >> efiwpool/ROOT/init/usr/home@init  mountpoint  -  -
> >> efiwpool/ROOT/init/varmountpoint  /media/var local
> >> efiwpool/ROOT/init/var@init   mountpoint  -  -
> >> efiwpool/ROOT/init/var/crash  mountpoint  /media/var/crash
> >> inherited from efiwpool/ROOT/init/var
> >> efiwpool/ROOT/init/var/db mountpoint  /media/var/db
> >> inherited from efiwpool/ROOT/init/var
> >> efiwpool/ROOT/init/var/db/pkg mountpoint  /media/var/db/pkg
> >> inherited from efiwpool/ROOT/init/var
> >> efiwpool/ROOT/init/var/empty  mountpoint  /media/var/empty
> >> inherited from efiwpool/ROOT/init/var
> >> efiwpool/ROOT/init/var/logmountpoint  /media/var/log
> >> inherited from efiwpool/ROOT/init/var
> >> efiwpool/ROOT/init/var/mail   mountpoint  /media/var/mail
> >> inherited from efiwpool/ROOT/init/var
> >> efiwpool/ROOT/init/var/runmountpoint  /media/var/run
> >> inherited from efiwpool/ROOT/init/var
> >> efiwpool/ROOT/init/var/tmpmountpoint  /media/var/tmp
> >> inherited from efiwpool/ROOT/init/var
> >>
> >> system not boot.
> >>
> >> Not found /boot/loader.efi (in BE system real path
> >> efiwpool/ROOT/init/boot/loader.efi) if copy this efiwpool/ROOT/init
> >> (blank in BE system) loader found this (but not found /boot/kernel) I
> >> can copy this and get a similar system
> >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192184#c15 (with out
> >> msdos kernel part), but this ruin BE update mechanism
> >
> > Your dataset hierarchy is not what beadm expects.  Specifically, you
> > have /boot separate from /, which I imagine is causing your problem.
> > /boot should be part of /.  Also, you have several file systems in the
> > BE that are usually not in it; I doubt this is part of your boot
> > failure, though.
> >
> > For reference, here is my layout, which is mostly the same as the
> > default installation:
> >
> > NAME  USED  AVAIL  REFER  MOUNTPOINT
> > zroot 117G   108G96K  none
> > zroot/ROOT   14.8G   108G96K  none
> > zroot/ROOT/10.2   444K   108G  6.35G  /
> > zroot/ROOT/103beta   14.8G   108G  8.75G  /
> > zroot/ROOT/103beta1 8K   108G  8.17G  /
> > zroot/ROOT/103beta3 8K   108G  8.75G  /
> > zroot/home   97.8G   108G  94.9G  /home
> > zroot/usr3.36G   108G96K  /usr
> > zroot/usr/ports   985M   108G   736M  /usr/ports
> > zroot/usr/src2.40G   108G  2.19G  /usr/src
> > zroot/var2.19M   108G96K  /var
> > zroot/var/audit96K   108G96K  /var/audit
> > zroot/var/crash96K   108G96K  /var/crash
> > zroot/var/log1.15M   108G   420K  /var/log
> > zroot/var/mail360K   108G   120K  /var/mail
> > zroot/var/tmp 416K   108G   144K  /var/tmp
> >
> > Eric
>
> If remove efiwpool/ROOT/init/boot and copy his content on
> efiwpool/ROOT/init my scheme work fine too.
> /usr /var /home and other included in BE for consistent boot system
> (CURRENT world may not boot with kernel other rev),  and old home
> snapshot sometimes useful for backup/restore
> 

Re: LSI SAS 3108 RAID Controller

[krad]

Just a sanity check 1st.

Are you going to be using zfs or ufs?

If zfs you probably want the reflash the card the the relevant HBA firmware
rather the the raid firmware. This will expose the disks nativly which is
best for zfs.

Sorry if this isn't appropriate for you but I would thought I would check
as it might save you a whole load of pain going in a direction you don't
need to.

On 2 February 2016 at 17:06, Zara Kanaeva  wrote:

> Dear list,
>
> I have one Fujitsu server with LSI SAS 3108 RAID Controller. These LSI SAS
> 3108 RAID Controller is supported by the mpr driver (
> https://www.freebsd.org/relnotes/CURRENT/hardware/support.html).
> If I try to install the FreeBSD-stable 10.0 or FreeBSD-current 11.0 on
> this server I can make partitions, but I can not write install files on the
> disks (better to say RAID5 virtual drive) without errors.
> The erorrs are:
> mfi0 failed to get command
> mfi0: COMMAND ... TIMEOUT AFTER  ... SECONDS
>
> By the installations I see my virtual drive as device with mfi0 as
> identifier.
>
> My questions are:
> 1) Why I see the virtual drive as device with mfi0 as identifier. I would
> expect that my virtual drive has identifier mpr0 or something like this.
> 2) Why I can install FreeBSD on one of the disks connected to LSI SAS 3108
> RAID Controller, if the disks do not build any virtual drive (no matter
> which RAID level). Is that possible because mpr driver supports the LSI SAS
> 3108 RAID Controller as SCSI Controller and not as RAID Controller (see
> Kernel configuration)?
>
> Thanks in advance, Z. Kanaeva.
>
> --
> Dipl.-Inf. Zara Kanaeva
> Heidelberger Akademie der Wissenschaften
> Forschungsstelle "The role of culture in early expansions of humans"
> an der Universität Tübingen
> Geographisches Institut
> Universität Tübingen
> Ruemelinstr. 19-23
> 72070 Tuebingen
>
> Tel.: +49-(0)7071-2972132
> e-mail: zara.kana...@geographie.uni-tuebingen.de
> ---
> - Theory is when you know something but it doesn't work.
> - Practice is when something works but you don't know why.
> - Usually we combine theory and practice:
> Nothing works and we don't know why.
>
> ___
> freebsd-sta...@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

ZFSROOT UEFI boot

[krad]

Hi, I need to get one of my machines converted over from bios GPT zfsroot
boot to efi. I know you can boot freebsd under EFI with a ufs kernel but
this isnt the route i want. There are patches under test for EFI zfs root.
However when I read the thread it was unclear which version of these
patches were needed and where to get them. Does anyone know where they are,
if there are any prebuilt zfsloader etc binaries, or if the patches have
made it to head yet?

Also does anyone have any pointers or good experience with grub efi and zfs
on root? I'm considering this option as it would make booting into specific
boot environments easier
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Freebsd 11 usb image zfs on root install on DN2820FYKH

[krad]

hmm,  got it working by downgrading to v32 firmware. It seems the is a bug
in intels wonderful uefi code, which of course the blame freebsd for 8/

On 18 September 2014 13:05, krad  wrote:

> Has anyone got freebsd booting on an intel NUC DN2820FYKH?
>
> It installs fine just wont boot (doesnt see boot loader). I'm doing legacy
> not efi mode.
>
> I'm starting to bang my head against the wall on this one. Time to leave
> it for a bit i think
>
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Freebsd 11 usb image zfs on root install on DN2820FYKH

[krad]

Has anyone got freebsd booting on an intel NUC DN2820FYKH?

It installs fine just wont boot (doesnt see boot loader). I'm doing legacy
not efi mode.

I'm starting to bang my head against the wall on this one. Time to leave it
for a bit i think
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Future of pf / firewall in FreeBSD ? - does it have one ?

[krad]

I always found natting in ipfw rather awkward and harder than in pf.
Looking at the man page it doesnt seem to have changed. I should probably
give it another go though as it has been about 10 years now


On 31 July 2014 14:41, Gleb Smirnoff  wrote:

> On Thu, Jul 31, 2014 at 10:02:22PM +1000, Da Rock wrote:
> D> Without diminishing your efforts so far, what do you think about
> D> pitching all efforts into IPFW to combine effort and reduce overhead of
> D> maintaining separate firewalls in the core? Is there an advantage to
> D> having our own pf?
>
> Is there any disadvantage keeping it? It is a plugin. It is optional
> and loadable. I removed most additions to the network stack that live
> outside netpfil/pf.
>
> Some people like it and use it.
>
> It is also the only tool to configure ALTQ now.
>
> --
> Totus tuus, Glebius.
> ___
> freebsd-questi...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "
> freebsd-questions-unsubscr...@freebsd.org"
>
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Future of pf / firewall in FreeBSD ? - does it have one ?

[krad]

all of that is true, but you are missing the point. Having two versions of
pf on the bsd's at the user level, is a bad thing. It confuses people,
which puts them off. Its a classic case of divide an conquer for other
platforms. I really like the idea of the openpf version, that has been
mentioned in this thread. It would be awesome if it ended up as a supported
linux thing as well, so the world could be rid of iptables. However i guess
thats just an unrealistic dream


On 19 July 2014 09:32, Stephen Hurd  wrote:

> krad wrote:
> > that is true and I have not problem using man pages, however thats not
> the
> > way most of the world work and search engines arent exactly new either.
> We
> > should be trying to engage more people not less, and part of that is
> > reaching out.
>
> One of FreeBSD's historic strengths has been the handbook and generally
> good quality documentation.  There is no way that the FreeBSD project
> can ensure that all Google results for everyone in the world are FreeBSD
> related "good" documentation, but it can ensure that the documentation
> included with FreeBSD is accurate and usable, and it can ensure that the
> FreeBSD documentation is available via the internet.
>
> Aside from blindly following whatever generates the most Google results
> (an obviously broken solution), what exactly can the FreeBSD project do
> to ensure that when someone "Googles" a problem they will end up with a
> correct FreeBSD solution?
>
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Future of pf / firewall in FreeBSD ? - does it have one ?

[krad]

that is true and I have not problem using man pages, however thats not the
way most of the world work and search engines arent exactly new either. We
should be trying to engage more people not less, and part of that is
reaching out.


On 18 July 2014 15:10, Matt Bettinger  wrote:

> Back in the day we didn't have Google to ask the oracle for cut and paste
> answers.   If the man page is accurate that should be good enough.
> On Jul 18, 2014 8:26 AM, "krad"  wrote:
>
>> this is also another important point. If you go onto google and search on
>> how to do this and that under pf, you get a mix of freebsd, and openbsd
>> stuff coming up. I havent analysed it but i think the majority of the
>> stuff
>> is openbsd related. THerefore I find some nice solution to my problem,
>> only
>> to find out a bit later I cant use it because its not supported under
>> freebsd. This is anoying, but more importantly confuses new sysadmins and
>> puts them off adopting pf and possibly a bsd at all.
>>
>>
>> On 18 July 2014 14:12, Gerrit Kühn  wrote:
>>
>> > On Fri, 18 Jul 2014 15:06:45 +0400 Gleb Smirnoff 
>> > wrote about Re: Future of pf / firewall in FreeBSD ? - does it have one
>> ?:
>> >
>> > GS> The pf mailing list is about a dozen of active people. Yes, they are
>> > GS> vocal on the new syntax. But there also exist a large number of
>> common
>> > GS> FreeBSD users who simply use pf w/o caring about syntax and reading
>> pf
>> > GS> mailing list. If we destroy the syntax compatibility a very large
>> > GS> population of users would be hurt, for the sake of making a dozen
>> > GS> happy.
>> >
>> > I have thought about this for some time now, and I think I do not
>> agree. I
>> > do remember quite well when OpenBSD changed from ipf to pf, and I had to
>> > come up with new rules files. Yes, this is a burden for people
>> maintaining
>> > these systems, but if the thing is well documented and comes with
>> benefits
>> > (like staying in sync with other developers, allowing new features
>> etc.) I
>> > doubt that many people will really be minding this.
>> >
>> >
>> > cu
>> >   Gerrit
>> > ___
>> > freebsd-questi...@freebsd.org mailing list
>> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>> > To unsubscribe, send any mail to "
>> > freebsd-questions-unsubscr...@freebsd.org"
>> >
>> ___
>> freebsd-questi...@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>> To unsubscribe, send any mail to "
>> freebsd-questions-unsubscr...@freebsd.org"
>
>
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Future of pf / firewall in FreeBSD ? - does it have one ?

[krad]

this is also another important point. If you go onto google and search on
how to do this and that under pf, you get a mix of freebsd, and openbsd
stuff coming up. I havent analysed it but i think the majority of the stuff
is openbsd related. THerefore I find some nice solution to my problem, only
to find out a bit later I cant use it because its not supported under
freebsd. This is anoying, but more importantly confuses new sysadmins and
puts them off adopting pf and possibly a bsd at all.


On 18 July 2014 14:12, Gerrit Kühn  wrote:

> On Fri, 18 Jul 2014 15:06:45 +0400 Gleb Smirnoff 
> wrote about Re: Future of pf / firewall in FreeBSD ? - does it have one ?:
>
> GS> The pf mailing list is about a dozen of active people. Yes, they are
> GS> vocal on the new syntax. But there also exist a large number of common
> GS> FreeBSD users who simply use pf w/o caring about syntax and reading pf
> GS> mailing list. If we destroy the syntax compatibility a very large
> GS> population of users would be hurt, for the sake of making a dozen
> GS> happy.
>
> I have thought about this for some time now, and I think I do not agree. I
> do remember quite well when OpenBSD changed from ipf to pf, and I had to
> come up with new rules files. Yes, this is a burden for people maintaining
> these systems, but if the thing is well documented and comes with benefits
> (like staying in sync with other developers, allowing new features etc.) I
> doubt that many people will really be minding this.
>
>
> cu
>   Gerrit
> ___
> freebsd-questi...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "
> freebsd-questions-unsubscr...@freebsd.org"
>
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Future of pf / firewall in FreeBSD ? - does it have one ?

[krad]

I would like to see an updated version of pf. I realize its a big job to
port it though


On 17 July 2014 00:12, Kristian K. Nielsen  wrote:

> Hi all,
>
> I have been encouraged by people on the pf-mailinglist to move this
> discussion to the current mailinglist since this may be an area in the OS
> where FreeBSD need to focus on next.
>
> First of all I am a happy user of the pf-firewall module and have been for
> years and think it is really great - the trouble is that lately (since
> 2008) its getting a bit dusty.
>
> The last few years it seem that pf in FreeBSD got a long way away from pf
> in OpenBSD where it originated
> - also looking at the ipfilter (ipf) and ipfw - they both to me do not
> seem to be as complete as pf.
>
> So I am curious if any on the mailing could elaborate about what the
> future of pf in FreeBSD is or should be.
>
> a) First of all - are any actively developing pf in FreeBSD?
>
> b) We are a major release away from OpenBSD (5.6 coming soon) - is
> following OpenBSD's pf the past? - should it be?
>
> c) We never got the new syntax from OpenBSD 4.7's pf - at the time a long
> discussion on the pf-mailing list flamed the new syntax saying it would
> cause FreeBSD administrators too much headache. Today on the list it seems
> everyone wants it - so would we rather stay on a dead branch than keep up
> with the main stream?
>
> d) Anyone working on bringing FreeBSD up to pf 5.6? - seem dead on the
> pf-list.
>
> e) OpenBSD is retiring ALTQ entirely - any thoughts on that?
> http://undeadly.org/cgi?action=article&sid=20140419151959
>
> f) IPv6 support?- it seem to be more and more challenged in the current
> version of pf in FreeBSD and I am (as well as others) introducing more and
> more IPv6 in networks.
> E.x. Bugs #179392, #172648, #130381, #127920 and more seriously #124933,
> which is the bug on not handling IPv6 fragments which have been open since
> 2008 and where the workaround is necessity to leave an completely open hole
> in your firewall ruleset to allow all fragments. According to comment in
> the bug, this have been long gone in OpenBSD.
>
> g) Performance, can we live with pf-performance that compared to OpenBSD
> is slower by a factor of 3 or 4, even after the multi-core support in
> FreeBSD 10?
> (Henning Brauer noted that in this talk at http://tech.yandex.ru/events/
> yagosti/ruBSD/talks/1488/ (at 33:18 and 36:53)) - credit/Jim Thompson
>
> h) Bringing back patches from pfSense?
>
> And my most important question:
>
> * Should this or could this be a project for the foundation to either do a
> summer project or funded project to bring this part of the OS up to date?
>
>
> Hope to heard from you all,
>
> Best regards,
>
> Kristian Kræmmer Nielsen,
> Odense, Denmark
>
> ___
> freebsd-questi...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-
> unsubscr...@freebsd.org"
>
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: /usr/home vs /home

[krad]

On 22 November 2011 13:36, C. P. Ghost  wrote:

> On Tue, Nov 22, 2011 at 11:30 AM,  <"Thomas Mueller
>  wrote:
> > But I don't see any advantage to putting /, /usr, and /var on separate
> partitions.
> >
> > Tom
>
> Regarding separate /usr and /var: the advantage is that you can
> keep /usr read-only which is also important for security reasons
> since modifying system binaries becomes less easy.
>
> Furthermore, you can NFS share a read-only /usr among many
> similar machines, while /var is a per-machine specific read-write
> area.
>
> -cpghost.
>
> --
> Cordula's Web. http://www.cordula.ws/
> ___
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>


I always have /var and /tmp on separate file systems than /, but dont
normally have a separate /usr, bur I have a /usr/local.

I like to keep the /var and /tmp fs separate as they as other are
mentioned. Therefore they are more prone to corruption in event of the
power failure. Keeping / separate in this case should make the system more
likely to reboot. Also it stops application filling up / which can stop you
logging into the system (I havent seen this issue for year admittedly)

/usr/local is just for tidyness as it keeps base os separate from ports etc

I also have /home on a separate as well to stops users filling up root as
well.

my zfsroot boxes have this setup as well, but i also add a few reservations
and quotas.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Strange ZFS filesystem corruption

[krad]

On 6 October 2011 02:27, Paul Mather  wrote:

> On Oct 5, 2011, at 9:03 AM, krad wrote:
>
> > Have you dont the simple thing and checked to see if you have any weird
> whitespace in the dir names. Try using bash tab completion for the dir name.
> Also drop all non bash completion rules as these might be messing things up.
> >
> > I have seen odd characters in dirs cause much confusion in the past.
>
>
> I don't believe that is the problem in this case.  An "ls" will list the
> file but "ls -l" reports "no such file or directory:"
>
> tape# ls
> 05DLAAdmin  07DLAAdmin
> tape# ls -l
> ls: 05DLAAdmin: No such file or directory
> total 3
> drwxrws---  4 500  501  4 Oct  3 11:53 07DLAAdmin
> tape#
>
> Plus, the "rm -rf" I tried (that failed) ought not to fall foul of such
> weird whitespace problems.
>
> Cheers,
>
> Paul.
>
>
>
try a zfs mount -a, just incase some mounting has gone adrift. This
certainly is strange
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Strange ZFS filesystem corruption

[krad]

On 4 October 2011 17:09, Olivier Smedts  wrote:

> 2011/10/3 Paul Mather :
> > I know ZFS does not have a fsck utility ("because it doesn't need one":),
> but does anyone know of any way of fixing this corruption short of
> destroying the pool, creating a new one, and restoring from backup?  Is
> there some way of exporting and re-importing the pool that has the
> side-effect of doing some kind of fsck-like repairing of subtle corruption
> like this?
>
> But there is the ZFS debugger, "zdb" !
>
> I can't really help you with that because I never had a corrupted
> zpool, but if you search on the lists for up to a year or so, you'll
> find some useful commands to inspect and destroy corrupted objects.
>
>
> Usage: zdb [-CumdibcsDvhL] poolname [object...]
>   zdb [-div] dataset [object...]
>   zdb -m [-L] poolname [vdev [metaslab...]]
>   zdb -R poolname vdev:offset:size[:flags]
>   zdb -S poolname
>   zdb -l [-u] device
>   zdb -C
>
>Dataset name must include at least one separator character '/' or '@'
>If dataset name is specified, only that dataset is dumped
>If object numbers are specified, only those objects are dumped
>
>Options to control amount of output:
>-u uberblock
>-d dataset(s)
>-i intent logs
>-C config (or cachefile if alone)
>-h pool history
>-b block statistics
>-m metaslabs
>-c checksum all metadata (twice for all data) blocks
>-s report stats on zdb's I/O
>-D dedup statistics
>-S simulate dedup to measure effect
>-v verbose (applies to all others)
>-l dump label contents
>-L disable leak tracking (do not load spacemaps)
>-R read and display block from a device
>
>Below options are intended for use with other options (except -l):
>-A ignore assertions (-A), enable panic recovery (-AA) or both
> (-AAA)
>-F attempt automatic rewind within safe range of transaction groups
>-U  -- use alternate cachefile
>-X attempt extreme rewind (does not work with dataset)
>-e pool is exported/destroyed/has altroot/not in a cachefile
>-p  -- use one or more with -e to specify path to vdev dir
>-P print numbers parsable
>-t  -- highest txg to use when searching for uberblocks
> Specify an option more than once (e.g. -bb) to make only that option
> verbose
> Default is to dump everything non-verbosely
>
> --
> Olivier Smedts _
> ASCII ribbon campaign ( )
> e-mail: oliv...@gid0.org- against HTML email & vCards  X
> www: http://www.gid0.org- against proprietary attachments / \
>
>   "Il y a seulement 10 sortes de gens dans le monde :
>   ceux qui comprennent le binaire,
>   et ceux qui ne le comprennent pas."
> ___
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>


Have you dont the simple thing and checked to see if you have any weird
whitespace in the dir names. Try using bash tab completion for the dir name.
Also drop all non bash completion rules as these might be messing things up.

I have seen odd characters in dirs cause much confusion in the past.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Passive FTP

[krad]

>Those who still want active FTP (what on earth for?)

I have encountered hosting companies in the past that only have inbound port
21 access for security reasons. I think this a bit odd but it is was it is.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: HEADS UP: ports/ and 10.0-CURRENT

[krad]

On 27 September 2011 10:18, Anton Shterenlikht  wrote:

> On Tue, Sep 27, 2011 at 10:28:49AM +0200, O. Hartmann wrote:
> > On 09/27/11 08:35, h h wrote:
> > >Kevin Oberman  writes:
> > >
> > >>On Mon, Sep 26, 2011 at 9:03 PM, Ade Lovett  wrote:
> > >>
> > >>>With the advent of the conversion of HEAD to 10.0-CURRENT and, as to
> be
> > >>>expected, ports/ is going to be essentially unusable for a while.
> > >>>
> > >>>The issue stems from configure scripts (to choose something completely
> > >>>at random) assuming that FreeBSD would never jump to a double-digit
> > >>>major version number, and as such, various regexps for "freebsd1*"
> (ie:
> > >>>FreeBSD 1.1.x) are now matching "freebsd10".
> > >[...]
> > >>
> > >>aDe,
> > >>
> > >>Could an entry to this effect be added to UPDATING (with a matching
> > >>entry when ports/ is "unbroken").
> > >
> > >Also mention a workaround, e.g.
> > >
> > >   $ export UNAME_r='9.9-BLAH'
> >
> >
> > Now I understand why some OS vendors have choosen the latin 10 'X' for
> > their tenth version of their operating system ...
>
> At least there will be a long rest after
> the move to 10 is complete.. until FreeBSD 100.
>
> --
> Anton Shterenlikht
> Room 2.6, Queen's Building
> Mech Eng Dept
> Bristol University
> University Walk, Bristol BS8 1TR, UK
> Tel: +44 (0)117 331 5944
> Fax: +44 (0)117 929 4423
> ___
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>


we can leave that to our grand children to figure out though 8)
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: I am very confused and would appreciate some help on device renameing or on renumbering on current fstab.

[krad]

On 4 May 2011 04:13, Jason Hellenthal  wrote:

>
> Edwin,
>
> >>> >>  /dev/acd0  /cdrom  cd9660  ro,noauto   0
> 0
> >>> >>  /dev/acd1  /cdrom1 cd9660  ro,noauto   0
> 0
>
> As a side note. These are also now useless & can be sent to /dev/null for
> extra padding ;)
>
> Shouldn't cause no harm being there but just for reference.
>
> --
>
>  Regards, (jhell)
>  Jason Hellenthal
>
>
Just a sanity check here people, but if the machine was built with freebsd
6.x i would guess it machine is a few years old. If so i doubt the hardware
would support ahci, and therefore wouldn't have the ada type devices, it
would have the old ad style ata ones and therefore noe fstab twiddling
should be necessary.

Forgive me if im missing something here.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: HEADS UP: ZFSv28 is in!

[krad]

On 28 February 2011 08:47, Pawel Jakub Dawidek  wrote:
> On Sun, Feb 27, 2011 at 04:03:01PM -0700, Shawn Webb wrote:
>> I'm so excited for your work. Thanks so much for bringing zpool v28 to
>> FreeBSD. Will v28 come to 8-stable?
>
> Yes, hopefully in 1-2 month(s).
>
> --
> Pawel Jakub Dawidek                       http://www.wheelsystems.com
> FreeBSD committer                         http://www.FreeBSD.org
> Am I Evil? Yes, I Am!                     http://yomoli.com
>

ive never managed to be able to boot off my 4k aligned pool
(ashift=12) on stable, does the import to head provide all the patches
for this or is it a case of using the latest zfs v28 patch set for
stable? I have no dying need for v28 yet, it just want to be able to
boot onto the 4k drive and tidy things up.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: BSDInstall: merging to HEAD

[krad]

On 14 January 2011 18:26, Nathan Whitehorn  wrote:
>
> As those of you who have been reading freebsd-sysinstall and freebsd-arch 
> know, I have been working for a few weeks on a lightweight new installer 
> named 'bsdinstall'. This is designed to replace sysinstall for the 9.0 
> release.
>
> After two weeks of testing and bug fixes on the sysinstall list, I believe 
> this now has all required functionality and is ready to be merged into the 
> main source tree. I would like to do this on Tuesday, 18 January. Switching 
> this to be the default installer would happen a few weeks after that, pending 
> discussion on release formats with the release engineering team. This should 
> provide a sufficient testing period before 9.0 and allow a maximal number of 
> bugs to be discovered and solved before the release is shipped.
>
> Demo ISO for i386: 
> http://people.freebsd.org/~nwhitehorn/bsdinstall-i386-20110114.iso.bz2
> SVN repository: svn://svn.freebsd.org/base/user/nwhitehorn/bsdinstall
> Wiki page: http://wiki.freebsd.org/BSDInstall
>
> Goals
> -
> The primary goal of BSDInstall is to provide an easily extensible installer 
> without the limitations of sysinstall, in order to allow more modern 
> installations of FreeBSD. This means that it should have additional features 
> to support modern setups, but simultaneously frees us to remove complicating 
> features of sysinstall like making sure everything fits in floppy disk-sized 
> chunks.
>
> New Features:
> - Allows installation onto GPT disks on x86 systems
> - Can do installations spanning multiple disks
> - Allows installation into jails
> - Eases PXE installation
> - Virtualization friendly: can install from a live system onto disk
>  images
> - Works on PowerPC
> - Streamlined system installation
> - More flexible scripting
> - Easily tweakable
> - All install CDs are live CDs
>
> Architecture
> 
> BSDInstall is a set of tools that are called in sequence by a master script. 
> These tools are, for example, the partition editor, the thing that fetches 
> the distributions from the network, the thing that untars them, etc. Since 
> these are just called in sequence from a shell script, a scripted 
> installation can easily replace them with other things, (e.g. hard-coded 
> gpart commands), leave steps out, add new ones, or interleave additional 
> system modifications.
>
> Status
> --
> This provides functionality most similar to the existing sysinstall 'Express' 
> track. It installs working, bootable systems you can ssh into immediately 
> after reboot on i386, amd64, sparc64, powerpc, and powerpc64. There is 
> untested support for pc98. The final architecture on which we use sysinstall, 
> ia64, is currently unsupported, because I don't know how to set up booting on 
> those systems -- patches to solve this are very much welcome.
>
> There are still some missing features that I would like to see in the 
> release, but these do not significantly impact the functionality of the 
> installer. Some will be addressed before merging to HEAD, in particular the 
> lack of a man page for bsdinstall. Others, like configuration of wireless 
> networking and ZFS installation, can happen between merge and release. The 
> test ISOs are also lacking a ports tree at the moment, which is a statement 
> about the slow upload speed of my DSL line and not about the final layout of 
> releases.
>
> Please send any questions, comments, or patches you may have, and please be 
> aware when replying that this email has been cross-posted to three lists. 
> Technical discussion (bug reports, for instance) should be directed to the 
> freebsd-sysinstall list only. Most other discussion belongs on -sysinstall 
> and -current.
> -Nathan
> ___
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


I dont follow the freebsd-sysinstall and freebsd-arc list so sorry if
this has already been discussed. From what I have seen pc-sysinstall
already does all these things, and can install freebsd. Therefore why
are we reinventing the wheel?

I don't mean this as any disrespect to the work you have done.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: DHCP server in base

[krad]

On 25 September 2010 21:10, Darren Pilgrim  wrote:

> M. Warner Losh wrote:
>
>> It would be very convenient to have this particular thing in the base, and
>> we shouldn't be too dogmatic about never having any new 3rd
>>  party things in the base.
>>
>
> Please no, don't add optional servers to the base.  I already don't like
> sendmail, bind, ntpd and inetd in the base.  These are *optional*
> software--not required for the normal operation of the OS.  They aren't
> even enabled by default except sendmail.  Adding sendmail_enable="NONE"
> to /etc/rc.conf is one of the first things I do on all new systems.  I
> only barely tolerate openssl in the base because it's needed for
> openssh; however, I'd rather both of those be in ports as well.
>
> There's also the issue of updating:
>
> It's very annoying to have to update the OS just to fix a BIND or
> OpenSSL vulnerability and, let's be honest, we'll likely never see the
> last of those.  Rebooting a production server is non-trivial.  By-hand
> partial installworlds on live systems are a disturbing prospect.  If it
> was a port, just update the port.  Its far easier justifying updating a
> port than modifying the OS on a production server.  The Ports System
> makes updating a port so fast and painless I can do many of the
> non-user-facing ones without an announced downtime.
>
> It's trivial installing ports and utterly so installing packages.  I'd
> love to see us use the awesomeness that is the Ports System to manage
> these things.
>
> ___
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>


have a look at man src.conf and named_program
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: gptboot rewrite, bootonce, etc.

[krad]

On 20 September 2010 14:37, John Hay  wrote:

> On Mon, Sep 20, 2010 at 03:59:20PM +0300, Andriy Gapon wrote:
> > on 20/09/2010 15:47 Pawel Jakub Dawidek said the following:
> > > No, it doesn't. ZFS works a bit differently. ZFS operate on pools, not
> > > really on partitions. One ZFS file system can span multiple
> > > disks/partitions. I'm not yet sure how to implement it, so it is
> > > intuitive, but I also haven't spend much time thinking about it. We
> > > needed UFS and that is what I implemented. It took me much more time
> > > than I expected anyway:)
> >
> > Maybe reserve some area inside zfs boot2 and put relevant information
> there.
> > Similarly to how boot0cfg modifies data within boot0.
> > The information could include "nextboot-pool" and "nextboot-fs".
>
> nextboot-fs sounds nice. I use the bootfs property of zpool and it would
> be nice if one can override it from the boot2 commandline.
>
> John
> --
> John Hay -- j...@meraka.csir.co.za / j...@freebsd.org
>

exactly what i was thinking. Its real nice how opensolaris odes its boot
environments.  I have a few custom scripts to replicate that with the
install world, but at yet have no easy way to flip flop the bootfs varible,
other than booting in on live(cd|usb)
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: gptboot rewrite, bootonce, etc.

[krad]

On 19 September 2010 18:10, Boris Samorodov  wrote:

> Hi!
>
> On Sat, 18 Sep 2010 01:45:42 +0200 Pawel Jakub Dawidek wrote:
>
> > My company was in need for functionality similar to nextboot(8), but on
> > boot loader level, so we can have two partitions we boot from where one
> > is known to be good and the other is used for upgrades. We upgrade by
> > dd(1)ing entire partition image onto unused partition, we mark it as
> > try-to-boot-from-it-but-only-once, reboot and if we fail to boot from
> > the new partition, we fall back to the old, good partition. If we
> > succeed on the other hand, we mark the new partition as our boot
> > partition and mark the other one as unused.
>
> > Well, how hard can it be?
>
> > After around two weeks of work, I ended up rewriting gptboot in large
> > parts, reorganizing a lot of code, improving and extending gpart a bit
> > and implementing desire functionality.
>
> > Here is the patch for review and test:
>
> >   
> > http://people.freebsd.org/~pjd/patches/gptboot.patch
>
> Great! Since I need to have both i386 and amd64 at my box
> here are my test results:
> -
> [~]b...@alya% uname -a
> FreeBSD alya 9.0-CURRENT FreeBSD 9.0-CURRENT #1 r212758M: Sat Sep 18
> 16:13:38 MSD 2010
> b...@alya:/space/FreeBSD/base/head/obj/space/FreeBSD/base/head/src/sys/ALYA
> amd64
>
> [~]b...@alya% glabel status
>  Name  Status  Components
> gptid/c6053c9b-abcc-11df-b740-00251124aff4 N/A  ad4p1
> label/9-amd64 N/A  ad4p2
>label/swap N/A  ad4p3
>   label/space N/A  ad4p4
>  label/9-i386 N/A  ad4p5
> [~]b...@alya% mount
> /dev/label/9-amd64 on / (ufs, local)
> devfs on /dev (devfs, local, multilabel)
> /dev/label/space on /space (ufs, local)
> /dev/md0 on /tmp (ufs, local, nosuid, soft-updates)
> procfs on /proc (procfs, local)
> linprocfs on /compat/linux/proc (linprocfs, local)
> linsysfs on /compat/linux/sys (linsysfs, local)
> fdescfs on /dev/fd (fdescfs)
>
> [~]b...@alya% gpart show
> =>   34  490234685  ad4  GPT  (234G)
> 341281  freebsd-boot  (64K)
>162   419430402  freebsd-ufs  (20G)
>   4194320283886083  freebsd-swap  (4.0G)
>   50331810  2097152004  freebsd-ufs  (100G)
>  260047010   419430405  freebsd-ufs  (20G)
>  301990050  188244669   - free -  (90G)
>
> [~]b...@alya% gpart set -a bootme -i 2 ad4
> bootme set on ad4p2
> [~]b...@alya% gpart set -a bootonce -i 5 ad4
> bootonce set on ad4p5
> [~]b...@alya% gpart show
> =>   34  490234685  ad4  GPT  (234G)
> 341281  freebsd-boot  (64K)
>162   419430402  freebsd-ufs  [bootme]  (20G)
>   4194320283886083  freebsd-swap  (4.0G)
>   50331810  2097152004  freebsd-ufs  (100G)
>  260047010   419430405  freebsd-ufs  [bootonce,bootme]  (20G)
>  301990050  188244669   - free -  (90G)
> -
>
> Install i386 kernel/world to ad4p5, successful reboot, get i386
> system. Next reboot (get amd64 system back):
> -
> [~]b...@alya% gpart show
> =>   34  490234685  ad4  GPT  (234G)
> 341281  freebsd-boot  (64K)
>162   419430402  freebsd-ufs  [bootme]  (20G)
>   4194320283886083  freebsd-swap  (4.0G)
>   50331810  2097152004  freebsd-ufs  (100G)
>  260047010   419430405  freebsd-ufs  (20G)
>  301990050  188244669   - free -  (90G)
> -
>
> All seems to work fine.
>
> > Any comments or suggestions?
>
> Only one for now. With current default syslog configuration
> logging to local0.warning and local0.info goes nowhere.
> It will be good if those messages have traces at the
> default system.
>
>
> Thank you! That's really great.
>
> --
> WBR, Boris Samorodov (bsam)
> Research Engineer, http://www.ipt.ru Telephone & Internet SP
> FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
> ___
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>


does it work for zfs boot as that would be really nice if it did?
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Dell Perc 5/i Performance issues

[krad]

On 18 June 2010 10:08, oizs  wrote:

> I've seen people with the same configuration doing 160MB/s writes and
> 250MB/s+ reads with raid5 so I still think something isn't right. And using
> raid10 with 4 disks is a rather large waste of capacity.
>
> -zsozso
>
>
> On 2010.06.18. 1:55, Chuck Swiger wrote:
>
>> On Jun 17, 2010, at 4:50 PM, oizs wrote:
>>
>>
>>> I've bought a Dell Perc 5/i because I couldn't make the onboard marvell
>>> 88sx7042 work with 8.0/8.1 or current, but as lucky as I am, the best I can
>>> do with 4x1.5tb samsung in raid5 is 60MB/s writes and 90MB/s reads, with
>>> bbu/write-back/adaptive-read-ahead.
>>>
>>> I was expecting at least twice of that, and I'm not sure what can I do to
>>> get that speed. (I've read man 7 tuning with no success)
>>>
>>>
>> Switch to using RAID-10 rather than RAID-5.  It's normal for RAID-5 to
>> have worse write performance than that of a single drive.
>>
>> Regards,
>>
>>
> ___
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>

what are your drives though? Are they SATA green/eco type drives or proper
SAS enterprise ones
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: newsyslog patch implementing file includes

[krad]

On 22 April 2010 08:33, Alex Keda  wrote:

> 22.04.2010 11:29, Gordon Tetlow ?:
>
>> On Thu, Apr 22, 2010 at 12:17 AM, Alex Keda > ad...@lissyara.su>> wrote:
>>
>>It's need feature. I test patch - it work for me (CURRENT, amd64)
>>Can I use some as:
>> /path/to/dir/*.conf
>>?
>>and can I create recursive include?
>>
>>
>> Yes, wildcards and recursive includes are supported.
>>
> great job!
> Thanks!
>
>
> ___
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>


i would be real nice is newsyslog also supported a date based file renaming
shceme rather than the cyclic 0,1,2,3, much like the datext option in
logrotate. eg

messages
messages.20100422
messages.20100421
messages.20100420
...

The cyclic renaming is a pain for incremental backups as all the log files
are backed up every time as their contents changes compared to their
filename
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: When will we can use ZFS v24?

[krad]

On 8 April 2010 17:47, Sam Fourman Jr.  wrote:

> > ZFS is still currently in heavy development so it might happen. Having
> siad
> > that it looks like oracle have totally buggered it up for everyone with
> > their retroactive licenses. I hope the CDL was tight enough that stuff
> wont
> > have to get pulled from freebsd
>
> is that even possible with CDDL?
>
> Sam Fourman Jr.
> Fourman Networks
>

im not a lawyer but it wouldn't surprise me
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: When will we can use ZFS v24?

[krad]

On 7 April 2010 18:33, Dan Nelson  wrote:

> In the last episode (Apr 07), krad said:
> > On 7 April 2010 05:38, Freddie Cash  wrote:
> > > On Tue, Apr 6, 2010 at 9:35 PM, lhmwzy  wrote:
> > > > What's your mean??
> > >
> > > See the archives for the freebsd-fs mailing list.  There are two
> > > separate groups working on getting ZFSv22 added to FreeBSD 9-CURRENT.
> > > And there's work ongoing to get ZFSv15 added to FreeBSD 8-STABLE.
> > >
> > > IOW, just be patient.  Good things will come to those who wait.  ;)
> >
> > If you re hankering for dedup you better have a big box as its a complete
> > resource hog.  From what we have seen on our x4500 filers we need about
> > 100gig of ram or l2arc ssd to hold the all the metadata for the 34TB of
> > storage, otherwise the system grinds to a halt.
>
> I wish they had an option for "opportunistic" dedup, where if a block is
> already in ARC it can be a dedupe candidate, but it won't look it up in the
> DDT if it isn't already in memory.  That catches the simple "cp -R dir1
> dir2" cases without blowing up the ARC on DDT blocks that 99.% of the
> time don't match.
>
> --
>Dan Nelson
>dnel...@allantgroup.com
> ___
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>

ZFS is still currently in heavy development so it might happen. Having siad
that it looks like oracle have totally buggered it up for everyone with
their retroactive licenses. I hope the CDL was tight enough that stuff wont
have to get pulled from freebsd
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: When will we can use ZFS v24?

[krad]

On 7 April 2010 05:38, Freddie Cash  wrote:

> On Tue, Apr 6, 2010 at 9:35 PM, lhmwzy  wrote:
>
> > What's your mean??
> >
>
> See the archives for the freebsd-fs mailing list.  There are two separate
> groups working on getting ZFSv22 added to FreeBSD 9-CURRENT.  And there's
> work ongoing to get ZFSv15 added to FreeBSD 8-STABLE.
>
> IOW, just be patient.  Good things will come to those who wait.  ;)
>
> --
> Freddie Cash
> fjwc...@gmail.com
> ___
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>

If you re hankering for dedup you better have a big box as its a complete
resource hog. From what we have seen on our x4500 filers we need about
100gig of ram or l2arc ssd to hold the all the metadata for the 34TB of
storage, otherwise the system grinds to a halt.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: recovery from terminated make installworld?

[krad]

On 18 March 2010 20:41, Freddie Cash  wrote:

> On Thu, Mar 18, 2010 at 1:07 PM, Justin Hibbits  >wrote:
>
> > On Thu, Mar 18, 2010 at 4:03 PM, Anton Shterenlikht  > >wrote:
> >
> > > I was in the single user mode doing 'make installworld'
> > > when the system froze and I had to cold reboot.
> > > Now in single user mode I get to:
> > >
> > > Enter full pathname of shell or RETURN for /bin/sh:
> > > /libexec/ld-elf.so.1: /lib/libc.so.7: invalid file format
> > > /libexec/ld-elf.so.1: /lib/libc.so.7: invalid file format
> > > Enter full pathname of shell or RETURN for /bin/sh:
> > >
> > > Is there a way to recover?
> > > Or do I have to reinstall from scratch?
> >
> > Try /rescue/sh (or tcsh).  It's all statically linked, so you should be
> > able
> > to recover from there.
> >
> > And if that doesn't work, try a LiveFS CD.
>
> And, if all else fails, you can do a minimal install overtop.  You'll lose
> all your /etc settings, but will get a bootable system again.
>
> --
> Freddie Cash
> fjwc...@gmail.com
> ___
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>


easier and less risky to boot in on some form of live cd, mount all the fs
up under /mnt, set the DESTDIR=/mnt and continue the installworld
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"