Zona dns

[Ricky Gutierrez]

Hola lista, pregunto esto xq en algún momento leí que se podía ocultar los
registros dns de una zona de dominio, por ejemplo cuando alguien te hace un
dig Any mizona.com ves todos los registros de esa zona.

Existe alguna forma?

Re: [Progress Report1] Re: Using debootstrap

[Richard Owlett]

On 04/27/2018 12:06 PM, Felix Dietrich wrote:

[SNIP]

Do not specify „--print-debs” if you want „debootstrap” to install the
packages.


*BINGO*
Proofreading one's own work is intrinsically error prone ;/

But it doesn't solve all my problems. Captured the session with 
SCRIPT(1). I haven't yet decoded the permission bits displayed by
the "ls -Rdl ..." lines. I don't see the two error messages being 
consistent with what I *think* I see when using Caja.

Yepp, I have some homework to do. ;}



Script started on Fri 27 Apr 2018 02:22:42 PM CDT

ls -Rdl /media/root/rco1


ls -Rdl /usr/sbin/debootstrap


ls -Rdl /media/root/rco1


debootstrap --verbose --arch=i386 --include=apt-get --variant=minbase 
--no-check-gpg stable /media/root/rco1 file:media/cdrom0/debian/


exit
root@debian-jan13:~# 
root@debian-jan13:~# ls -Rdl /media/root/rco1

drwxr-xr-x 3 root root 4096 Apr 27 14:08 /media/root/rco1
root@debian-jan13:~# 
root@debian-jan13:~# 
root@debian-jan13:~# ls -Rdl /usr/sbin/debootstrap

-rwxr-xr-x 1 root root 18981 Mar 10  2017 /usr/sbin/debootstrap
root@debian-jan13:~# 
root@debian-jan13:~# 
root@debian-jan13:~# ls -Rdl /media/root/rco1

drwxr-xr-x 3 root root 4096 Apr 27 14:08 /media/root/rco1
root@debian-jan13:~# 
root@debian-jan13:~# 
root@debian-jan13:~# debootstrap --verbose --arch=i386 --include=apt-get --variant=minbase --no-check-gpg stable 
 /media/root/rco1 file:media/cdrom0/debian/

/usr/sbin/debootstrap: 1454: /usr/sbin/debootstrap: cannot create 
/media/root/rco1/test-dev-null: Permission denied
E: Cannot install into target '/media/root/rco1' mounted with noexec or nodev
root@debian-jan13:~# 
root@debian-jan13:~# 
root@debian-jan13:~# exit

exit

Script done on Fri 27 Apr 2018 02:22:42 PM CDT

Re: [Progress Report1] Re: Using debootstrap

[Felix Dietrich]

Richard Owlett  writes:

> On 04/25/2018 09:19 AM, Richard Owlett wrote:
>> My goal is a very minimalist install to a flash drive. It will NOT
>> have GRUB - GRUB on this machine is on a dedicated partition for
>> convenience in some of my experiments.
>
> Doing:

> debootstrap --verbose --arch=i386 --include=apt-get \
>   --variant=minbase --no-check-gpg --print-debs \
>   --keep-debootstrap-dir stable /media/richard/rco \
>   file:media/cdrom0/debian/
> 
> generates no error messages. HOWEVER, very few files are actually
> written to the flash drive at /media/richard/rco and a subsequent run
> of "debootstrap --second-stage" yields a file not found message.

You are providing „--print-debs” as an argument to „debootstrap” which
will cause „debootstrap” to print the packages it would install and
exit.  Here is the manual entry for „--print-debs”:

 Print the packages to be installed, and exit.  Note that a TARGET
 directory must be specified so debootstrap can download Packages
 files to determine which packages should be installed, and to
 resolve dependencies.  The TARGET directory will be deleted unless
 --keep-debootstrap-dir is specified.

Do not specify „--print-debs” if you want „debootstrap” to install the
packages.

Also: if you run debootstrap from the same target architecture (or a very
similar one like creating an i386 environment from an amd64 host, I
suspect) you do not need to run the second stage manually.

--
Felix Dietrich

