Re: does your Thunderbird for deb11 often become unresponsive?
On 3/3/23 12:17, Alexander V. Makartsev wrote: On 03.03.2023 09:02, hlyg wrote: at first i suspect Thunderbird(TB) try to access some sites that are blocked in china i disable show Start Page when it launches i disable check email automatically for each account but it becomes unresponsive when i File->New->Message i really don't know cause of unresponsiveness PS: even if blocked sites cause trouble, it's bug of TB, it shall timeout after it can't access sites for some time I don't have any issues with TB on a PC with operating system on SSD. If I had to guess the culprit, it could be a failing HDD. You should check "/var/log/syslog" for anything suspicious and\or "smartctl". This also could be a symptom of resource starvation. Run "free -h" and\or "top" to see if there is any resource hogs. It's a bug in Thunderbird. It is the result of using multiple accounts and something about multi-threading, I think, (on mine, anyway). I have not filed a bug, but surely they know about it, it's present on both Linux and Windows, and through several versions. I have been patiently waiting for a fix, perhaps we should all file bugs, if they are inundated with bug reports, maybe they'll be more motivated to fix it. Mark A. -- With kindest regards, Alexander. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org ⠈⠳⣄
Re: Trying to find the source iso's for debian buster and bookworm
Thats correct buster and bullseye is released bookworm is testing and still being developed for a couple of months more On 3/5/23, davidson wrote: > On Sat, 4 Mar 2023 Keith Christian wrote: >> Several versions back, we could download the source code >> on various iso files for previous and current releases. > >Debian CDs/DVDs archive >https://cdimage.debian.org/cdimage/archive/ > >> Where can those be found for Buster [...] > > I would look in the archives linked above. > >> [...] and Bookworm? > > I understand the Bookworm is, at the moment, still on the testing > branch. That is, it is not yet a release. > > I have a lot of trouble mixing up the codenames that start with > "B". Maybe I am confused. > >> Several searches turned up nothing. > >Debian on CDs/DVDs >https://www.debian.org/CD/#content > >Frequently Asked Questions about Debian CD/DVD/USB images >https://www.debian.org//CD/faq/#content > > -- > Ce qui est important est rarement urgent > et ce qui est urgent est rarement important > -- Dwight David Eisenhower > >
Re: Git Branching
On Sat, Mar 04, 2023 at 09:59:29PM -0600, William Torrez Corea wrote: > I am working with remotes, when i want push to the remote with this command > appear the following error: > > *git push main master* > > fatal: 'main' does not appear to be a git repository > > fatal: Could not read from remote repository. > > > > Please make sure you have the correct access rights > > and the repository exists. > > > > I have the following branching: > > > main > > * master > > > > I don't want to create a new branching, I want to push my advance to the > main but it is impossible. This creates a new branching. Too little context to try to help you: what are you trying to do? Cheers -- t signature.asc Description: PGP signature
Re: Git Branching
On Sat, Mar 4, 2023 at 11:00 PM William Torrez Corea wrote: > I am working with remotes, when i want push to the remote with this > command appear the following error: > > *git push main master* > > fatal: 'main' does not appear to be a git repository >> fatal: Could not read from remote repository. >> >> Please make sure you have the correct access rights >> and the repository exists. >> > > I have the following branching: > >> main >> * master >> > > I don't want to create a new branching, I want to push my advance to the > main but it is impossible. This creates a new branching. > This has nothing to do with Debian, but I think the command you want is: git push origin main >
Git Branching
I am working with remotes, when i want push to the remote with this command appear the following error: *git push main master* fatal: 'main' does not appear to be a git repository > fatal: Could not read from remote repository. > > Please make sure you have the correct access rights > and the repository exists. > I have the following branching: > main > * master > I don't want to create a new branching, I want to push my advance to the main but it is impossible. This creates a new branching. -- With kindest regards, William. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org ⠈⠳⣄
Re: how to activate my wireless card? nmtui only shows wireless connections . . .
On 3/4/23, David Wright wrote: > Also, now that the firmware is in place, if you repeat those steps, > you're /likely/ to find that ath10k_pci is busy, because the link > will be configured automatically in the first few seconds after > booting up. I would always go into exposed mode using a DL DVD that is what I meant when I said "re start". So, I will need to run a dkpg script whenever I boot it. sudo iwlist wlp2s0 scan | grep ESSID will list the wireless networks around. All I need now is a way to somehow pass the password into the script in the command line of through a config file so that I don't have to enter it every time. I tried to find a way to do just that. How do you?
Re: alias in bash script issue
On Sun, Mar 05, 2023 at 09:26:41AM +0800, Ken Young wrote: > On Sat, Mar 4, 2023 at 5:53 PM David wrote: > > Debian's default shell is 'dash'. Its manual, readable using 'man dash', > > says > my debian 11's default shell is just bash. > > root@nxacloud-bloghost:~# echo $SHELL > > /bin/bash Both statements are correct, within their contexts. The default *interactive* shell for user accounts is /bin/bash. The default /bin/sh symlink (for scripts using #!/bin/sh, etc.) is dash. The author of a script chooses whether the shebang says #!/bin/bash (which makes it a bash script) or #!/bin/sh (which makes it an sh script). The languages are different.
Re: alias in bash script issue
On Sat, Mar 4, 2023 at 5:53 PM David wrote: > On Sat, 4 Mar 2023 at 19:30, Ken Young wrote: > > > Do you know why my alias can't work in the bash script? > > The info is as follows. > > > > 1) this alias does exist > > $ alias |grep 'k=' > > alias k='minikube kubectl --' > > > > 2) it also exists in .bash_profile > > $ cat ~/.bash_profile |grep 'k=' > > alias k="minikube kubectl --" > > [...] > > > ./get.sh: line 5: k: command not found > > [...] > > > Please give suggestions. > > Hi. Friends don't help friends to do bad things :) > > Debian's default shell is 'dash'. Its manual, readable using 'man dash', > says > > > Hi, my debian 11's default shell is just bash. root@nxacloud-bloghost:~# echo $SHELL /bin/bash root@nxacloud-bloghost:~# lsb_release -cd Description: Debian GNU/Linux 11 (bullseye) Codename: bullseye Thanks
slapd access to private key owned by root
I think the problem is probably unsolvable but I thought I'd ask. I understand slapd starts as user root and reads config etc and then changes to user openldap This means that it could potentially read a private key owned by root during startup? The problem is when I try and configure private keys for ldap TLS the permissions are checked and if it's not owned by openldap and permissions 400 or 600 the configuration fails. Is there a known solution to this problem? My config: apt show slapd ldap-utils Package: slapd Version: 2.4.57+dfsg-3+deb11u1 Package: ldap-utils Version: 2.4.57+dfsg-3+deb11u1 Jeremy
Re: Trying to find the source iso's for debian buster and bookworm
On Sat, 4 Mar 2023 Keith Christian wrote: Several versions back, we could download the source code on various iso files for previous and current releases. Debian CDs/DVDs archive https://cdimage.debian.org/cdimage/archive/ Where can those be found for Buster [...] I would look in the archives linked above. [...] and Bookworm? I understand the Bookworm is, at the moment, still on the testing branch. That is, it is not yet a release. I have a lot of trouble mixing up the codenames that start with "B". Maybe I am confused. Several searches turned up nothing. Debian on CDs/DVDs https://www.debian.org/CD/#content Frequently Asked Questions about Debian CD/DVD/USB images https://www.debian.org//CD/faq/#content -- Ce qui est important est rarement urgent et ce qui est urgent est rarement important -- Dwight David Eisenhower
Trying to find the source iso's for debian buster and bookworm
Several versions back, we could download the source code on various iso files for previous and current releases. Where can those be found for Buster and Bookworm? Several searches turned up nothing. Thanks.
Re: Debian 12
On Sat, Mar 04, 2023 at 06:37:48PM -0300, Marcelo Eduardo Giordano wrote: > Estimados: > > Como viejo usuario de Debian entiendo que las versiones salen cuando está > terminada la mismo, pero escuché versiones que a mediados de año sale la > versión 12. > > Hay algo de cierto? > Estamos ahora en la etapa del "freeze", así que luce como que lo más probable es que salga en el verano. Saludos, -Roberto -- Roberto C. Sánchez
Debian 12
Estimados: Como viejo usuario de Debian entiendo que las versiones salen cuando está terminada la mismo, pero escuché versiones que a mediados de año sale la versión 12. Hay algo de cierto? Saludos
Re: ¿Esta exdebian muerto?
Ver si te satisface : https://wiki.debian.org/es/FreedomBox/Manual , https://www.debian.org/doc/manuals/maint-guide/index.es.html , https://wiki.debian.org/es/FreedomBox/Manual , https://www.debian.org/international/Spanish y hay mucho mas , Claro yo lo use hace 10 atras y luego lo guarde . USAR para ello : https://duckduckgo.com/?atb=v325-1=v325-1 , Que es un buscador : Colaboratvo_No _Corporativo. Tendrás que buscar ahí . El sáb, 4 mar 2023 a las 13:40, JavierDebian () escribió: > > > El 4/3/23 a las 05:18, Parodper escribió: > > Tal vez se le podrían pedir a los administradores de forums.debian.net > > que añadan un subforo en castellano, pero, la verdad, ni idea de si > > recibiría algo de actividad. > > > No tendría nada de actividad. > Hoy por hoy, la mayoría de los problemas se resuelve, y en español, con > una búsqueda rápida. > Y los pocos problemas que surgen, son muy, muy específicos, y salvo > debian-urser-spanish, no existe otra lista en este idioma con gente con > suficientes conocimientos para hilar tan fino. > La única que ayuda mucho www.archlinux-es.org > > La única que la supera son las listas de desarrolladores, que por ser > gente de todos lados del planeta, son en inglés. > > > JAP > > -- arescor...@gmail.com
Re: how to activate my wireless card? nmtui only shows wireless connections . . .
On Sat, Mar 4, 2023 at 12:12 PM David Wright wrote:
>
> On Sat 04 Mar 2023 at 01:02:54 (-0500), Jeffrey Walton wrote:
> > On Fri, Mar 3, 2023 at 6:10 PM Greg Wooledge wrote:
> > > On Fri, Mar 03, 2023 at 05:45:54PM -0500, Jeffrey Walton wrote:
> > > > The 'p' is a pci bus, the 's' is a slot number. Since the interface
> > > > does not move around once installed, the interface will always have
> > > > the same name like 'enp4s0'.
> > >
> > > That's a wonderful idea, but it doesn't quite work in practice. There are
> > > ways that a "predictable" interface name may change. A BIOS/firmware
> > > upgrade can do it. Adding or removing devices can also do it, in
> > > some cases. They don't even have to be network interfaces.
> >
> > Yeah, that's udev and systemd screwing things up.
>
> Not really. You've got plenty of choice:
>
> net.ifnames=0, biosdevname=0 (on Dell), and
> NamePolicy={kernel,database,onboard,slot,path,mac,keep}
If you are creating the problem you should not be surprised there is a problem.
Jeff
call for beta testing emu10k1 driver improvements
moin, i did some hacking on the emu10k1 driver, and now need it tested on a variety of hardware. the cards still have a market value, so *someone* must be still using them, or at least have some in the basement ... the driver targets SoundBlaster Live! / 512PCI / Audigy and the E-MU 0404/1010/1212/1616m/1820 PCI/PCIe/CardBus series. the exact labeling of the relevant cards can be found in the table at https://github.com/torvalds/linux/blob/master/sound/pci/emu10k1/emu10k1_main.c#L1273 the primary objective of the patch series was adding support for 96/192 khz sample rates on the e-mu cards, but a variety of other (mostly minor) improvements and bugfixes is included as well. i have only an e-mu 0404 card, so my own testing is obviously limited. to fully unleash the driver, emu_das=1 needs to be added to the module options. this switches the driver to a mode which is incompatible with existing configuration files and saved mixer states (the cost/benefit ratio of extending the legacy mode in a compatible way is unreasonable). only the multi-channel device is available in this mode (it's still usable as a regular sound card, but you won't have much fun with it without a sound server - but most people have that nowadays anyway). things that need testing in particular: - the source & destination routing in the mixer; the internals were pretty much completely rewritten. test at different settings of the clock multiplier, as that massively affects the routing. - capture on 2nd generation e-mu 1010 and 1616m cardbus cards: 8 channels at 192 khz and 16 channels at 96 khz (whether the upper half of the channels actually records something, and whether these channels aren't delayed by a single sample or otherwise distorted) then there are a few things that don't need testing as such, but rather help me with understanding the hardware in the first place: - inspect the contents of /proc/sound/card?/spdif-in with various digital sources - adat and s/pdif, both on the card and the dock, and bnc sync. what are the lock status and the displayed rates with no signal, good signal async to internal clock, and synced signal? test s/pdif at least with 48 & 96 khz (192 works on 1010b & 1616m cards on the RCA port). use the mixer to switch around the clock source between internal and the connected external one. - if you have a second e-mu card: 1. if it's in a different machine, make sure it's also running my patched kernel 2. connect its s/pdif output to the 1st card's s/pdif input 3. make sure the clock multiplier is the same on both cards 4. select s/pdif as the 1st card's clock source 5. switch the 2nd card's word clock between 48 and 44.1 khz 6. see if the kernel journal (dmesg) for the 1st card reports "emu1010: External clock rate changed" 7. if it reports "emu1010: External clock lost" instead, go back to point 4. retry a few times. 8. if it (occasionally) doesn't report anything, that's valuable info, too. but switch either card's clock multiplier to make sure that a clock loss is actually reported at all. for soundblasters barely anything changed, so it's only necessary to test whether i didn't break anything - playback and the mixer in particular. /proc/sound/card?/emu10k1 should be somewhat more useful than before. on cards with an additional CA0151 chip (various audigy 2/4 cards), playback over hw:?,4 should be tested. the code is available from https://github.com/ossilator/linux/tree/ossis-alsa and is supposed to work out of the box (like any rc kernel ...). if someone wants to provide me with hardware (temporarily or permanently), go ahead (i'm in berlin, germany). please send responses directly to me. you can cc the list if you have questions relevant to a wider audience. regards
Re: Forcing dhclient to not ignore tun0 interface when it's available
On Fri 03 Mar 2023 at 17:03:49 (+), daven...@tuxfamily.org wrote: > On 2023-03-03 05:21, David Wright wrote: > > On Thu 02 Mar 2023 at 11:44:17 (+0100), daven...@tuxfamily.org wrote: > > > > > > I finally had the time to dig into the logs from two days ago, when > > > the problem happens again > > > It seems that dhclient does it requests trying different interfaces > > > EXCEPT tun0 (see syslog below) > > > > > > I looked into /etc/dhcp/dhclient.conf, which mostly commented. In the > > > non-commented part shown below > > > I don't see anything related to which interfaces are to be used as > > > arguments when dhclient is executed > > > But I'm not a dhclient expert. > > > > > > At boot time/without VPN, dhclient is executed with enp.* interface > > > accondinng to systemctl/ps -eFH. > > > But It still tries different interfaces according to logs. And I have: > > > no idea how it detects > > > which interfaces to use for it requests and why it doesn't > > > detect tun0. > > > Maybe because tun0 is not yet exposed by the system at boot time when > > > dhclient is started? > > > > > > It stills try wlan interface even if it is down, which is weird, but > > > doesn't seem to do harm except > > > spamming syslog and spending a few additional seconds before trying > > > another interface. > > > > It's not clear what the status of your vpn was when the logs were > > written, AFAICT. It's obviously not soon after booting, as you have > > processes running with PIDs in the 40,000s. > > The VPN was obviously running at that time. I'm writing from what I've gleaned from the logs. You're writing from the viewpoint of running the machine. If you'd originally written some of what's below, I wouldn't have had to. Why do I have to? Because there's no point in my writing anything unless I give the assumptions on which it's based, enabling you to correct any false assumptions. > IF the VPN was not running the 28th february (almost allday, including > around 14:30), it wouldn't make sense to > - make /etc/resolv.conf immutable so dhlient doesn't overwrite it > while my home's resolver address > - complain about dhclient ignoring tun0, which obviously exists only > when the vpn is running > - searching for logs for the 28th february around 14:30 > > I never said those logs were soon after running. Nor me. I presumed that they weren't, and wrote that down in case my presumption was incorrect. > I'd love to start my > workday after 14:00/2 pm… but obviously it not the case. > These logs are from after dhcp leases ends and dhlicent tries to > overwrite resolv.conf. > Several hours after openconnect is executed (around 9:00 am). > > I said when the system boots, before the VPN is up and ruuning, I can > see dhclient has only one (eth0/ens-whatever_its-name_is) as an > argument > So I don't how dhclient determines what interfaces to use, and why it > ignores tun0 BUT still detects and try to use ALL other interfaces, > even when there down/not used > > > > > It would make sense to start and stop the vnc from a terminal in which > > script (bsdutils) was running, preferably with -T to add timestamps to > > each command. You could then reconcile the logs with what you were > > doing. > > I guess you mean vpnc, or vpn? not vnc? or am I misinterpreting? Yes, I used vpnc as a shorthand for starting your VPN session. I know openconnect only as a package name, and I had no idea whether you start it in a GUI (assuming X is running) or with some terminal command. So again, I'm second-guessing pretty much what you already do. Yes, this keyboard doesn't have a good touch, so I often have to add missing letters while I read through what I've written. > vpnc_script is started by openconnect (vpn client for cisco, among > other things). OpenConnect is executed from terminal > OpenConnect has timestamp but there is no output from openconnect when > /etc/resolv is overwritten by dhclient. As OpenConnect doesn't know > about it when it happens > > That why I used auditd and ausearch with timestamp, and reconciled > logs from auditd > showing a process failing (as expected) to overwrite /etc/resolv.conf > with logs from syslog showing dhclient trying to renew DHCP leases > > Around 9:00 am, openconnect is executed manually from the terminal and > works as expected. > Right after the VPN is connected, I make resolv.conf file immutable > and tell auditd to monitor write or append actions to this file > > Everything works until around 14:30, dhclient tries to overwrites > /etc/resolv and fails as expect. > Auditd logs that action. The VPN is still running. I ^C openconnect > only at the end of the day > (unless something breaks, like temporary network issues forcing me to > reconnect) > > At that moment, things still works just because I made /etc/resolv.conf > But it's annoying to have to think about adding/removing the immutable > flag each time… As you start your VPN in a terminal, it would be easy to script it.
Re: alias in bash script issue
On Sat, Mar 04, 2023 at 11:14:39AM -0600, David Wright wrote: > > This use is discouraged > > There's a place for warning about the use of aliases in, say, > Greg's BashPitfalls, or books, but not here. Discouraging the use of legacy features that are considered dangerous in modern usage is fair game for software manuals, I would say.
Re: alias in bash script issue
On Sat 04 Mar 2023 at 20:52:15 (+1100), David wrote:
> Hi. Friends don't help friends to do bad things :)
>
> Debian's default shell is 'dash'. Its manual, readable using 'man dash',
> says
>
> Aliases provide a convenient way for naive users to create shorthands
> for commands without having to learn how to create functions with
> arguments.
IMHO manpages should be about function, not policy. I don't like
this condescension. man bash is more straightforward:
For almost every purpose, aliases are superseded by shell functions.
> They can also be used to create lexically obscure code.
What has that got to do with the price of fish?
In view of the Obfuscated Perl Contest, is the author railing
against writing anything in Perl?
> This use is discouraged
There's a place for warning about the use of aliases in, say,
Greg's BashPitfalls, or books, but not here.
> To achieve your goal, do this instead.
>
> In .bash_profile, replace the line
> alias k='minikube kubectl --'
>
> with these two lines:
> k() { minikube kubectl "$@" ; }
> export k
Overkill for those I've written. And I would discourage the use
of that sort of shortcut function anywhere else but interactively.
Exporting it and then using it in scripts is going to produce
code that's just as lexically obscure.
I guess it falls to me to provide some examples of mine:
alias 1234='printf AmexD\\n'
Redacted; one of several. (I don't have an American Express card.)
alias cal='ncal -3 -A1'
For me, cal output needs transposing. This range is so useful.
alias cdeject='eject # mask cdeject which produces I/O error and locks up
drive'
From the days when I played red-book CDs at work.
alias hekspace='od -t a -t x1 -An'
Can anyone memorise all those switches.
alias py='python3'
A sophisticated calculator.
alias tnef='tnef -v --directory ~/Documents --number-backups'
Curse MS Exchange's attachments.
Finally, I'm not arguing against manpage warnings like this:
--drq-hsm-error
VERY DANGEROUS, DON'T EVEN THINK ABOUT USING IT. …
… VERY DANGEROUS, DO NOT USE!!
(man hdparm)
that guard against accidental bricking.
Cheers,
David.
Re: how to activate my wireless card? nmtui only shows wireless connections . . .
On Sat 04 Mar 2023 at 01:02:54 (-0500), Jeffrey Walton wrote:
> On Fri, Mar 3, 2023 at 6:10 PM Greg Wooledge wrote:
> > On Fri, Mar 03, 2023 at 05:45:54PM -0500, Jeffrey Walton wrote:
> > > The 'p' is a pci bus, the 's' is a slot number. Since the interface
> > > does not move around once installed, the interface will always have
> > > the same name like 'enp4s0'.
> >
> > That's a wonderful idea, but it doesn't quite work in practice. There are
> > ways that a "predictable" interface name may change. A BIOS/firmware
> > upgrade can do it. Adding or removing devices can also do it, in
> > some cases. They don't even have to be network interfaces.
>
> Yeah, that's udev and systemd screwing things up.
Not really. You've got plenty of choice:
net.ifnames=0, biosdevname=0 (on Dell), and
NamePolicy={kernel,database,onboard,slot,path,mac,keep}
Who could want more?
Cheers,
David.
Re: how to activate my wireless card? nmtui only shows wireless connections . . .
On Sat 04 Mar 2023 at 00:03:16 (+), Albretch Mueller wrote: > On 3/3/23, David Wright wrote: > > > > Try removing the atheros module with: > > > > # rmmod ath10k_pci > > > > (check its name in /proc/modules), and then reload it with > > > > # modprobe ath10k_pci > > > > and check dmesg again. > > Bingo! Those were the steps that enable me to see the wireless > network with nmtui ... Good to hear. > a) sudo rmmod ath10k_pci > > b) cat /proc/modules | grep "ath10k_pci" > > c) sudo modprobe ath10k_pci > > d) sudo ip link > > e) nmtui > > I will retest all the steps when I get a chance to make sure to go > through the steps from a "blank slate", new start I'll just point out that cat /proc/modules was added as an afterthought in case (a) failed, so if (a) succeeds, you don't need to do (b). There's always a chance, when removing modules, that one is busy, or another has to be removed at the same time as the one, because it's a dependent. Also, now that the firmware is in place, if you repeat those steps, you're /likely/ to find that ath10k_pci is busy, because the link will be configured automatically in the first few seconds after booting up. Cheers, David.
Re: solution to / full
On Fri 03 Mar 2023 at 15:42:37 (-), Curt wrote: > On 2023-03-02, Jonathan Dowland wrote: > > On Thu, Mar 02, 2023 at 07:25:58AM -0500, Greg Wooledge wrote: > >>I don't understand why you used sort -r, but then reversed it again with > >>tac at the end. You could drop both of the reversals, and just change > >>head to tail. > > > > The short answer is because I wrote all but the last "tac" several years > > ago, and added the last "tac" in writing the mail, when I realised the > > output was the other way around to how I'd prefer. > > You'd think you'd want the biggest pigs listed first. But then when there's a drove, the biggest go AWOL off the top of screen. > But I haven't been following. Cheers, David.
Re: ¿Esta exdebian muerto?
El 4/3/23 a las 05:18, Parodper escribió: Tal vez se le podrían pedir a los administradores de forums.debian.net que añadan un subforo en castellano, pero, la verdad, ni idea de si recibiría algo de actividad. No tendría nada de actividad. Hoy por hoy, la mayoría de los problemas se resuelve, y en español, con una búsqueda rápida. Y los pocos problemas que surgen, son muy, muy específicos, y salvo debian-urser-spanish, no existe otra lista en este idioma con gente con suficientes conocimientos para hilar tan fino. La única que ayuda mucho www.archlinux-es.org La única que la supera son las listas de desarrolladores, que por ser gente de todos lados del planeta, son en inglés. JAP
Re: ¿Esta exdebian muerto?
El 4/3/23 a las 04:46, Camaleón escribió: Pero para qué buscar copias si tienes disponible la original, la genuina, la mejor lista de Debian en español que es ésta. La única lista donde aún encontrarás valientes que escriben «sólo» con acento ¡Ajajajajaja..! Y mucho se lo debemos a APR, miembro T de la RAE, aunque no te guste JAP
Re: alias in bash script issue
On Sun, Mar 05, 2023 at 01:39:35AM +1100, David wrote: > I am aware. 'man dash' better describes how aliases should be > used in modern times, ??? Is this the paragraph you mean? Aliases provide a convenient way for naive users to create shorthands for commands without having to learn how to create functions with arguments. They can also be used to create lexically obscure code. This use is dis‐ couraged. > 'man bash' avoids this clear language, which is unfortunate > because that advice is what anyone who knows what they are > doing will advise. Do you mean this: For almost every purpose, aliases are superseded by shell functions. Your statements are so incredibly vague that I can't tell what you're trying to say. In any case, the Subject: header still says "bash script", and in bash scripts, aliases are disabled by default. They have to be enabled explicitly (shopt -s expand_aliases), before they can even be used.
Re: alias in bash script issue
On Sun, 5 Mar 2023 at 00:12, Tom Furie wrote: > On Sat, Mar 04, 2023 at 08:52:15PM +1100, David wrote: > > Debian's default shell is 'dash'. Its manual, readable using 'man dash', > > says > > The script explicitly calls bash. The rest of your point is still > (coincidentally) valid though, as it would be in most of the popular shells > as far as I'm aware. I am aware. 'man dash' better describes how aliases should be used in modern times, so I referred to it to reference an authority greater than my own personal opinion. 'man bash' avoids this clear language, which is unfortunate because that advice is what anyone who knows what they are doing will advise. So, my point was made intentionally, not coincidentally. Thanks for drawing attention to that ambiguity in my message.
Re: alias in bash script issue
On Sat, Mar 04, 2023 at 08:52:15PM +1100, David wrote: > Debian's default shell is 'dash'. Its manual, readable using 'man dash', > says The script explicitly calls bash. The rest of your point is still (coincidentally) valid though, as it would be in most of the popular shells as far as I'm aware. Cheers, Tom -- To understand the heart and mind of a person, look not at what he has already achieved, but at what he aspires to do. signature.asc Description: PGP signature
Re: alias in bash script issue
On Sat, 4 Mar 2023 at 19:30, Ken Young wrote:
> Do you know why my alias can't work in the bash script?
> The info is as follows.
>
> 1) this alias does exist
> $ alias |grep 'k='
> alias k='minikube kubectl --'
>
> 2) it also exists in .bash_profile
> $ cat ~/.bash_profile |grep 'k='
> alias k="minikube kubectl --"
[...]
> ./get.sh: line 5: k: command not found
[...]
> Please give suggestions.
Hi. Friends don't help friends to do bad things :)
Debian's default shell is 'dash'. Its manual, readable using 'man dash',
says
Aliases provide a convenient way for naive users to create shorthands
for commands without having to learn how to create functions with
arguments. They can also be used to create lexically obscure code.
This use is discouraged
To achieve your goal, do this instead.
In .bash_profile, replace the line
alias k='minikube kubectl --'
with these two lines:
k() { minikube kubectl "$@" ; }
export k
Re: alias in bash script issue
On Sat, Mar 04, 2023 at 10:23:24AM +0100, Kamil Jońca wrote: > Ken Young writes: > [..] > > I am not bash expert (prefer zsh) but as far as I know they are > expadnded during interactive session only, not in scripts. That's at least what the man page says (man bash(1)): ALIASES Aliases allow a string to be substituted for a word when it is used as the first word of a simple command. [...] Aliases are not expanded when the shell is not interactive, unless the expand_aliases shell option is set using shopt I'd recommend reading the whole section. Perhaps what the OP needs is a shell function, not an alias. Cheers -- t signature.asc Description: PGP signature
Re: besides ping/nslookup, any other tools to resolve a hostname?
Hi, I just launched an ubuntu container in that namespace and installed dnsutils/iputils-ping to resolve the hostname issue. Thank you. On Sat, Mar 4, 2023 at 1:11 PM Rodrigo Cunha wrote: > I have bitnami/mysql container (debian OS) running on kubernetes. >> This container seems too restricted for system software, these following >> commands are removed: >> >> sudo (so I can't su to root for apt) >> ping >> dig >> nslookup >> net-tools >> > It is a good practice to build small images for pods without commands for > the network. To solve this problem, you can do that: > Create a pod in the same network with net tools. > Or > 1 .rebuild a new docker image with another version, with net-tools. > 2. then change the current pod with edit in deployment. > > > > On Fri, Mar 3, 2023 at 9:59 PM Ken Young wrote: > >> Hello, >> >> I have bitnami/mysql container (debian OS) running on kubernetes. >> This container seems too restricted for system software, these following >> commands are removed: >> >> sudo (so I can't su to root for apt) >> ping >> dig >> nslookup >> net-tools >> >> Do you know any other way to resolve a hostname by manual on this >> container? >> >> Thanks >> Ken >> > > > -- > Atenciosamente, > Rodrigo da Silva Cunha > São Gonçalo, RJ - Brasil > >
Re: alias in bash script issue
Ken Young writes: [..] I am not bash expert (prefer zsh) but as far as I know they are expadnded during interactive session only, not in scripts. > > $ ./get.sh > > ./get.sh: line 5: k: command not found > https://www.gnu.org/software/bash/manual/bash.html#Aliases --8<---cut here---start->8--- Aliases are not expanded when the shell is not interactive, unless the expand_aliases shell option is set using shopt (see The Shopt Builtin). --8<---cut here---end--->8--- KJ -- http://wolnelektury.pl/wesprzyj/teraz/
Re: Forcing dhclient to not ignore tun0 interface when it's available
David Wright writes: [...] > > This is the job that packages like openresolv are designed > to do. BTW if you look up that package in apt's lists, note > that this is a case where you need man's section number, because > man 8 resolvconf without the 8 will give you a systemd page. +1 I have configured resolvconf + some scripts in my (dhcp,openvpn,ipsec) configurations and they take care to properly preparing name resolution during different situations. KJ -- http://wolnelektury.pl/wesprzyj/teraz/
Re: besides ping/nslookup, any other tools to resolve a hostname?
Greg Wooledge (12023-03-03): > Dedicated lookup tools: > > getent hosts > host > dnsqr It is important to know that host and dnsqr do actual DNS requests, and therefore ignore local configuration about other means of resolving hosts, including /etc/hosts. getent hosts is the dedicated command, the one that matches directly the libc API that is used by most applications. Regards, -- Nicolas George signature.asc Description: PGP signature
alias in bash script issue
Hello, Do you know why my alias can't work in the bash script? The info is as follows. 1) this alias does exist $ alias |grep 'k=' alias k='minikube kubectl --' 2) it also exists in .bash_profile $ cat ~/.bash_profile |grep 'k=' alias k="minikube kubectl --" 3) the content of bash script $ cat get.sh #!/bin/bash source ~/.bash_profile k get node 4) alias can't work $ ./get.sh ./get.sh: line 5: k: command not found The system is debian 11 and the shell is bash. Please give suggestions. Thank you. regards.
Re: ¿Esta exdebian muerto?
O 04/03/23 ás 08:46, Camaleón escribiu: El 2023-03-03 a las 18:53 -0300, Carlos Villiere escribió: Hola Hola y bienvenido :-) Soy un usuario nuevo de Debian, quise consultar en exdebian o anteriormente esdebian, y la pantalla se encuentra en blanco. ¿Saben si todavía esta activa o es error del navegador? Desde ya gracias No hay muchos recursos de ayuda para Debian en español, tienes algunos por aquí: https://www.debian.org/support.es.html Por esta lista también llegaron coletazos de los problemas de esdebian, incluso en esta lista los hemos vivido en las propias carnes. A ver cuándo ponen al ChatGPT a moderar listas y foros y todo irá mejor >:-) Tanto los foros de esdebian como exdebian parecen fuera de combate. La primera desde el año 2015 y la segunda desde el 2021. Lo puedes comprobar fácilmente desde https://web.archive.org. Tal vez se le podrían pedir a los administradores de forums.debian.net que añadan un subforo en castellano, pero, la verdad, ni idea de si recibiría algo de actividad.
Re: how to activate my wireless card? nmtui only shows wireless connections . . .
On 3/3/23, Dan Ritter wrote: > ... the messages you > are seeing are from the first 88.2 seconds after boot. Most probably and luckily no one has reported such problems, but from the corner from which I see reality it may as well be not "after boot". I haven't exactly timed it (I will when I get a chance, in fact, dmesg logs should do), but booting the 16Gb RAM laptop I am using right now with a Debian Live DVD takes definitely more than one minute. Something else "weird" that I noticed is that the BIOS not only kept a connection to a wireless network around me (which I used more than a year ago and which password I don't even remember) but was able to connect through it. I wonder why on earth should a BIOS be WiFi enabled?!? but, well, these days even microwaves are! I think the only way to deal with such matters is by physically disconnecting the wireless card if possible and/or keeping your laptop in a (optimally grounded) Faraday cage. Unfortunately, I can't do so right now because my cell phone is also acting up, . . . once for just writing a poem my connection to the Internet and cell phone didn't work for 8 months! (hsymbolicus poems "lies ..."); so, for now, I will have to keep "hugging the Germans". I really don't give a sh!t about Windows (I would just use it as test based for my java code), but something I have noticed is that from the Debian Live boot I can't access the internal SSD in my DELL Inspiron box. Do you have experience with, would you suggest ways out of such problems? lbrtchx
