Re: i386 nanobsd w/11.1-RELEASE-p10

2018-05-21 Thread Gary Palmer 
On Mon, May 21, 2018 at 04:05:24AM +0700, Eugene Grosbein wrote:
> On 19.05.2018 20:46, Gary Palmer wrote:
> > 
> > Hi,
> > 
> > I haven't tried building an i386 image with nanobsd since 8.x or 9.x,
> > so apologies if this is a known issue
> > 
> > I've tried to build an i386 nanobsd using nanobsd on an amd64 host,
> > and when that didn't work in an i386 jail on an amd64 host, and
> > now in an i386 vm.
> 
> I routinely update my 11.1-STABLE/i386 home router running nanobsd
> built using 11.1-STABLE/amd64 desktop. I do not use any of chroot/jail/vm to 
> build it.
> 
> > The i386 vm is failing with the logs at the end of the message,
> > taken from _.bw in the nanobsd build directory.  I think similar
> > errors were seen in the other environments also.  A "make buildworld"
> > in /usr/src passes, so it looks like something specific to nanobsd
> > is tickling the problem.
> > 
> > I included the first few lines from the start of boot2.s also.
> > 
> > The nanobsd config file has been stripped down to remove any 
> > options that should affect the build
> > 
> > == begin ==
> > NANO_PMAKE="make -j 1"
> > NANO_NAME=net5501-nopkg
> > NANO_SRC=/usr/src
> > NANO_OBJ=/mnt/space/obj/nanobsd.${NANO_NAME}
> > NANO_KERNEL=NET5501
> > NANO_IMAGES=2
> > NANO_INIT_IMG2=0
> > # The following are in 512 byte sectors.  The "2" is to convert from
> > # sectors to kilobytes
> > NANO_CONFSIZE=48195 # 32 MB
> > NANO_DATASIZE=1975932
> > NANO_RAM_ETCSIZE=$(( 2 * 1024 * 64 )) # 64 MB
> > NANO_RAM_TMPVARSIZE=$(( 2 * 1024 * 32 )) # 32 MB
> > 
> > FlashDevice generic 2048m
> > == end ==
> 
> Here is my gw.conf:
> 
> src=/home/nanobsd/gw
> NANO_PMAKE="make -j9"
> NANO_NAME=gw
> NANO_KERNEL=GW
> NANO_DRIVE=ada0
> NANO_MEDIASIZE=2097152
> NANO_SECTS=63
> NANO_HEADS=255
> NANO_BOOTLOADER="boot/boot0"
> NANO_BOOT0CFG="-o packet -s 1 -m 3 -t 36"
> # no NANO_DATASIZE but this should be irrelevant
> NANO_RAM_ETCSIZE=16384 # 8MB
> NANO_RAM_TMPVARSIZE=409600 # 200MB for large /var/spool
> NANO_CUSTOMIZE="..."
> NANO_LATE_CUSTOMIZE="..."
> CONF_BUILD='
> TARGET=i386
> TARGET_ARCH=i386
> NANO_ARCH=i386
> CPUTYPE?=k6-3
> BOOT_COMCONSOLE_SPEED=115200
> BOOT_MBR_FLAGS=0x0
> BOOT_BOOT1_FLAGS=0x0
> # here come lots of WITHOUT_XXX
> MODULES_OVERRIDE=ipfw_nat
> '
> CONF_INSTALL="
> $CONF_BUILD
> WITHOUT_BINUTILS=
> WITHOUT_CLANG=
> WITHOUT_CLANG_FULL=
> WITHOUT_CXX=
> WITHOUT_TOOLCHAIN=
> WITHOUT_INSTALLLIB=
> "

Thanks.  Using this as a base I was able to build an i386 image
and boot it.  Not entirely sure what was tickling the problem in
my old configuration

> > No /etc/src.conf or /etc/make.conf present.
> 
> That's not good, see above for CONF_BUILD and CONF_INSTALL.
> I've just run /usr/src/tools/tools/nanobsd/nanobsd.sh -c gw.conf
> using my amd64 system and get images for i386.

I had a bunch of stuff in my old config for both settings, but trimmed
them out to see if that was causing the compile problem