Re: [Progress Report1] Re: Using debootstrap

[deloptes]

Richard Owlett wrote:

> The error message when attempting "debootstrap --second-stage" is
> "cat: /usr/share/debootstrap/suite: No such file or directory".

I don't recall to be using second stage. I just make debootstrap with
perhaps architecture and I think it takes the minimal as default.



Systems$ ls
ARM  BUSTER  GEOD  Geode_Old  JESSIE  RaspBerryPI  SID  STRETCH

Systems$ ls */usr/share/debootstrap/
BUSTER/usr/share/debootstrap/:
functions  scripts

SID/usr/share/debootstrap/:
functions  scripts

AFAIR all is installed via debootstrap. There is a small chance that before
Buster it was installed somehow different, but could be that it is
something new with this second stage

regards

Re: [Progress Report1] Re: Using debootstrap

[rhkramer]

On Friday, April 27, 2018 10:16:22 AM Richard Owlett wrote:
> I thought I was doing that. My TARGET is "/media/richard/rco" where
> "rco" is the label of a partition on the flash drive.

Just chiming in from left field: have you mounted that partition?

Re: Inexplicable memory usage after move to Debian9

[Cindy-Sue Causey]

On 4/27/18, Reco  wrote:
>   Hi.
>
> On Fri, Apr 27, 2018 at 12:26:11PM +, Eduardo M KALINOWSKI wrote:
>> On sex, 27 abr 2018, Simon Beirnaert wrote:
>> > The bottom line for me is that I when I shut down everything I install
>> > and manage on the system, it's still conuming about half a gig more
>> > than a system running the exact same base image right after use,
>> > without
>> > the extra memory being accounted for by monitoring tools.
>>
>> How are you determining what you call "consumed memory"?
>
> OP's original e-mail mentioned free(1), vmstat(1) and smem(1).
> All three lie :).
>
>
>> Keep in mind that the kernel will by default use almost all free memory
>> (not
>> actually used by processes and libraries) as cache space, because it
>> makes
>> no sense to leave memory just laying around. However, once it's really
>> needed, the caches will be dropped. Thus "free" memory is usually
>> reported
>> as low. Compare with "available" memory as reported by free.


Yeah, I took a shot at trying to help with this one, too, via
searching apt for "monitor memory usage". Saw a couple possibilities,
but so far nothing's reflecting what I know is going on.

smemstat was the current standout. As normal user, it said my browser
was using ~60MB or so. smemstate via root user shows closer to 1GB.
That's a big difference...

Meanwhile in reality and on a fresh reboot, "free -m" will lurch
"used" from ~350MB to ~5 1/2 gigabytes as soon as all... open browser
tabs.. are refreshed (offline). User experience of sporadic crashes
lately backs that up as pretty much verified.

Apparently ~600 tabs this morning. When a browser flashes that warning
that opening more than a few tabs has potentially negative
consequences.. they ain't just whistling Dixie... :)

Cindy.
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs... in search of more (very) cheap RAM *

Re: [Progress Report1] Re: Using debootstrap

[Richard Owlett]

On 04/27/2018 08:49 AM, deloptes wrote:

Richard Owlett wrote:


QUESTION:
Has anyone personally used debootstrap to install to a flash drive?


I do install in a directory and then copy the content to the flash drive
then chroot and make it bootable


I was installing to the flash drive because I have less than 1GB 
available on my hard drive.




alternatively you ma install into directory where flash drive is mounted


I thought I was doing that. My TARGET is "/media/richard/rco" where 
"rco" is the label of a partition on the flash drive.



and
then chroot and make it bootable


I'm not that far yet.
My immediate goal is for debootstrap to write what would "resemble" a 
system to the flash drive.


The error message when attempting "debootstrap --second-stage" is
"cat: /usr/share/debootstrap/suite: No such file or directory".



forget not that you need to mount the system related /proc/ etc.

this is what I am using

 mount --make-unbindable -obind /proc/ $SYSTEM/proc/ && \
 mount --make-unbindable -obind /dev/ $SYSTEM/dev/ && \
 mount --make-unbindable -obind /dev/pts $SYSTEM/dev/pts && \
 mount --make-unbindable -obind /run $SYSTEM/run && \
 mount --make-unbindable -obind /sys $SYSTEM/sys/ && \
 chroot $SYSTEM su -