Thanks

Gary
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: ftpd in base

2018-05-21 Thread tech-lists 

On 20/05/2018 18:35, Eugene Grosbein wrote:

Our ftpd applies -u and by default instantly overrides it with login class 
setting.

You should add your own login class to /etc/login.conf with 0111 value
then run "cap_mkdb /etc/login.conf" and "pw usermod ftpusername -L 
ftploginclass"


Hi,

Thanks for this - have sorted it now.
--
J.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

R.V Dealers Email List

2018-05-21 Thread ara.gates 

Hi,

Would you be interested in reaching out to R.V Dealers Email List for any of
your marketing initiative for 2018?

We can also help you with: RV Parts and Accessories, RV Insurance, RV Parts
and Accessories, Motorhomes and Recreational Vehicle and many more across
globe.

Data Fields includes: Contact name, Company name, Job Title, Website,
Industry, SIC Code, Email address, Direct mail address, Telephone number,
Revenue Size, Employee Size, etc.

To provide further details counts and a sample file for your review, I would
like to understand your requirement. Please fill in the details below of
your

Target audience: - (Industry vertical you want to target): __ 
Job titles you want to target: __ 
Target geography: ___

Regards,
Ara Gates
Sr. Data Manager


You were specifically sent this email based upon your company profile, if
you do not wish to receive future emails from us, please reply as "No
Requirements".

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: removable storage usability, devd, hald and X11-desktop in general

2018-05-21 Thread Harry Schmalzbauer 

Am 20.05.2018 um 23:52 schrieb EBFE:

On Sat, 19 May 2018 20:35:59 +0200
Harry Schmalzbauer  wrote:

Hi,


Biggest question: How are useres expected to handle removable media?

I'm a happy user of autofs(5) in several environments (mostly for NFS
mounts), but I'm not aware of any helper tool which enables _users_
to unmount before pulling the UFD.
I've heard of PC-BSD and Lumina (see later why I haven't really tried
out the modern "light" desktops) and I think I remember having read
they utilize devd(8).  But again, how to unmount?


There is a nice little daemon: sysutils/dsbmd
(see https://freeshell.de/~mk/projects/dsbmd.html
and /usr/local/etc/dsbmd.conf.sample)

with a simple GUI sysutils/dsbmc and cli (sysutils/dsbmc-cli) clients.
It supports automounting using devd and/or polling and automatic
or manual unmounting.



Thanks!  Also to Kurt and Edward for their answers.  Suitable advises 
for people with an idea what a filesystem is about, but not for my step 
daughter.  Even if her biggest idol would tell her that it's cool to 
wait 5 seconds before pulling the UFD, she wouldn't accept; if she's 
ready with copying, the device also has to be ready. period. But she 
accepts the "eject" step from other OS...  it's a instruction she tells, 
so it's acceptable.  As long as she needn't to type anything...  And 
she's by far not the only one I know with similar expectations – the 
computer has to do what the user tells, as soon as the user has to 
follow "strange" computer "rules", fun abruptly ends ;-)


sysutils/dsbmc is completely new to me.

Meanwhile I read about sysutils/bsdisks – UDisks2 compliant.  Never 
heard of UDisks2 before, but will have a look asap, sounds interesting too.


It's supposed to be supported by x11-fm/pcmanfm-qt – by far the most 
sensible x11 filemanager I've tried so far (offers checkmark to store 
folder specific preferences, switches from beautified path to text path 
on click, easy to configure single-click, and the usual thumbnail etc. 
is working too at acceptable performance – not even close to Rox filer 
or Thunar, but this might vary if one doesn't use it from gtk session 
but Qt based session/desktop).


Also found out that it should be easily possible to use xfce4wm with LXQt.
As time permits I'll keep trying out those highly appreciated 
alternatives – I've always been happy that my X11/xfce4 desktop helped 
my saving time compared to Windows XP, but since then, many usability 
cherries grew in windows, which I'm missing on X11 and hoped that the 
famous X11 desktop projects would have picked.  pcmanfm-qt at least 
catches up with XP usability...


-harry

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"