For the umount

 umount $SYSTEM/proc/ && \
 umount $SYSTEM/dev/pts && \
 umount $SYSTEM/dev/ && \
 umount $SYSTEM/run/ && \
 umount $SYSTEM/sys/


regards

Re: Inexplicable memory usage after move to Debian9

[David Wright]

On Fri 27 Apr 2018 at 12:26:11 (+), Eduardo M KALINOWSKI wrote:
> On sex, 27 abr 2018, Simon Beirnaert wrote:
> >The bottom line for me is that I when I shut down everything I install
> >and manage on the system, it's still conuming about half a gig more
> >than a system running the exact same base image right after use, without
> >the extra memory being accounted for by monitoring tools.
> 
> How are you determining what you call "consumed memory"?
> 
> Keep in mind that the kernel will by default use almost all free
> memory (not actually used by processes and libraries) as cache
> space, because it makes no sense to leave memory just laying around.
> However, once it's really needed, the caches will be dropped. Thus
> "free" memory is usually reported as low. Compare with "available"
> memory as reported by free.

In which case, this could be a useful recipe:

# free -m
 total   used   free sharedbuffers cached
Mem:  2016   1251764  0301774
-/+ buffers/cache:175   1840
Swap: 3861  0   3861
# echo 3 > /proc/sys/vm/drop_caches
# free -m
 total   used   free sharedbuffers cached
Mem:  2016119   1896  0  0 24
-/+ buffers/cache: 94   1921
Swap: 3861  0   3861
# 

Now you can watch it creep up again.

Cheers,
David.

Re: [Progress Report1] Re: Using debootstrap

[deloptes]

Richard Owlett wrote:

> QUESTION:
> Has anyone personally used debootstrap to install to a flash drive?

I do install in a directory and then copy the content to the flash drive
then chroot and make it bootable

alternatively you ma install into directory where flash drive is mounted and
then chroot and make it bootable

forget not that you need to mount the system related /proc/ etc.

this is what I am using

mount --make-unbindable -obind /proc/ $SYSTEM/proc/ && \
mount --make-unbindable -obind /dev/ $SYSTEM/dev/ && \
mount --make-unbindable -obind /dev/pts $SYSTEM/dev/pts && \
mount --make-unbindable -obind /run $SYSTEM/run && \
mount --make-unbindable -obind /sys $SYSTEM/sys/ && \
chroot $SYSTEM su -


For the umount

umount $SYSTEM/proc/ && \
umount $SYSTEM/dev/pts && \
umount $SYSTEM/dev/ && \
umount $SYSTEM/run/ && \
umount $SYSTEM/sys/


regards

Re: [Progress Report1] Re: Using debootstrap

[Richard Owlett]

On 04/27/2018 08:00 AM, songbird wrote:

Richard Owlett wrote:
...

QUESTION:
Has anyone personally used debootstrap to install to a flash drive?


   not yet...  :)

   i'm currently having other bigger fish to fry...



My environment is:
OS is i386 Debian stable
DVD is DVD-1 of Debian 9.1.0
Flash drive has a:
  4 GB ext2 partition
  4 GB swap partition


   get rid of swap partition and change ext2 to ext4 and use all
space on drive for that.


Done. No change :{



   don't ask me what i think of uefi...






   when using flash drive on main system you can use the
main system drive swap (modify /etc/fstab on flash drive to use
main system drive swap).


I know. When my first attempt failed I added the swap partition "just in 
case" debootstrap expected to see it on the destination device.





   songbird

Re: [Progress Report1] Re: Using debootstrap

[songbird]

Richard Owlett wrote:
...
> QUESTION:
> Has anyone personally used debootstrap to install to a flash drive?

  not yet...  :)

  i'm currently having other bigger fish to fry...


> My environment is:
>OS is i386 Debian stable
>DVD is DVD-1 of Debian 9.1.0
>Flash drive has a:
>  4 GB ext2 partition
>  4 GB swap partition

  get rid of swap partition and change ext2 to ext4 and use all
space on drive for that.

  don't ask me what i think of uefi...

  when using flash drive on main system you can use the
main system drive swap (modify /etc/fstab on flash drive to use
main system drive swap).


  songbird

Re: Inexplicable memory usage after move to Debian9

[Reco]

Hi.

On Fri, Apr 27, 2018 at 12:26:11PM +, Eduardo M KALINOWSKI wrote:
> On sex, 27 abr 2018, Simon Beirnaert wrote:
> > The bottom line for me is that I when I shut down everything I install
> > and manage on the system, it's still conuming about half a gig more
> > than a system running the exact same base image right after use, without
> > the extra memory being accounted for by monitoring tools.
> 
> How are you determining what you call "consumed memory"?

OP's original e-mail mentioned free(1), vmstat(1) and smem(1).
All three lie :).


> Keep in mind that the kernel will by default use almost all free memory (not
> actually used by processes and libraries) as cache space, because it makes
> no sense to leave memory just laying around. However, once it's really
> needed, the caches will be dropped. Thus "free" memory is usually reported
> as low. Compare with "available" memory as reported by free.

The free's 'available' value is computed without taking "SUnreclaim"
(unreclaimable kernel slabs) value from /proc/meminfo.
The difference is not that great, usually, but for NFS server it can
lead to funny things like "I have plenty of free swap and OOM killer was
invoked, despite 'available' telling me there's plenty of free RAM".
Can happen with Java too, as OP e-mail shows us.

Happened to me with kernel 4.9.0-5, continued with kernel 4.9.0-6, seems
to be solved by upgrading to backported kernel version 4.14.

Reco

Re: Inexplicable memory usage after move to Debian9

[Eduardo M KALINOWSKI]

On sex, 27 abr 2018, Simon Beirnaert wrote:

The bottom line for me is that I when I shut down everything I install
and manage on the system, it's still conuming about half a gig more
than a system running the exact same base image right after use, without
the extra memory being accounted for by monitoring tools.


How are you determining what you call "consumed memory"?

Keep in mind that the kernel will by default use almost all free  
memory (not actually used by processes and libraries) as cache space,  
because it makes no sense to leave memory just laying around. However,  
once it's really needed, the caches will be dropped. Thus "free"  
memory is usually reported as low. Compare with "available" memory as  
reported by free.


--
Eduardo M KALINOWSKI
edua...@kalinowski.com.br

Re: [Progress Report1] Re: Using debootstrap

[Richard Owlett]

On 04/27/2018 06:38 AM, Richard Owlett wrote:


Doing:

debootstrap --verbose --arch=i386 --include=apt-get --variant=minbase
--no-check-gpg --print-debs --keep-debootstrap-dir stable 
/media/richard/rco

file:media/cdrom0/debian/

generates no error messages.
HOWEVER, very few files are actually written to the flash drive
at /media/richard/rco and a subsequent run of
    "debootstrap  --second-stage"
yields a file not found message.

I have some ideas about my problems and will have time this weekend.



I just ran a couple of quick tests of what should be a more typical case 
with no different results.


QUESTION:
Has anyone personally used debootstrap to install to a flash drive?

My environment is:
  OS is i386 Debian stable
  DVD is DVD-1 of Debian 9.1.0
  Flash drive has a:
4 GB ext2 partition
4 GB swap partition

TIA

[Progress Report1] Re: Using debootstrap

[Richard Owlett]

On 04/25/2018 09:19 AM, Richard Owlett wrote:
My goal is a very minimalist install to a flash drive. It will NOT have 
GRUB - GRUB on this machine is on a dedicated partition for convenience 
in some of my experiments.


 From reading several references I believe my command should be:

debootstrap --arch=i386 --include=apt-get --variant=minbase 
--no-check-gpg --print-debs --keep-debootstrap-dir stable 
/media/richard/rco /media/cdrom0/


I have two questions:
   1. What should replace "" as I'll be using DVD1 of Debian 9.1.0
  as my "repository"?
   2. As I expect the console display may exceed the scroll back limits,
  I wish to pipe the console display for later reference without
  impeding answering any prompts I get. I've seen a description for
  doing that, but I can't remember it. Pointers?




Taking those questions in reverse order ;}

SCRIPT(1) was the command I had been trying to recall. I does things in 
a comfortable way.


I was reading man page for SCREEN(1) when SCRIPT(1) was  suggested. Part 
of the recommendation for SCREEN(1) was it being mentioned in the 
release notes for *upgrades*. In fact the release notes describe using 
it for _remote_ upgrades, not local new installs via debootstrap.


Doing:

debootstrap --verbose --arch=i386 --include=apt-get --variant=minbase
--no-check-gpg --print-debs --keep-debootstrap-dir stable /media/richard/rco
file:media/cdrom0/debian/

generates no error messages.
HOWEVER, very few files are actually written to the flash drive
at /media/richard/rco and a subsequent run of
   "debootstrap  --second-stage"
yields a file not found message.

I have some ideas about my problems and will have time this weekend.
Thank you.

Re: Using debootstrap

[Richard Owlett]

On 04/26/2018 02:43 PM, Henning Follmann wrote:

On Thu, Apr 26, 2018 at 08:02:38PM +0200, deloptes wrote:

Henning Follmann wrote:


Happy to read the man page to you buddy.


-H


while I can understand your feeling quite well, I had to teach myself either
to ignore affecting questions or to answer for the sake of the answer.

sometimes it is really frustrating how one can not understand obvious
things, however not all are same age, have same background or level of
intelligence.

its better you give example in such case

debootstrap [OPTION...]  stable /mypath/to/target/installation file:///DVD1

this is how I understand it, correct if I'm wrong



I am no expert on the install ISO images but if I understand correctly
there is a "debian" directory on it. So I guess:
debootstrap [OPTION...]  stable /mypath/to/target/installation
file:///DVD1/debian

however just hope that the current DVD is also "stable"



The purchased DVD is Debian 9.1.0.  My OS used is stable installed via 
netinst.

Re: Using debootstrap

[Richard Owlett]

On 04/26/2018 02:39 PM, Felix Dietrich wrote:

deloptes  writes:


its better you give example in such case

debootstrap [OPTION...]  stable /mypath/to/target/installation file:///DVD1

this is how I understand it, correct if I'm wrong


Almost: as has been stated elsewhere in this thread, at least according
to Appendix D of the Debian Installation Guide [1] you may provide a
„file://” URL to the debian/ directory below the mount point of the disc
for the MIRROR parameter, e.g.: file:///cdrom/debian/

Admittedly, I have not to tested either this or your variant.

[1] https://www.debian.org/releases/stable/i386/apds03.html.en#idm46014282700896




Apparently file:media/cdrom0/debian/ work.
I say "apparently" because:
  1. I get no "file not found" messages.
  2. I have some undiagnosed problems using debootstrap.

Re: Inexplicable memory usage after move to Debian9

[Simon Beirnaert]

I'm not sure that a ratio of 512MB swap to 1.8GB RAM really proves
anything. If the swap space matched RAM in size and still filled up, I
think that would be more definitive.


The bottom line for me is that I when I shut down everything I install
and manage on the system, it's still conuming about half a gig more
than a system running the exact same base image right after use, without
the extra memory being accounted for by monitoring tools.

Enabling swap just helped me realize that the allocated memory isn't
actively used, otherwise the system would be swapping it in/out more than
it is.

These machines (thousands) have been running on without swap on Debian 7
for a *long* time without issues. I wasn't intending on activating swap
now either. It's just a debugging step.

What I'm actually looking for is a way to trace where to which process
that mistery half-a-gig is allocated. As I said: I can't find a memory
list which acocunts for everything. This is what makes me think of a
memory leak somewhere. I just want to debug this. I'm not trying to imply
that I was solving anything by allocating RAM.


Also note this comment at the top of the stackexchange article:
"UPDATE: I'm no longer having this problem on 4.9.* Not sure when 
it was fixed."


I know. Just wanted to indicate that I had looked at slab allocation
issues, but it doesn't seem to be related


Thanks
Simon